When client work goes sideways, the first casualty is usually the record of what actually happened. Progress gets communicated verbally, in scattered chat threads, through two layers of intermediaries. Then the customer asks how things are going, and you cannot confidently answer, because the evidence is spread across a month of informal conversation.
The fix is boring and it works: a formal weekly email. What you asked for this week. What we delivered. What is blocked, and by whom. Sent to every level of the stakeholder stack, from sponsor to end user, so nothing gets lost in translation on its way up.
The objection is always the same: it feels awfully formal for a collaborative engagement. That framing misses what the report actually is. It is not bureaucracy, it is an artifact. Four weekly emails constitute a complete, queryable history of the engagement. Ask an agent what progress was made since the start of the month, feed it those four emails, done. Try doing that with a pile of chat fragments and things someone said on a call.
The artifact also protects both sides when scope churns, which in services engagements it always does. Say a customer replaces most of the backlog two weeks into a project. With a written record, the next conversation is factual: here is what you dropped, here is what you added, here is where we stand on the new list. Without one, the same conversation feels like excuse-making, and any progress you did make gets discounted because nobody can point to it.
There is one tactical wrinkle worth respecting: timing. If a customer expresses discomfort and you immediately produce a formal status document, it reads as defensive, a paper shield thrown up under fire. Start the cadence before you need it, or at least put a few days between the complaint and the first report. The report should look like how you operate, not how you react.
Mechanically this costs almost nothing. Keep a shared tracker, freeze a snapshot each week, and let an agent draft the delta. The discipline is not in the writing. It is in deciding that progress only counts when it is written down.
Key takeaways
- Verbal and scattered chat updates evaporate; a weekly written report is a permanent artifact of progress that both humans and agents can query later.
- A useful update lists three things, what was requested this week, what was delivered, and what is blocked and by whom, and it goes to every level of the client's stakeholder stack.
- Start the reporting cadence before trouble arrives; a status document produced right after a complaint reads as defensive rather than disciplined.
FAQ
Doesn't formal weekly reporting feel too heavy for a small, collaborative engagement?
It feels heavy until you need the record. The cost is one email a week; the payoff is a complete history you can reconstruct in minutes instead of a month of scattered threads you can never fully summarize.
What is the lightest way to implement this?
A shared spreadsheet tracker works. Clone the tab each week to freeze a snapshot, then have an agent draft the delta into an email. The discipline is in committing progress to writing, not in the tooling.
Related Essays
Always Too Early, Never Wrong
Serial entrepreneurs show up before the wave forms. Being early looks identical to being wrong — right up until the moment it does not.
Because I Had To
The story of leaving safe jobs and building companies — Differential, Astronomer, and now Tembo — because I had no other choice.
What I Learned Shutting Down OSSRank
We built OSSRank to score open source project health beyond GitHub stars. The framework was right; the product wasn't. Here's what I took away.
Drowning in pull requests that need your review? Try Tembo Review, a beautiful AI-assisted PR review tool unlike anything you’ve used.