What to Do When a Client Pauses a Project Mid-Stream

The email comes in on a Tuesday. 'Hey, we need to put the project on hold for a few weeks. Nothing wrong, just some internal stuff. We'll be back in touch.'

A few weeks becomes two months. When they come back, they want to restart immediately and are fuzzy on where things left off. And somehow, the invoice you sent before the pause is suddenly being questioned.

This is a billing situation, not just a scheduling one. Treat it like one from the start.

Close Out Before You Step Away

When a project pauses, do a proper close of your time log before you stop working. Do not leave timers open, tasks half-labeled, or notes scattered across three apps. Spend twenty minutes tying it off.

Total your hours. Export or screenshot the log. Note the last completed deliverable. Send a summary email to the client that documents exactly where the project stands at pause.

That email is your boundary marker. Everything before it is already done. Everything after it is new work, potentially with new scope.

Pauses Are When Scope Creep Hides

Clients use pauses to quietly revise what they thought they were getting. They sit with the project for two months, talk to their team, read some articles, and come back with a slightly different vision.

They usually do not announce this. They just start making requests that are slightly off from the original plan. And because you are happy to have the work back, you start saying yes without comparing it to what was agreed.

Your original project setup in your time tracker is your reference point. When the project restarts, pull it up. Look at the task list you built at kickoff. Anything the client is asking for now that is not on that list gets logged separately and flagged for a conversation.

Do Not Restart Without a Written Confirmation

Before you open your timer again, send a short email. Something like: 'Picking back up on [project name]. Here's where we left off and what's still in scope. Let me know if anything has changed.'

Give them a chance to tell you it has changed. If it has, you price the additions before you start them. If it has not, you have a second written confirmation of scope.

This takes five minutes and saves you from billing arguments later.

Track Your Ramp-Up Time

Getting back into a paused project takes real time. You have to re-read notes, re-open files, remind yourself where things were. That is billable work.

Log it. Create a task called 'Project restart review' or similar. Start the timer when you start re-reading. This is not padding your hours. This is work you are doing because the client paused the project, not because you were disorganized.

Most clients accept this if it is labeled honestly. Some will push back. Either way, it needs to be on the record.

What to Do If the Invoice From Before the Pause Is Disputed

This happens. The client comes back, gets the new invoice, and suddenly has questions about the one you sent two months ago.

If you closed your time log properly before the pause, you have the data to answer every question. If you did not, you are reconstructing from memory, which is exactly the position you do not want to be in.

The time log from before the pause should still be in your tracker. Pull it up. Walk them through it by task. Let the data do the talking.

The Habit

Treat every project pause like a mini project close. Log it, export it, document it, send a summary. It adds twenty minutes to your day when it happens and saves hours of billing headaches when the project comes back to life.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots