How to pause a freelance project when a client goes quiet or stops paying

Most advice for freelancers covers how to get a project started and how to deliver it. Far less covers what to do in the middle, when a client simply stops responding: no feedback, no payment, no explanation. Work keeps sitting half-finished, you are not sure whether to keep going, and every week you wait is a week of unpaid risk.

Pausing work is not a punishment and it does not have to end the relationship. It is a normal business decision: you stop spending time and money on a project until the conditions to continue are met again. Below are templates for the three situations where a pause is usually the right call, plus how to restart cleanly once the client comes back.

Why pausing in writing matters

A pause that only happens in your head is risky. If you quietly stop working without saying so, the client may assume you are still on it, miss their own deadline, and blame you. If you say so in writing, you have a record of exactly when and why work stopped, which protects you if the project is ever disputed later or if the client resurfaces months later expecting the same timeline. Keep a copy of every pause message in your approval log, next to the deliverable or invoice it relates to.

1. Pausing because feedback has stopped

Use this when a client has gone silent on a draft and enough time has passed that the delivery date is now at risk.

Hi [name], I have not heard back on [deliverable] since [date], so I want to flag that the project timeline is now affected. I will pause further work here until I get your feedback, so I do not build further on an unapproved draft. Whenever you are ready, just reply and I will pick it straight back up. No rush on my end, just wanted you to have visibility.

This version avoids blame. It states a fact (no response since a date), a consequence (pause), and an easy way to restart (reply).

2. Pausing because payment is overdue

Use this after at least one payment reminder has already gone unanswered, and only for amounts that are genuinely due under the agreement, not for a payment that is a day or two late.

Hi [name], following up on invoice [number] for [amount], due [date]. I understand things come up, but I need to pause work on [project] until this is settled, so I can keep taking on new work reliably. As soon as the payment goes through, I will resume immediately — current remaining work is [list / estimate]. Let me know if there is an issue with the invoice itself and I will sort it out.

Naming the exact remaining work reassures the client that pausing is not an excuse to disappear; it is a specific, temporary hold.

3. Pausing because the scope keeps expanding without a decision

Use this when you have already sent a scope or pricing question (see our guide on scope creep messages) and the client has not answered it, but keeps sending new requests anyway.

Hi [name], I still need your answer on [the scope question from date] before I can take on [the new request]. To avoid building more on assumptions, I will pause new work until I hear back on that. The parts already agreed in [list] are unaffected and continue as planned.

This keeps the agreed-scope work moving while clearly separating it from the unresolved part.

What to do while work is paused

Keep the record current. Note the pause date, the reason, and the last approved deliverable in your approval log. If the client returns after a long gap, this is what lets you answer "where were we?" in under a minute instead of re-reading the whole thread.

Set yourself a check-in date, not an indefinite wait. A pause with no end point quietly becomes an unfinished project that costs you mental space for months. Decide now: if there's no reply in two weeks, does the project auto-close, go to a kill fee, or just stay open with no further chasing?

Do not do new work during the pause, even small requests "just to keep momentum." If you keep delivering through a pause, the client has no reason to resolve the actual blocker.

Stay polite even if you are frustrated. A pause message that reads as a threat tends to provoke a defensive reply or silence. A pause message that reads as a simple status update tends to get a quick, cooperative one.

Restarting after a pause

When the client comes back, a short recap keeps both sides aligned on where things stand and avoids re-litigating what was already settled.

Good to hear from you, thanks for [the update / the payment]. Picking back up now: current status is [status], next step is [step], and I expect to have [deliverable] to you by [date]. Let me know if anything has changed on your side since we paused.

Build the pause habit into your process

A pause is only awkward the first time you send one. After that, it becomes a normal, professional tool, like a revision limit or a deposit request, rather than a last resort you reach for only when you're already upset. The Client Approval Log + 50 Client Messages pack includes templates for exactly these difficult conversations, alongside the approval log that tells you, at a glance, what was last confirmed before things went quiet.

Get the Client Approval Log + 50 Client Messages ($9)