Direct answer
Stop at the gate, in writing. Work that depends on a missing decision is rework waiting to happen.
The draft went over days ago. No comments, no approval, no rejection, just silence, and your delivery date is walking toward you. Both obvious moves lose. Keep building on an unapproved draft and you may build the wrong thing at full speed, then own the rework because you chose to continue. Stop silently and you own the missed deadline, because nobody agreed the clock paused. The working move is a third one: declare the feedback gate in writing, state that the deadline moves day for day while the decision is missing, keep working only on the parts that cannot be invalidated by the feedback, and put the waiting days on the record as they pass. This page gives you the gate message word for word, what counts as feedback dependent work, and the escalation ladder when silence stretches.
Updated November 17, 2026. First published November 17, 2026. The records quoted below are real and public, read back from the live service on November 17, 2026.
Step 1. Name the gate: the exact decision you are waiting for, and what it blocks
Silence is hard to act on because it is vague, so make it specific first. Write down the one decision you need, in the form the client can give it in two minutes: approve draft two as the basis for the build, or mark the three changes you want first. Then list what that decision blocks and what it does not. It blocks everything built on top of the draft: later stages, integrations, final files, anything whose shape the feedback could change. It does not block independent work: research for a later stage, setup that is identical under either version, documentation of what already exists. That split is the whole strategy. You are not stopping the project; you are stopping the dependent line, visibly, while the independent line continues and is logged. A client who sees that distinction stated calmly understands the position instantly, because it is obviously fair: you are protecting their money from rework, not sulking about a late reply.
Step 2. Send the gate message today, with the day for day rule inside it
The message has four lines and it goes today, not after another week of hoping. Line one: the draft and the decision needed, with the date the draft was sent. Line two: the dependent work is paused from today to avoid building on an unapproved base. Line three: the deadline moves day for day for each working day feedback is outstanding, so a decision on Thursday moves delivery by the three waiting days, stated as the new date in numbers. Line four: the independent work you are continuing in the meantime, so the client sees motion where motion is safe. Send it on the channel the client actually reads and keep a copy with the project record. The day for day rule is the heart of it: it is not a threat and it is not a fee, it is arithmetic both sides can count, and because you stated it before the deadline passed, the moved date is an agreed consequence rather than a late delivery you are explaining afterwards.
Step 3. Log the waiting state on the record, so the pause is a fact and not a story
A declared pause only protects you if the waiting days are visible somewhere other than your inbox. 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 two states a stage can sit in:
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 pending record is the honest picture of a feedback gate: the work is checked, 5 steps, and the state is hold, waiting on a decision that has not been made. That is a respectable state to be in, as long as it is dated and shared. The accepted record shows the gate clearing: a named decider, a date, and the release state flipping to ok_to_release. Keep your gated stage in the pending shape on purpose: hand over what exists, name the decision it waits for in the handover notes, and let each waiting day sit next to a record the client can open. If the deadline is ever disputed later, you are not reconstructing a silence from memory; you are pointing at a dated, checked stage and a gate message sent before the date passed.
Step 4. Run the escalation ladder if silence lasts: nudge, call, reprice the slot
Day three to five, one short nudge that repeats only the decision and the new delivery date the delay has already created; no new information, no apology for asking. Around day seven to ten, change channel: a call or a voice note, because silence in writing often means the written channel is buried, and ask the blocking question directly, is this project still live and am I still the person building it. Past two weeks, protect your calendar in writing: state that the slot held for this project is released on a stated date if no decision lands, and that restarting later means a new start date based on your then current schedule, with the gated stage and its record intact and resumable. That last step is not abandonment; the work and its record wait safely. It is the honest boundary between a paused project and an unpaid reservation on your working life, and clients who resurface almost always accept it because you told them the date before it arrived.
Honest limits
This page is general information about handling a feedback delay, not legal advice: if your contract fixes a delivery date with no pause provision, a gate message proposes a variation rather than creating one, which is one more reason to send it early and get any reply, even a one line agreement, in writing. Silence also sometimes means something has gone wrong at the client that has nothing to do with you, illness, a budget freeze, a person leaving, and the ladder above is written to surface that kindly rather than to punish it. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove feedback was read, which is why the gate rests on the dated handover and the dated message together.
Step 5. Put a feedback window in the next agreement, so the gate is pre agreed
Every term that saved you here belongs in the next contract as a standing rule, three short lines. Feedback on each stage is due within a stated number of working days. If feedback is outstanding past that window, dependent work pauses and the delivery date moves day for day. After a stated number of days without a decision, the held slot may be released and restart takes a new date. With those lines signed in advance, the gate message in step 2 stops being a negotiation and becomes a reminder of a rule the client already accepted, which is a much easier message to send and a much easier one to receive. The best time to agree how silence works is before anyone is silent.
Frequently asked questions
My client will not give feedback and my deadline is passing. Should I keep working or stop?
Stop the work that depends on the missing feedback, keep the work that does not, and declare both in writing today. Building past an unapproved draft risks full speed rework that you will be expected to absorb, while stopping silently leaves you owning a missed deadline nobody agreed to move. The gate message fixes the position in four lines: the decision needed and the date the draft was sent, dependent work paused from today, the deadline moving day for day for each working day feedback is outstanding with the new date stated, and the independent work continuing meanwhile. Log the gated stage as a dated, checked handover waiting on that decision, then run the ladder: a short nudge, a channel change, and a written slot release date if silence passes two weeks.
How many days should I wait for client feedback before pausing?
Pause the dependent work as soon as the agreed feedback window passes, and if no window was agreed, after a short, stated grace period of two to three working days from a clear request. Waiting longer does not make the feedback more likely; it makes the rework larger and the deadline argument harder, because you continued in silence. The pause is not the project stopping: independent work continues, and the gate message tells the client exactly which line is paused and why. What matters is that the pause and the day for day deadline move are declared before the original delivery date arrives, not explained after it.
Does my deadline automatically move when a client is late with feedback?
Not automatically, which is exactly why the gate message matters. A deadline moves cleanly when a contract already contains a feedback window with a day for day rule, or when the client agrees the move in reply to your message. Without either, you hold a strong fairness argument and a dated record, but not an agreed new date, so send the message early, state the new date as a number, and treat even a one line reply as the agreement. Never simply deliver late on the assumption the client knows their silence caused it; in a dispute, the side with the dated declaration and the dated, checked stage record is the side whose timeline gets believed.
What work can I safely keep doing while I wait for feedback?
Anything whose shape cannot be changed by the missing decision. Safe work is identical under either version of the draft: research and gathering for later stages, environment and account setup, templates and tooling you will use regardless, and documentation of stages already accepted. Unsafe work is anything built on top of the unapproved draft itself: later stages that inherit its structure, final files, integrations, and polish. When in doubt, ask the inversion question: if the feedback says change the base, does this task survive untouched. If the answer is no, it waits at the gate with the rest, logged as waiting rather than done in hope.
How does a job record help when a client goes silent on feedback?
It turns the waiting period into a dated, shared fact instead of a claim in a later argument. 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 gated stage sits on the record as checked work in a pending, hold state with the decision it waits for named, and the day it clears, the acceptance lands with a decider and a date. 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 a feedback silence is a visible hold on a shared page instead of a gap in your inbox: 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
- My client has not approved the final draft. Can I still send the final invoice?
- My client keeps missing review meetings. What do I do?
- My client wants to pause the project for a few months. How do I protect the work already done?
- My client wants a kill fee if they cancel the project early. How do I set one?
- Do unused retainer hours have to roll over to the next month?
- Start with your problem: every problem in this directory, routed to its page