A roofing sales-to-production handoff is complete only when one production owner accepts the sold-job record and every missing item has a named next owner. A signature alone is not the handoff. Sales submits the current agreement, approved scope, selections, job records, customer commitments, and known exceptions. Production either accepts the packet, returns a specific gap, or routes a defined question to the person authorized to decide it.
Keep the handoff separate from ordering materials, assigning a crew, or promising an install date. Those are downstream production steps. The handoff gate answers a narrower question: does production have the company-required source information to begin its own work?
Define the boundary before you build the checklist
Your CRM stage names should mirror the way your company actually works. Roofr's current Job Board training shows roofing teams how to create, edit, and reorder stages, move job cards through a workflow, and view time in stage. That is a useful model for visibility, not a universal definition of when your company accepts a job. Review Roofr's current Job Board training.
Write your own start event in one sentence. For example: “The sales owner may submit a retail replacement after the company's accepted agreement and selection records are stored in the job.” If deposits, financing, insurance documents, permits, or another approval matter to your process, record the status your authorized team requires. Do not let the checklist invent contract or legal rules.
Use a three-outcome handoff gate
- Accepted by production: the receiving role found every required source record and logged acceptance. Downstream work may begin.
- Returned for missing information: the reviewer names the exact missing record, assigns one person who can supply it, and leaves the return history visible.
- Decision required: the evidence exists, but the reviewer lacks authority to resolve a scope, price, contract, technical, insurance, or schedule question. The record goes to the company-designated decision-maker.
“Looks good” is too vague to audit. “Waiting on sales” is not an owner. Record the reviewer, outcome, time, missing item if any, next owner, and next review point.
Build the packet from source records
1. Name the sales submitter and production receiver
The sales owner assembles the packet and remains responsible for fixing a returned sales-side gap. One production coordinator, project manager, or other company-designated role reviews it. Other people can help, but the current record should always show who owns the next move.
2. Link evidence instead of rewriting it
Do not ask an office coordinator to paraphrase an accepted scope, infer a color from a text message, or copy a customer promise into a fresh summary without its source. Link the current document and label superseded versions. A short handoff summary is useful for navigation, but it should not become an unofficial second contract, scope, or selection record.
Keep common categories separate: accepted agreement, approved scope, company-required selections, inspection or measurement records, photos, approved changes, property logistics, administrative statuses, customer commitments, and unresolved questions. “Attached” is only complete when the reviewer can open the current item and recognize what it is.
3. Return precise gaps
A useful return reason is inspectable: “current selection source not linked,” “approved change has no attached record,” or “homeowner timing commitment needs authorized review.” Avoid vague labels such as “bad handoff.” Keep the earlier submission and return visible so the team can see what changed.
Start production only after acceptance
After production accepts the packet, create the downstream work your company requires. Keep ordering, scheduling, crew assignment, customer updates, execution, and closeout as distinct tasks with their own owners and dependencies. ServiceTitan's current roofing Production Queue documentation uses stages for review and approval, order and schedule, execution, and closeout. It also documents assignees, due dates, attachments, and task dependencies that keep a later task blocked until the preceding one is complete. See ServiceTitan's current Production Queue documentation.
You do not need that specific software or those exact stage names. The operating principle is useful in any CRM, job board, or spreadsheet: an accepted handoff should create visible downstream responsibilities, not a new set of private reminders.
Keep materials, scheduling, and updates in separate lanes
The handoff packet can state the approved selection source and the current material-order status. It should not let an administrative reviewer choose products, calculate quantities, substitute items, or approve technical specifications. Assign those decisions to the qualified role your company names.
Likewise, “ready for production review” does not mean “install date promised.” Scheduling depends on the production calendar, crew capacity, material status, weather, and other company rules. Let the authorized production owner confirm the schedule, then give the office an approved homeowner update and the next communication date.
Customer commitments deserve their own field because they often disappear inside sales notes. Record what was promised, where it came from, and whether production accepted it. If a commitment conflicts with the current plan, route it for a decision before anyone repeats it to the homeowner.
Review the handoff queue by exception
A short daily review should surface submitted jobs with no receiver, returned packets with no owner, decisions waiting on an authorized person, accepted packets with no downstream task, and jobs whose homeowner update has no owner or due date.
Track counts that describe the process instead of inventing a financial promise: packets submitted, accepted on first review, returned by missing-item category, waiting for a decision, and time in the handoff stage. Review repeated return reasons to improve the form, required fields, training, or source-document rules.
Where a dedicated assistant fits
Early Bird provides one dedicated, full-time executive assistant with ongoing support. Onboarding maps the complete operating scope, including sales stages, production roles, systems, documents, decision boundaries, customer communication, and downstream dependencies. The team then stabilizes one priority workflow at a time without treating the assistant as a disconnected one-task hire.
Inside the client's approved process, the assistant can maintain the handoff queue, confirm that required links are present, request missing routine records, assign or remind the named owner, log review outcomes, prepare approved customer updates, and keep exceptions visible. Technical scope, material specifications, ordering decisions, pricing, contracts, insurance interpretation, crew assignment, safety, and final scheduling remain with the qualified or authorized people the company names.
See how Early Bird supports roofing contractors, connect the front end with the roofing storm-lead workflow, and review the field-service software handoff guide.
Roofing production handoff questions
Does a signed agreement mean the job is ready for production?
Not automatically. A signature may be your submission trigger, but production still needs the company-required source records and an explicit acceptance outcome before downstream work begins.
Who owns a returned handoff?
Assign the person who can supply the exact missing item. Do not assign a department label. The production reviewer owns the review outcome; the named correction owner supplies the missing record and resubmits it.
Should the checklist include every roofing specification?
No. The checklist should confirm that the approved technical source exists and is linked. Qualified people remain responsible for creating, reviewing, and approving technical scope and specifications.