Nobody on their side is going to write to you this week. The document is signed. The people who joined for it have gone back to their own work. Your contact has three other things running. The quiet is fine for now. It turns into a problem in week four, when somebody asks how it’s going and the honest answer is that they had no way to know.
So you send a weekly update. Everyone agrees with that. What stops it is the first one. It takes an hour you hadn’t planned for, and an hour is enough to make it a Friday problem, then a next week problem. By the time you write one it reads as an explanation rather than a report.
The hour is real. It’s also almost all in the first one. Spend it on purpose and every update after it takes about ten minutes, because it’s an edit of the last one rather than a piece of writing.
What the first one is for
If your first update has nothing to report, you’re in the ordinary place. Week one of a warehouse review is badges, a kickoff, a request for three months of data and four days booked in somebody’s calendar. Writing that up feels like sending an email about having started.
Send it anyway. It’s the week you settle four things that would otherwise get re-decided every Thursday for the next three months: who receives it, which day it lands, what it looks like, and what kind of thing you’re going to ask for in it. Deciding is the slow part. Once those four are fixed, the weekly cost drops to the part that genuinely changes.
It also starts the record on the right date. A run of updates beginning in week one is an account of an engagement. A run beginning in week four is an account of an engagement that somebody had to ask about first, and the gap at the front is the part people remember.
Week one is also the only week with the slack to do this properly. It’s the quietest week of a delivery you’ll ever have.
The list is not the one from the contract thread
The thread the statement of work ran on finished with seven or eight people on it. Their counsel, somebody from finance, a director who appeared on day nine, the assistant who scheduled the signing call. That list was built to get a document signed.
Delivery has its own audience. Three kinds of reader.
Your day to day contact, who reads the whole thing and is the only person who will act on anything in it.
The person who has to be comfortable with this engagement. You identified them during scoping and they usually sit outside the working list, which is fine. They read your first two lines, some weeks, forwarded by somebody else with no context attached. Those two lines are written for them.
And the person who will actually receive the work. On the contract thread they stayed quiet for two weeks, because a statement of work is somebody else’s document. On the update they’re the most valuable reader you have. They’re the one who can tell you in week three that you’re building the wrong thing, while there’s still room to change it.
Who to leave off matters more than it sounds. A distribution list with the client’s lawyer on it changes what you’re willing to write. “Two days behind, back on track by the sixth” turns into “the schedule is under review,” and an update written defensively is worth nothing to anybody, including you. Procurement and legal rejoin the conversation when there’s an invoice question or a change to the agreement, on their own thread, at their own pace.
Setting this list takes one line. The contract thread is finished, so a new message goes to the people who need it, and the first update names who’s on it and asks whether anyone is missing or would rather not be. Corrections come back within a day, and they come back from the client, which makes the list theirs rather than a decision you took about their organization.
Why this one is not a reply
Reply, never compose, was the rule through the proposal and the statement of work, and it was worth keeping. Delivery is where it flips, and the reason takes a sentence.
A negotiation is one record. Everything in it means something in sequence, and one long thread is what keeps the sequence. A delivery update works the other way round. It’s a series of dated records, and each one has to make sense alone, because each one gets forwarded on its own to somebody who has read none of the others. Bury week nine inside a thread of thirty messages and the person your contact forwards it to scrolls past eight weeks of history to reach it.
So each update is its own message, with one subject stem and the date on the end. Northgate warehouse review, update, October 8. A year of them sorts into order by itself, and any single week is findable by the week it belongs to rather than by what you happened to write in it.
One thing stays a reply, and that’s a reply. When the client asks a question, answer it where they asked. The update is a standing broadcast on a fixed day. Live conversations stay live, and a question that lands on Monday gets its answer on Monday.
The first update, in full
This is the whole thing, and it’s about two hundred words.
Subject: Northgate warehouse review, update, October 8
Dana, Ray, Alex,
Where we are: started on the 6th as planned. On track for interim findings on November 6.
This week: site access and badges sorted for both buildings. Kickoff with Dana and the shift leads on Tuesday the 6th. Read the 2025 layout drawings and the last two inventory counts. Booked the observation days, October 13 to 16.
Next: four observation days next week, then the picking route analysis. Interim findings, November 6.
What I need: Dana: the goods in exception log for July through September, as a data export rather than a formatted report, by Tuesday October 13. Nothing else is holding up the observation days, and without it I spend four days measuring by hand something you already have. Alex: half an hour on the floor first thing on Tuesday, before I start the observation days, so I’m not asking you the same question four days running.
Open: nothing outstanding yet.
These will come on Thursday mornings for the length of the engagement. I have Dana, Ray and Alex on this list. Tell me if somebody is missing, or if you’d rather not be on it.
Four things in there do work that lasts longer than the week.
The date in the first line is the one every later update gets measured against. Naming it in week one, before anything can have gone wrong, is what lets you say “still November 6” for six weeks and then say something else without it landing as an announcement.
Both asks carry a name, the thing in the form it’s needed in, a date, and what it unblocks. A request that goes to three people goes to nobody. A request for “the exception data” comes back as a PDF of a dashboard.
The open line says nothing is outstanding, which looks like filler and earns its place. It establishes that the section exists and is honest, so the first week it has something in it, the client reads that as the section doing its job.
And the last line does the list. One sentence, once, and you never have to raise it again.
The second one is an edit
Here’s where the ten minutes comes from. Most of a weekly update is decided by the previous week’s update, so writing one from scratch redoes work that’s already done.
Open last Thursday’s message. Leave your inbox closed for now. Change five things, in this order.
The date, in the subject line and in the first line.
The position. This is the only sentence you write fresh, every single week, and the section below is about why.
What was under “next” moves up into “this week,” corrected to what actually happened. This step does the reconstructing for you. Last week’s forecast is a list of the things you meant to do, so you’re checking a list against a week rather than recalling a week from nothing. Recognizing is much cheaper than remembering, and it’s where most of the hour used to go.
The new “next,” which mostly comes off your calendar rather than out of your head.
Then the asks. Anything from last week that went unanswered drops into “open,” carrying the date you first asked. Anything answered gets marked as received and comes off the following week. New asks go in.
Then read the whole message once and delete anything that’s still in it because it was in it last week. An edit is fast because it preserves, which means it preserves a line that stopped being true in week five just as faithfully as one that’s still true in week nine.
That’s the second update, and it looks like this.
Subject: Northgate warehouse review, update, October 15
Where we are: on track for interim findings on November 6.
This week: observation days running in both buildings, three of the four done and the last one tomorrow. Picking routes timed on the three highest volume aisles. First pass through the goods in exceptions.
Next: the remaining routes, and a half day with the night shift if it’s in scope. Interim findings, November 6.
What I need: Ray: a decision on whether the night shift is in the review. It sits outside the statement of work, and Alex thinks most of the exceptions happen there. It would add about two days and I’d price it before either of us commits. Thursday October 22 would keep it out of the critical path.
Open: Goods in exception log, asked October 8, arrived October 14. Closing this out.
Roughly seventy percent of that message came from the previous one. The work in it was the position line, one new ask, and the ninety seconds it took to notice that the exception log had arrived.
The scope question in there is a good example of what the update is for. A change to the agreed work gets settled in a conversation of its own. What the update does is put it on the record in the week it came up, in the client’s sight, with a number attached, so that nobody is surprised by it in November. The conversation itself happens elsewhere.
The two lines you never copy
The method has one blind spot, and naming it plainly is worth a paragraph, because this is the failure that costs something.
An edit makes carrying a line forward the default. Most weeks that’s correct and it’s the whole saving. Twice in an engagement, it costs you.
The position line. It isn’t a formality. It’s a claim about work somebody is paying for, and it’s the one line in the message that the person furthest from the work reads every week. Carrying “on track” forward because you didn’t have time to think about it is the cheapest keystroke in this method and by far the most expensive. Write it fresh, from what you actually know on Thursday morning, before you touch anything else in the message.
Bad news. The moment the position line changes, the shape of the update changes with it. The slip goes at the top, said plainly, with the new date and what you’re doing about it, and everything else moves down. The method makes a real change look like a small one, because on the screen that’s exactly what it is. Break the rhythm on purpose here. When the position line moves for the first time, call your contact before the email goes out, so the person who has to explain it internally hears it from you rather than reading it at the same time as their boss.
There’s a third thing an edit carries forever without complaining, and that’s an ask nobody has answered. Week two, week three, week five, the same line, patiently reappearing. The update is very good at showing you that on the Thursday you write it, and it has forgotten it by Friday.
When an email is the wrong shape for this
Three cases, and in all three something else does the job better.
The client already has a reporting system. Some clients run a project portal, a shared board, or a weekly ops call with a standing slot for suppliers. Write into whichever one they actually read, and let your email shrink to three lines and a pointer. Maintaining both is how one of them quietly goes stale, and it’ll be the one you own.
The engagement is short. For a three or four week piece of work, a weekly update is most of the engagement and it starts to read as activity for its own sake. Two messages do the job better: one at the start setting out what’s happening and by when, and one at the end. Anything in between that needed saying was urgent enough to send on its own.
The question is where the work stands against a plan. If what the client wants is percentage complete, dependencies and a critical path, buy project management software, which is built for exactly that. A mailbox holds what happened and who owes what to whom. A schedule lives somewhere else, and no amount of good email discipline moves it into your mail. The two work together: the plan says what should happen and the update says what did.
What Point has ready before you sit down
The judgment in all of this stays yours. What to report, what to admit and whose name goes on which ask are the work. What moves is the gathering, and the gathering was most of the hour.
Have your briefing arrive on Thursday morning rather than at a fixed hour somebody else chose. Point brings you the day’s account when you want it, so the morning you write updates opens with what’s happened since the last one rather than an inbox to be excavated.
The excavation itself gets shorter. Every conversation carries a plain summary of its own, so the pass over a week is a page of accounts rather than eleven threads opened one at a time. A fifteen minute reconstruction becomes a two minute one, and that’s what reading a long chain in a line buys you. When you want the message where Alex mentioned the second dock door, describing it is enough to find it. That helps, because nobody remembers their own wording six weeks later.
The open items block is the part people write from memory and get wrong. Memory can hand it over. A request you sent out stays on the books. It carries whatever date you put on it, and it stays tied to its thread. It comes back to you once the wait has gone on longer than it should have, rather than whenever you happen to think of it. In the other direction, a message that asks something of you becomes a dated item without anyone typing it into a list, which is most of what next week’s update is assembled from. For one specific reply you’re waiting on, the exception log from Dana, a standing request is plainer still. Ask to be told when it lands and you hear once, on the morning it arrives. Setting a watch like that takes a sentence.
Then the edit. Point drafts as well as replies, and Point writes the way you write, which for a message whose shape you fixed in week one is close to the whole job. Ask in ordinary words for this week’s version of last week’s update, and what comes back is something to correct rather than something to compose.
One boundary belongs here rather than in a footnote. How far Point goes on its own is set per kind of action, and review is where those settings start: the work gets readied and then waits for you. Once you’ve watched a kind of action run, moving that one up is reasonable. A weekly client update is the last candidate for it, because every line in one is a claim about work somebody is paying for. Leave it at review and spend the saving on the gathering, which is where it was anyway. Whatever Point does for you is logged with a time on it and can be put back. A message that has already reached your client’s mail server has gone, which is true of every mail system there is.
And the limit that matters for this subject: Point has never seen your plan. Point holds your mail, so a schedule, milestones and percentage complete live with you, and ahead or behind is a question only you can answer. That sentence is yours to write every Thursday. The full list of what it does do is written out flat, and the version of it shaped around consulting covers the engagement rather than this one message in it.
The count nobody keeps
Twelve weeks of a warehouse review is twelve of these. Call it two asks and two commitments in each, once the engagement is properly running, and by the end you’ve put a couple of dozen small promises in writing and collected about as many back.
Almost all of them are fine. They were answered inside a week, marked as received, and dropped off the list the way they were supposed to. That’s the method working.
The run of Thursday emails stays quiet about the rest. The update makes an item visible on the day it’s written and forgets it entirely by Friday, because it’s a record rather than a list, and a record has no opinion about what’s still open in it. The line about the night shift that Ray never answered is sitting in week two, still true, still unanswered. The one thing standing between it and November is that you happen to reread last Thursday’s message before writing this Thursday’s.
Which works until the week you’re traveling, or the week the interim findings are due, or the week you write the update from an airport at eleven at night. The commitments keep getting made, whether or not anybody is holding them.