Guides
Monthly client reports for a virtual assistant agency: one page, five blocks
Build virtual assistant agency reports clients actually read: one page, five blocks, written in the client's vocabulary and sent on the same day each month.
What to take away
- One page. A report longer than a page is filed, not read, and a filed report does no work at renewal.
- Five blocks cover it. Four look at what happened and one looks forward, and the forward one is why anybody reads it.
- Write in the client's vocabulary, not your task types. A report organized by your internal categories asks the reader to translate.
- Same day every month. Predictability is most of the value; a brilliant report sent irregularly is worse than a plain one sent reliably.
No metrics targets or benchmarks are stated here. Every figure in your report should come from your own delivery log.
Who the report is for
Not the person who sends you work. They already know what happened.
It is for the person who approves the recurring cost and sees the retainer once a quarter as a line item. They need to be able to answer, in one sentence, what this is for. Write for them and the day-to-day contact will read it too.
That single change, writing for the absent approver, fixes most of what is wrong with agency reporting.
Five blocks
| Block | What it contains | Why it is there |
|---|---|---|
| What was done | Six to ten lines, in the client's own categories | The approver needs one glance to see activity |
| Capacity | Reserved against used, one line | It makes the price legible to both sides |
| Outside scope | Named, with no invoice attached | It turns a future repricing into a routine step |
| Waiting on you | Blocked items with dates | It attributes delay correctly rather than to you |
| Next | Plans, and one suggested change | It invites participation instead of judgment |
1. What was done. Grouped the way the client thinks about their business, not by your task taxonomy. Six to ten lines at most, with the largest or most consequential first.
Five Blocks of the Report
- What was donesix to ten lines
- Capacityreserved against used
- Outside scopenamed, no invoice
- Waiting on youblocked items with dates
- Nextplans and one suggested change
2. Capacity. Reserved against used. One line. This is the block that makes the price legible and it is the one most agencies leave out.
3. Outside scope. Anything delivered beyond the agreement, named, with roughly what it consumed, and no invoice attached. Naming it monthly is what makes a repricing conversation routine later.
4. Waiting on you. What is blocked on the client's side, with dates. Short and factual.
5. Next. What is planned, and one thing you would suggest changing. This is the block that turns a report into a conversation.
Nothing else. Not a satisfaction score, not a chart of message volumes, not a summary of your process.
What to cut
- Task counts as a headline. Volume is not value, and a rising count can mean the client's process is getting worse.
- Response time averages with no distribution behind them. One bad week disappears into an average and reappears in a complaint.
- Screenshots of dashboards. If a number matters, write it as a sentence.
- Anything that measures your effort rather than their outcome.
- Praise for yourself. Let the record read as a record.
Language
Use the client's words for their own things. If they call it the inbox, do not call it the communication channel. If their customers are members, do not call them users.
Keep sentences short. The reader is skimming and deciding whether to keep paying, and dense prose reads as an attempt to look busy.
Write the outside-scope block especially plainly, since it is the one most likely to be quoted back to you.
Reporting on work that touches customers
Where the retainer includes anything customer-facing, the report carries a second duty: it is the record of what was said in the client's name.
Two constraints belong in the working standard so nobody improvises them. Public statements about the client's business need a basis before they are made.
For tasks involving reviews or testimonials, the FTC's guidance on soliciting and paying for online reviews applies. Incentives may not be conditioned on a favorable review, material connections must be disclosed, and suppressing unfavorable reviews while showing favorable ones is not acceptable.
Report what was done in those areas factually and completely. It is exactly the material a client may need later.
The one figure worth arguing about
Reserved against used, month by month, over the whole relationship.
Reserved vs Used Capacity
Consistently under
- Client outcome
- Notices waste
- Your move
- Offer lower tier
- Likely result
- Most stay anyway
Consistently over
- Client outcome
- Being subsidized
- Your move
- Repricing talk
- Likely result
- Adjust the price
A client consistently well under their reserved capacity will eventually notice on their own, and by then they will have decided they are wasting money. Raise it first and offer to move them down a tier. Some accept, most do not, and almost all of them stay.
A client consistently over is being subsidized by the quiet ones, and that is a repricing conversation rather than a reporting one. The reasoning behind it is in the pricing and profit guide.
Making it cheap to produce
A monthly report should take minutes, not a morning. It does if the raw material accumulates as work is delivered.
Make the Report Cheap
- Two lines on every delivered item
- What was done, and what client should know
- Month endcompile, do not reconstruct
- Keep notes retrievable for whole term
Two lines on every delivered item: what was done, and anything the client should know. At month end the report is a compilation. Without those lines it is a reconstruction, and reconstruction is where the exaggeration creeps in.
Keep those notes somewhere retrievable for the whole term, not just the month. A client asking in November what happened in March is asking a fair question, and the answer should not depend on anyone's memory.
Who writes it
The account owner, not the assistant, because it includes scope and money. But it is assembled from the assistant's delivery notes, so its quality depends on a habit trained at the start of somebody's employment, not on writing skill at month end. That habit belongs in the training sequence in the hiring and training guide.
Where an account has changed hands, the report is also how the new person shows continuity. The handover practice that makes that possible is set out in the guide on improving agency client onboarding.
Reporting and the renewal
The report is the renewal, delivered in monthly installments. By the time a term ends, the client should have twelve pages describing exactly what they bought.
Anything sent to the client should match the agreement, not exceed it. A report promising more than the document is a claim.
The terms it must match, including how renewal and cancellation work, belong in the material described in the sales and proposal guide. Where auto-renewal is involved, the FTC's account of a risk free trial that was neither shows why the terms have to be disclosed plainly and canceling made no harder than joining.
The full term calendar these reports sit inside is in the renewal and reporting playbook. State in the report who directs the work day to day, since that is both a scope question and one the Labor Department's page on misclassification myths treats as central to worker status.
Common questions
Should the report include hours in detail?
Reserved against used, yes. A line-by-line timesheet invites an audit of minutes and turns the relationship into a billing dispute.
What if the client never reads it?
Send it anyway. It is written for the approver who reads it once, at the moment the recurring cost is questioned.
Can it be automated?
The assembly can. The judgment about what to highlight and what to raise cannot, and that judgment is most of the value.
How do I report a bad month?
Plainly, in the first block, with what you changed. Clients forgive a bad month described honestly and remember one they discovered themselves.
