What Is the Right Process From Booking a Job to Finishing It?

By Bill Stilwell · Last reviewed October 18, 2026

The short answer

A scheduling and delivery procedure covers every sold job from the calendar to the final handshake. Book it, confirm people, materials, tools, access, and safety ahead of time, do the work as agreed, keep the customer posted on changes, check the work before you call it done, and close out with acceptance, payment, records, and a follow-up. The detailed rules for each step live in Part 17.

Why it matters

A gutter cleaning crew shows up without the long ladder and has to come back. A handyman finds a problem mid-job and adds it to the bill without asking. A cleaner finishes but never checks the bathrooms. Each of these turns a paid job into a complaint. A written procedure catches them before the customer does.

22.5.1 Schedule

What it means: put approved work on the calendar.

How to do it: only schedule jobs with a signed estimate and any required deposit. Block enough time, including travel and setup. Send a confirmation with the date, arrival window, and what the customer needs to do (see 17.1 Scheduling and 17.3 Appointment Reminders).

Common mistake: booking jobs back to back with no travel time, so every job after the first runs late.

22.5.2 Prepare

What it means: confirm staff, materials, tools, access, and safety before the day.

How to do it: the day before, check who is assigned, that materials are ordered and on hand, that tools and the vehicle are ready, how to get in (gate code, pets, parking), and any safety hazards (see 11.4.1 Hazard Identification).

Common mistake: finding out about the dog or the locked gate when the crew is already in the driveway.

22.5.3 Deliver

What it means: do the work according to the scope.

How to do it: bring the scope to the job. Do what’s written. If you find something outside the scope, stop and talk to the customer before doing it (see 11.1.5 Change Order).

Common mistake: doing extra work as a favor and then billing for it as a surprise.

22.5.4 Update

What it means: tell the customer about progress and changes.

How to do it: send short updates at set points: on the way, started, any delay, any change, and done. For longer projects, set a regular update day (see 17.5 Project Delivery).

Common mistake: going quiet when there’s a delay. Silence makes customers assume the worst.

22.5.5 Inspect

What it means: check quality before calling it done.

How to do it: use a short checklist for each service. Take before and after photos. Walk through it with the customer when possible (see 17.7 Quality Control).

Common mistake: the person who did the work is the only one who checks it, every time.

22.5.6 Close

What it means: get acceptance, payment, records, and follow-up.

How to do it: get the customer’s sign-off, collect final payment (see 10.7.4 Final Payment), save photos and notes to the job record, and schedule any follow-up or warranty check (see 16.9 Closing the Job). Ask every customer for a review in the same neutral way, not only the ones who seem happy. Google’s policies don’t allow asking only satisfied customers (see 14.6.2 Neutral Review Requests and 14.10.3 Review Gating and Incentives). With the customer’s permission, add a good job photo to your Google Business Profile (see 14.1.9 Photos and 11.1.12 Photo Permission).

Common mistake: leaving without payment or photos, then chasing both for weeks.

When to get help from a pro

An operations consultant or field service software provider can help set up scheduling and job checklists. Questions to ask:

Can the software send confirmations, reminders, and on-the-way texts automatically?
Can crews attach photos and checklists to each job from their phones?
How do change orders get approved and recorded in the field?

Bill’s note

[Bill: add a short note. For example, how SiteSmarty runs a website project from kickoff to launch, or a client whose reviews improved once they started sending on-the-way texts.]

How I did this for SiteSmarty

[Date I did this:]
[What I actually did, step by step: my project steps from signed proposal to launch and handoff]
[What it cost and how long it took:]
[What surprised me or what I’d do differently:]
[Screenshot or photo to add, with private info blurred: the project checklist]
[Result so far:]

Questions people ask

What should I confirm before a job starts? Staff, materials, tools, access, and any safety issues, ideally the day before.

How often should I update customers? At set points: on the way, started, any delay or change, and done.

What should a final inspection include? A service checklist, before and after photos, and a walk-through with the customer when possible.

When should I ask for a review? At close-out, and ask every customer the same neutral way.

Audit check

Outline line	Question	Pass looks like	Fail looks like	Evidence to collect
22.5.1 Schedule	Are only approved jobs scheduled with confirmations sent?	Signed jobs, confirmation sent	Unsigned jobs booked	Calendar and confirmations
22.5.2 Prepare	Are staff, materials, tools, access, and safety confirmed ahead?	Prep checklist done	Surprises on site	Prep checklist
22.5.3 Deliver	Is work done to scope with changes approved?	Change orders signed	Surprise extras	Scope and change orders
22.5.4 Update	Are customers updated at set points?	Update log	Silence during delays	Message history
22.5.5 Inspect	Is quality checked with photos?	Checklist and photos	No check	Job record
22.5.6 Close	Are acceptance, payment, records, follow-up, and a neutral review request done?	All five	Unpaid, no records, or reviews asked only of happy customers	Job record, payment, review request log

Where this fits

Do this first: 22.4 Sales and Estimate Procedure, 17.1 Scheduling

Do this next: 22.6 Payments and Bookkeeping Procedure

Sources

Google Business Profile Help, "Tips to improve your local ranking on Google" (checked October 18, 2026)

This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.