A video editor in one of the freelance communities we follow recently described the “Ghosting” feeling: “I don’t mind waiting for feedback. I mind not knowing whether I’m waiting for feedback or whether they just forgot I exist.”
That distinction—waiting versus wondering—is the actual source of professional stress. A known two-week wait is a manageable line item on a calendar. An unknown delay, where you don’t know if the client is busy, confused, or has quietly abandoned the project, is a threat to your cash flow.
When a client delayed project approval happens, the instinct is to send a “just checking in” email. But after the third “checking in” message, you aren’t a professional partner—you’re a nuisance.
To fix the delay, you have to fix the process that allowed the silence to happen in the first place.
Why Clients Delay: The “Homework” Problem
Most freelancers assume a delay means the client is unhappy with the work. In reality, it’s usually Feedback Friction.
Giving feedback is “high-effort” work. It requires the client to switch from “manager mode” to “creative critic mode.” If you send a client a 20-minute video or a 3,000-word document and simply ask, “What do you think?” you have just given them a massive homework assignment.
They don’t delay because they’re mean; they delay because they don’t have a 90-minute block of focused time to complete the “assignment” you just sent.
Other common causes include:
- The Invisible Chain: Your contact is waiting on a stakeholder you’ve never met.
- The Inbox Fog: Your update is one of 400 unread emails.
- Decision Paralysis: They aren’t sure how to articulate what they want to change, so they put it off until they “feel inspired.”
The Contractual Shield: The “Pause Clause”
The most effective way to handle a client delayed project approval is to have a rule already written in your contract. This is often called a Pause Clause or an Idle Project Fee.
A standard Pause Clause states:
If a project remains idle for more than 14 days due to a lack of client feedback, the project will be officially ‘Paused.’ To resume the project, a re-activation fee of $X will apply to cover the cost of re-scheduling and administrative overhead.
This changes the dynamic. You aren’t “begging” for feedback; the client is simply choosing whether or not to trigger a fee they already agreed to.
A 3-Step Framework for Professional Pushback
Step 1: Name the Blocker (Not the Person)
Don’t make it about the client’s failure to reply. Make it about the project’s failure to move.
Wrong: “You haven’t replied to my email yet.”
Right: “The [Project Name] is currently at a standstill while we wait for approval on Milestone 2.”
Step 2: Attach a Fact-Based Consequence
Deliver the news without apology. A consequence isn’t a threat; it’s a logistical reality.
The Script:
To keep our launch date of [Date] on track, I’ll need your feedback by [Day]. If we miss that window, I’ll have to shift the final delivery to [New Date] to accommodate other scheduled projects.
Step 3: Follow Through and Document
If the date passes and you don’t move the deadline, you have taught the client that your boundaries are fake. If you move the date, send a brief notification:
The Script:
Since I didn’t hear back by our cutoff of [Date], I have moved this project to ‘Paused’ status. Let me know when you’re ready to pick this back up, and I’ll send over a refreshed timeline based on my current availability.
3 Follow-Up Scripts for Every Stage of Delay
Level 1: The “Soft Nudge” (2 Days Past Due)
Hi [Name], I’m checking to ensure you received the latest version of [Project]. I’m ready to dive into the next phase once you’ve had a chance to review. Is there anything I can clarify to help you get through the feedback?
Level 2: The “Firm Boundary” (5 Days Past Due)
Hi [Name], we are now five days past the feedback window for [Project]. This delay is starting to impact our ability to hit the [Date] launch. If I can get your thoughts by tomorrow, I can still keep us on the current schedule. Otherwise, we’ll need to adjust the final delivery date.
Level 3: The “Project Pause” (10+ Days Past Due)
Hi [Name], as I haven’t heard back regarding [Project], I’ve had to move this into my ‘Inactive’ queue to make room for other scheduled commitments. I’d love to finish this strong for you—whenever you’re ready to resume, just reach out and we can look at my next available start date.
What Not to Do
Don’t Apologize for Following Up:
Saying “Sorry to bug you” implies that your time is less valuable than theirs. You are a business owner, not a solicitor.
Don’t Escalate in One Channel:
If they aren’t answering email, try a quick LinkedIn DM or a brief text. Some people live in their DMs and treat their inbox like a graveyard.
Don’t Keep Working:
One of the biggest mistakes freelancers make is continuing to work on the next phase while waiting for approval on the previous one. This is how you end up doing 20 hours of work that the client eventually asks you to “completely redo.”
How SwiftSignoff Removes the “Awkwardness”
The reason most freelancers hate following up is that it feels personal. It feels like you’re nagging a friend for money.
SwiftSignoff changes this by moving the “nudge” into a system.
Automated Reminders:
The portal sends the follow-up, not you. The client doesn’t feel “pestered” by a person; they feel “notified” by a tool.
The Rolling Timeline:
When a client delays an approval, the portal automatically shifts the entire project schedule forward. The client sees the launch date move in real-time as they sit on feedback. This makes the “cost” of their delay visible without you having to say a word.
The Central Source:
There is no “I didn’t see the email” excuse. The project link is persistent and holds the latest version of the work, the revision history, and the pending tasks in one place.
FAQ
How long should I wait before following up?
If the project is fast-moving (1–2 weeks), follow up every 48 hours. For longer projects (1–3 months), follow up every 4–5 business days.
What if the client says they are “too busy” for months?
Transition them to a “Maintenance” or “Retainer” fee to hold their spot in your calendar, or officially close the project and require a re-initiation fee to start again later. You cannot be expected to keep your schedule open for someone who isn’t using it.
Is it okay to charge for a rush fee at the end?
Yes. If the client’s delay forces you to work over a weekend or pull all-nighters to hit their original (now compressed) deadline, a rush fee of 25–50% is standard.
Should I call the client if they aren’t emailing back?
Yes. A 2-minute phone call can often resolve a 2-week email delay. Sometimes they just need to hear a human voice to realize that their silence is causing a real person real stress.
Stop chasing approvals in a cluttered inbox. See how SwiftSignoff automates your client follow-ups.