A weekly update is the cheapest thing a consultant sends and the one most often late. The writing is the fast part. What’s slow is Thursday afternoon, when you go looking for your own week and find it scattered through the mailbox you’ve been avoiding since Tuesday.
- Almost all of the hour goes on gathering rather than wording. Fix the gathering and the writing becomes filling in a form.
- The update is the one client-facing thing you can send rough. Plain and on time beats considered and Monday.
- Every update carries asks, and an ask addressed to four people is addressed to nobody.
- A repeated request changes its date and keeps its words. Escalation belongs in the dates rather than the adjectives.
What the weekly update actually buys
Keeping the client informed is the stated reason, and it’s too vague to get anybody writing on a busy Thursday. The real returns are more specific.
It heads off the message you’d least like to get: a client asking how things are going. That one costs far more than the reply it needs. By the time it’s sent, the person has been wondering for a while. They’ve probably said so to somebody. And you’ve lost a small amount of confidence you now have to earn back. An update that arrives before the question is the cheapest client management there is.
It makes waiting visible to the only person who can end it. What usually holds a consulting engagement up is an answer somebody still owes you. An answer like that is silent in your inbox: no message, no notification, nothing to see. The weekly update is the standing place where it becomes a written line in front of the person who can clear it. A question nobody has answered is otherwise very easy to mistake for one that was.
It builds a record for free. Fifty-two dated notes saying what was done, what was promised and what was outstanding is the best account of an engagement you’ll ever have. It costs you only the minutes you were spending anyway. The mailbox is the only engagement file an independent has, which is argued at the front of this collection. The weekly update is the part of that file you write on purpose.
And it buys quiet. A client who knows where things stand leaves you alone, so twenty minutes of a Thursday buys you the other four days. The last return shows up much later. When something eventually goes over, a client who watched it happen a line at a time is annoyed for an afternoon. A client seeing it for the first time feels misled.
Why an hour goes on a fifteen minute job
Three things are happening in that hour, and only one of them is writing.
Reconstruction. You’re trying to remember a week. Your mailbox holds it in arrival order, spread across eleven threads and however many clients. So you scroll. Somewhere on the second screen a message pulls you in, and forty minutes are gone before a word of the update exists. This is the largest cost by a distance, and it’s a reading cost rather than a writing one.
Composition from nothing. Starting from a blank page, you re-decide every week what goes in, in what order, at what length, and whether the awkward thing goes in at all. Deciding is the slow part of writing. Typing four bullet points is quick for everybody.
Polish. A lot of what a consultant sends genuinely is the product, and the habit of making client-facing paragraphs good is a right habit almost everywhere in the mailbox. Here it costs you the deadline. Nobody has ever hired a consultant on the strength of their status updates, and nobody has ever ended an engagement over a clumsy sentence in a Thursday email. What clients notice about an update is whether it came.
There’s a fourth cost, hidden inside the first. Writing an update is where the loose ends turn up. The answer you assumed had arrived never did. A date you promised in August has quietly passed. A request from three weeks ago is still open. Each discovery pulls you out of writing and into work, which is why the job expands. So separate the gathering from the writing, rather than gathering faster.
The fix is always the same. Write the update across the week and assemble it on Thursday, rather than trying to remember it on Thursday.
In practice that’s a running note, one line at a time, kept wherever is closest to hand. You finish something, hit a wall, promise a date, ask somebody for something: that’s a line, and it takes about five seconds. When the running note slips, the fallback is a single reconstruction pass read off summaries rather than messages. One rule comes with it. You read, and you leave everything closed until the pass is done. Skimming a full inbox in minutes is the skill that pass depends on.
The shape that does not change
Use the same five blocks, in the same order, for every client, every week. A fixed shape removes the decisions, and the decisions were the expensive part.
Where it stands. One or two sentences giving the position of the job against the plan. On track for the fourteenth. Two days behind, back on schedule by the twenty-first. It goes first because it’s the only line some readers read properly, and because the person your contact forwards it to needs it before anything else.
Done since the last one. Three to five lines, past tense, each naming an object rather than an activity. Draft findings for the second site, sent Tuesday. Interviews with the four regional managers, finished. A line that names something a person could point at belongs here. Anything vaguer belongs in the sentence above, where vagueness is honest rather than padding.
What happens next, with dates. The same length, forward looking, carrying the date the next thing actually lands. That date is what stops most of the interruptions. Be specific about it even when specific is uncomfortable.
What I need, and by when. The asks, one to a line, each with a person’s name on it. This is the block that pays for the whole email, and it gets its own section below.
Open items. What you’re still waiting on, with the date you first asked. It’s a reminder that rides along free, because you were writing the email anyway.
A sixth block appears in the weeks that need it: anything that changed the shape of the job. A date that moved, a piece of work that grew, a cost. One line, on the week it happened, is the cheap version of a conversation that gets very expensive if it waits for the final two weeks. What to do about a change to the agreed work is a craft of its own, and this collection takes it separately.
Four format decisions come with the shape.
Put it in the body of the email. Your contact reads it on a phone in a parking lot, and an attachment stays shut there. Being read at a glance is the entire job.
Keep it under about three hundred words. When it runs longer, what it needs is a call, and the call is faster than the email you were about to write.
Use the same subject line every week, with the date on the end. A year later the whole run sorts into order, and any one of them is findable by the week it belongs to.
And send each week as a new message rather than replying into a growing thread. A live negotiation goes the other way, where one subject line holding everything is worth a great deal. An update works differently, because it’s a series of dated records. Each one has to make sense alone, because somebody will forward a single week to a person who is reading their first.
The ask that gets answered
Most requests inside a status update fail for one structural reason. The email goes to four people, so the ask goes to four people, so every one of them reads it as belonging to somebody else. A request addressed to a group is not a weak request. It’s not a request at all.
Six things make one work.
A name at the front of the line. Start the line with the name. Priya, could you send me, rather than we need, or could someone, or it would be helpful if. The name does the work a distribution list destroys.
The thing in the form you need it. The March payroll export as a spreadsheet, one row per employee, rather than the payroll data. A good share of late items arrived on time in the wrong shape. The first version was unusable, the round trip cost a week, and you spent that week to save eight words.
A date. A real one, chosen by you. The client’s own process runs on its own deadlines, so yours has to come from you. The argument for inventing them is made at the front of this collection, and the weekly update is where they get said out loud.
What it unblocks, in their terms. If it arrives after Wednesday the workshop moves to the twenty-fourth. That’s a consequence, because it lands on them. So I can proceed is a description of your week, and it lands on you.
A reply that costs nothing. The best asks can be answered with a date, a yes, or a name. When the honest answer is two hours of somebody’s work, say so plainly and offer a smaller version. A two hour job buried in a status update sits there for two weeks while you both pretend it might get done.
One ask per person per week. Two is a menu, and a menu gets read and deferred. If there are genuinely four things, ask for the one that unblocks the others and hold the rest until it lands.
Some requests travel on their own. Two cases: the person who can act on it is somewhere off the distribution, or the item matters more than everything else in the email put together. Send it that day as its own short message, on its own subject line, where it can be answered at the top of the screen. The update then carries a single line saying you sent it, which keeps the record complete.
A word on wording, because requests go wrong in two opposite directions and both are common. Too soft reads as optional. Whenever you get a chance, no rush at all, is an instruction to do it later. Too stiff reads as procurement. Please provide the following by close of business Friday gets resented by somebody doing you a favor on top of their own job. What sits between them is a plain sentence carrying the name, the thing, the date and the reason. Priya, could you send me the March payroll export as a spreadsheet by Wednesday the tenth? It’s the last thing I need before the workshop pack goes out.
Know which of two things you’re asking for, because they behave differently. A request for information can be answered by anybody who has it, so a name on the line is a convenience. A request for a decision has exactly one person who can give it. When you’re unsure who that is, ask who decides this rather than asking for the decision. That’s a smaller thing to ask and it comes back faster.
Carrying an item into a second week
If the open items block exists, you’ve already sent the reminder. A standing weekly list of what’s outstanding replaces most of the chasing emails a consultant writes. That’s the largest single saving in this whole subject, and the one people miss.
Carrying an item forward has a small technique to it.
Use the same words as last week. Paste the line across word for word, at the same temperature, and leave the just out of it. A request that changes its phrasing every week reads as a new request each time, and each new request starts its history over.
Put the date you first asked at the front. Requested September 4, still open. Three of those stacked up over three weeks is a fact. A fact reads clearly to anybody carrying the update up their own chain, and the dates do the complaining for you.
Let the escalation live in the date rather than the adjective. Mark something urgent in week three when it was ordinary in week one, and you teach the reader that your labels are decoration. That costs you every future week.
Add the consequence once it has actually happened. Week one says the payroll export is needed by the tenth. Week three says the workshop has moved to the twenty-fourth as a result. That sentence is the entire reminder, and a client can forward it exactly as it stands.
And take things off the list. An open items block that only ever grows stops being read within a month. When something arrives, keep it one more week marked as received, then drop it. Visibly closing items is what makes the list credible, and a credible list is one where the open items get believed.
There’s a point where this stops being the right instrument. After about the third week, an item that’s still sitting there has something behind it, and more lines in a weekly email will keep sliding off it. Usually it’s one of three things: a person who needs asking directly, a decision waiting on somebody the update never reaches, or a quiet no. That’s a different job, done by phone or by name, and this collection takes the approval that has gone quiet as a subject of its own.
Writing it with AI, without inventing a week that did not happen
An hour a week on a routine email is exactly the sort of thing a language model should be able to take, and mostly it can. The catch is the one this whole guide turns on. The hour is in the gathering.
A general chatbot writes clean prose, and your week is the one thing it has never seen. So you paste. To paste enough for a useful update, you first assemble the record of what happened, which was the slow part. The saving lands on the part that was already fast. That’s the honest arithmetic on the obvious approach, and it’s worth knowing before you decide the tool let you down. There’s a second cost. Assembling that paste puts a client’s engagement material into whichever tool has a tab open, and that’s a decision worth taking deliberately rather than at four o’clock on a Thursday. Whether AI belongs near client mail at all is a prior question, and it’s answered properly rather than assumed.
Given the material, though, three things are genuinely worth handing over.
Shaping. In go twelve fragments of your own shorthand from the running note, out come the five blocks in order with the past tense in the right place. That’s most of the fifteen minutes, and it’s the part machines are actually good at.
Cutting. An update you wrote at four hundred words comes back at two hundred and fifty with everything still in it. Length is where these emails lose their readers, and cutting your own writing at 4:30 is beyond most people.
Leveling the tone. A bad week is when writing is hardest and the urge to over-explain is strongest. Cutting somebody else’s calm draft down is easier than writing one from inside your own irritation.
Three things stay with you.
Anything outside the record you gave it. Asked to produce an update from thin material, a model produces a plausible week rather than an empty one. It smooths the data has not arrived into we continue to make progress on the data workstream, and it reports a thing as finished on no evidence at all. Every line in a status update is a claim you’re making to a client about work they’re paying for. Read the done block as though a stranger wrote it, because one did.
The asks. A request carrying a name, a date and a consequence is exactly the sentence a language model softens most reliably, because politeness is its safe default. What comes back is a sentence anybody can leave alone. Check those lines by hand every week: one name, one thing, one date each.
And the bad news. If the report is slipping, the sentence saying so has to be yours, in the words you’d use on the phone. The reason is practical. A generated apology has a texture to it, and a client who has read three of them starts skipping the whole email, which costs you the only thing it was for.
The rule underneath all of that is short. A machine can shape the week. It cannot know it. Give it the record and keep the claims.
The two weeks that get skipped
The week nothing happened. The client was late with the data, you were on another engagement, the workshop sits on the twenty-fourth. Sending an update that says so feels absurd, so the week goes by in silence. It’s the most expensive skip available. A client reads silence from a consultant as a problem being hidden, or as an engagement sitting idle. Three lines take ninety seconds and close off both readings: the week was quiet, here’s why, here’s when the next thing lands. And a quiet week holds the one line that most needs saying, which is that the thing you’re waiting for is still out there.
The week it went wrong. Behind, over, or a deliverable that slips. The instinct is to hold the update until you have a fix, and that instinct costs more than the problem does. A client told on Thursday that the report slips by a week is irritated for an afternoon. A client who finds out on the day it was due has to go and explain the gap to somebody upstairs, and what you did to them there is worse than what you did to the schedule. Put it in the first block, in plain words, with what you’re doing about it and the new date attached. First block, first line, ahead of the good news.
Both cases come back to the same rule. The update goes on the same day, news or no news. Skipping once is what kills the habit. Week two then needs an explanation for the gap, week three needs an apology, and by week four the easiest thing is silence.
The standing slot
Fix the day and the time, say so at the kick off, and let it be expected. An update that arrives on a schedule reads as a service. One that arrives when you happened to have an hour reads as a mood, and then the weeks you skip are the weeks something looks wrong.
Thursday beats Friday for a mechanical reason. An ask sent on Friday afternoon has the whole weekend to die in, and a Friday update reaches somebody who has stopped making decisions until Monday. Thursday morning gives your requests a working day and a half to be answered inside the same week. If your client’s own internal reporting goes up on a Monday, Thursday lands while yours is still useful to them.
Put it on the calendar as a recurring appointment with the client’s name on it. An appointment survives a delivery day that overruns. Everything looser than an appointment is the first thing to move.
Fifteen minutes, in order, looks like this. Two minutes reading last week’s update, which is where the open items and the dates you promised come from, and which gets skipped more often than any other step in this guide. Two minutes on the running note. Five assembling the blocks. Three on the asks, which are the only part that rewards care. Two reading the first line as your contact’s boss would read it, since that’s who it’s really written for. Then send it. If the whole thing runs past twenty minutes, something inside it should have been a phone call.
Several clients on the same Thursday morning is a related but different problem, and this collection has a piece on running parallel engagements.
What Point takes off a Thursday afternoon
The judgment is yours, and it stays yours. What to report, what to admit, what to ask for and whose name goes on it are the job, and no software has a view on any of them. What moves is the gathering and the first pass, which is where the hour actually went.
Reconstruction goes first, because it’s the biggest cost. Every conversation arrives carrying a plain account of itself in a line. The pass over a week reads as a page of summaries rather than eleven threads to be opened one at a time. Point weighs each message before you reach it. How much a thing matters is kept separate from how fast it needs you. That’s two measurements rather than one, and it’s the reason a quiet client thread is still where you can find it on Thursday.
Then the open items, the block people write from memory and get wrong. A question you sent out is held as a debt owed to you, with the date you chose on it and the conversation still attached. The list is read rather than recalled. It runs the other way too. When a message asks something of you, that becomes a dated item on its own, and that’s what the next block is assembled from. A standing request goes in ordinary words too. The export you need out of one named person is reported to you once, the morning it turns up, rather than looked for on four separate mornings. Leaving a standing instruction like that has a walkthrough of its own.
Drafting is the part that turns the assembling into an edit. Point composes from scratch as well as replying, and what comes back is written the way you write, which for a fixed weekly shape is close to the whole job. Search runs off a description rather than an exact phrase, so last week’s update turns up when all you remember is roughly what it said.
One limit belongs here rather than in a footnote. How far Point may act alone is decided per type of action. Every one of those settings ships at the point where the work is readied and then held back for you. If you want the mechanics, there’s a full account of that dial. Sending an acknowledgement is a reasonable thing to move up once you’ve watched it happen often enough. Leave the weekly update where it ships, and the reason is worth saying plainly. It is a set of claims about work somebody is paying for, and a claim is the last thing that should ever leave unread. Anything done on your behalf lands in a log with a time on it, and most entries can be put back from there. A message that has already reached the far end is the exception, and no mail software is in a position to offer otherwise.
All of it runs where you already are. Point works on top of a mailbox that stays put, Google or Microsoft 365, so the address at the bottom of the update is the one your client already has.
Point is a mailbox, and a project reporting tool is a different purchase. Point holds no plan, no percentage complete, no milestone list and no status color. The schedule is something Point has never seen, so whether you are ahead or behind is a question for somewhere else. If the question is where the work stands against the plan, that’s project management software and it’s the right thing to buy. If the question is what actually happened this week and who still owes you an answer, that’s the mailbox, and it’s the half this guide has been about. The benefits page lists everything Point does, Point for consultants puts the case in the language of a practice, and Point sets out the product itself.
Common questions
How long should a weekly client status update be?
Under three hundred words, in the body of the email, in five short blocks. Where the work stands. What was done. What happens next, with dates on it. What you need and by when. What is still outstanding. When it runs longer, the overflow is usually something that needs a conversation rather than a paragraph, and the conversation is quicker for both of you. Length is the most common reason these emails stop being read. An unread update is worse than no update, because you pay for it every week and get nothing back.
Can AI write my weekly client update?
A model can shape one. Knowing your week is the part you supply. Given a rough note of what happened, a model turns twelve fragments into a clean update in your usual order, cuts four hundred words to two hundred and fifty, and keeps the tone level in a week you’d rather skip past. Given thin material it invents a plausible week instead of reporting an empty one. That’s the failure that matters, because every line in an update is a claim about work a client is paying for. Two parts stay in your hands. The requests, which a model politely softens into a sentence anybody can leave alone. And the bad news, which has to sound like you. The saving is real, and it comes from having the record ready rather than from the prose.
The client has not answered the same request for three weeks. What should I write?
Send the same line again, for the first two of those weeks. Carry it forward word for word with the date you first asked at the front. Add the consequence once it has genuinely happened, so week three reads as requested September 4, still open, and the workshop has moved to the twenty-fourth as a result. The escalation belongs in the accumulating dates rather than in stronger wording, because a fact reads clearly to anybody up the chain and an adjective is only an argument. Past about the third week the weekly line has done what it can, and what’s left is a person who needs asking directly, which is a phone call rather than an email. Unanswered questions and the threads that come back is the general shape of that problem.
What do I send in a week when nothing happened?
Three lines, on the usual day. Say the week was quiet, say why, and say the date the next thing lands. It feels like the least worthwhile email you’ll send all week, and it has the highest return in the whole set. A client reads silence from a consultant as a problem being hidden, or as an engagement sitting idle, and those are the two readings three lines close off. A quiet week also holds the line most worth saying, which is that the thing you’re waiting for is still out there, and that line does more on a slow week than on a busy one.
Should the update go to my day to day contact or to everyone?
Send one update to the working group and let it be forwarded. Writing different versions for different people doubles the work and eventually contradicts itself. Write the first line for the person furthest from the work, since that’s who your contact passes it to, and the update is all they get. Then put individual names on the asks, because a request that belongs to a group belongs to nobody. Anything genuinely sensitive or genuinely urgent goes out as its own short message to the one person who can act on it, with a line in the update recording that you sent it.
The short version
A weekly client update is slow because you’re reconstructing a week from your own mailbox on a Thursday afternoon. Writing four bullet points is the easy part. Keep a running note during the week and the writing becomes assembly. Use the same five blocks every time, in the body of the email, under three hundred words: where it stands, what was done, what is next with dates, what you need and by when, and what is still open. Put a name, a form, a date and a consequence on every ask, one per person, because a request made to a distribution list is not a request. Carry unanswered items forward in the same words with the date you first asked, and let the dates do the escalating. Send it on a Thursday, on a schedule, in the weeks when nothing happened and in the weeks when it went wrong, and put the bad line first. A model can shape the update, cut it, and hold your tone steady. Knowing your week is yours. Give the model the record and keep the claims for yourself. The inquiry before this engagement started, the approval that will not come, and the hours you gave away getting here are each taken separately elsewhere in this collection, which opens on the practice as a whole.