Home Services & Contractors — full operating guide

Speaking the language of this industry

• Dispatch — assigning and routing a technician or crew to a scheduled job based on skill, location, certification, and availability
• Change order — a documented adjustment to a job's scope, price, or materials discovered after the original estimate was approved
• Truck roll — any trip a technician makes to a job site, the cost driver every contractor tries to minimize per completed job
• First-visit completion — a job resolved fully on the initial visit, with no return trip or callback required
• Callback — a return visit for the same problem on the same job, distinct from a new sale or a maintenance-agreement visit
• Maintenance agreement — a recurring service contract (seasonal HVAC tune-ups, quarterly pest treatments) with its own schedule and renewal date
• Job costing — matching actual labor, material, and change-order cost against the priced estimate to determine real margin on a specific job
• Crew lead — the technician responsible for a multi-person crew on a job, the point of contact between the field and dispatch
• Punch list — the remaining items to complete or correct before a customer or general contractor signs off on finished work
• Draw / progress billing — invoicing tied to project milestones rather than a single final invoice, common on general-contracting jobs
• Toolbox talk — a documented pre-job safety briefing, required for OSHA compliance on many crews and often audited after an incident

Information The Forge tracks

• Job — the central record: customer, property, scope, schedule, assigned crew, documentation, change orders, and invoice for one piece of work
• Estimate — a priced proposal tied to a job before it is approved, with its own aging, follow-up status, and close outcome
• Crew — a group of technicians (often with a crew lead) assigned together to jobs, tracked as a unit for scheduling and profitability
• Technician — an individual field employee with skills, certifications, license expirations, and a personal schedule and time log
• Change order — a scope or price adjustment raised against an in-progress job, requiring acknowledgment before it reaches billing
• Invoice — the billing record generated from a completed job, including any approved change orders, tracked through payment and reconciliation
• Maintenance agreement — a recurring-service contract tied to a property and a schedule, with its own renewal date and covered equipment
• Property / site — the physical location where work happens, carrying its own service history independent of who currently occupies it

The full process, start to finish

• Lead — inbound call, form, or referral creates a customer record
• Qualification — need, location, urgency, and service type are confirmed
• Site visit — a tech or estimator visits to assess scope and conditions
• Estimate — pricing, materials, and labor are scoped and sent to the customer
• Follow-up — automated follow-up runs until the estimate is accepted, declined, or expired
• Approval — customer approves and the estimate converts to a scheduled job
• Scheduling — the job is placed on the calendar with the right crew and materials
• Dispatch — the assigned crew receives the job details, address, and any special instructions
• Service — work is performed, hours are logged, and documentation is captured in the field
• Documentation — photos, forms, permits, and customer signatures attach to the job record
• Change order — any scope change is documented, priced, acknowledged, and pushed to billing
• Billing — the completed job, including change orders, generates an invoice
• Payment — payment is collected and reconciled against the job
• Review — a review request is sent to the customer after completion
• Recurring service — maintenance agreements and repeat schedules are set and tracked for renewal

Other places this industry loses time and margin

Beyond the four themes covered on the main industry page (missed calls, estimate follow-up, dispatch, job-to-invoice/labor visibility), these show up often enough to plan for.

• Job-site photos, forms, and signatures go missing — field documentation attaches to the job record from any device instead of living only on a phone or in a text thread
• Multiple locations each run a different process — one operating blueprint standardizes intake, dispatch, and documentation while keeping per-location visibility
• Customer communication drops between roles — anyone in the office can see the full job history, last tech note, and outstanding invoice when a customer calls
• Recurring service agreements expire without renewal — maintenance schedules trigger renewal workflows before they lapse

What changes for every role

• Owner — company-wide dashboard with revenue, margin, and labor cost by location; lead-source ROI; overtime exposure and crew profitability in real time; open-estimate aging; review rate and rating trend
• Operations Manager — completion rate and first-visit resolution by crew; scheduling conflicts and unassigned jobs; jobs missing documentation; escalation queue; weekly KPI summary generated automatically
• Dispatcher — dispatch board with crew availability, skills, and location; job queue with certifications flagged; real-time job status; drag-and-drop rescheduling with automatic notification (full depth: /home-services/dispatch)
• Estimator — personal estimate pipeline with age, value, and follow-up status; site-visit notes and photos; close ratio and average close time; one-click conversion to a scheduled job (full depth: /home-services/estimate-follow-up)
• Technician — daily job list with address, scope, and customer history; photo and form capture attached to the job; change-order submission from the field; time logging tied to the job (full depth: /home-services/job-costing)
• Office Administrator — inbound call log with follow-up history; full customer record on ring; invoice generation from completed jobs; aging receivables and payment status

Who can see and do what

• Owner — sees company-wide revenue, margin, and labor cost across every location; can edit pricing and tier configuration; sees every job, estimate, and invoice; can view individual pay records
• Operations Manager — sees completion rates, documentation compliance, and KPI reporting across assigned crews; can reassign jobs within their scope; cannot edit company-wide pricing or view aggregate payroll unless separately granted
• Dispatcher — sees crew schedules and certification flags; can reschedule and reassign jobs; cannot see job pricing, margin, or customer payment status; cannot edit a completed job record
• Estimator — sees their own estimate pipeline, team-wide only if granted; can build, price, and send estimates; cannot see technician labor cost or company-wide reporting; change orders above a set value require manager approval
• Technician — sees only jobs assigned to them; can submit photos, forms, change orders, and time; cannot see other technicians' schedules, pay rates, or company-wide reporting
• Office Administrator — sees full customer records, invoicing, and payment status; can generate and send invoices; cannot edit pricing or view payroll unless separately granted; dispatch-board editing rights are granted separately

