The 9-day rule: when to nudge, when to escalate

You do not need a better feeling about chasing invoices. You need a schedule that tells you, without any feeling involved, what today’s message is. The chasing guide covers the mindset: why the nudge is not rude, why silence is the actual problem. This one is the opposite kind of useful. It is the calendar. Print it, save it, stop deciding on the fly.

Here is the aging schedule, with the exact tone at each stop.

Day 1: log it, send the shrug

The invoice went overdue today. Two things happen, and both are small. First, the noticing: write the due date somewhere you will actually look, whether that is a spreadsheet, a calendar reminder, or a sticky note on the monitor. A freelance translator with six clients on different net terms cannot hold this in her head, and she should not have to. Second, the friendly bump the chasing guide calls the assumption of innocence: “Bumping this in case it slipped through. Invoice attached again for ease.” It reads like a shrug because it is one. Most late payments are forgetfulness, and a shrug is all forgetfulness needs. No follow-up question required. This one is allowed to be ignored once.

Day 9: the day you stop assuming forgetfulness

This is the rule this post is named for. Day 9 is not the day you first speak. It is the day the tone turns.

The day-1 shrug assumed the client forgot. If nine days have passed and nothing moved, forgetfulness stops being the working theory, and your message should say so, politely. Wait much longer and you have let a week and a half of silence do the talking for you, which reads as either forgetfulness on your end or a business too disorganized to notice its own receivables. Nine days is long enough to be generous, short enough that the invoice is still fresh in the client’s mind and not buried under three weeks of other email.

This is a rule of thumb I am proposing, not a finding from anywhere. Pick your own number if nine feels wrong for your business; the point is picking one and using it every time, so the timing itself carries no signal. The day-9 message is still warm, just no longer weightless: “Following up properly this time: the June invoice is now nine days past due. Could you let me know when it is scheduled?”

Day 16: the specific, answerable ask

One week after the tone turned, the question gets teeth. Restate the invoice number, the amount, and the original due date, then ask something the client has to actually respond to: “Is there anything blocking this on your end?” A vague nudge gets skimmed and forgotten again. A specific question with a number attached gets answered, even if the answer is “sorry, chasing it internally now.”

This is also the rung where you make paying stupidly easy. Reattach the invoice. Restate the payment link. Do not make anyone dig through a three-week-old thread to remember what they owe you and how to send it. If a client has to ask “wait, how much was this again,” you have already lost a day to that reply.

Day 23: the boundary, stated as fact

Three weeks and change is where friendly persistence needs backup. Not a threat, a term you already have and are simply naming out loud: “New work on this account pauses until the balance clears. I would rather just get paid and keep going; can we close this out this week?” The tone here is calm, not cold. You are not angry. You are informing the client of a mechanism that was already true and giving them a clean way to avoid it.

This is also the rung where a lot of freelancers privately give up and just let it get awkward. It does not need to be. Stating a real boundary is not the same as chasing, and clients who deal with a lot of freelancers respect the ones who have terms and use them.

Beyond day 23: it stops being an email problem

If the boundary message does not move things, the schedule has done its job: it has surfaced a decision for you rather than a hundred more days of low-grade dread. Call the client, or decide whether this is a relationship worth continuing. That call is yours to make, deliberately, instead of by default because nobody ever escalated it out of your inbox.

Why the schedule dies in practice

None of these four messages is hard to write. The problem was never the words. It is that day 9 for one client lands on the same afternoon as day 16 for another and a lead reply for a third, and something has to give. It is usually the invoice, because it feels less urgent than whatever just came in. Then day 9 quietly becomes day 20, the tone calibration is gone, and you are drafting a boundary message that reads like a first nudge because you never sent one.

An AI operator is built for exactly this kind of schedule: not clever, just relentless about dates. Amber tracks every invoice’s age against the rungs above, drafts the message for whichever day it is, and sends it in your voice on the day it is due, not the day you got around to it. She does not confuse day 9 with day 16 because she is not doing five other things at the same time. If you want every message approved before it goes out, that is one setting; if you would rather she handle day 1 through day 16 alone and only bring you the day 23 boundary call, that is also one setting. Either way, the schedule runs on the calendar’s clock, not your mood.

The one thing to do today

Write down your own version of this schedule now, before any invoice is overdue: pick your first-nudge day, your direct-ask day, and your boundary day, and save the three messages so future you can send the right one in seconds instead of composing it from scratch while annoyed. If you would rather hand the calendar itself to someone else, see how the pieces run without you.