Example document
The Brain page for the agency's first agent, during its side-by-side run.
Status: side by side since 4 Jan 2027 (pilot: one account manager, 9 clients)
Owner: head of analytics · Flow: monthly reporting, steps 1 to 3 · Wave: 1
Job
Drafts each client's monthly report and the "what happened" paragraph, so the account manager starts from a draft and spends the time on the client.
Starts when
The first working day of the month. During the side-by-side run: when the owner says "Run the report drafter for [account manager]".
Reads
| What | Where | Can it reach it? |
|---|---|---|
| Clicks, impressions, positions | Google Search Console | Yes |
| Traffic and conversions | Google Analytics | Yes |
| Backlinks and keyword rankings | Ahrefs export in the client folder | Yes, once the analyst drops it in (no Ahrefs connection) |
| Last month's report, the account manager's notes | Client folder, Google Drive | Yes |
Writes
| What | Where | Marked as agent work by |
|---|---|---|
| Report draft | Google Doc in the client folder | "[draft]" in the file name |
| One task per client | Monthly reporting board, list "Drafting (agent)" | Tag "agent", "[agent]" in the title |
How it does the work
- Read last month's report and the account manager's notes.
- Pull the month's numbers, and the same month last year.
- Fill the template in its order. Every number says where it comes from.
- Write "what happened": the three biggest changes, compared with last month and last year, each with what the data shows.
- Run the checks below, then put the task in "Drafting (agent)" for the analyst.
What good looks like
Every number traceable to its source in one click, and a "what happened" an account manager can read to a client after light edits. The bad example we keep: a report that blamed an algorithm update for a drop that was really a broken redirect.
May do alone
- Pull the data, write the draft, create the task.
Asks before
- A number moved more than 30% → asks the analyst, on the task
- The client changed their site this month → asks the account manager before writing "what happened"
- A client has no data → asks the analyst
Never
- Send anything to a client, or share the draft outside the client folder
- Leave out a drop of more than 10 clicks a day
- Name a cause it can't show in the data
Checks before it hands over
- Every number matches its source.
- Every drop over 10 clicks a day is in the report.
- Seasonal clients are compared with the same month last year.
Good enough
Every number matches its source, and the account manager rewrites at most the "what happened" paragraph, for every pilot client, three months in a row. The analyst checks every draft. After the handover: spot checks of 1 in 5.
Success measure
Reports that start from an agent draft (0 → 68 a month by March) and hours per report (half by 31 March).
Record, undo, off switch
- Record: the task per client per month, with a comment listing what it pulled and what it skipped.
- Undo: delete the draft and its task.
- Off switch: the owner stops the schedule.
Review
In Monday's team meeting: corrections from the week. What it may do alone: decided by Priya and the head of analytics, every quarter.
Open questions
- The report goes out as Google Slides. The drafter writes a Google Doc in the template's order, and the analyst pastes it into the slides for now. Revisit after the pilot.
Changes
- 12 Dec 2026: also compare with the same month last year (found in the test on past reports), approved by the head of analytics.
- 18 Jan 2027: a drop under 10 clicks a day isn't worth a line, approved by the head of analytics.