# CoolRoute Command statement of work package

A buyer-signable SOW packet for turning HVAC Dispatch into a paid, rebrandable hvac dispatch software for same-day service boards and technician routing pilot with scoped deliverables, acceptance gates, data responsibilities, support terms, change controls, and signature ownership.

Buyer default: Evergreen Mechanical
Recommended tier: Dispatch board pilot
Investment summary: $24k-$42k setup and $1.2k-$4k/month recurring. 45 percent due at signature for territory setup, job import mapping, and dispatcher workflow design.
Target launch window: Weeks 2-6; 1 week job import, 2 weeks board and notification workflow, 2 weeks same-day dispatch pilot.
SOW term: 5-week dispatch overlay pilot for one dispatch team, daily job import, technician roster, and prepare-only ETA workflow.
Production domain: hvac-dispatch.ideas-realized.com
Preview URL: https://hvac-dispatch.ideas-realized.com
JSON manifest: /demo-library/hvac-dispatch/statement-of-work.json

## Agreement Snapshot

- Product: CoolRoute Command
- Buyer: Evergreen Mechanical
- First proof screen: route
- First proof URL: https://hvac-dispatch.ideas-realized.com?screen=route

## Scope Modules

- Tenant setup: Dispatch command workspace. Scope: Configure service zones, technician roles, priority labels, dispatch stages, subdomain, and brand tokens. Acceptance: Dispatch board and route panel show technician load and sequence changes.
- Data onboarding: Jobs, technicians, routes, and parts blockers. Scope: Map field-service export, technician capacity, route order, customer risk, and parts hold data. Acceptance: Message queue data is present; SMS provider not selected.
- Workflow configuration: Assignment and ETA preparation. Scope: Configure urgent-job escalation, ETA message prep, parts hold route blocks, and daily dispatch review. Acceptance: Parts hold workflow shows ETA, risk, and owner.
- Pilot review: Dispatch performance and writeback decision. Scope: Deliver assignment report, ETA readiness summary, parts blocker list, and field-service writeback recommendation. Acceptance: Surface parts holds and customer-risk blockers in the app and export report.

## Delivery Milestones

- Kickoff (Week 1, Dispatch manager): Job import, technician roster, and message policy are approved. Exit: Daily job import template and technician skill map are accepted. Payment: 45 percent due at signature for territory setup, job import mapping, and dispatcher workflow design.
- Configuration (Weeks 2-3, Implementation lead): Board, assignment logic, ETA templates, and blocker rules are configured. Exit: Dispatcher can assign sample jobs and prepare ETA messages. Payment: 35 percent due after dispatch board, route sequence, and customer ETA queue pass live review.
- Pilot (Weeks 4-5, Dispatcher): Team uses the board for live schedule review and blocker triage. Exit: Assignment clarity, ETA readiness, and parts blocker report are accepted. Payment: 20 percent due after parts-hold report, dispatcher acceptance notes, and expansion plan are delivered.

## Acceptance Criteria

- Daily job import shows all unassigned urgent jobs and technician capacity.
- Dispatcher can assign at least 12 jobs and review route/order changes.
- ETA messages remain prepare-only unless client approves send workflow.
- Parts holds and customer-risk blockers appear in the board and export report.
- Territory and schedule accepted: Pilot territory, technician roster, skill tags, and schedule windows validated.
- Customer message copy approved: ETA, delay, and parts-hold templates approved with opt-out/compliance notes.
- Dispatcher workflow accepted: Dispatcher completes reschedule, route review, and parts-hold scenarios in the pilot workspace.

## Buyer Responsibilities

- Provide daily job export and technician roster before configuration starts.
- Approve customer message language before any send workflow is considered.
- Assign one dispatch lead to validate board behavior and field-service handoff.
- Daily job export with customer, address, priority, service type, window, status, and assignment fields.
- Technician roster with skills, service zones, availability, and current dispatch policy.
- Approved ETA message language and customer communication policy.
- Parts hold categories, escalation thresholds, and dispatch owner assigned.

## Ideas Realized Responsibilities

