Sometimes the work is not late because you are behind. It is late because the project cannot move until the client sends feedback, approves a direction, provides content or answers a question.
That waiting time becomes dangerous when it is invisible. Your calendar still shows a project. Your client may still remember the original deadline. But the next move belongs to somebody else.
Know when a project is actually blocked
A project is blocked when there is no useful next action you can complete until somebody else does something first.
Examples include waiting for homepage copy, approval of a design direction, access credentials, legal review, product images or a decision between two options.
That distinction matters. If you still have independent work you can do, the project is not fully blocked. If you cannot move without client input, record that dependency instead of leaving the project looking normally “in progress.”
What to record while waiting
You do not need a complicated dependency-management system. For most freelance projects, six fields are enough:
The exact thing needed from the client.
The person responsible for providing or approving it.
When you asked for it.
The date required to protect the current schedule.
When you last contacted the client about it.
What happens if the dependency arrives late.
Now “waiting for feedback” becomes something you can manage rather than something you have to remember.
Follow up without chasing blindly
A useful follow-up should tell the client what you need, why it matters and what happens next. It does not need to sound irritated or apologetic.
Hi Alex — I’m ready to continue with the homepage. I’m waiting on approval of direction B before I move into the remaining pages. If I receive it by Thursday, I can keep the current delivery window. If it comes later, I’ll confirm the next available production slot.
This is stronger than repeatedly asking “Any update?” because it reconnects the request to the project.
Do not invent a universal rule such as “follow up every 48 hours.” The right interval depends on the agreed deadline, the importance of the dependency and what you already told the client. Instead, set the next follow-up date when you record the dependency.
Make schedule impact visible
A deadline should not silently survive every client delay. If the project needs three working days after approval and approval arrives a week late, the original delivery date may no longer be realistic.
Record the dependency and communicate the consequence before it becomes a dispute.
This does not mean punishing the client for being slow. It means keeping the project plan connected to reality.
A practical waiting-on-client example
| Project | Waiting on | Requested | Needed by | Status | Next action |
|---|---|---|---|---|---|
| Website redesign | Homepage approval | Sep 22 | Sep 25 | Waiting | Follow up Sep 26 |
| Brand identity | Logo direction | Sep 24 | Sep 29 | Waiting | Review after approval |
| Landing page | Final copy | Sep 25 | Sep 28 | Waiting | Build final sections |
| Case study | Customer quote | Sep 20 | Sep 23 | Overdue input | Confirm schedule impact |
The important column is not just Status. It is Next action. Even blocked work should tell you what happens next.
Six dependencies: separate reminders from production
This fictional review takes place on 12 October 2026. Add Next follow-up as a Date property and use Waiting or Resolved as dependency states. The dates below are agreed checkpoints for the example, not a recommended universal cadence.
| Project | Waiting on | Owner | Next follow-up | Next action |
|---|---|---|---|---|
| Website redesign | Homepage approval | Alex | 12 Oct | Confirm approval timing |
| Brand identity | Logo direction | Maya | 14 Oct | Confirm decision owner |
| Landing page | Final copy | Jo | 12 Oct | Request the agreed copy version |
| Case study | Customer quote | Sam | 13 Oct | Confirm publishable wording |
| Portfolio site | Image selection | Lee | Empty | Choose next checkpoint |
| Campaign assets | Final sign-off | Dana | — | Resolved; archive approval |
Website redesign and Landing page have checkpoints on 12 October. Ask for the specific missing input.
Portfolio site has no follow-up date. Choose a checkpoint; it should not disappear from review.
Filter the dated queue with AND: dependency state is Waiting AND Next follow-up is on or before 12 October 2026. Website redesign and Landing page should appear. Create a separate Waiting AND Next follow-up empty view for Portfolio site. The resolved campaign stays outside both views.
Keep production tasks separate: receiving the missing input lets you reassess remaining effort and availability; it does not automatically confirm a delivery date. Record the revised date after agreement. Use the AND/OR guide to check the queues and the weekly planner to schedule the work that can restart.
A simple Notion setup
If you manage several clients, add dependency fields to your Projects database rather than creating a separate complicated system immediately.
Useful properties are Status, Waiting on, Waiting owner, Requested date, Needed by, Last follow-up and Next action.
Then create a Waiting on client view filtered to projects with unresolved client dependencies. Sort by Needed by or Next follow-up so the oldest problem does not automatically become the highest priority.
This fits naturally with the broader workflow in How to Manage Multiple Freelance Clients Without Losing Track of Work. If what you are waiting for is feedback scattered across different channels, use the client feedback workflow. If the client is requesting additional work rather than approving existing work, use the scope-creep process.
Do not let blocked work occupy invisible capacity
A delayed client can create a second problem: when several blocked projects suddenly restart together, the work returns to your schedule at the same time.
That is why a good waiting-on-client system tracks more than reminders. It tells you which commitments may re-enter production and which original dates need to be revisited.
The objective is simple: know what is blocked, who owns the next move, when you will check again and what the delay changes.
Frequently asked questions
Is the whole project blocked if one input is missing?
Only if no useful independent work remains. Record the blocked deliverable or task and keep available work visible instead of labelling everything blocked.
How often should I chase client feedback?
Use the agreed checkpoint, the input’s needed-by date and the impact on production. Set a specific next follow-up and respect any request to pause contact.
Does late feedback automatically move the delivery date?
Reassess remaining effort and availability, communicate the impact and confirm a revised plan. Do not silently keep or replace the original date.
What should I record when approval arrives?
Keep the approver, date, exact deliverable and version, along with unresolved conditions. Then update the dependency and identify the next production action.
Use the approval documentation guide when the answer arrives. If that answer changes the work, follow the change request workflow.