Billing a client project — Patter

The case

The end of a project should be the easy part. The work is done. The client is happy, or happy enough. All that’s left is the paperwork.

And yet this is exactly where things go quiet. The deliverable goes out, the reply takes longer than expected, the invoice gets raised a week later than it should have, the files end up in three different places, and the follow-up email sits in drafts for four days because it feels awkward to send.

None of that is inevitable. It’s what happens in the absence of a routine.

The close-out is its own phase of the project, with its own steps, in a specific order. Sign-off before invoice. Invoice as soon as sign-off. Follow-up on a schedule, not when the discomfort finally outweighs the avoidance. Files archived before the project is mentally closed, not six months later when you can’t remember what anything was called.

Done properly, the close-out takes an hour. Done without a routine, it takes three weeks and a lot of unnecessary anxiety.

Closing Out a Client Project

Do a final check of the deliverable Before it leaves your hands. Not a full review — a last pass for anything obvious you'd be embarrassed to have missed.
Send the final deliverable to the client With a short note. What you're sending, what you need from them, and by when. Clear, not effusive.
Follow up if you haven't heard back Give it the time you agreed, or a reasonable amount if you didn't. Then follow up once, directly. @8 if still no response.
Get sign-off in writing An email reply is fine. You need something that says yes, this is approved. Not a thumbs-up emoji on Slack.
Raise the invoice As soon as sign-off is received. Not later today. Now. The longer you wait, the longer you wait to get paid.
Send the invoice with the correct details Client name, address, project reference, payment terms, due date. Check these before sending. Errors here cause delays that are entirely your fault.
Confirm the invoice was received Especially if you're working with a larger organisation where invoices go to a different person or department. A quick confirmation saves a lot of chasing later.
Follow up on the invoice if unpaid On the due date, not after. A short, factual message. No apology for asking. @8 again if needed.
Archive the project files Everything in one place, clearly named, in a structure you'll understand in two years. Not your desktop.
Back up any client assets you're responsible for If you're holding their files, make sure they're in more than one place. This is not optional.
Write a short project note What went well, what didn't, what you'd do differently. Three sentences is enough. This is for you, not a post-mortem for anyone else.
Close the project in your system Whatever you use — mark it done. Update the status, close the thread, remove it from your active list. Finished work shouldn't live alongside current work.

Make it yours

The link between step 3 and step 8 is the part most freelancers hate. Following up feels uncomfortable until you've waited long enough to be genuinely annoyed, at which point it feels worse. The routine makes it procedural rather than personal — you follow up because that's the next step, not because you're chasing.

If sign-off is taking longer than expected and the invoice is time-sensitive, it's reasonable to raise the invoice against the submitted deliverable with a note that final payment is contingent on approval. Whether that works depends on your contract and your client. Worth knowing before you're in that situation.

Step 11 is the one that compounds. A two-year archive of brief project notes is worth more than it sounds — patterns emerge, scope creep becomes visible, and the projects that looked profitable often aren't when you write down what actually happened.

Some projects need a formal retrospective with the client. Most don't. If yours does, add it before step 5 — you want that conversation to happen before the invoice goes out, not after.