- Owns configuration, runbook, QA evidence, and post-pilot backlog recommendation.
- A buyer-ready support model for launching HVAC Dispatch with triaged tickets, service levels, training artifacts, success milestones, and renewal proof tied to the first pilot cohort.
- Dispatch launch thread: Business days during pilot
- Maintain the demo-derived production domain plan for hvac-dispatch.ideas-realized.com.

## Data And Security Responsibilities

### Buyer operations owner

- Start with a read-only job and technician import, reconcile service categories, then allow dispatchers to update pilot board status while the source platform remains system of record.
- Service jobs export: provide 40 to 160 open jobs from ServiceTitan, Housecall Pro, FieldEdge, or CSV schedule export with [object Object], [object Object], [object Object], [object Object].
- Technician roster: provide 8 to 60 technician records from Field-service platform or HR roster export with [object Object], [object Object], [object Object].
- Parts holds: provide 10 to 80 parts-held job rows from Inventory hold list or parts counter spreadsheet with [object Object], [object Object], [object Object].

### Ideas Realized implementation lead

- The first pilot can sit beside the field-service platform. Import jobs and technician capacity, then use the board to expose assignment risk, parts blockers, and ETA message readiness.
- Job ID system-of-record rule: Dispatch updates must map back to the source service job record. Resolution: Confirm external job ID and export ownership before pilot launch.
- Technician capacity review: Missing skills or home zones weakens route and assignment signals. Resolution: Service manager approves skill and zone taxonomy during setup.
- Customer messaging consent: ETA message templates require approved phone/email usage rules. Resolution: Limit message previews until communication policy is confirmed.

## Support And Service Levels

- Dispatch launch thread: Business days during pilot; response Same or next business day for schedule-blocking issues. Included: Import triage, board tuning, message template review, and parts blocker workflow changes.
- Weekly dispatch review: One 45-minute session per week; response Scheduled. Included: Assignment review, ETA readiness review, blocker report, and writeback scope decision.

## Change Orders And Exclusions

- Change control: Live SMS/email sending or customer communication automation: Requires sender approval, compliance review, and separate messaging implementation. Owner: Client sponsor.
- Change control: Two-way field-service writeback, invoices, or technician mobile app: Quote as a follow-on integration or module after daily board pilot acceptance. Owner: Implementation lead.
- Exclusion: No live customer SMS without approved consent language and sender setup.
- Exclusion: No field-service-system writeback unless the integration add-on is signed.
- Exclusion: Route optimization remains dispatcher-assisted in the base pilot, not autonomous dispatching.
- Exclusion: Do not promise autonomous route optimization as part of the base pilot.
- Exclusion: Do not send live SMS from the app until consent and sender setup are approved.
- Exclusion: Do not commit to FSM writeback before API and field-ownership review.

## Legal Review Notes

- This demo SOW package is a sales and implementation planning artifact, not legal advice.
- Final MSA, DPA, payment terms, taxes, procurement language, and security addenda require buyer/legal review before signature.
- No regulated production data should be loaded until data-processing, access, retention, and incident-response terms are approved.

## Signature Blocks

- Client sponsor: Approves budget, pilot scope, and launch decision.
- Buyer operations owner: Provides source data, validates workflow language, and accepts launch criteria.
- Ideas Realized implementation lead: Owns configuration, runbook, QA evidence, and post-pilot backlog recommendation.

## Implementation Handoff Links

- Deal desk package: /demo-library/hvac-dispatch/deal-desk
- Deal desk package JSON: /demo-library/hvac-dispatch/deal-desk.json
- Procurement pack: /demo-library/hvac-dispatch/procurement-pack
- Client proposal: /demo-library/hvac-dispatch/client-proposal
- Client launch plan JSON: /demo-library/hvac-dispatch/client-launch-plan.json
- Implementation work order: /demo-library/hvac-dispatch/implementation-work-order
- Deployment launch plan JSON: /demo-library/hvac-dispatch/deployment-launch.json
- Production data contract JSON: /demo-library/hvac-dispatch/data-contract.json
- Tenant seed package JSON: /demo-library/hvac-dispatch/tenant-seed-package.json
- Buyer launch room: /demo-library/hvac-dispatch/launch-room