August 5, 2026
The Job Handoff Checklist: From Estimate Approval to Crew Dispatch
A structured job handoff ensures every project is truly ready before dispatch. Confirming scope, materials, customer selections, access details, and crew requirements prevents delays, miscommunication, and costly scheduling mistakes.
.png)
The customer signed. The deposit cleared. Everybody's happy.
Three weeks later your crew is standing in a driveway with no gate code, the material showed up in the wrong color because nobody confirmed the selection, and the customer is irritated because your salesperson promised a start date that never made it onto anyone's calendar.
Nothing went wrong with the sale. Something went wrong in the handoff - the gap between "we sold it" and "we're building it." In most shops that gap isn't a process at all. It's a salesperson forwarding an email and hoping.
A handoff checklist closes it. Think of it as a readiness gate: a job doesn't get dispatched until one person has confirmed it's actually ready to build. It takes an afternoon to set up and it kills an entire category of problems permanently.
Where handoffs break
Four failures cover almost everything.
The first is the promise nobody wrote down. Your salesperson told the customer "we'll start in about two weeks." Nobody else in the company knows that. The customer treats it as a commitment, because it was one, and you find out when they call asking why nothing's happening.
The second is the selection that was never made. Color, finish, fixture, material grade. The proposal said "customer to select," nobody went back and got it, and ordering quietly stalls for a month while everyone assumes someone else handled it.
The third is the scope that only lives in the salesperson's head. They walked the site. They saw the tight driveway, noticed the ceiling height, clocked the tricky corner by the stairs. None of it reached the crew, because the proposal says "install flooring, 400 sq ft."
The fourth is the job that got scheduled before it was ready. Material hasn't shipped, permit isn't in, deposit didn't actually clear. It went on the calendar because the calendar had a hole. Now you're calling a customer to move them, which costs you more credibility than the empty slot ever cost you money.
Every one of these is prevented by asking a single question before dispatch: is this job actually ready?
The commercial half
These items confirm the money and the agreement are solid. Miss one and you're exposed.
You need a signed agreement on file - not a verbal yes, not an email saying "looks good." You need the deposit received and cleared, and those are two different things when you're about to spend money on material. You need the final scope and price locked in writing, including anything renegotiated on a phone call after the original proposal went out.
You need every customer selection confirmed, with the exact product named. Every "customer to select" line in the proposal has to be resolved before this job moves.
You need the payment schedule agreed - deposit, progress payments, final, and what specifically triggers each one. And you need any promised dates recorded, including verbal ones. Especially verbal ones. Write down what was said and who said it.
The field-readiness half
This is the half that gets skipped, because the sale feels finished once the money is handled. It's also the half your crew actually needs.
The crew needs the full address with directions, not "the blue house on Maple." They need access details: gate code, lockbox, which door, where to park, whether there's a dog, whether the HOA restricts work hours. They need the on-site contact and phone number, which is frequently not the person who signed the contract.
They need the scope written in crew language - a few plain sentences someone can read on a phone. Your proposal is a sales document. This is a work document. They are not the same thing and one does not substitute for the other.
They need the site conditions and gotchas: the tight driveway, the ceiling height, the neighbor's fence, the corner by the stairs. Whatever your salesperson noticed and would otherwise forget by Thursday.
Then the operational facts.
Material status with dates - ordered, delivered, or on site. "Handled" is not a status.
Permit status, where somebody has actually checked rather than assumed. E
stimated duration in crew-days and crew size, because "two days, three guys" can be scheduled and "bathroom remodel" cannot.
And the skills or certifications required, so you know who on your team can actually do this job.
Who signs off, and what happens when something's missing
A checklist with no owner is a suggestion. Two rules turn it into a gate.
One named person approves the handoff, and it isn't the salesperson. Salespeople are motivated to push jobs through - that's their job and it's fine. But the gate needs someone whose job is readiness, not volume. Office manager, ops lead, whoever fits your shop.
And an incomplete job doesn't get dispatched. It gets a blocker with a name and a date attached. "Waiting on customer tile selection, Sarah is chasing, expects Thursday" is a managed job. "Mostly ready" is a job that's about to go wrong on somebody else's time.
Two exceptions are worth writing down, because they'll happen whether you plan for them or not. Emergency and warranty work skips the gate and gets documented afterward. And owner override exists, but gets logged with a reason - if you're overriding every week, the gate isn't your problem, your intake is, and that pattern is worth being able to see.
One more thing, and it solves more handoff problems than the checklist itself: a five-minute spoken conversation between the salesperson and whoever's dispatching. Not an email. Everything in the gotchas category only exists in the salesperson's head, and it comes out in conversation, never on a form.
The checklist
Copy this onto a clipboard or into a shared doc.
Commercial:
- Signed agreement on file.
- Deposit received and cleared.
- Final scope and price locked in writing.
- All customer selections confirmed.
- Payment schedule agreed.
- Promised dates recorded, including verbal.
Field readiness:
- Full address with directions.
- Access details - code, lockbox, door, parking, dog, hours.
- On-site contact and phone.
- Scope in crew language.
- Site conditions and gotchas.
- Material status with dates.
- Permit status.
- Duration in crew-days and crew size.
- Required skills.
Sign-off:
- Salesperson-to-dispatch conversation completed.
- If all items are complete, release to schedule.
- If anything is outstanding, mark it blocked and record what it's waiting on, who owns it, and the expected clear date.
What a paper checklist can't do
Run that for a month and your handoffs will get measurably better. Then you'll hit its limits, and there are three.
A paper checklist confirms information exists. It doesn't move it. You tick "access details captured" and the gate code is now on a clipboard in your office while your crew is standing at the property. The check passed and the crew still calls you. In MotionOps those details go into the appointment itself as instructions, so the gate code, tools needed, and dog in the backyard arrive in the crew's mobile app next to the work description, site contact, and directions. Capturing it and delivering it become one action instead of two.
A paper checklist also has no teeth. Nothing physically stops a job from getting scheduled with a box unticked, which means the whole thing holds exactly as long as everyone stays disciplined. That's usually about three weeks. MotionOps puts the gate inside the flow instead: an accepted proposal becomes a work order that carries its own status, so nothing gets dispatched off a separate list somebody forgot to update. You schedule as a draft, where nobody is notified and nothing is promised, and only when you publish do the crew and customer get told. That's a readiness gate as an actual step rather than a good intention. Scheduling also filters to employees with the right skills and service area, blocks anyone who's off, and catches double bookings while you're still scheduling rather than at seven in the morning on the job site.
And a paper checklist ends at dispatch. The moment work starts it's a filed piece of paper, and everything the handoff established - scope, selections, promised dates - starts drifting the first time the customer asks for something extra. Because the proposal, change orders, schedule, timesheets, photos, and invoices all live on the same work order in MotionOps, the handoff record and the live job stay the same object. When the customer wants extra work, the crew prices it and takes the signature on site, so the scope you locked at handoff either stays locked or gets properly updated - instead of getting quietly renegotiated in a text thread you'll be arguing about at invoicing.
The checklist gets your handoffs right. A system keeps them right.
Book a Demo and we'll walk one of your own jobs through it, sale to dispatch.
.png)
.png)
.png)