A weekly status note that replaces the standing meeting
Picture a custom ERP build for a small fabrication unit. Six weeks in, the person who signed off on the project writes to ask why the updates have stopped. They have not stopped — they have been given verbally, in a Monday call that runs 45 minutes and covers everything touched the previous week. The call is useful to the developers. It is not useful to the client, because by Thursday they cannot remember what is in flight and what is blocked.
The standing meeting is the default. Clients ask for it because they want visibility. Developers agree to it because it feels like communication. What it actually does is compress all information into a single weekly burst, delivered at a time when the client is thinking about something else, and then forgotten.
We replaced it with a written rhythm. Friday afternoon, we send a note. Monday morning, we hold a 15-minute call block. The note carries the substance. The call exists only for the client to ask questions about the note.
The Friday note has three sections, always in the same order. What shipped this week. What is in flight next week. What we need from them. We keep it under 200 words. If it runs longer, we are either over-explaining or doing too many things at once, and either way the note is telling us something.
Here is what a note for that ERP build might look like around week seven:
SHIPPED
- Purchase order PDF export (with tax breakdown)
- Vendor master: bulk edit for GST rates
- Fixed: PO line items disappearing on slow connections
NEXT WEEK
- Goods receipt note module, first pass
- Vendor master: import from Excel template
NEED FROM YOU
- Sample GRN from your existing process (any format)
- Confirm: should GRN auto-create a liability entry, or manual?That is the whole note. No preamble, no "hope this finds you well," no summary paragraph. The client reads it over the weekend or first thing Monday. By the time we get on the call, they have either decided the answers to our questions or written back saying they need until Wednesday.
The Monday call block is optional on our end and mandatory on theirs. We show up. If they have no questions, we hang up after two minutes. We do not fill the time. Filling the time is what turns a status check into a standing meeting.
The tradeoff: this rhythm assumes the client will actually read the note. Most do, because it is short and arrives at a predictable time. A few do not, and for those clients we have the call read the note back to them verbatim. That sounds tedious. It is. But it takes 10 minutes instead of 45, and the client gets the same information.
We also use the Friday note as an internal forcing function. If we cannot write "what shipped this week" in concrete terms — meaning specific features, specific fixes, specific decisions made — then we did not ship enough. The note is not a report we write for the client. It is a check we run on ourselves.
One thing we do not do: Slack or WhatsApp updates during the week. We have tried it, and it corrodes the Friday note. Clients stop reading the note because they assume anything urgent will come through chat. Then they stop reading chat because there is too much of it. Going back to the weekly note and the single call block fixes it, and clients adapt within a couple of weeks.
The test of a good note is whether the client can forward it to their finance head or production manager without adding a covering explanation. The note has to be readable by someone who was not on the call. If a status update requires the meeting to make sense, the meeting has become the product and the software is secondary.