In this article
A contractor lead handling process is real only when one fact is obvious at any moment: who must do what next. If a new inquiry can sit in an inbox with no owner, change status without evidence or reach an estimator without its history, the team does not have a process. It has alerts and good intentions.
Build the workflow before buying more volume. Define a small set of states, require one owner and one next action, and put exceptions where a manager can see them. That operating layer is separate from how quickly a lead should be called and what the caller should ask.
theBuildd publishes this guide and sells residential home-improvement leads. The procedure below is a contractor operating template, not a claim that a particular response time, follow-up sequence or software will create a particular result. Contact, qualification, scheduling, attendance, sold work and return on investment are not guaranteed.
A lead-handling SOP starts before the alert arrives
The first lead is too late to decide who watches alerts, which projects fit or what happens after hours. Write those decisions down while the queue is empty. The document can be short, but each rule needs an owner and a visible test.
| Control | Decision to write | Proof that it is ready |
|---|---|---|
| System of record | Where the current state and next action live | Every authorized user can find the same record |
| Coverage | Which staffed hours and channels the team covers | The schedule names a primary and backup |
| Accepted work | Trade, residential scope, service area and exclusions | Intake staff can route fit, non-fit and unknown separately |
| Ownership | Who receives a new record and who covers an unavailable owner | A new test record produces one accountable owner |
| Response policy | The internal target and what starts the clock | Delivery and first action have separate timestamps |
| Escalation | What makes a record overdue and who resolves it | An overdue test enters a visible exception queue |
| Contact policy | Permitted channels, stopping rules and recordkeeping | Staff can find the consent context and record a stop request |
| Final dispositions | The allowed reasons a record can close | Closed records require a reason, not a blank note |
Do not copy a timing target or attempt count simply because another contractor uses it. Coverage, consent, project urgency and office capacity differ. The response-speed guide owns that evidence; this SOP owns whether your chosen rule is visible and followed.
If the leads are part of a small paid test, establish these controls beside the lead-generation trial checklist. A trial cannot evaluate a source cleanly when the team invents its workflow after delivery begins.
Use states that say what is true now
A state should describe a fact, not the team’s mood. “Hot,” “good” and “follow up” are weak states because two employees can interpret them differently. Use labels with entry and exit rules.
| State | What must be true | Required next move | Do not use it to mean |
|---|---|---|---|
| Received | The record entered the system | Check routing and create an owner | Contacted or accepted |
| Assigned | One current owner is recorded | Owner acknowledges the record | Everyone in the inbox owns it |
| Acknowledged | The owner has accepted responsibility | Complete the next due action | Homeowner answered |
| Working | An action is in progress or has just occurred | Record the result and next action | Keep the record open indefinitely |
| Next action due | A specific action, owner and due time exist | Complete, reschedule with reason or escalate | “Try again sometime” |
| Contacted | A two-way contact occurred | Apply the qualification process | Project fits automatically |
| Qualified next step | Written criteria were met and a defined next step exists | Complete the handoff | A sold job or guaranteed appointment |
| Closed | A final disposition and reason are recorded | Preserve the record for reporting | Hide an overdue lead |
Keep not reached, unknown, outside written scope, qualified and closed distinct. They answer different questions. Not reached describes contact. Unknown preserves missing information. Outside scope applies a written fit rule. Qualified reflects an actual qualification conversation. Closed says no open action remains.
The guide to what counts as a qualified home-improvement lead explains the underlying stage boundary. Do not let a workflow shortcut turn an opt-in into a qualified project before your team has the necessary conversation.
Build one minimum lead record
Keep source information and contractor work in the same accessible record, but do not blend them. A homeowner-reported project is not a contractor-verified condition, and an available provider field is not evidence that your team acted on it.
| Field group | Minimum fields | Why the group exists |
|---|---|---|
| Identity and request | Name, contact details, location, requested trade or work, and the original wording available to your team | Preserves what was submitted without adding a diagnosis |
| Source context | Provider or channel, campaign when known, receipt timestamp, and consent context available to the contractor | Supports routing, permitted contact and source reporting |
| Ownership | Current owner, assigned time, acknowledgement time and backup rule | Shows who is accountable now |
| Activity | Last completed action, timestamp, channel and factual result | Stops staff from reconstructing history from memory |
| Next action | Specific action, accountable owner and due time | Turns an open record into scheduled work |
| Stage and disposition | Current state, final reason when closed and reason last changed | Makes reporting reproducible |
| Handoff | Receiving role, promised next step and material context | Lets the next person continue without guessing |
Use unknown when a field is missing or unclear. Do not fill a blank with a likely answer, copy the same vague note into several fields or rewrite what the homeowner reported as a technical conclusion.
This schema is a recommended operating minimum, not a statement about what any provider sends. Ask each source what fields and consent context will be available, then configure the contractor-owned fields separately.
Give every lead one owner and one backup
Several employees may work a lead over time, but only one person should own the next action. A group notification is useful for visibility. It is not ownership.
| Role | Accountability | When ownership changes |
|---|---|---|
| Intake monitor | Confirms the record arrived and routing worked | After a working owner accepts it |
| Working owner | Completes and records the current next action | At an explicit reassignment or completed handoff |
| Backup owner | Takes records under the written coverage or escalation rule | When the primary is unavailable or the rule fires |
| Estimator or field role | Receives a complete project handoff | When the next stage is accepted, not merely forwarded |
| Manager | Resolves unassigned, overdue and disputed records | Does not silently become the working owner |
Microsoft’s Dynamics 365 assignment documentation, checked 26 September 2026, shows the same underlying routing concepts at software scale: rules can assign records to a person, team or queue, while availability, capacity and unmatched rules can leave a record unassigned. Your tool may be far simpler. The control still needs the same answer: what happens when the preferred owner cannot take the record?
Reassignment must change the owner field, preserve who changed it and create a new next action. Forwarding a message while leaving the old owner in place creates two versions of the truth.
Treat exceptions as queues, not notes
Normal work receives attention naturally. Exceptions disappear because they do not fit the happy path. Give each one a visible state, decision owner, evidence requirement and route back into the workflow.
| Exception | Evidence to preserve | Decision owner | Return-to-flow rule |
|---|---|---|---|
| Unassigned | Receipt time and routing result | Intake monitor or manager | Assign one eligible owner and due action |
| Owner unavailable | Availability issue and time found | Backup or manager | Reassign explicitly; do not duplicate the record |
| Overdue | Due time, current owner and last action | Manager | Complete, reschedule with a reason or close correctly |
| Possible duplicate | Matching contact, property or request fields | Intake monitor | Merge or link records without deleting source history |
| Missing or unclear field | Exact unknown and why it blocks routing | Working owner | Obtain the fact or send it to the defined review path |
| Outside written scope | Failed criterion and supporting detail | Authorized reviewer | Close with the correct reason or reroute under policy |
| Requested later contact | Homeowner’s requested window and channel | Working owner | Create the agreed next action and due time |
| Stop-contact instruction | Instruction, time and channel | Working owner or compliance role | Apply the relevant suppression process and close open outreach |
Microsoft’s assigned-record documentation, checked 26 September 2026, exposes unassigned records, assignment errors, reruns, manual reassignment and run history rather than hiding them in a general queue. Its run history includes the start time, duration, status, trigger and number of records affected. Those product fields are not mandatory for every contractor, but they show why an auditable exception record is more useful than a note that says “system issue.”
Do not use bad lead as an all-purpose exception. A source mismatch, unanswered outreach, duplicate record, unavailable estimator and homeowner stop request require different evidence and different action.
Define when a handoff is complete
A handoff is complete when the receiving role can act without reconstructing the previous conversation. Sending a screenshot, forwarding an email or changing a dropdown does not meet that standard on its own.
Before the receiver accepts ownership, confirm that the record shows:
- The homeowner’s reported request and location.
- The source and consent context available to the contractor.
- The current state and the facts supporting it.
- Prior actions, timestamps and factual results.
- The next step already explained or promised.
- The next action and due time.
- The person who owns that next action.
The qualifying caller also needs a consistent way to establish project, property, service area, timing and decision fit. Use the separate contractor lead qualification questions guide for that conversation. This SOP deliberately does not supply first-call wording; the call script is a different operating asset.
ServiceTitan’s home-service CRM guide, checked 26 September 2026, shows how contractor software brings customer history, communication, scheduling and follow-up into one system. ServiceTitan is a software vendor, so that page supports only the workflow context here. The software does not decide whether a handoff is complete. Your written acceptance rule does.
No open lead should lack a next action
A note records the past. A next action controls the future. Every open record needs three fields together: the action, its owner and its due time.
Use specific action labels such as review requested scope, return contact at homeowner-requested time, route for service-area decision or prepare estimator handoff. The field should describe the work, not contain a full call script.
Avoid entries such as:
follow up: no channel, purpose, owner or due time;left message: a past result, not a future action;waiting: no statement of who waits for what;call again: no defined trigger or stopping rule;good lead: an opinion, not a state or action.
Pipedrive’s current lead-management guide, published 8 June 2026 and checked 26 September 2026, reduces the same idea to four controls: an owner, a score, a next action and a timeline. Pipedrive is a CRM vendor, and no product-performance claim is used here. A contractor does not need to adopt its scoring model, but the owner-next-action-timeline combination is a useful test. If one part is blank, the work can stall without becoming visibly overdue.
Choose the contact cadence and stopping rules with the appropriate compliance advice for your business. The SOP should enforce the policy you approve, not invent one inside each record.
Run a short daily exception review
Managers do not need to read every note to keep the queue healthy. Start with the records most likely to be stranded and work in a fixed order:
- New records with no owner.
- Assigned records with no acknowledgement.
- Open records past their next-action due time.
- Open records with no next action or no action owner.
- Temporary states that have no exit rule.
- Handoffs that the receiver has not accepted.
- Records closed without a permitted disposition and supporting note.
For each exception, ask one question: what exact change returns this record to a valid state? The answer might be an assignment, a corrected due time, a manager decision, a completed handoff or an evidence-backed closure. It should not be another vague note.
Keep the audit distinct from performance coaching. The queue review repairs today’s records. Coaching addresses repeated behavior after the evidence shows a pattern.
Use the weekly review to fix the process, not blame the source
The weekly review should compare stable definitions across sources and owners. Begin with stage counts, then diagnose where the movement stopped.
| Review lens | Question to answer | Likely control to inspect |
|---|---|---|
| Receipt | Did every delivered record enter the system once? | Integration, inbox monitoring and duplicate rule |
| Assignment | Did every record receive an eligible owner? | Routing logic, coverage and workload |
| First action | Did owners act inside the company’s chosen policy? | Alerts, staffing and acknowledgement |
| Contact | Which records reached two-way contact? | Contact data, channel policy and follow-through |
| Qualification | Which contacted records met the written criteria? | Accepted scope and question discipline |
| Next step | Which suitable projects moved to the defined next stage? | Handoff completeness and capacity |
| Outcome | Which appointments held, proposals issued, work sold or revenue collected? | Scheduling, estimating, sales and attribution |
| Exceptions | Which reason codes repeated or stayed unresolved? | Source fit, routing, training or policy gap |
Do not compress these rows into one conversion percentage. Delivery, first action, contact, qualification, scheduling and sales performance have different owners. A weak final result does not identify the broken stage by itself.
Carry source cost through the same stable outcome definitions using the cost-per-booked-job guide. Keep the operational review focused on the stage that needs repair, then assign one process change to one owner and record when the team will check it again.
Copy this contractor lead handling process
Complete this template with your team. Replace every bracketed item; a blank is an unresolved operating decision.
| SOP field | Contractor decision |
|---|---|
| System of record | [Name the only place where current state and next action are authoritative] |
| Covered sources | [List providers, forms, calls and referral channels governed by this SOP] |
| Staffed coverage | [Write the days, hours and after-hours treatment] |
| Accepted work | [Write trade, residential scope, service area, material exclusions and capacity limits] |
| Receipt event | [Define the event and timestamp that begin your response clock] |
| Primary owner rule | [Name the person or routing condition] |
| Backup rule | [Name the shift, person or trigger that takes ownership] |
| Allowed open states | [List the states and entry/exit rules] |
| Next-action rule | [Require action, owner and due time on every open record] |
| Overdue rule | [Define the company target and the escalation owner] |
| Contact policy | [Reference the approved channels, consent evidence, cadence and stop rules] |
| Qualification owner | [Name the role that applies the written project criteria] |
| Handoff acceptance | [List the fields the receiver must see before accepting ownership] |
| Exception queues | [List unassigned, overdue, duplicate, unclear, out-of-scope and stop-contact paths] |
| Final dispositions | [List permitted close reasons and their evidence requirements] |
| Daily audit owner | [Name the role that clears operational exceptions] |
| Weekly review owner | [Name the role that reviews stage movement and process defects] |
| Change control | [Name who may change states, definitions, targets and reason codes] |
Test the SOP with records that exercise the normal path and each exception path. Confirm that an employee who did not handle the prior action can still identify the current truth and next responsibility. When the process changes, update the controlled template before asking staff to follow the new rule.
The home-improvement trade directory shows the residential categories theBuildd serves generally. Exact availability still depends on agreed trade and ZIP coverage.
Apply the SOP to a theBuildd lead
theBuildd sends opted-in homeowner leads by text and email within 10 minutes. That is the delivery event. Your contractor lead handling process should then confirm receipt, create or update the record, assign one owner and begin the contractor’s approved qualification and follow-through process.
| Stage | theBuildd’s stated role | Contractor-owned control |
|---|---|---|
| Source and delivery | Supply the residential opt-in under agreed trade and ZIP coverage; send it by text and email within 10 minutes | Monitor delivery channels and preserve the receipt timestamp |
| Distribution | There is one buyer per lead through theBuildd. The homeowner may still seek other quotes independently. | Do not describe distribution as a promise that no one else can compete |
| Qualification | No provider-run qualification is promised | Make the qualifying call and apply written criteria |
| Lead fields | Only use the fields actually supplied and agreed | Preserve unknowns; do not assume condition, budget, authority or project fit |
| Follow-through | No outcome is guaranteed | Own next actions, handoffs, scheduling, estimating and disposition |
| Remedy | Replace, rather than refund, bad leads that meet the replacement criteria | Preserve the evidence required by the agreed terms |
The current plans are month to month, with 10 days’ written notice before the next billing date. Results are not guaranteed. Review theBuildd’s current pricing and terms before treating any offer detail as fixed.
Bring the SOP before you add lead volume
Share your trade, ZIP codes, lead owner and qualification process. We will confirm whether theBuildd’s current one-buyer lead model fits that workflow.