Local services

Field Service Dispatcher

Scheduling, route optimization, a technician mobile app, and invoicing for residential service trades — one workflow from first call to paid.

Full planning bundle — BRAND, MRD, BRD, PRD, DESIGN
Branded styleguide — typography, color, components
4 previewable mockups

Cloning copies the full plan into a new project you own — edit it freely.

Inside the bundle

Styleguide and mockups

A look at the brand palette and screen-level mockups that ship with this plan. Cloning copies all of them into your project.

Mockups

Style guide

Styleguide

What this blueprint gives you

The operational spine of a residential service business — HVAC, plumbing, electrical, garage door, pest. Customers book or call in, the dispatcher fills the board and optimizes the route, the tech sees the day on their phone with directions and parts, and the invoice goes out before they leave the driveway.

Five planning documents (BRAND, MRD, BRD, PRD, DESIGN) at senior-team depth covering the dispatch board, the mobile tech app, routing, pricebook, and accounts-receivable. Built around the reality that truck rolls cost money and same-day rescheduling is the norm.

Planning documents

Preview the plan

Each blueprint includes the senior-level planning files. These cards show the opening text before you clone the full bundle.

Brand Guidelines Document

BRAND.md

Preview

BRAND — Field Service Dispatcher One line The dispatch board, the tech's phone, and the invoice — one tool, one workflow, one paid call. Who it speaks to Owners and dispatchers at residential service companies running 2 to 40 trucks: HVAC, plumbing, electrical, garage door, pest, appliance repair. People who answer the phone at 7am, juggle a whiteboard at 9, send a tech across town at 11, and want to be paid by 4. They've outgrown a paper calendar and aren't going to learn enterprise software. V

Design Specification Document

DESIGN.md

Preview

DESIGN — Field Service Dispatcher Information architecture Office app (desktop first): Dispatch (today, week), Bookings inbox, Customers, Pricebook, Invoices & AR, Reports, Settings (shop, techs, service area, integrations). The truck (mobile first): Today (ordered route), Job (details, checklist, photos, quote, payment), Customer (history), Messages, Time. Customer portal (lightweight): Upcoming, History, Invoices & pay, Reschedule. Key screens & layout Dispatch board: the heart of the product.

Market Requirements Document

MRD.md

Preview

MRD — Field Service Dispatcher The problem A residential service shop runs on a whiteboard, three group texts, a fuel app, a paper invoice book, and one harried dispatcher who knows everything. Jobs miss. Techs drive across the city twice. Parts are forgotten. Invoices land in the customer's inbox three days later, half of them never get paid, and the owner finds out about the unhappy customer from a Google review on Saturday morning. The work breaks into four moments — booking, dispatch, on sit

Business Requirements Document

BRD.md

Preview

BRD — Field Service Dispatcher Business outcomes 1. Revenue per truck day. The compounding KPI. Tighter routing + on site invoicing + fewer callbacks = more billable hours per shift. 2. Days sales outstanding. Same day payment is the goal. Tools that don't move DSO down aren't earning their seat. 3. Dispatcher leverage. Trucks managed per dispatcher. The product justifies itself when one dispatcher can comfortably run 8–12 trucks on a heavy day. 4. Tech retention & adoption. Closeouts done on th

Product Requirements Document

PRD.md

Preview

PRD — Field Service Dispatcher Phase 0 — Shop, people, and the pricebook Auth + roles: owner , dispatcher , technician , office (AR/billing). Shop setup: business hours, service area (zip codes or polygons), trades enabled, tax jurisdictions. People: techs (skills, certifications, working hours, home base), dispatchers. Customers and properties: a customer can have multiple properties; each property has its own equipment history. Pricebook v1: categories (Diagnostic, Repair, Install, PM), line i