The call comes in February, about a deck you finished in October.
The client is polite, which somehow makes it worse. "We were out there clearing snow and my husband noticed the gate latch was never done. And honestly we don't think the skirting on the north side got its second coat either. We figured we'd flag it before we do the final review."
You genuinely cannot remember. October was four decks, a fence repair, and a bathroom, and this one closed out in the middle of it. You have a memory of the gate working. Or is that the other deck's gate? The final payment cleared months ago, so at least it is not a squeeze play. Or it is exactly a squeeze play, and the "final review" line was the tell. You cannot know, because you have nothing: no photo of the latch, no note, no signature, nothing but two memories, one of which belongs to someone who now believes you cut a corner.
So you drive out. Forty minutes each way, in February, to look at a latch. It works fine. The skirting has two coats. The client is slightly embarrassed and you are out a morning, and a small permanent dent has appeared in a relationship that was perfect in October.
"Done" is the most disputed word in the trades, and it is disputed because it usually ends with a whimper: the truck just stops showing up. The last day on site looks like every other day. Nobody stands in front of the work and agrees, out loud and on the record, that this is finished and this is what finished looks like. That is the gap the February call climbs through.
The walkthrough is a ritual, and rituals are the point
The fix is not a document first. It is a habit the document hangs off: the completion walkthrough.
On the last day, you walk the job with the client. Not a wave from the driveway: a walk. Every room you touched, every item on the scope, at the pace of the slowest question. You point at the things they cannot see: the extra blocking behind the towel bar, the drip edge, the reason the transition strip sits where it does. They point at the things they have been quietly wondering about, and you answer them now, in person, while answering is cheap.
The walkthrough does three jobs at once:
It flushes out the punch list while you are still mobilized. The smudge, the sticky drawer, the missed touch-up: finding them today costs you twenty minutes with tools already on site. Finding them by phone in three weeks costs you a trip.
It transfers the work. There is a real psychological handover in walking a client through their own project. It converts "the contractor's job site" back into "our kitchen," and clients who have had that handover call less, worry less, and refer more.
It creates the moment where sign-off is natural. Asking someone to sign a completion certificate cold, by email, a week after you left, reads as legalistic. Asking at the end of a walkthrough they just participated in reads as the obvious last step. Same signature, entirely different conversation.
Here is the whole script, and it is not adversarial:
"That's everything on the scope, so let's do the walkthrough: I'll show you what we did and you tell me anything that doesn't look right. Anything we find today, I fix today or it goes on a list with a date. Then I'll have you sign off that we're done, you get a copy with the photos, and I'll send the final invoice tonight."
Notice what that promises: their concerns get a guaranteed hearing before they sign anything. That is why clients say yes to it.
What is a completion certificate?
In Zeus, the walkthrough ends in a completion certificate. It is a short document that says this job, at this address, was completed on this date, with the client's signature captured on your phone, on the spot. What they signed is frozen at that moment, so a later edit to the job cannot quietly restate the document their signature sits on. The job's photos sit on the same record.
The photos matter as much as the signature. Sign-off proves the client agreed the work was done; the photos prove what "done" looked like on that date. The February latch question dies against either one; together they do not leave it room to be asked. Photos taken from the job's Photos tab are already on that job. For the ones that went to your camera roll instead, the Job Photo Organizer's Find Nearby Photos scan reads their GPS and proposes the job for you to confirm. The deck photos end up on the deck job, not lost between lumber receipts and your kid's birthday.
If the client is not there on the last day (a rental, a client who travels, a landlord three provinces away) the same signature happens remotely. You send the certificate the way you send a quote for remote signing, they sign from wherever they are, and the record is identical. Slower by a day, weaker as a ritual, just as strong as paper.
And then it stays findable. The signed certificate lives with the job and in your Sent Documents archive. The you of next February answers the latch call from your phone in the driveway of a different job, in about ninety seconds, without driving anywhere.
Sign-off first, then the final invoice
The sequence is the strategy: walkthrough, signature, then the final invoice.
A final invoice that arrives after a signed completion certificate is administrative. The client already agreed, in person, standing in the work, that the job is complete. The invoice merely bills the thing they signed. Payment terms start against a clean position. If collection ever does get ugly, "signed completion certificate dated the 14th, invoice sent the 14th, unpaid since" is about the strongest position a small contractor can hold.
A final invoice that arrives without that sign-off is an invitation. It lands, the client walks their own house alone looking for reasons it is too big, and every smudge becomes a negotiation. Most final-invoice disputes are not really about money; they are about the client never having been told, in a way they participated in, that the job was over.
One number worth naming: the last invoice is usually your margin. On a $30,000 job billed in stages, the final $6,000 might be most of what you actually earned. Spending forty-five minutes of walkthrough to protect that specific payment is the best hourly rate on the whole project.
What if the client won't sign yet?
Sometimes the walkthrough finds real items. The client is happy but not done: the closet door rubs, one screen is on backorder, there is a paint touch-up behind the fridge. They are not refusing to sign; they are refusing to pretend, which is fair.
Do not push for a signature on "done" when both of you can see it is not. A signature extracted over objections is worth less than no signature; it converts your clean document into evidence of pressure. Handle it as a punch list instead:
Write the list on the spot, with the client, with dates. Three items, each with what happens and when. In Zeus this is the job's record: notes and photos on the items, a scheduled return visit on the board, so the punch list is a plan, not a promise.
Decide what happens to the invoice out loud. Two honest options. Bill the final invoice minus a holdback that reflects the punch list. The backordered screen is not worth $6,000 of your money, so name a number that maps to the work: "I'll invoice now and knock the last $400 to after the screen's in." Or, if the list is trivial and the trust is good, finish the items this week and run the normal sequence a few days late. What you never do is leave it vague, because vague is where February calls are born.
Then sign when it is true. Punch list cleared, certificate signed, invoice settled. The delay costs you days. The alternative (a signature that papers over a known list, or no signature at all) costs you the entire point of the document.
A client who will not sign and will not name items is a different animal. That is not a punch list. That is a dispute arriving early, and the walkthrough just did you the favor of surfacing it while you are still on site with goodwill and something to trade, instead of six weeks later with neither.
The habit, sized honestly
None of this is heavy. The walkthrough is thirty to sixty minutes on jobs that run days or weeks, and five minutes on a one-day repair. Even a service call can end with "come look at this before I pack up" and a two-photo, one-signature close. The certificate is a couple of minutes on a phone you were already holding.
What it asks of you is consistency, because the whole value is that it is always there. An archive with sign-offs on eight jobs out of ten protects eight jobs out of ten, and the February call always comes from the other two.
Frequently asked questions
Is a completion certificate legally binding?
It is strong evidence, which is what you actually need. It documents that on a specific date the client inspected and accepted the work: the exact fact most completion disputes turn on. It does not override your contract or local lien and consumer-protection rules, which vary by province and state, and holdback regimes on larger jobs have their own timelines. For the residential disputes small crews actually see, a signed certificate with photos usually ends the argument long before anything legal begins.
Does sign-off waive the client's warranty?
No, and say so at the walkthrough; it makes signing easier. The certificate records that the scope was completed and accepted, not that the client forfeits recourse if a fitting fails in March. Completion and warranty are different clocks; if anything, the certificate helps warranty work too, because it fixes the date coverage started and what condition the work was in.
What if the client just never responds to a remote signing request?
Send it once, nudge once by message, then document and move on: note the completion date, keep the photos, send the final invoice referencing the completed walkthrough. Silence after a delivered certificate and photo set is a far better position than silence after nothing. The remote case is also the argument for doing the signature on site whenever a human is available: on-site sign-off has a near-perfect completion rate, because it is ten seconds and the person is standing right there.
We're a two-person crew. Isn't this overkill?
Size the ritual to the job, not the paperwork to the company. The certificate takes minutes regardless of headcount, and small crews are exactly who cannot absorb a $4,000 final-invoice haircut or a wasted February morning. The smaller you are, the more each dispute costs you relative to the month.
ZEUS