Back to all articlesAgency customer operations

Handle Late Client Reviews Without Treating Silence as Approval

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

The client’s review deadline has passed. Your designer is booked for revisions, another project needs the same capacity, and nobody knows whether to keep waiting. Proceeding would mean acting without a clear decision; waiting indefinitely would leave useful production time unavailable.

The answer is to agree two separate things before review starts: what requires explicit client approval, and what happens to reserved capacity when that approval is late. A missed deadline can trigger a pause, release of capacity, or escalation. It must not turn silence into permission.

The recommended process below connects each review decision to a booking state. Its worked example includes a later wording change, showing exactly what remains approved and what must be resolved before a replacement date becomes firm.

1. Separate permission from the production booking

“Can we proceed?” and “Can we still deliver on the original date?” need separate answers. Approval concerns a particular version of the work. Scheduling concerns whether the agency still has the people and time needed for the next stage.

Late approval does not automatically restore a released production slot. Releasing a slot does not mean the client rejected the work. Keep three states visible:

  • Review: awaiting decision, changes requested, or explicitly approved, tied to a version.
  • Capacity: reserved until a cutoff, released, provisionally held, or confirmed.
  • Delivery: conditional on timely review, awaiting replanning, provisionally estimated, or confirmed.

This prevents a familiar disagreement: the client says they approved, while the agency says the date moved. Both can be true. The record should show when approval arrived and what capacity remained available.

A single “on hold” label hides those distinctions. Dependent work can be paused while a short reservation remains open. After that reservation expires, the review can still be unresolved even though the original slot is no longer available.

2. Agree the fallback and restart conditions in advance

Introduce the fallback during planning, then repeat the relevant details with each review request. Frame it as a capacity-planning rule, not a punishment.

  • Review package: the exact deliverable and version.
  • Required response: explicit approval or consolidated changes.
  • Decision owner: the authorised approver and agreed backup.
  • Review deadline: a date, time, and time zone.
  • Capacity cutoff: when the reservation ends if review remains unresolved.
  • Fallback: what pauses, what capacity is released, and who receives escalation.
  • Restart conditions: the content decision, scope assessment, and schedule confirmation needed to book again.

The review deadline and reservation cutoff need not match. A short buffer can absorb a small delay, but the agency must be able to sustain its cost. Do not reserve time indefinitely merely because a response might arrive.

A useful operating statement is: “Dependent production requires explicit approval of the named version. If review is late, dependent production pauses. After the capacity cutoff, the original slot is released. Replacement dates require resolved content, an assessed scope, and confirmation of an available booking.”

If no fallback was agreed, do not present a new cutoff as an established rule. Explain the actual capacity constraint and seek agreement on the revised plan.

3. Use a filled decision table with one clear chronology

Fictional worked example: All people, dates, times, capacity figures, and deliverables below are hypothetical. All times are UTC. The client has agreed to the review and capacity rules.

An agency is producing an onboarding guide. Maya is the client approver; Daniel is the escalation contact. Version 3 is due for review on 14 October at 12:00. Four hours of final layout are reserved for 15 October, supporting delivery on 16 October. The reservation expires on 14 October at 16:00.

Hypothetical late-review decision table: sequential events for one onboarding guide
Event and triggerApproval and agency actionCapacity effectDelivery consequenceNext owner and cutoff
A: 14 October, 12:00 — no review decisionVersion 3 remains unapproved. Pause dependent layout and send notice.Keep the four-hour reservation until 16:00.16 October remains conditional on timely approval and the work fitting the slot.Maya: approve version 3 or send consolidated changes by 16:00.
B: 14 October, 16:00 — still unresolvedNo permission to finalise. Notify Maya and Daniel.Release the 15 October slot.16 October is no longer the active delivery plan.Project manager: check replacement capacity. Maya: resolve review.
C: 15 October, 10:00 — Maya approves version 3Record explicit approval of version 3. Offer a replacement booking.Provisionally hold four hours on 20 October until 15 October, 16:00.21 October is a provisional delivery estimate, not confirmed.Maya: confirm the revised schedule by 16:00.
D: 15 October, 11:00 — Maya requests replacement eligibility wordingVersion 3 approval remains recorded, but the request blocks finalisation of the affected section. Issue version 4 for decision.The same provisional hold remains; it does not extend automatically.21 October also depends on approval of version 4 and scope fitting the slot.Maya: approve exact version 4 wording by 14:00. Project manager: assess fit by 15:00.
E: 15 October, 16:00 — booking checkpointConfirm only if content approval, scope fit, and schedule acceptance are recorded.Confirm the booking if all conditions are met; otherwise release the hold.21 October becomes confirmed only with agency booking confirmation. Otherwise, replan.Project manager: send confirmation or release notice at the cutoff.

Row D follows Row C; it is not an alternative scenario. Version 3 was approved first. Maya then requested a change, and stakeholders disagreed about its wording. The agency sends version 4 at 11:30, identifying the changed passage and carrying forward unchanged material.

The historical approval of version 3 does not approve version 4. Unchanged, independent work remains authorised, but the agency must not finalise the disputed passage or release the complete guide. It also should not silently revert to version 3 after receiving the change request. That would require a clear decision from Maya.

