The half-day rule: invoice when client feedback stalls

Client feedback arrives late. You wait. The project stalls. And somehow, at the end of the month, you're the one apologising for the invoice being "a bit later than usual."

That stops now.

Why delayed feedback is a billing problem, not just a scheduling one

Most designers treat a slow-reviewing client as a workflow inconvenience. It is that, but it's also a cash flow event. Here's the mechanics:

You agree on a milestone: "I'll send the final brand files once you've approved the revised logo." The client goes quiet. Five days pass. They come back with "love it, one small change" (it's never one small change). You absorb those days into the project timeline and invoice whenever the dust settles.

What you've just done is offer a free overdraft facility to a business that almost certainly pays its own suppliers on terms.

A €5,500 branding project with a 50% deposit means €2,750 sitting in your accounts receivable. If the client drags approval across two weeks and then you invoice on Net 30, you're looking at six weeks between doing the work and receiving the money. That's a €2,750 cash gap you're financing with your own income.

The 48-hour threshold

The rule is simple: if a client hasn't responded to a feedback request within 48 working hours, you treat that milestone as client-side-delayed and you invoice for the completed portion immediately.

You don't wait for approval. You invoice for what you've delivered.

This isn't punitive. It's a boundary that separates your output from their process. You finished the work. The clock on payment should not be controlled by how long it takes someone else to check their inbox.

How to set this expectation before it ever becomes awkward

The worst time to introduce the half-day rule is after a client has already gone quiet. Build it into your contract and your project kick-off email.

One line in the contract covers it:

"Invoices for completed deliverables will be issued within 48 hours of delivery. Payment terms begin on the invoice date, regardless of approval status."

In your kick-off email, frame it practically: "I'll be sharing work for feedback in stages. If I don't hear back within two business days, I'll invoice for the completed stage and we'll pick up revisions in the next phase."

Clients who are good to work with will appreciate the clarity. Clients who bristle at this are telling you something useful before the money is already owed.

What "completed portion" actually means

Be specific in your contracts about what each milestone covers:

• Brand discovery: research, moodboards, and strategic brief
• Concept round: two or three initial directions, presented in context
• Refinement: agreed revisions on the chosen direction
• Final delivery: production-ready files in agreed formats

Each of these is a distinct invoiceable unit. When you deliver concept round files and the client goes quiet for 72 hours, that stage is done on your end. Invoice it.

The invoice you send when feedback stalls

The invoice itself needs to do some communication work. Don't just send a blank invoice and hope the client connects the dots. Use the description line:

"Brand concept development (Stage 2 of 4) - delivered 14 Jan. Revision session to be scheduled on approval."

This confirms what's been done, references the delivery date, and signals that the project continues. It doesn't feel like a threat. It feels organised, which it is.

If you're invoicing a UK client in GBP and a German client in EUR on the same day, you need to handle those separately without the admin overhead eating into the time you saved by invoicing promptly.

Handling the pushback

Two objections come up repeatedly.

"The client will be annoyed." Some will be mildly surprised. Almost none will be genuinely upset, because you explained the rule upfront and you're invoicing for work that is genuinely complete. The designers who get pushback are the ones who introduce this rule mid-project without warning.

"What if they don't approve the final files?" Your contract should separate payment from approval. You're not billing for their happiness with the work. You're billing for the professional output you produced. If revisions are in scope, do them. If they're out of scope, quote for them separately. Either way, the invoice for delivered work stands.

A note on the "after launch" trap

The half-day rule is particularly powerful as a defence against the classic final-payment delay: the client who sits on approvals for weeks, then owes you the back half of a €6,000 project, then goes quiet again after launch. If you've invoiced each stage on delivery, the outstanding balance at launch is the final file handover, not half the entire project. The financial exposure shrinks dramatically.

Make the rule automatic, not heroic

The half-day rule only works if you actually send the invoice. Under deadline pressure or in the middle of another project, it's easy to let 48 hours become 72, then a week. Remove the friction:

• Keep an invoice template ready for each active project with the milestone description pre-filled.
• Set a calendar reminder for 48 hours after every deliverable you send.
• If you use recurring structures (monthly brand retainers, for example), set up auto-send so the invoice leaves your account at 8am on the agreed date without you touching it.

The designers who get paid on time are not the ones with the most leverage or the scariest contracts. They're the ones who have turned invoicing into a reflex, not a task they get around to. A clear rule, built into your process before the first file is ever shared, is the simplest version of that reflex you can build.