Your freelancer stopped responding mid-project: what to do, and what to have in hand

The short answer

Most silences are not disappearances. People get sick, travel, or lose a week to another client. So start with one calm, dated message, then a formal update request through Fiverr, and only cancel once the delivery date has passed. Fiverr gives you a clean route for that: if the freelancer is late and no extension was agreed, you can cancel 24 hours after the expected delivery time without their approval.

The harder question is what you do next. Whether a new freelancer can finish the job in days or has to start again depends on five things you either have in hand or do not: the work on your accounts, the keys in your name, a record of what is done, a run-book, and the brief. Check those before you cancel, while the order is still open.

First, rule out the ordinary silence

Before you treat it as a disappearance, look at the order page:

• Is the delivery date still in the future? If so, the freelancer is not late. A quiet week before a deadline is normal for a lot of sellers.
• Did you send everything they asked for? An order often waits on the buyer: a login, a sample file, an answer to a question you missed in the thread.
• Did they warn you? Scroll back. “I’ll be travelling next week” is easy to forget.

If all three check out and you still have no reply after a couple of working days, move to the steps below.

The steps, in order

A message you can copy for step 1:

Hi, I have not heard back since [date]. Could you tell me where the work stands and when you expect to deliver? If I don’t hear from you by [date], I’ll request an update through the Resolution Center. Please also make sure everything built so far is on my [platform / repository] account.

Calm and factual works better than a complaint. If they come back, you want to continue the project, not repair a relationship.

The five things that decide whether someone else can finish it

This is where most of the cost of a disappearance is decided, and it was decided on day one, not today.

What	Where it should be	If it is missing
The work itself	Workflow in your automation account, or code in your repository	The new freelancer rebuilds from the brief
Every key and login	Created in accounts you own	You recreate them, and anything using the old ones stops
What is done	Notes in the order thread, or commits with messages	The new freelancer has to rediscover it
How to run it	A short run-book: how to start it, where the logs are	Every restart is guesswork
What it should do	Your brief and acceptance line	Scope drifts again with the next person

The first two matter most. If the workflow lives in the freelancer’s own n8n, Make or Zapier account, or the code only exists on their laptop, you do not own a half-finished project. You own an idea. Who should own the accounts goes through the inventory in detail.

Why “on your accounts” decides it

A half-finished job is only worth something if its progress is written down somewhere you can reach.

I saw the same principle from the other side in my own setup. A batch job of mine that writes drafts from a queue was killed halfway through when the PC ran low on memory. Nothing that was already done was lost, because each item’s state was recorded in the queue file, not held in the running process. I restarted it and it carried on from where it stopped (the full note).

A freelancer project works the same way. If the progress lives in your repository, your workflow account and your order thread, a new person can pick it up. If it lives in the freelancer’s head and accounts, it stopped when they did.

Credentials are the other half. One of my scheduled publishing jobs kept starting on time for two days while the token it relied on had stopped working, and nothing was published. Keys you hold yourself can be checked, rotated and handed to the next person. Keys only the absent freelancer holds cannot.

Handing it to someone new

When you message a new freelancer, give them the situation straight:

• What exists and where. Links to the workflow export or repository, and which parts were finished.
• What was promised and not delivered. Your original brief and acceptance line, unchanged.
• What you are not sure about. “I don’t know if the error handling was built” is useful. Guessing is not.

For an AI-built app, a paid review before a fix is the sensible first order: someone reads what exists and tells you whether to continue or restart. Some gigs are set up for exactly that; Amish Sohail lists a cheap first review of a vibe-coded site before bigger fixes. For an automation, a short scoped order to get the existing workflow running is a good start, and some sellers, such as Ramon C, also offer live one-hour fix sessions. The AI coding brief and the handover note for a Cursor or Claude Code project cover what to send.

Set up the next project so silence costs less

None of the freelancers I have hired has gone quiet mid-project, so the steps above come from Fiverr’s own rules, not from a rescue I ran. What I can speak to is the setup. I always ordered through a custom offer, and I have paid both ways: a fixed price released on a schedule, and milestones released after checking each stage’s work. Milestones make a disappearance much cheaper, because you have only paid for stages you have seen working. Fixed price or milestones explains how they work on Fiverr.

Put these in the first message, before you order:

The maintenance terms add one more line worth having: what happens if the freelancer stops working on it later. It is the same problem, a few months on.

Where it goes wrong anyway

• They come back after you have cancelled. It happens. If the work is on your accounts, you can still choose to continue with them in a new order. Nothing is lost either way.
• The work is on their account and they will not transfer it. You cannot force it. Write down what you know, keep the brief, and start again with the day-one terms above.
• You cancel in anger before the date. A late order is your right to cancel; an early one is a negotiation. Wait for the date, keep the record clean.

Wrap-up

A freelancer going quiet is annoying. Losing the work is expensive. Send one dated message, request an update, and cancel only once the delivery date has passed. Before you do, collect what is on your accounts. Then make “built on my accounts, saved as you go” the first line of the next brief, so the next silence costs you a few days, not the project.