4. Send messages that expose every restart requirement

A useful notice identifies the missing decision, its production consequence, and the recipient’s next action. These filled briefs and messages are hypothetical and reusable: replace the version, owners, deadlines, and capacity details, while retaining the distinction between approval and booking.

Missed-review message brief: The project manager writes to Maya about version 3 in the existing review location. The request is explicit approval or consolidated changes. Daniel receives escalation if the capacity cutoff passes.

Subject: Onboarding Guide v3 — review overdue; slot held until 16:00 UTC

Hi Maya, the review deadline passed today, 14 October, at 12:00 UTC. We have not received your decision on version 3, so dependent final layout remains paused.

As agreed, the 15 October production slot remains reserved until 16:00 UTC today. Please explicitly approve version 3 or send consolidated changes by then. We will assess any changes before confirming whether delivery on 16 October remains achievable.

If review is unresolved at the cutoff, we will release the slot and include Daniel in the update. This does not approve the guide. A replacement delivery plan will depend on resolved review and available capacity.

Replacement-booking message brief: After the new wording request, the project manager writes to Maya, with Daniel informed. The message records version 3 approval, identifies version 4 as unresolved, and gives separate content and booking cutoffs.

Subject: Onboarding Guide — decisions needed for proposed 21 October delivery

Thanks, Maya. We recorded your approval of version 3 today, 15 October, at 10:00 UTC. Your subsequent wording change at 11:00 is shown in version 4, sent at 11:30. Version 3 approval does not cover that replacement wording.

We are provisionally holding four hours on 20 October, supporting an estimated delivery on 21 October. To confirm that booking, please explicitly approve the exact version 4 wording by 14:00 UTC today. We will assess whether it fits the reserved work by 15:00 UTC. Please also confirm acceptance of the revised schedule by 16:00 UTC.

Schedule acceptance alone does not confirm production. We need the content approval, a scope assessment showing the work fits, and your schedule acceptance. We will then send booking confirmation.

If content remains unresolved at 14:00, the proposed delivery stays unconfirmed and we will reassess feasibility. The provisional hold expires at 16:00 unless all prerequisites are met and we confirm the booking. Otherwise, we release it and offer new dates after the outstanding decisions are resolved.

5. Make escalation resolve a specific blockage

Escalation should identify an available approver, resolve conflicting feedback, agree reduced scope, or accept a later plan. Adding senior recipients without a decision request creates visibility, not necessarily progress.

Send the escalation contact a compact record: the version awaiting decision, the missed deadline, capacity already released, and the exact decision needed. Ask whether the named approver remains available or an authorised substitute should take over.

Do not assume the most senior person copied into a thread can approve. A coordinator’s acknowledgment that they forwarded a file is not approval either. Confirm who holds the decision role.

Reminders can flag elapsed deadlines, but they should not convert silence into approval or independently authorise dependent work. Disputed instructions and exceptions need a named agency owner.

6. Recover without hiding scope or responsibility

Some delays require more than moving a date. Use the cause of the blockage to choose the next action:

  • The original date is essential: Check actual capacity. Offer feasible reduced scope or staged delivery, stating what remains unfinished. Do not promise an urgent slot before confirming resources.
  • The agency sent the wrong file: Correct it, acknowledge the error, and reset the review plan. Waiting for a usable package is not client review lateness.
  • Approval has conditions: Identify which conditions need another decision. A request to change wording does not establish approved final wording.
  • Feedback conflicts across channels: Consolidate it and ask the approver to resolve contradictions. Do not select whichever comment makes production easiest.
  • The replacement scope exceeds capacity: Offer a new estimate or smaller scope rather than treating schedule acceptance as permission for extra work.

Independent, already-authorised tasks may continue when useful. Preparing approved assets might help; laying out disputed copy may create avoidable rework. Record the boundary rather than keeping people occupied for its own sake.

7. Keep a record that explains the date change

Use one shared record containing the version, approver, deadlines, time zone, reservation cutoff, actual response time, approval evidence, changed scope, booking prerequisites, and next owner.

Record work state separately from booking state. “Version 3 approved; version 4 wording unresolved; replacement slot provisional” explains more than “delayed.” When decisions arrive privately, bring the evidence into the shared record and clarify ambiguity with the approver.

For the hypothetical example, the final entry should show whether all booking conditions were met by 16:00. If not, record that the hold expired and identify what must happen before another availability check. Do not leave an expired provisional date displayed as a commitment.

8. Evaluate whether the buffer earns its place

Track observable outcomes across review cycles: unresolved review time, reserved hours left unused, time to confirm replacement bookings, rework after late changes, and any dependent work started without recorded approval.

Investigate patterns rather than assigning a single cause. Replies routinely arriving just after release may justify reviewing the cutoff. Repeated difficulty reassigning reserved time is a reason to examine the buffer’s cost and usefulness, not proof that it is too expensive.

Review those observations alongside actual utilisation, the suitability of alternative work, unpredictable review effort, and the service commitments the buffer supports. Adjust the reservation and escalation rules while keeping permission explicit and booking expiry visible.

Agency operationsClient approvalsCapacity planningProject management

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications