Direct answer
No retainer, no queue. Pause it clean, in writing.
A retainer is simple: the client buys your time in advance, month by month. When the payment stops, the month it bought stops with it, no matter how friendly the requests stay. Here is how to read the ledger, pause without burning the relationship, and restart on terms that do not recreate the problem.
Updated October 23, 2026. The two delivery records quoted below are real and public, with their client decision states read back from the live service on publication day.
Step 1. Read the retainer as a ledger, not a relationship
Write down three lines before you answer anyone: the periods paid, with dates; the period currently unpaid, and how many days late it is; and the work you have already done inside the unpaid period, if any. Retainers fail in a fog of goodwill, where work keeps flowing because the requests are small and the relationship is good. The ledger ends the fog. Either the current period is paid and work is owed, or it is unpaid and work is paused, and the work already donated inside the unpaid period is a number you can see, and decide about once, instead of a leak you never notice.
Step 2. Check the boring causes once
One check, once: a card that expired, an accounts contact who changed, an invoice that never arrived, a payment sent to old details. Ask one factual question in writing: the payment for this period has not arrived, is it on its way? If it is a genuine admin slip, you get a date and the story ends. If the answer is vague, delayed, or about their cash flow, treat the period as unpaid and move to the pause. What you do not do is ask the same hopeful question every week while the work continues. One check is diligence. Four checks is financing their business with your time.
Step 3. Pause new work in writing, with the restart attached
The pause message is short and carries its own restart: retainer work is paused from today because the current period is unpaid; work already delivered is listed and invoiced; the moment the unpaid period is settled, work resumes for the remainder of that period or rolls to the next one, whichever you both prefer. Attach the ledger to the message. A pause with a restart attached is not a threat, it is a schedule, and good clients treat it as one. Then honour your own pause: no small favours, no quick calls that become deliverables, no starting the urgent thing while payment is sorted. Every exception teaches that the pause is a negotiating mood, not a term.
Step 4. Let the record show what was delivered, and when
Retainer arguments later are almost always about the boundary: what was done while the retainer was live, and what was asked after it lapsed. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the decision states your deliveries can carry:
Accepted: the decision is on the record
- Status: accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release_hint ok_to_release.
- Steps: 4 steps total, 4 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Pending: checked, and still waiting on a decision
- Status: pending, release_hint hold.
- Steps: 5 steps total, 5 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Read them as the retainer pattern. The accepted record, 4 of 4 steps checked, decided by the client, release_hint ok_to_release, is work inside a settled period: delivered, checked, accepted. The pending record, 5 of 5 steps checked with release_hint hold, is work still waiting for a decision, which is exactly where an unpaid period leaves everything. When each retainer period's work is delivered as a handover on a record like this, the boundary question answers itself from the record: these stages were delivered and accepted in the paid months, these requests arrived after, and nothing in between is blurred.
Step 5. Settle the old period before any new work starts
The restart sequence matters more than the restart price. First the unpaid period is settled in full, for the work already done and the time already held. Then the next period is paid in advance again, because that is what a retainer is. Only then does new work enter the queue. The offers to refuse are the friendly consolidations: roll the arrears into next month, double up later, start now and square it at the end. Each one converts a one month problem into a permanent overdraft. If the client genuinely cannot settle in full, the honest smaller shape is a dated payment plan for the arrears with work paused until the first payment lands, written down, with dates.
Step 6. Restart on a retainer that cannot leak
On restart, tighten the three terms that failed. Payment date: a fixed day, in advance, with work auto-pausing a set number of days after a missed payment, stated in the agreement so the pause is the contract working, not you being difficult. Scope rhythm: a simple monthly note of what the retainer covers and what counts as extra, so requests outside it get quoted instead of absorbed. Delivery record: each period's work delivered and accepted on the record, so the next boundary, good or bad, is already documented. A client who accepts those terms was having a cash problem. A client who refuses all three was having a you problem, and you have your answer.
What a record does not settle
A verifiable receipt proves the saved result was not changed since it was saved; it does not prove the retainer was paid, does not by itself pause anything, and cannot collect an unpaid month. The agreement, the payment ledger, and your written pause settle the money. This page is general information, not legal advice.
Frequently asked questions
My client stopped paying their monthly retainer but keeps asking for work. What do I do?
Treat the retainer as a ledger. List the periods paid, the period unpaid and how late it is, and any work you already did inside the unpaid period. Check the boring causes once, in writing: an expired card, a changed accounts contact, a missing invoice. Then pause new work in writing with the restart attached: work is paused from today because the current period is unpaid, delivered work is listed and invoiced, and work resumes the moment the unpaid period is settled. Honour the pause completely, including small favours, because every exception teaches that the pause is negotiable. Settle the old period first, take the next period in advance again, and only then let new work into the queue.
Can I keep working and trust them to catch up?
You can, and freelancers do, and it is how one missed month becomes three. The requests feel small because each one is small; the total is the overdraft you are quietly extending to a client whose own bank would charge for it. If you choose to keep working as a deliberate decision, price it as one: name the total exposure you will carry, name the date it stops, and get both in writing. What never works is drifting, continuing because stopping feels awkward while hoping the money appears. Hope is not a payment term, and a client who respects you will respect a clean pause far more than a resentful drift that ends in a blowup.
How do I handle work I already did in the unpaid period?
Invoice it, itemised, with its delivery record attached, as part of the pause message. Work done in good faith inside a period the client led you to believe was live is owed work, and presenting it calmly and completely in the first pause message is far stronger than dribbling it out later as grievances. If the client disputes a piece, the record shows what was delivered and when, and the acceptance state shows what they decided. If they settle, the piece closes with the period. If they do not settle, that invoice, its record, and your written pause and restart offer are the complete file any formal route would ask you for.
What if the client says pausing will damage their business?
It might, and that is the retainer working as designed: continuous work is what the monthly payment buys, and a pause is the visible price of stopping it. Answer with the restart, not with guilt: the pause lifts the same day the period is settled, and you will hold their place in your schedule until a stated date. Offer the smaller honest shapes if they help, a dated plan for the arrears with the first payment before work resumes, or a reduced retainer at a reduced scope that they can actually sustain. What you do not offer is the one shape that damages your business instead: full work at no payment, indefinitely, on trust.
How do I set up the retainer so this cannot repeat?
Three terms, written before the first month: the payment lands in advance on a fixed day; work pauses automatically a set number of days after a missed payment, with the restart spelled out; and each period's work is delivered and accepted on a record, so paid and unpaid periods never blur. When the work runs through Zambo, every step is saved as it happens and the client gets one handover link per delivery to accept or flag, so the boundary between settled work and new requests is visible to both sides. For $0.99, run the restart month on a record where every delivery is saved and accepted as it lands, and the next missed payment pauses a queue you can prove: get the Day Pass. A Day Pass covers 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 for 30 days, one payment, or $290 for 365 days, and $19 for 30 days for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.
Related
- Can I stop work if a client has not paid my last invoice?
- A client owes me for finished work and wants a new project started. Should I start?
- How do I ask a client for a deposit before starting work?
- My client changed their mind and wants me to redo the work for free. What should I say?
- My client says the files I delivered will not open. How do I prove the delivery was fine?
- How do I charge a client for extra meetings and calls?
- Start with your problem: every problem in this directory, routed to its page