What this industry has to stay ahead of

• Trade licensing and certification expiration tracked per technician (electrical, plumbing, HVAC)
• OSHA safety documentation and toolbox-talk records for field crews
• Workers'-compensation classification by labor type and job class
• Permit and inspection deadline compliance tracked per job, not per memory
• EPA refrigerant-handling compliance and technician certification for HVAC work
• Backflow-testing and cross-connection compliance documentation for plumbing work
• Lien-waiver documentation for general-contracting and subcontractor work
• Local business-licensing renewal tracking across multiple operating locations

Runs without anyone remembering to do it

• Maintenance-agreement renewal trigger — a maintenance agreement approaching expiration starts the renewal workflow and pre-schedules the next service
• Review-request auto-send on completion — marking a job complete automatically sends a review request instead of relying on someone to remember
• License and certification expiration reminder — an expiring license or certification notifies the office and restricts dispatch once it lapses

What a typical view looks like

• Owner Daily Ops Dashboard — lead response time, open estimate value, overtime exposure, jobs completed yesterday, crew profitability trend
• Dispatch Board — crew availability and location, jobs requiring certification match, unassigned jobs, real-time job status
• Crew Profitability Report — revenue by crew, labor cost by crew, job gross margin, first-visit completion rate by crew
• Overtime Exposure Monitor — overtime hours accumulating, overtime cost by employee and location, scheduled versus recorded hours
• Estimate Pipeline Board — open estimate count and value, estimate age, follow-up status, close rate by estimator

What may be replaced, and what stays (full list)

• May be replaced — standalone scheduling and dispatch apps, a separate CRM used only for leads, lead- and estimate-tracking spreadsheets, manual reminder and follow-up systems, disconnected field-photo and form apps, per-crew time-tracking files, text-message threads used as dispatch communication
• Stays connected — your accounting platform, your payroll provider, your phone system or call-tracking service, payment processing, advertising platforms and lead sources, estimating and takeoff tools you already use

Why not something else?

A CRM tracks the lead. It does not dispatch the crew, capture field documentation, tie technician hours to the job, push a change order to billing, or show crew profitability. Contractors don't have a sales problem — they have an operations problem that starts at the sale and runs through payment.

• Why not separate apps — a call-tracking app, a scheduling app, a field-documentation app, a timesheet app, and accounting software can each run fine alone, but the job exists in none of them completely and all of them partially; every handoff is a place a change order gets lost or labor time detaches from the job
• Why not an industry-specific field-service platform — those are strong in the middle of the job (dispatch, work orders) and weak at the edges: lead capture, estimate follow-up, labor-cost visibility, customer communication, and recurring-service renewal

What a typical launch looks like

• Discovery & data migration (3-5 days) — customer records, job history, and open estimates migrate in; crews, locations, and technician licenses/certifications are set up
• Workflow & permissions configuration (4-6 days) — dispatch rules, estimate follow-up cadences, change-order routing, and role-based permissions are configured to match how the business runs
• Integration connections (2-4 days) — accounting, payroll, phone/call-tracking, and payment-processing connections are established and validated
• Testing, training & go-live (3-5 days) — office staff, dispatchers, and field technicians train on their day-to-day screens before a coordinated cutover

Where this typically goes next

• Add a second operating location on the same blueprint, with per-location visibility preserved
• Move to Forge Operations for cross-location executive reporting once multiple locations or entities are running
• Add a subindustry-specific workflow set — HVAC, plumbing, electrical, roofing, or general-contracting — as the business specializes
• Scale maintenance-agreement automation as recurring-service revenue becomes a larger share of the business
• Layer in marketplace add-ons — additional locations, advanced reporting, priority support — as headcount and complexity grow
• Add a second business entity under the same account if the company expands into a related trade or market

Additional questions

• Can it handle multiple crews and locations? — Yes. One operating blueprint standardizes intake, dispatch, and reporting across crews and locations while preserving per-location visibility into revenue, labor, and completion.
• Does it keep my accounting and payroll systems? — Yes. The Forge integrates with your accounting and payroll providers rather than forcing you to replace them.
• What happens to our existing customer and job data? — Customer records, job history, and contact data migrate into The Forge during onboarding, for one complete customer record rather than a second system running alongside your current one.
• Does it work for companies that do both residential and commercial work? — Yes. Job records carry their own scope, pricing, billing terms, and documentation requirements, with separate reporting rollups if you need them.
• How long does it take to get running? — Most home-services companies are operational in two to four weeks: data migration, workflow configuration, crew/location setup, integration connections, then training.
• Can it handle maintenance agreements and recurring service schedules? — Yes. Maintenance agreements track covered equipment, service schedules, and renewal dates, with pre-scheduled upcoming services and a renewal workflow that starts before the agreement expires.