Direct answer
Retainer hours ran out mid-month: the running record that makes the stop fair
It is the 18th of the month and the retainer is empty. The client, who has three more urgent things queued, has no idea the hours are gone, because the only person tracking them was you, in a spreadsheet they have never seen. Stopping now feels to them like an ambush; working on feels to you like training them that the limit is fiction. Both feelings come from the same defect: no running record the client could watch. Build the record, and the limit moment turns into a calm decision, stop or top up, made on shared numbers. Here is the pattern.
Updated October 26, 2026.
The over-delivery trap: free hours today become the expected baseline
Every freelancer who has run a retainer knows the slide. You go four hours over in March because the extra work was small and the client is good. In April those four hours are inside the client's mental picture of what the retainer covers, so the baseline moved and nobody signed anything. By June you are donating a week a month and resenting a client who genuinely believes they are inside the deal. Free hours are never read as generosity for long; they are read as the real terms. The trap is not the client's character, it is the absence of a visible count. When hours burn where the client can see them burn, the limit is a shared fact long before it is a problem, and nobody has to be the villain who announces it.
A running hours record the client can watch, receipt by receipt
Keep the retainer on a running record the client can open at any moment: each task logged as it runs, the hours it took, and the balance left, updated the same day the work happens. When the work runs through Zambo, every call carries a verifiable receipt under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so each logged task ties to a dated record of what was actually done, not a timesheet written from memory on Friday. A receipt proves the saved result was not changed since it was saved; it does not prove a task should have taken the hours it took, and it does not replace agreeing what counts against the retainer. What it does is make the running balance checkable line by line, so the mid-month conversation is about the queue, not about whether the count is real. New users get 20 free calls per day, then they upgrade when the job needs more.
The limit moment: stop or top up, decided on the record, in writing
When the balance hits zero, there are exactly two professional options, and the record makes both easy to offer: stop here and the remaining queue waits for the next block, or top up a stated block of hours at the retainer rate and the queue keeps moving today. Send the message below with the record link and the balance on it, and let the client decide in writing. The writing matters: a verbal keep going in a hallway call is how a top-up becomes a dispute in the next invoice. A written decision on the record is the new agreement, priced and dated. What never happens is the silent third option, work continuing on empty, because that is the trap from the first section wearing a helpful face.
Restarting clean: the new block starts from the same record
When the new block starts, whether it is next month's retainer or a top-up bought mid-month, it starts from the same record, not a fresh sheet. The old block closes with its final balance visible, the carried queue is listed as the first items the new hours will serve, and the balance resets to the block size where the client can watch it from day one. That continuity is what makes the system fair in both directions: the client can see they got every hour they paid for in the block that closed, and you can see the new hours are the only hours you owe. Over a few months the record also becomes planning data: which work eats the retainer, what a realistic block size is, and whether the retainer should grow, all arguable from numbers instead of impressions.
Copy-paste: the limit-moment message
Heads up from the retainer record: this month's block is fully used as of today, and the record with every task and its hours is here: [record link]. Two clean options: we pause the queue here and the remaining items start the next block on [date], or you top up [10] hours at the retainer rate and I keep moving today. Tell me in this thread which one you want and I will log the decision on the record. Nothing is running on empty in the meantime, so there is no surprise on the next invoice either way.
What a record does not settle
A verifiable receipt proves the saved result was not changed since it was saved; it does not prove an hour was well spent, does not decide what counts against a retainer, and cannot make a client top up or pay. The running record both sides can open, the written decision at the limit, and the terms you agreed at kickoff are what the conversation stands on. This page is general information, not legal advice.
Frequently asked questions
Retainer hours ran out mid-month. Do I stop work or keep going?
Stop, and make the stop a decision the client makes on the record: show the running balance with every task and its hours, then offer the two clean options, pause until the next block or a written top-up at the retainer rate. Working on past the limit without that decision converts the extra hours into the expected baseline and usually into unpaid hours. The exception is a genuine emergency you choose to cover as goodwill, labeled as goodwill in writing, once.
The client disputes my hours count at the limit. What settles it?
A record kept as the work ran settles it: each task logged the day it happened, the hours it took, and a dated receipt for the work itself that the client can open line by line. A timesheet assembled at month end from memory invites dispute and deserves some of it. If your count was built live and theirs is an impression, walk the record together task by task; that conversation almost always ends at the record.
Should unused retainer hours roll over to next month?
Only if you agreed it in writing at kickoff, because rollover changes what the retainer is: without rollover the client is buying your reserved capacity for the month, with rollover they are buying a bank of hours. Either model is fair when it is stated before the first block starts and the running record shows the balance under that rule. The unfair version is deciding at the limit, under pressure, in whichever direction the moment favors.