Direct answer
Replace daily chasing with one standing rhythm: fixed update days, one live view, and exceptions only in between.
A client who asks for a progress update every day is rarely asking for information. They are asking for reassurance, because from their side the project is a closed box: money went in, a date was promised, and nothing visible happens in between. Daily updates feel like the fix and fail like one too, because each update costs you real time to write, says very little on a one day horizon, and trains the client that silence from you means trouble. The working fix closes the trust gap instead of feeding it: a standing rhythm the client agrees to, with fixed update days, one live progress view they can open any time without asking you, exception only messages between updates, and a set shape for what each update contains. This page gives you the rhythm, the proposal wording, and what to do when the daily asks continue anyway.
Updated November 18, 2026. First published November 18, 2026. The records quoted below are real and public, read back from the live service on November 18, 2026.
Step 1. Read the daily ask correctly: it is a trust gap, not an information gap
On most projects, one day of work contains almost nothing worth reporting: a step finished, a problem found, a decision now needed. A client with full visibility would not ask daily, because they could see the small movements themselves. The daily ask appears when the client has no window into the work at all, so asking is the only instrument they have, and each unanswered day raises the volume. That diagnosis changes the remedy. More frequent manual updates treat the symptom while making the underlying gap worse, since the client still cannot see anything between your messages and now also knows you can be made to report daily. Closing the gap means giving the client a way to see progress that does not route through your time: a view they can open, plus a rhythm they can rely on. Once a client can look for themselves, the daily ask usually fades on its own, because the need underneath it is being met continuously instead of in daily doses.
Step 2. Propose the standing rhythm: fixed update days, and what each update contains
The rhythm has three parts, proposed in one message and agreed once. Part one, fixed update days: for most projects, two updates a week, for example Tuesday and Friday, beats five daily ones, because each covers enough ground to contain real movement. Short or urgent projects can run three; long builds can run one. Part two, the set shape: every update contains the same four lines, done since the last update, next before the following one, anything blocked and what it is blocked on, and any decision needed from the client with its date. The fixed shape matters as much as the fixed days: the client learns where to look, comparisons between updates become easy, and a missing decision is visible in writing, update after update, without you ever raising your voice about it. Part three, the promise that makes the rhythm acceptable: between updates, you send exception messages only, which step 4 defines, so the client is never actually out of the loop on anything that matters.
Step 3. Give the client one live progress view they can open any time
The live view is the piece that replaces the daily ask rather than merely refusing it. It is one link the client can open at any hour and see the state of the work as it stands: which steps are done, which are in progress, what has been delivered, and what is waiting on a decision. It updates as the work happens, not when you remember to write about it, so a client who wakes up anxious at midnight can look instead of messaging. It also changes the update itself: the fixed day update stops being a from scratch report and becomes a short pointer, the record moved here and here, this decision is the one I need. Clients who have a live view ask fewer questions and better ones, because the view answers the factual layer, what is the state, and leaves the human layer, what do you recommend, for the actual conversations. If your current tooling has no such view, that absence, not client anxiety, is the thing to fix first.
Step 4. Define exception only contact between updates, and run the work on the record behind the view
Between fixed updates, messages flow in both directions for exceptions only, and the list is short enough to state in one breath: work is blocked and needs the client, a decision is needed before the next step can start, something has been delivered, or a date has moved. Everything else waits for the update day. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the states the client sees in the live view:
Accepted: the decision is on the record
- Status: accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release_hint ok_to_release.
- Steps: 4 steps total, 4 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Pending: checked, and still waiting on a decision
- Status: pending, release_hint hold.
- Steps: 5 steps total, 5 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
The accepted record is a stage the client can watch close: 4 steps, all checked, decided by the client on a stated date, release state ok_to_release. The pending record is equally useful to a watching client: 5 steps checked and a hold state, which tells them without a single message that the project is waiting on a decision, and whose decision it is. When the work runs on a record like this, the live view is not a dashboard you maintain as a second job; it is the work record itself, filling as you go, and the fixed update is a two minute summary of a page the client could already open.
Step 5. Send the proposal in this wording, and handle the client who still asks daily
The proposal, word for word in shape: So you are never guessing where this stands, here is how I will keep you posted. You will get an update from me every Tuesday and Friday covering what is done, what is next, anything blocked, and any decision I need from you. You can also open this link any time to see the current state of the work as it happens. Between updates I will message you straight away if something is blocked, a decision is needed, or a date moves. That gets you everything a daily update would, without either of us spending the week writing them. If the daily asks continue after the rhythm is agreed, do not break it by complying and do not scold: answer the first with the link and the next update day, answer the second the same way, and let the rhythm prove itself for two weeks, which is how long the habit usually takes to die once the view is genuinely live. If a client insists on daily written reports as a hard requirement, that is a priced service like any other: daily reporting is work, quoted as a line, and clients who see the price usually discover the rhythm was enough.
Honest limits
This page is general information about client communication, not a rule for every engagement: some contracts, regulated work, and incident response genuinely require daily or faster reporting, and where that duty exists it should be scoped and priced as the work it is. A live view also only reassures if it is honestly kept: a record that sits stale for a week while work happens elsewhere will deepen the trust gap it was meant to close, so the view has to be the real record of the work, not a display maintained for the client. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove the work is good, which is why the update still carries your judgement in its four lines.
Step 6. Write the rhythm into the next agreement, so it is the default and not a negotiation
The rhythm that ends this problem belongs in your standard terms, three short lines agreed at signing: progress updates are provided on stated days in a stated shape, the client has a live view of the work record at a stated link, and contact between updates is for exceptions, blocked work, decisions needed, delivery, and date changes. With those lines in place, the daily ask never forms, because the client starts the project already able to look, and the question in this page becomes a mid project repair instead of a standing condition. The clients worth keeping prefer it this way once they have lived it: they get more visibility than daily emails ever gave them, and you get your working days back, which is where the progress they are asking about actually comes from.
Frequently asked questions
My client keeps asking for a progress update every day. How do I handle it?
Replace the daily ask with a standing rhythm the client agrees to, rather than complying daily or refusing flatly. The rhythm has four parts: fixed update days, two a week suits most projects; a set shape for every update, done, next, blocked, and decision needed; one live progress view at a single link the client can open any time to see the current state of the work; and exception only messages between updates, sent when work is blocked, a decision is needed, something is delivered, or a date moves. The daily ask is a trust gap caused by having no window into the work, and the live view closes that gap continuously, which manual daily updates never do. Propose the rhythm in one message, then hold it kindly and consistently.
How often should I send a client progress updates?
On a fixed rhythm matched to the project length, not on demand. Two updates a week, for example Tuesday and Friday, is the working default for most projects, because each update then covers enough ground to report real movement. Three a week suits short, fast projects; one a week suits long builds with slow stages. Daily written updates are almost never the right default: a single day rarely contains reportable change, the writing time compounds across the project, and the habit teaches the client that your silence signals trouble. Whatever rhythm you choose, pair it with a live view the client can check between updates, and reserve in between messages for exceptions only.
What should a progress update contain?
Four things, in the same order every time, so the client can read it in under a minute and compare it with the last one. Done: what was completed since the previous update, named concretely. Next: what will be worked on before the following update. Blocked: anything stuck, what it is stuck on, and whose move clears it. Decision needed: any choice the client must make, stated as a choice, with the date it is needed by and what waits on it. That is the whole shape. Skip praise, skip apologies, skip restating the whole project history: the live record carries the history, and the update carries the movement, which is the part the client actually asked about.
What if my client still asks for an update every day after we agree a rhythm?
Hold the rhythm kindly, answer with the instrument, and give it two weeks. Reply to the daily ask with the live view link and the next update day, briefly and without irritation, and send the fixed updates exactly when promised, because reliability is what retrains the expectation. Do not send extra full updates in between, which teaches that asking works, and do not ignore the client either, which confirms the fear underneath the asking. Most daily habits fade within two weeks once the view is genuinely live and the updates land on schedule. If a client still requires a written report every day as a hard term, treat it as the work it is and quote it as a priced reporting line; at a price, most clients rediscover that the rhythm was enough.
How does a job record help with a client who wants daily updates?
It gives the client a live view of the work itself, so reassurance stops depending on your writing time. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so the client opens one link and sees steps done, steps waiting, and the acceptance state as it stands, and your fixed update becomes a short summary of a page they could already read. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, put your next client job on one record, so the next daily update request is answered with a link instead of an hour of writing: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.
Related
- What did my AI agents do today?
- How do I document AI work for client billing?
- My client will not give feedback and my deadline is passing. Should I keep working or stop?
- My client wants me to be available on weekends for the same price. Should I agree?
- My client asked me to delete all my copies of the work after I deliver it. Should I?
- A subcontractor I hired let me down and my client is waiting for the work. What do I do?
- Start with your problem: every problem in this directory, routed to its page