A job management process for a service business is the path one job takes from first inquiry to final payment — and in most small service companies, that path runs through the owner seven separate times. Not once. Seven. The lead comes in and you decide whether it's real. You price it. You chase the signature. You put it on the board. You answer the tech's question from the field. You rebuild the invoice from memory. You call about the check.
Each of those is a handoff: a point where a job changes hands, changes state, or waits. Every handoff either has a system or has you. This is a decision framework, not a lecture — seven handoffs, and at each one a rule for deciding whether to hand it off, automate it, or keep it on purpose.
What counts as a job management process, exactly?
A job management process is a defined sequence of states a job moves through, where each state has one owner, one entry condition, and one exit condition. The states are the same in every service business: inquiry, qualified, quoted, won, scheduled, delivered, invoiced, paid. What differs between a company that scales and one that doesn't is whether each transition is written down and assigned, or improvised by whoever is nearest. If a job can sit in a state with nobody accountable for moving it, that state is where your week disappears.
Before you fix anything: find the handoff that's absorbing you
Don't redesign all seven. Diagnose first. Pull your last 20 completed jobs and, for each one, write down two timestamps: when the job entered a stage and when it left. Most owners have never looked at this, and the answer is rarely where they'd guess.
Then apply the test I use on my own operation:
- Volume test: which stage did you personally touch on more than 15 of the 20 jobs?
- Dwell test: which stage has the longest average time-in-stage relative to the actual work it requires? A quote that takes four minutes to write but sits six days is a handoff problem, not a workload problem.
- Variance test: which stage has the widest spread between fastest and slowest job? Wide variance means no rule exists — the outcome depends on who caught it.
The stage that fails two of three is your first project. Fix it completely before touching another. If this diagnostic feels familiar, it's the same logic behind running an operations audit on your own business — measure before you rebuild.
Handoff 1: Inquiry to Qualified
The tell: you can't answer "how many leads came in last week?" without checking three places — the phone, the inbox, and a text thread.
The decision:
- If qualification requires trade judgment (is this a repair or a replacement? is this scope even something we do?), then the judgment stays with a person — but the capture never does. Every inquiry from every channel lands in one intake record within 60 seconds, automatically.
- If qualification is really just five factual questions — address, service type, property age, urgency, how they found you — then it is a form and a script, and it belongs to whoever answers the phone.
What replaces you: a single intake destination and a written disqualification rule. Write down the three conditions under which you say no: outside the service radius, scope you don't self-perform, or a customer who won't give an address. A person who knows the three no's doesn't need to ask you about the yes's.
One detail owners skip: capture property year built at intake. In residential trades that single field decides whether the job triggers EPA's Lead Renovation, Repair and Painting requirements later. Catching it at minute one is free; catching it on scheduling day costs you the slot.
Handoff 2: Qualified to Quoted
The tell: quotes go out at night. If your estimates are written after 8pm, the pricing knowledge lives only in your head and the day never has room for it.
The decision:
- If more than 70% of your work is repeatable scope, then build a priced task library — line items with standard labor hours and material assumptions — and any trained estimator can produce the same number you would.
- If the work is genuinely custom every time, then you keep the number but give away everything around it: the site visit scheduling, the photos, the measurements, the draft document. You should be supplying one input, not producing one document.
- If you can't articulate your own pricing logic out loud in two minutes, then this handoff is not delegable yet, and your project is writing that logic down — not hiring.
What replaces you: a task library plus a service-level rule — every qualified lead gets a quote within one business day, no exceptions, and the clock is visible on the board.
Handoff 3: Quoted to Won
This is the handoff most owners never staff, and it is usually the most expensive one. A quote that never gets a second contact isn't a lost sale — it's an unfinished process step.
The tell: your follow-up depends on whether you remembered.
The decision:
- If the quote is under your average job size, then follow-up is fully automated: a sequenced touch at day 1, day 3, and day 7, then the record closes as declined. No human judgment required.
- If the quote is above average size or the customer is a repeat account, then the automation triggers a task for a person, not a message to the customer. Big jobs need a call; the system's job is to make sure the call happens.
What replaces you: a follow-up cadence that runs whether or not anyone is thinking about it, which is exactly the discipline covered in automating customer communication across the seven touchpoints.
The compliance step nobody builds in: if you sell in the customer's home, the FTC's Cooling-Off Rule gives buyers three business days to cancel most sales of $25 or more, and requires you to hand over two copies of a cancellation form at signing. Read the requirements directly at the FTC's cooling-off rule guidance. Bake the form into your signed-document packet so it goes out automatically. Electronic signature is fine — ESIGN and UETA have made that settled ground for two decades — but the packet contents can't depend on the salesperson remembering.
Handoff 4: Won to Scheduled
The tell: you are the dispatcher. Every schedule change routes through your phone.
Scheduling is the handoff owners defend hardest, usually with a real argument: "only I know which tech can handle that job." Fine. That's a skills-matrix problem, and a skills matrix is a spreadsheet.
The decision:
- If assignment depends on certification, licensure, or demonstrated capability, then write the matrix — techs down the side, job types across the top, yes/no in the cells — and dispatch becomes lookup instead of intuition.
- If assignment depends on "who's closest," then it's already a routing rule and your software does it better than you do.
- If the job has a pre-work compliance gate, then scheduling is blocked until the gate clears.
That last branch is where residential contractors get hurt. For pre-1978 housing, EPA's Lead Renovation, Repair and Painting Program requires a certified firm, a certified renovator on the job, delivery of the "Renovate Right" pamphlet before work begins, a signed acknowledgment, and three years of retained records. That's a scheduling-stage checklist item. So is the preliminary lien notice in states that require one — Florida's Notice to Owner runs 45 days from first furnishing, and that clock starts long before you invoice.
What replaces you: a skills matrix, a pre-work checklist that blocks the calendar slot until complete, and one named dispatcher — even if that dispatcher is part-time.
Handoff 5: Scheduled to Delivered
The tell: field techs call you with questions that have the same answer every time.
The decision: count the inbound field calls for one week and sort them into three piles.
- Answered by a document — where's the shutoff, what's the standard torque, which supplier do we use. These become written SOPs with a fill-in template. Pile one should shrink to near zero within a month.
- Answered by a rule with a limit — "can I spend on a part?" becomes a standing purchase authority up to a set threshold, above which they call.
- Genuinely novel — unexpected structural damage, an angry customer, a safety issue. These stay with you or a lead tech. They should be rare.
What replaces you: documented answers, spending authority, and a defined escalation path. Also: the job isn't "delivered" until the field close-out packet exists — photos before and after, materials used, hours, customer signature. No packet, no state change. That single rule is what makes the next handoff possible, and it's the same standard behind a real quality control process for service work.
Handoff 6: Delivered to Invoiced
The tell: you can name a job that finished more than a week ago and hasn't been billed.
This is the quietest profit leak in the trades, because nothing looks broken. The work got done. The customer is happy. The money just hasn't been asked for.
The decision:
- If your close-out packet is complete and standardized, then invoicing is clerical and should be same-day, done by an administrator or an outsourced back-office function.
- If your invoices require you to reconstruct what happened, then the defect is upstream at handoff 5. Fix the packet; the invoice fixes itself.
- If change orders are the reason invoices stall, then the rule is: no unsigned change order, no work performed. Verbal change orders are the single most common cause of a billing dispute I see.
What replaces you: a same-day invoicing standard and a weekly "delivered but not invoiced" report that someone other than you reads. Set a target — no job older than 48 hours in that state. This is also where lien deadlines bite. Texas residential claimants generally must file by the 15th day of the third month following the month the work was done; Florida's claim of lien runs 90 days from last furnishing. Put your state's deadline on a calendar rule, not in your memory.
Handoff 7: Invoiced to Paid
The tell: collections is a mood. You call when the bank balance makes you nervous.
The decision:
- If the invoice is under 30 days, then reminders are automated and impersonal — day 7, day 14, day 25.
- If the invoice is 30 to 60 days, then a named person calls, on a schedule, with a script.
- If the invoice is past 60 days, then it stops being an accounts-receivable task and becomes a decision: payment plan, lien or demand letter, or write-off. Pick one within five business days. Aging receivables that nobody decides about are the ones that never get collected.
What replaces you: a weekly aging review and a deposit policy. Track days sales outstanding as a single number; most healthy residential service companies sit under 15 days because they collect on completion, while commercial and new-construction work runs 45 to 60 by contract.
Two practical notes for this stage. First, if you're considering passing card fees to customers, the rules are jurisdictional: Visa and Mastercard cap surcharges at 3%, Colorado caps them lower, and states including Connecticut and Massachusetts prohibit them entirely. Second, the reporting threshold on card and third-party payments changed — the July 2025 tax law restored the $20,000 and 200-transaction standard for Form 1099-K, so check current IRS guidance on Form 1099-K before assuming what your processor will report. Clean books at this handoff are what make every earlier number trustworthy.
How to sequence the rebuild
You cannot fix seven handoffs at once, and the order matters more than the effort. Use this rule: work backward from money, forward from volume.
- If cash is tight, start at handoff 7, then 6. Collections and invoicing produce results in weeks, not quarters.
- If cash is fine but you're drowning, start wherever the diagnostic flagged two of three failures.
- If you're about to hire, fix handoff 5 first. Undocumented field work makes every new tech a training project.
- If growth has stalled, it's almost always handoff 3. Quotes with no follow-up are demand you already paid to generate.
Give each rebuilt handoff one metric and one owner. Handoff 2 gets quote turnaround time. Handoff 3 gets close rate. Handoff 6 gets days-to-invoice. Handoff 7 gets DSO. Four numbers on one page, reviewed weekly, and you'll know where a job is stuck without asking anyone.
The endpoint isn't a company you've abandoned. It's a company where the job moves whether or not you're thinking about it — the practical version of not being the bottleneck in your own business. Good books, a website that captures inquiries properly, and a few sensible automations all live inside these seven handoffs. None of them is the system. The system is the path, defined once, that every job takes. At Turnkey Services that's the first thing we map, because everything else an owner wants to fix turns out to be a symptom of a handoff nobody owns.
Questions owners actually ask about this
Do I need field service software to run this? No, but you'll outgrow spreadsheets around the point you have three field crews. The platforms in this market — ServiceTitan, Jobber, Housecall Pro, Workiz, ServiceM8, Aspire on the landscaping side — already model jobs as states. Define your handoffs first, then choose the tool that matches them. Buying software before defining the process just gives you a faster version of the same confusion.
Frequently asked questions
How many stages should a job management process have?
Seven handoffs covers nearly every service business: inquiry to qualified, qualified to quoted, quoted to won, won to scheduled, scheduled to delivered, delivered to invoiced, invoiced to paid. Fewer stages hide where jobs stall; more stages create administrative work nobody does. Each stage needs one owner and one exit condition.
Which handoff should I fix first?
Run the diagnostic on your last 20 jobs and fix the stage that fails two of three tests: you touched it on more than 15 jobs, it has the longest dwell time relative to actual work required, or it has the widest spread between fastest and slowest. If cash is tight, start at collections and invoicing instead — those produce results in weeks.
How do I hand off estimating without losing margin?
Build a priced task library before you hand off anything. List your repeatable scopes with standard labor hours and material assumptions, so an estimator produces the same number you would. If you can't explain your own pricing logic out loud in two minutes, this handoff isn't ready to delegate — writing the logic down is the actual project.
What belongs in a field close-out packet?
Before-and-after photos, materials used, hours worked, any signed change orders, and the customer's signature. Treat the packet as the exit condition for the delivered stage — no packet, no state change. Complete packets make invoicing clerical instead of investigative, which is what allows same-day billing.
Should verbal change orders ever be allowed?
No. Unsigned change orders are the most common cause of billing disputes and stalled invoices in service work. The rule is simple and should be non-negotiable across your crews: no signed change order, no work performed. Field techs need a documented path to get one signed on the spot from their phone.
What is a reasonable days-sales-outstanding target?
It depends on your work mix. Residential service companies that collect on completion commonly run under 15 days. Commercial and new-construction work is frequently 45 to 60 days by contract terms. Track the number weekly, and set a hard decision point at 60 days past due: payment plan, lien or demand, or write-off.