Most client status updates get under a minute, on a phone, from somebody who didn’t plan to read anything. That’s normal. What decides whether yours lands is the first two lines: whether they say where the work stands, and whether anything under them was news.
- An unread update costs you the thing it was meant to buy, which is a client who never has to ask how it’s going.
- Readers learn to skip. The last four updates told them what they’d already guessed, so the fifth can wait.
- The person whose opinion decides the engagement usually reads your update second hand, with no context attached to it. Write the top for them.
- Adjectives spend your credibility. Dates rebuild it. An update that has never carried anything awkward stops reading as an account of the work.
How to tell it is not being read
Clients stop reading quietly. The signal arrives sideways, and it’s easy to file as something else.
A question comes back that the update answered. This is the clearest one there is. Your contact asks when the findings are due, and the date was in Thursday’s email. So the email got a skim, or no open at all. Answer the question, then make a note of it. Two of these in a month is a pattern rather than a lapse.
Somebody asks you to walk them through where things stand. At a review, on a call, in a meeting you’ve described in writing four times. The request tells you the written record exists and sits unused. That’s a strange thing to keep paying for.
Your requests sit there while your other mail gets answered. A client replies to a direct message the same afternoon and leaves three weekly asks untouched. They’re organized. Your direct messages get read, and your updates get filed. That’s a readership problem wearing the costume of a chasing problem, and chasing harder makes it worse. A question nobody has answered is easy to mistake for one that was.
A decision you reported gets taken again. Or somebody acts on a version of the plan you retired three weeks ago. You delivered the information in writing, on time, and it still didn’t arrive.
The updates stop producing any reply at all. Not agreement, not a question, not a thanks. This client acknowledges everything else, so a month of silence on a weekly email is the client telling you something politely.
The client is surprised at a review by something you reported. This is the expensive one, and it’s nearly always a date. You have the email and you’re right. Being right won’t help here, because what they’ll remember is the surprise.
Your client isn’t careless. Reading is a decision they make again every week, based on what the last few were worth, and by the time you notice any of the signals above that decision is weeks old. The rest of this guide is about what goes into it.
The first two lines do the work
You write a weekly update in a window with the whole thing visible. Your client reads it in a preview pane, or on a phone between two meetings, where what exists is a subject line and roughly one sentence.
So the first sentence isn’t an opening. It’s the update, for a good share of the people who receive it. A greeting, a remark about the weather, a line saying please find below this week’s update: each one spends the only sentence some readers will ever see.
What belongs there is the position. On track for delivery on the fourteenth. Two days behind after the site visit moved, back on schedule by the twenty-first. Blocked on one thing, and it’s the payroll export. A reader who gets that much has been served even if they close the email there. Most weeks that’s exactly what should happen. An update lets a client decide, in one sentence, whether they need to think about you this week.
Two smaller things follow from how it’s read. Keep the top left aligned and short, because a first line that runs three clauses long gets truncated by the phone before it reaches the useful part. And put the one thing you need from them second, not seventh. A reader who stops after two lines has still met the request. The naming convention for the subject line is a filing question rather than a reading one, and it’s worth settling separately. Here its only job is to be recognized on sight.
Activity is not news
The deepest reason updates go unread sits under format. Most of them say what the reader could have predicted before opening.
A list of what you did is a receipt for time. Your client already assumed you worked last week. That’s what the engagement is. Eight lines confirming it return nothing, and a reader who gets nothing four weeks running learns, correctly, that the fifth is optional. What taught them that is the missing news, and the shape of the email had little to do with it.
Four things count as news. An update carrying any one of them is worth the reader’s minute.
The position changed. Ahead, behind, blocked, unblocked. If it held steady, one line saying so is honest and takes three seconds to read.
A date moved. Yours or theirs. This is the single most-read fact in any status update, because it’s the only one that lands on somebody else’s calendar.
You learned something about their business. About their business, not about your process.
A decision is needed from them, and it’s now. The asks in an update have a craft of their own, covered on a page of its own. What matters here is that a decision request is news, so it belongs where news belongs.
The trap is that padding feels like diligence. A full done list looks like value and reads like noise, and every line of it thins the news around it. If the honest content of a week is one sentence, send one sentence. A short update that says something gets read next week. A long one that says nothing gets skipped.
Say what you now know
The line that makes an update worth opening is almost always a finding, and consultants write it least, because it feels like giving the answer away before the report.
A pair of sentences shows the difference. Completed fourteen interviews across the two sites is activity, and it’s what most updates say. The delay is in the shift handover rather than on the line, which moves where the savings are: that’s the same week reported as knowledge. One of those tells a client they’re getting value. The other tells them you were busy.
Two cautions come with it. Say the confidence plainly, because an early read stated as a conclusion is the fastest way to lose the argument later. Early, from four of the fourteen is a complete sentence. It costs you nothing. And if a finding changes what the client should do, it has outgrown a bullet in a weekly email. Say the headline in the update, and pick up the phone the same day.
Assume it will be forwarded
The person who signed your contract is rarely the person you email every week, and the person deciding whether the engagement continues may be a level above that. Your update reaches them, if it reaches them, as a forward with no covering note.
That reader arrives with no thread, no history, and no idea what was said on the call. Write the top of the update so it survives the trip.
In practice that means a handful of small habits. Give people roles the first time they appear each month, since a first name alone means little to somebody who has never met them. Spell out the acronyms that live inside your own team, and the ones that live inside the client’s project rather than inside their business. Skip as discussed and per our conversation, because a forwarded reader missed the conversation and the phrase quietly tells them so. And once a month, put the purpose of the engagement back into the first paragraph in six or seven words, so a reader who last thought about your work at the kickoff can place it.
There’s a second reason to do this, and it’s the one that matters commercially. An update your contact can forward as it stands is a small gift to somebody whose own standing depends on being able to say what you’re doing. An update they have to rewrite before passing on gets rewritten once, and after that it stops moving. Who should receive which thread, and how to keep several stakeholders in one conversation, is its own subject, and this collection handles it separately.
Why a reader stops believing it
Being read is the first problem. Being believed is the one that decides whether anybody acts on it, and belief goes slowly, in ways that look harmless at the time.
Unbroken good news. Every engagement has friction. An update that has run for six weeks without a single difficult sentence reads as a filtered report, and the reader begins discounting the good news too.
Adjectives standing where facts should be. Good progress. Significant work. Substantially complete. Readers turn these into noise almost immediately, and a paragraph made of them costs attention and returns zero.
The date that moves one week, every week. Three consecutive slips of seven days do more damage than a single honest slip of three weeks. The weekly slip says you’re guessing, and knowing is the thing they’re paying for.
Learning it from somebody else. A client hears from their own staff about a problem you already knew about. From that moment every future update is read with a discount applied, and the discount stays.
The repair is ordinary. Numbers where you have them, names where they belong, dates instead of adverbs. Write the uncomfortable sentence in the same register as everything else, and let it stand. Precision is free to produce, and it buys you the benefit of the doubt on the week you need it. What to actually say in the week the work goes wrong is a piece of craft in its own right, and it’s handled elsewhere. What matters here is that a reader who has watched you report one difficult thing plainly will read the next update properly.
What to take out
Most updates get long by accretion rather than by decision. These are the parts that reliably cost more attention than they return.
Percent complete, unless it’s measured against something real. A number invented to fill a column teaches the reader that your numbers are decoration. That’s expensive, because later you’ll need a number believed.
A status marker that has been green for six weeks. It’s furniture now. Nobody reads furniture.
Meeting logs, attendance and process narrative. Which workshop format, which tool, who dialed in. That’s the inside of your business, and the client didn’t buy it.
The effort story. We spent considerable time on. A great deal of work went into. This reads as a claim on sympathy, and clients pay for position and knowledge.
Restating the scope every week. You agreed it once. Repeating it signals padding, or a worry about scope, and if it’s the worry then it’s a conversation rather than a paragraph.
The apologetic furniture at both ends. Apologies for length, hopes that the week went well, and the closing line inviting the reader to let you know if they have any questions, which asks a busy person to generate work for themselves. Nobody takes it up.
Anything that was true last week and is unchanged this week. Repetition is the specific thing that trains skipping. One exception earns its place: the register of what’s still outstanding. That one is supposed to repeat, because its whole value is that it accumulates.
Three reads before you send
Each of these takes under a minute. Between them they catch nearly everything.
Read the subject line and the first two lines only, as somebody two levels above your contact. Do they now know the position, and whether anything is wanted from their side? That answer decides the update for most of the people who’ll see it, whatever the rest of it says.
Underline every sentence carrying something the reader didn’t already know. An empty page means you’ve written a receipt. Either there’s news you’ve missed, or the week genuinely produced none. On that week, three honest lines are the right email.
Ask what the reader does differently after reading it. Sometimes the honest answer is nothing, and on a given week that’s fine. Four weeks in a row means you’re sending a report into a process that has no use for it, and finding out why is cheaper than writing another one.
One habit is worth adding to those. Send yourself a copy and look at it on a phone before it goes out. That’s the only way to see what your reader sees, and about ten seconds is enough to discover that your position sentence has been cut off after the word currently.
When an email is the wrong instrument
An update is a good default, and it doesn’t fit every situation. Knowing where it stops is part of writing one well.
If the position changed materially, the email is the record and the call is the telling. Call, then write it down the same day. A client who learns something significant from a document will treat every later document as a place bad news hides.
If the question the client actually has is where the work stands against a plan, that’s project software or a shared plan document, and it’s the right thing to use. A schedule sits badly in an email, and an update that tries to hold one becomes a poor copy of a tool they may already own.
If they want more detail than an email holds, a living document they can open beats a longer email every time, with the update carrying the two lines that say what changed in it.
And if a client demonstrably reads nothing, stop paying for prose. A standing ten-minute call plus three written lines afterward gets you the reception and the record together, for less than the email nobody opens. Which kind of client you have is a fair thing to ask at the kickoff, and the answer changes what you write for the rest of the engagement.
What Point can do about this
The judgment in all of this stays with you. What to report, what to admit, what to call a finding and how confident to sound are the work itself. Software has no opinion about any of them. What changes is the material you write from, and that’s where the failures above mostly begin.
Knowing what this client already knows comes first. Repetition is what teaches a reader to skip, and you repeat because last month’s outbox is hard to hold in your head. In Point, each conversation arrives carrying a plain account of itself. A month with one client reads by skimming rather than opening, so you write from the record instead of from memory.
The promises you made come second. A date you gave in an email three weeks ago is the fact most likely to be wrong in this week’s update, and the hardest to look up. When a message commits you to something, it becomes a dated item you can see. What you asked of them is held the same way, with the date you asked still attached. That register is also the closest thing you have to a readership signal, since asks that produce nothing week after week are the measurable end of an update nobody is reading.
Drafting helps with the part that is genuinely mechanical. Point composes as well as replies, and writes in your own patterns, so a rough note about the week comes back as something to edit. Read hardest the sentences making claims about work a client is paying for, because a model handed thin notes will smooth an empty week into a confident one. If you’d otherwise paste an engagement’s material into whichever chat window is open, the prior question of AI and client mail is worth settling before the habit forms.
Two limits belong in the open rather than in a footnote. Point won’t tell you whether your update was read. Nothing honest will, and the tracking pixel that claims to is unreliable as well as a poor thing to be caught using on a client. The signals in the first section of this guide are what you actually have. Point also holds no plan, no milestones and no completion figure, so Point has no view on whether the work is ahead of schedule or behind it. If that’s the question you’re stuck on, project software is the right purchase, and this guide is about a different half of the problem.
You set how much Point does on its own, one type of action at a time, and every type starts on review out of the box. A weekly update is a good candidate for leaving there permanently, whatever else you raise, because it’s a set of statements about paid work and those are worth reading before they go. The full account of that setting is worth ten minutes before you change anything. Every action Point takes is recorded with a timestamp beside it, and most of them can be reversed from that record. Recall is the exception. Once a message has landed at the far end, no mail client can reach it.
Your setup stays where it is. Point sits over the mailbox you already run, whether that’s Google or Microsoft, and your client goes on writing to the same address they always used. Benefits lists every capability, Point for consultants makes the case for a practice, and Point is the product itself.
Common questions
Why do my clients never reply to my status updates?
Most of the time silence is benign, since a well-written update needs no reply and a client who has nothing to say is behaving correctly. Silence matters when it arrives with the other signals: requests sitting unanswered while your direct emails get replies the same day, questions coming back that the update already answered, or a client surprised at a review by something you sent in writing. One of those is a bad week. Two of them over a month means the update is being filed rather than read. The usual cause sits in the content rather than the format: the last several said what the reader could have predicted.
Can I tell whether the client opened it?
Not reliably, and the attempt costs more than the answer is worth. Read receipts get declined or ignored. Tracking pixels get stripped by a growing share of corporate mail systems and by image blocking. A pixel that fires tells you a preview pane rendered, which is a different thing from a person reading. There’s also the ordinary risk of being seen doing it, which is a strange note to introduce into a client relationship for data this weak. The behavioral signals are slower and much better: what gets asked, what gets acted on, and whether your requests move.
How do I write for the sponsor when I only email my day to day contact?
Write the top of the email for the sponsor and the body for your contact. That means the first two lines carry the position and the ask in plain terms. Leave out the internal shorthand, the acronyms and any reliance on a previous thread, so the whole thing can be forwarded without a covering note. Give people roles rather than first names, and put the purpose of the engagement back into a sentence about once a month for the reader who last thought about it at the kickoff. What you want is an update your contact can pass upward unedited, because one they have to rewrite gets rewritten once and then stops moving.
Does using the same shape every week make it look automated?
The opposite, in practice. A predictable shape is what lets a busy reader find the one line they care about in four seconds, and readers reward that. An update feels automated when nothing specific sits inside it: no names, no numbers, no dates, and adjectives standing where facts should be. Keep the frame identical every week and put real content in it. If a reader could swap your update for a generic one with the client name removed, the problem is the sentences.
The client says my updates are too long. What should go first?
Cut everything that was true last week and is still true, which is usually a third of it. Then cut the process narrative and the effort story, which is most of the rest. What survives is the position, anything that moved, what you now know about their business, and what you need from them and by when. Length is rarely the real complaint anyway. Readers say too long when they mean the ratio was bad, and nobody calls an update of three hundred words with four pieces of news too long.
Should an update repeat what I said last week?
Only the register of what’s still outstanding, which is meant to accumulate and is the reason the whole email pays for itself. Everything else that held steady should either disappear or shrink to a clause. Repetition is the specific mechanism that trains a reader to skip, because each unchanged paragraph is evidence that opening the next one is optional. After four weeks of that, a reader has learned something about your updates that’s hard to unlearn. Where an item has genuinely stalled and it matters, say so in one line with the date it was first raised, and let the accumulating dates carry the weight.
The short version
A client status update is read for under a minute, on a phone, by somebody who wasn’t planning to read it, and often by somebody you’ve never met at the far end of a forward. That’s why the first two lines carry the position and the ask, not a greeting. Updates stop being opened because the last four said what the reader could have guessed. So make each one carry a change of position, a moved date, something you now know about their business, or a decision that’s needed now. When the week produced none of those, say so in three lines rather than padding to a page. Report knowledge rather than activity, since fourteen interviews completed is a receipt and the delay is in the shift handover is the thing they’re paying for. Take out the invented percentages, the status marker that has been green since August, the process narrative and everything that was true last week. Then read the subject and first two lines as somebody two levels up, underline what the reader didn’t already know, and ask what they do differently afterward. Credibility is the quiet variable underneath all of it. Adjectives spend it, dates and names rebuild it, and an update that has never carried a difficult sentence reads as a filtered one. When the news is big, call first and let the email be the record. The inquiry that started the engagement, the recap after a meeting, the scope conversation you have been avoiding and the question of how often to write at all each have a page of their own here.