# CoolRoute Command tenant cutover plan A buyer-and-implementation cutover packet for moving HVAC Dispatch from polished demo to branded live tenant: commercial approval, domain, data dry-run, access, automation, release gates, rollback, support, and SEO/AEO publication. Product: CoolRoute Command Tenant: Evergreen Mechanical Preview URL: https://hvac-dispatch.ideas-realized.com?screen=route Preview screen: Route (route) - dispatch route board and technician schedule proof Production domain: hvac-dispatch.ideas-realized.com Launch window: Medium-high Cutover score: 72/100 Cutover decision: Ready for buyer input on tenant brand and production domain. Next cutover move: Client confirms launch name, brand tokens, CNAME/TXT ownership, and fallback preview URL https://hvac-dispatch.ideas-realized.com. Primary owner: Dispatch launch thread JSON manifest: /demo-library/hvac-dispatch/tenant-cutover-plan.json ## Cutover Phases ### 1. Commercial signoff Owner: Client sponsor Timing: Before kickoff Status: Implementation Confirm the buyer wants this demo rebranded as a paid tenant and accepts the commercial boundaries. Entry criteria: - Buyer has reviewed the live app proof route. - Recommended offer, setup range, and recurring range are understood. Exit criteria: - Order packet approved. - SOW and rebrand rights accepted. - Implementation kickoff can be scheduled. Assets: - Client launch plan: /demo-library/hvac-dispatch/client-launch-plan - Buyer-facing launch plan with order, data, SEO/AEO, and support steps. - Statement of work: /demo-library/hvac-dispatch/statement-of-work - Buyer-signable scope, milestones, responsibilities, service levels, and change controls. - Statement of work JSON: /demo-library/hvac-dispatch/statement-of-work.json - Machine-readable scope and acceptance manifest. - Deal desk package: /demo-library/hvac-dispatch/deal-desk - Order form, pricing bands, approval gates, add-ons, and redlines. - Deal desk JSON: /demo-library/hvac-dispatch/deal-desk.json - Machine-readable commercial close manifest. ### 2. Tenant identity and domain Owner: Implementation lead Timing: Kickoff day 1 Status: Buyer input Swap the demo identity into the buyer tenant, confirm DNS, and preserve the preview fallback. Entry criteria: - Client name, logo, colors, and launch domain are available. Exit criteria: - Production domain is confirmed. - Tenant seed package references the buyer identity. Assets: - White-label kit: /demo-library/hvac-dispatch/white-label-kit - Naming, domain, terminology swaps, copy blocks, brand assets, and checklist. - White-label kit JSON: /demo-library/hvac-dispatch/white-label-kit.json - Machine-readable rebrand manifest. - Tenant clone package: /demo-library/hvac-dispatch/tenant-clone-package - Rebrand-and-launch handoff for a buyer tenant. - Tenant clone JSON: /demo-library/hvac-dispatch/tenant-clone-package.json - Machine-readable tenant clone package. - Tenant seed package: /demo-library/hvac-dispatch/tenant-seed-package - Users, roles, data sources, integrations, feature flags, automations, and notifications. - Tenant seed JSON: /demo-library/hvac-dispatch/tenant-seed-package.json - Machine-readable tenant seed manifest. ### 3. Data dry-run and tenant seed Owner: Dispatch manager Timing: Kickoff days 1-2 Status: Buyer input 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. Entry criteria: - Source exports and sample CSV templates are available. Exit criteria: - Dry-run import passes validation. - Required source fields and tenant boundaries are accepted. Assets: - Sample data package: /demo-library/hvac-dispatch/sample-data-package - CSV templates, sample rows, and import validation gates. - Sample data JSON: /demo-library/hvac-dispatch/sample-data-package.json - Machine-readable data dry-run manifest. - Production data contract: /demo-library/hvac-dispatch/data-contract - Entities, source systems, events, boundaries, and API-shaped routes. - Production data contract JSON: /demo-library/hvac-dispatch/data-contract.json - Machine-readable production data contract. ### 4. Access, roles, and automations Owner: Product lead Timing: Kickoff days 2-4 Status: Buyer input Confirm buyer seats, permissions, integration credentials, notification owners, and disabled-by-default automation rules. Entry criteria: - Named users and roles are available. - Required credentials and sender identities have owners. Exit criteria: - Access checks pass. - Automation fallbacks have owners. - No buyer-facing automation fires without signoff. Assets: - Sample data package: /demo-library/hvac-dispatch/sample-data-package - CSV templates, sample rows, and import validation gates. - Sample data JSON: /demo-library/hvac-dispatch/sample-data-package.json - Machine-readable data dry-run manifest. - Production data contract: /demo-library/hvac-dispatch/data-contract - Entities, source systems, events, boundaries, and API-shaped routes. - Production data contract JSON: /demo-library/hvac-dispatch/data-contract.json - Machine-readable production data contract. - White-label kit: /demo-library/hvac-dispatch/white-label-kit - Naming, domain, terminology swaps, copy blocks, brand assets, and checklist. - White-label kit JSON: /demo-library/hvac-dispatch/white-label-kit.json - Machine-readable rebrand manifest. ### 5. Release, monitoring, and support Owner: Dispatch launch thread Timing: Go-live day Status: Implementation A production handoff plan for taking HVAC Dispatch from sales preview to a client-owned launch domain with Netlify hosting, environment gates, monitoring, rollback, and canonical SEO/AEO checks. Entry criteria: - Release gates are reviewed. - Support owner is assigned. - Monitoring thresholds are documented. Exit criteria: - Production route is promoted. - Monitoring is active. - Support and rollback owners are known. Assets: - Live sales preview: https://hvac-dispatch.ideas-realized.com?screen=route - First proof screen: Route. - Canonical landing page: /demo-library/hvac-dispatch - Indexable buyer proof page and primary demo-library route. - White-label kit: /demo-library/hvac-dispatch/white-label-kit - Naming, domain, terminology swaps, copy blocks, brand assets, and checklist. - White-label kit JSON: /demo-library/hvac-dispatch/white-label-kit.json - Machine-readable rebrand manifest. - Tenant clone package: /demo-library/hvac-dispatch/tenant-clone-package - Rebrand-and-launch handoff for a buyer tenant. - Tenant clone JSON: /demo-library/hvac-dispatch/tenant-clone-package.json - Machine-readable tenant clone package. ### 6. SEO/AEO publication Owner: Growth lead Timing: Go-live week Status: Implementation A publish-ready growth kit for using the HVAC Dispatch demo as an industry pillar, answer-engine proof source, comparison asset, and sales-qualified routing path. Entry criteria: - Buyer proof claim is approved. - Canonical and industry routes are available. Exit criteria: - Industry pillar, answer blocks, and internal links route demand back to the demo proof. Assets: - Canonical landing page: /demo-library/hvac-dispatch - Indexable buyer proof page and primary demo-library route. - Industry SEO/AEO page: /industries/hvac-dispatch-software - HVAC dispatch software ## Acceptance Gates ### 1. Commercial order and SOW approval Phase: commercial-signoff Owner: Client sponsor Timing: Before kickoff Status: Implementation Source: Commercial Proof: Order packet, SOW, and rebrand rights point to CoolRoute Command as the client launch product. Acceptance criteria: Sponsor accepts scope, $28k-$55k pilot build, then $1.5k-$5k/month for hosting, support, messaging, and service-platform handoff work, launch boundaries, and payment milestone. Rollback: Hold tenant setup and keep the app as sales-preview only until pricing or scope redlines are resolved. ### 2. Tenant brand and production domain Phase: tenant-identity Owner: Client DNS owner Timing: Kickoff day 1 Status: Buyer input Source: Brand and domain Proof: Evergreen Mechanical is seeded for hvac-dispatch.ideas-realized.com; 3 DNS records are tracked. Acceptance criteria: Client confirms launch name, brand tokens, CNAME/TXT ownership, and fallback preview URL https://hvac-dispatch.ideas-realized.com. Rollback: Keep traffic on https://hvac-dispatch.ideas-realized.com and delay production alias activation until DNS checks pass. ### 3. Source data dry-run Phase: data-cutover Owner: Dispatch manager Timing: Kickoff days 1-2 Status: Buyer input Source: Data import Proof: 3 source groups and 3 tenant seed sources are mapped. Acceptance criteria: Confirm external job ID and export ownership before pilot launch. Rollback: Use seed data and read-only import review until source exports satisfy required fields and validation gates. ### 4. Access roles and permission boundaries Phase: access-automation Owner: Implementation lead Timing: Kickoff days 2-3 Status: Implementation Source: Access control Proof: 3 roles, 3 scopes, and 3 launch permission groups are documented. Acceptance criteria: Technician role is scoped to assigned work and mobile status updates. Rollback: Revert affected users to internal-only review access and disable buyer-facing invitations until roles are corrected. ### 5. Automation and integration readiness Phase: access-automation Owner: Product lead Timing: Kickoff days 3-4 Status: Buyer input Source: Integrations Proof: 4 integrations, 3 automations, and 2 notifications are in the tenant seed package. Acceptance criteria: Credentials, sender identities, fallback owners, and disabled-by-default automations are confirmed before live users enter. Rollback: Disable automation rules, keep manual queue ownership, and preserve audit entries for replay after credentials are repaired. ### 6. Release gates and first proof screen Phase: go-live-release Owner: Dispatcher Timing: Go-live day Status: Implementation Source: Deployment Proof: 5 release gates protect Route: dispatch route board and technician schedule proof Acceptance criteria: Dispatch board and route panel show technician load and sequence changes. Rollback: Keep the sales preview subdomain live until the client production domain passes route, SSL, auth, and acceptance checks. ### 7. Monitoring and support handoff Phase: go-live-release Owner: Dispatch launch thread Timing: Go-live day + 1 Status: Ready Source: Support Proof: 3 monitors and 2 support levels are defined. Acceptance criteria: Dispatch launch thread: Business days during pilot. Renewal signal: Dispatch scheduling inquiry: 2 qualified HVAC service inquiries per quarter. Rollback: Pilot support scope: $1.2k-$4k/month recurring for hosting, support, and workflow tuning. ### 8. SEO/AEO publication and internal links Phase: seo-aeo-launch Owner: Growth lead Timing: Go-live week Status: Implementation Source: SEO/AEO Proof: /industries/hvac-dispatch-software anchors 3 launch-calendar entries and 3 answer blocks. Acceptance criteria: Canonical page /demo-library/hvac-dispatch, industry page /industries/hvac-dispatch-software, and app proof URL are internally linked with buyer-ready CTA language. Rollback: Noindex unfinished support pages, preserve the canonical landing page, and republish after the buyer proof claim is verified. ## Rollback Controls ### DNS promotion rollback Trigger: Production domain fails verification, SSL, or route rewrite checks. Owner: Client DNS owner Response: Keep the sales preview subdomain live until the client production domain passes route, SSL, auth, and acceptance checks. Evidence: hvac-dispatch.ideas-realized.com: ready; hvac-dispatch.ideas-realized.com: needs-client; _netlify.hvac-dispatch.ideas-realized.com: needs-client ### Data import rollback Trigger: Required field validation, duplicate detection, or record counts fail during dry-run. Owner: Dispatch manager Response: Keep tenant in seed-data mode and rerun the import after source mapping changes are approved. Evidence: Job ID system-of-record rule: blocking; Technician capacity review: warning; Customer messaging consent: blocking ### Automation rollback Trigger: Notification, escalation, integration, or automation action sends to the wrong owner or channel. Owner: Product lead Response: Disable automation rules, keep manual workflow ownership, and replay audit events after correction. Evidence: Unassigned urgent job alert: ready; ETA message preparation: needs-client; Parts hold route block: template ### SEO/AEO claim rollback Trigger: Buyer proof, KPI claim, or industry language is not yet approved for public publication. Owner: Growth lead Response: Noindex unfinished support routes and keep only the canonical demo page published until claims are approved. Evidence: HVAC dispatch scheduling software for same-day service teams: Service + SoftwareApplication + FAQPage; HVAC parts hold workflow for dispatch teams: Article + HowTo/FAQPage; HVAC dispatch board vs field service software customization: Article + FAQPage ## Buyer Signoff - Approve commercial order, SOW, rebrand rights, and first payment milestone for CoolRoute Command. - Confirm production domain hvac-dispatch.ideas-realized.com, buyer sponsor, launch window, and support owner. - Provide source exports for Service jobs export, Technician roster, Parts holds and approve import validation results. - Approve role matrix for Dispatcher, Technician, Service manager before inviting live users. - Approve public proof language for /industries/hvac-dispatch-software and /demo-library/hvac-dispatch. ## Implementation Handoff - Seed tenant package: /demo-library/hvac-dispatch/tenant-seed-package and /demo-library/hvac-dispatch/tenant-seed-package.json. - Data contract: /demo-library/hvac-dispatch/data-contract and /demo-library/hvac-dispatch/data-contract.json. - First proof screen: Route at https://hvac-dispatch.ideas-realized.com?screen=route. - Monitoring: Demo app availability under Homepage and app route return 200 from production domain after DNS cutover.; Urgent jobs assigned with approved ETA or parts status before service window risk under Pilot usage is visible in the buyer dashboard within the first review cycle.; Confirm scheduling source of truth and technician calendar rules. under No open launch blocker can affect first user workflow.. - North-star analytics: Urgent jobs assigned with approved ETA or parts status before service window risk; instrumentation phase: Instrument dispatch landing CTA, app preview, job search, reassignment, ETA draft approval, parts hold review, route view, and spec download.. ## SEO/AEO Publication - Canonical page: /demo-library/hvac-dispatch - Industry page: /industries/hvac-dispatch-software - HVAC dispatch scheduling software for same-day service teams: /industries/hvac-dispatch-scheduling-software - HVAC parts hold workflow for dispatch teams: /resources/hvac-parts-hold-workflow - HVAC dispatch board vs field service software customization: /compare/hvac-dispatch-board-vs-field-service-customization - CoolRoute Command canonical demo: /demo-library/hvac-dispatch - CoolRoute Command app-only preview: https://hvac-dispatch.ideas-realized.com - HVAC Dispatch demo: /demo-library/hvac-dispatch ## Route Map - Live sales preview: https://hvac-dispatch.ideas-realized.com?screen=route (app) - First proof screen: Route. - Canonical landing page: /demo-library/hvac-dispatch (canonical) - Indexable buyer proof page and primary demo-library route. - Industry SEO/AEO page: /industries/hvac-dispatch-software (industry) - HVAC dispatch software - Client launch plan: /demo-library/hvac-dispatch/client-launch-plan (commercial) - Buyer-facing launch plan with order, data, SEO/AEO, and support steps. - Statement of work: /demo-library/hvac-dispatch/statement-of-work (commercial) - Buyer-signable scope, milestones, responsibilities, service levels, and change controls. - Statement of work JSON: /demo-library/hvac-dispatch/statement-of-work.json (commercial) - Machine-readable scope and acceptance manifest. - Deal desk package: /demo-library/hvac-dispatch/deal-desk (commercial) - Order form, pricing bands, approval gates, add-ons, and redlines. - Deal desk JSON: /demo-library/hvac-dispatch/deal-desk.json (commercial) - Machine-readable commercial close manifest. - Sample data package: /demo-library/hvac-dispatch/sample-data-package (data) - CSV templates, sample rows, and import validation gates. - Sample data JSON: /demo-library/hvac-dispatch/sample-data-package.json (data) - Machine-readable data dry-run manifest. - Production data contract: /demo-library/hvac-dispatch/data-contract (data) - Entities, source systems, events, boundaries, and API-shaped routes. - Production data contract JSON: /demo-library/hvac-dispatch/data-contract.json (data) - Machine-readable production data contract. - White-label kit: /demo-library/hvac-dispatch/white-label-kit (deployment) - Naming, domain, terminology swaps, copy blocks, brand assets, and checklist. - White-label kit JSON: /demo-library/hvac-dispatch/white-label-kit.json (deployment) - Machine-readable rebrand manifest. - Tenant clone package: /demo-library/hvac-dispatch/tenant-clone-package (deployment) - Rebrand-and-launch handoff for a buyer tenant. - Tenant clone JSON: /demo-library/hvac-dispatch/tenant-clone-package.json (deployment) - Machine-readable tenant clone package. - Tenant seed package: /demo-library/hvac-dispatch/tenant-seed-package (deployment) - Users, roles, data sources, integrations, feature flags, automations, and notifications. - Tenant seed JSON: /demo-library/hvac-dispatch/tenant-seed-package.json (deployment) - Machine-readable tenant seed manifest. - Tenant cutover plan: /demo-library/hvac-dispatch/tenant-cutover-plan (deployment) - Downloadable cutover packet for buyer and implementation signoff. - Tenant cutover JSON: /demo-library/hvac-dispatch/tenant-cutover-plan.json (deployment) - Machine-readable cutover manifest for automation and QA.