Starting with Why: What pushed this into the open?

• Briefly describe what triggered your interest in changing how you dispatch technicians today.
• Which of the following was the clearest trigger for this initiative? Options: SLA penalties/financial exposure, Drop in customer satisfaction/renewal risk, New VP/leader demanding change, Manual dispatch (whiteboard/phone) revealed as outdated, Operational scaling issues, Other
• If SLA penalties drove this, what was the rough magnitude last quarter (estimate is fine)? Options: <$50,000, $50k–$250k, $250k–$500k, >$500k, Don't know / need to check
• Who first raised the alarm internally and what was their core concern—costs, customer churn, or something else?
• Tell us a short story of a recent dispatch that went wrong—what happened and how did it make you feel about the operation?

Are We Still Letting Repeat Truck Rolls Eat Our Margins?

• How often do technicians need to return to the same customer for the same issue within 30 days? Options: >10% of jobs, 5%–10% of jobs, 1%–5% of jobs, <1% of jobs, We don't track this reliably
• When a repeat truck roll happens, what are the most common root causes you see? Options: Missing parts on truck, Incorrect technician skill/certification, Inaccurate asset history, Poor scheduling window/SLAs, Customer unavailability, Other
• Can you estimate the average hard cost (parts + labor + travel) of a failed first-time fix for you? Options: <$250, $250–$750, $750–$1,500, >$1,500, Unsure / varies widely
• How do repeat visits show up in your customer conversations—are they cited in warranty claims, escalations, or renewal negotiations? Options: Yes—frequent in renewals, Occasionally referenced, Rarely mentioned by customers, We are not tracking customer mentions
• Walk me through a specific job type or customer segment where repeat truck rolls are most painful—what makes it different?

Who’s Really Owning the Problem (and Who Could Stop It)?

• If you had to bet who will block this project, which role would you put your money on and why? Options: IT / Integrations, Field Supervisors, Finance/Procurement, Technicians / Unions, Operations leadership, Other
• List the key stakeholders we must win over for a successful deployment (name, role, and primary concern).
• Which of these groups are already aligned behind a change to scheduling and mobile workflows? Options: Executive leadership, Regional field managers, Dispatchers, Technicians, IT/Integrations team, Finance
• How do technicians typically react to process changes—do they see new tools as helpful, as surveillance, or something else? Options: Mostly positive/helpful, Cautious but open, Resistant due to perceived surveillance, Mixed depending on region/team, Unknown
• Who will sign final acceptance on SLA and utilization improvements—title and how they prefer success to be reported?

How Trustworthy Is Your Data — and What Breaks When It’s Not?

• If your parts and asset records were only 60% accurate, what would that mean for a real-world optimization test? Options: Optimization results unreliable, Pilot will need data cleanup, We can still learn directional value, Not sure—need to run analysis
• How complete and accurate are the following data sources today? Options: Technician skills/certifications, Truck inventory by VIN, Asset service history, Work order time stamps, Customer SLA terms
• Do you have access to 90 consecutive days of historical dispatch data (work orders, technician IDs, timestamps, parts used, outcomes) for a test? Options: Yes—ready to provide, Yes—but requires anonymization/cleanup, Partial dataset only, No / would need assistance
• How often does your inventory sync to field vans or depots (real-time, nightly, weekly, manually)? Options: Real-time, Near real-time (hourly), Daily, Weekly, Manual / ad hoc, Not sure
• Share an example of a data gap that has directly caused dispatch mistakes—what happened and how long did it take to detect?

What Would Success Actually Feel — and Look — Like?

• If you could pick one headline metric that would convince leadership to expand this solution, which would it be? Options: Reduced SLA breaches, Increased technician utilization, Higher first-time fix rate, Improved customer satisfaction (CSAT/NPS), Reduced drive time/cost
• What are realistic percentage targets for those metrics in 90 days? Options: Utilization: +1–5%, Utilization: +6–10%, Drive time: -5–15%, First-time fix: +1–10%, SLA breaches: -10–50%
• Who will be responsible for daily tracking and reporting during the 90‑day evaluation, and how do they prefer results delivered? Options: Weekly dashboard, Daily digest, Executive summary, Ad hoc meetings, Integrated into CRM/BI
• Would you accept a pilot that prioritizes the highest‑impact regions or job types first, or do you need enterprise-wide coverage to validate results? Options: Targeted pilot (regions/job types), Enterprise-wide test, Hybrid phased approach, Undecided
• Beyond metrics, what qualitative signals will tell you the solution is working (e.g., technician feedback, customer comments, fewer escalations)?

Where Could Deployment Get Stuck — and Who’s Ready to Clear the Path?

• What single risk keeps you awake about a 3–6 month deployment: integrations, adoption, data quality, cost, or something else? Options: Integrations complexity, Technician adoption/resistance, Poor data quality, Regulatory/union constraints, Budget/contracting delays, Other
• Which integrations are must-haves before go‑live (select all that apply)? Options: ERP (parts & invoicing), CRM (customer & SLAs), Inventory management/WMS, HR / technician roster, Telematics/location data, None required for pilot
• Do you have an internal change management plan for technician adoption—trainers, incentives, feedback loops—or would you need help building one? Options: We have a plan and resources, We have a plan but need external support, No plan—need full support, Unsure
• How much time can your trainers and field leaders commit to initial enablement during pilot weeks (hours per week)? Options: <5 hours/week, 5–10 hours/week, 10–20 hours/week, >20 hours/week, Not available
• Describe a recent rollout (any tool) that went well or poorly—what lessons should we apply to avoid the same pitfalls?

Ready to Test: The 90‑Day Run That Proves It

• Are you willing to run the scheduling engine against 90 days of historical dispatch to validate utilization, drive time, and first‑time fix improvements? Options: Yes—ready now, Yes—but needs data prep, Interested but need executive buy-in, Not ready
• What format and fields does your historical dispatch data currently exist in (CSV exports, API, SQL, proprietary)? Options: CSV / Excel exports, API access, SQL database export, Proprietary system extract, Mixed formats, Unknown
• Who will provide the historical dataset and own data validation for the test (name, role, contact)?
• What acceptance criteria do you require to sign off on the validation checklist (specific KPIs, thresholds, and sign‑off roles)?
• If the test shows mixed results (e.g., utilization improves but technician satisfaction drops), what trade-offs are you prepared to accept and who decides? Options: Prioritize operational metrics, Prioritize technician adoption, Seek balanced remediation plan, Escalate to executive sponsors

• Solution Experience Kickoff — Current State, Consequence & Success Metrics
• Data & Scenario Preparation Workshop
• Optimizer Dry Run — Sample Batch Proofs (Diagnosis → Proof → Validation)
• Full Historical 90-Day Run & KPI Validation
• Stakeholder Validation & Acceptance Walkthrough

• Provide an ROI estimate that ties optimizer performance to SLA and financial outcomes.
• Both: Agree on a scheduled window for the Sample Dry Run.
• Re-state Hypothesis & Acceptance Criteria
• Prove that optimizer decisions address specific current-state causes in concrete cases.
• Obtain customer validation (or specific corrections) on optimizer logic for edge cases.
• Agree required config/data adjustments prior to full 90-day run.
• Schedule the full historical run with a mutually agreed timeline.
• Seller: Deliver a run log and decision rationale for each sampled case and implement low-effort rule tweaks.
• Customer: Confirm any business-rule exceptions and provide missing enrichment (e.g., tech certification mappings).
• Both: Lock the date for the full historical 90-day optimization run.
• Methodology Recap & Baseline Validation
• Deliver a definitive measurement of optimizer impact against agreed KPIs.
• Identify and document residual gaps with clear root causes and owners.
• Reach a decision: accept and proceed to pilot/deployment or iterate on data/configuration.
• Introductions & Objective
• Seller: Share a full validation report with run logs, case-level examples, cohort charts, and ROI estimate.
• Customer: Approve acceptance results or provide a prioritized remediation list for a repeat run.
• Both: If accepted, schedule the pilot scope and kickoff; if not, schedule targeted remediation sprint.
• Executive Summary of Problem → Proof → Outcome
• Operational and executive stakeholders understand and agree that results meet business needs.
• Obtain formal acceptance or a conditional acceptance with a clear remediation plan.
• Define next steps: pilot kickoff schedule with owners and success metrics or remediation sprint.
• Customer Executive: Provide formal sign-off or conditional acceptance and name pilot sponsor.
• Seller: Deliver pilot runbook, trainer plan, and deployment checklist aligned to validated optimizer configuration.
• Both: Schedule pilot kickoff and assign owners for any outstanding remediation items.
• Customer articulates current state in one sentence.
• Consequence is quantified and documented for use in ROI and urgency messaging.
• Future-state operational success metrics and acceptance criteria are agreed.
• Data owners and delivery deadlines are confirmed for the next workshop.
• Customer: Deliver 90 days of historical dispatch, technician roster, parts/asset records, and SLA rules (CSV/SQL extract) by agreed date.
• Seller: Share data template, anonymization guidance, and validation checklist within 24 hours.
• Both: Confirm pilot cohort (regions/technician groups) and the acceptance signatory.
• Data Inventory Review
• Dataset is understood, gaps logged, and remediation owners assigned.
• Field mapping is complete so optimizer can consume the data without guesswork.
• Representative validation scenarios are agreed and prioritized.
• Delivery date for the cleaned/anonymized dataset is confirmed.
• Customer: Deliver cleaned/anonymized dataset and fixes for high-priority quality issues.
• Seller: Provide mapping scripts and runbook for data transformation; create scenario definition table.
• Representative Workflow Walkthrough
• One-Sentence Current State
• Optimized Results — Executive KPI Summary
• Run Overview & Methodology
• Critical Data Quality Gaps
• Before vs After Walkthrough (Top 6 Cases)
• Cohort Breakouts & Sensitivity
• Operational Readiness Check
• Field Mapping & Enrichment Plan
• Quantified Consequence
• Acceptance Criteria Review & Sign-Off
• Defined Future State (One Sentence)
• KPIs Snapshot — Sample Delta
• Select Representative Scenarios & Edge Cases
• Root-Cause of Remaining Failures
• Case Validation & Challenge
• Dataset Sign-Off & Anonymization
• Validation & Acceptance Criteria
• Acceptance Criteria Check & ROI Estimate
• Pilot/Deployment Decision & Next Steps
• Data & Prework Checklist

• Deploy Technician Mobile App to Devices
• Configure Digital Work Orders and Mobile Forms
• Implement Parts-on-Van Inventory Sync with Barcode Scanning
• Integrate ERP Parts Catalog and Auto-Replenishment
• Enable Technician Certification and Skill Validation on Mobile
• Auto-Generate Parts Picklists and Van Replenishment Orders
• Capture Time, Travel, and Job Costs via Mobile GPS
• Deploy Offline Asset History and Parts Lookup on Mobile
• Integrate CRM for Customer Context and Invoicing Handoff
• Launch Navigation Integration with Turn-by-Turn Directions
• Configure SLA Priority Flags and Escalation Notifications
• Deliver Hands-On Technician Mobile App Training

Deploy Technician Mobile App to Devices

• How many technicians will need the mobile app in the initial rollout? Options: Less than 50, 50-200, 201-500, 501-1,000, More than 1,000
• Which device operating systems must be supported? Options: iOS, Android, Both, Other
• Are devices company-owned (MDM), BYOD (bring-your-own-device), or mixed? Options: Company-owned (MDM), BYOD, Mixed
• Do you require Mobile Device Management (MDM) or enterprise app distribution? Options: Yes, No
• What authentication method is required (SSO, MFA, local credentials)? Options: Single Sign-On (SAML/OIDC), SSO + MFA, Username/Password, Other
• Describe any device restrictions, UI branding, or accessibility requirements for the app.

Configure Digital Work Orders and Mobile Forms

• How many distinct mobile form/work-order templates do you need initially? Options: 1-5, 6-15, 16-50, More than 50
• Do work orders need conditional logic (show/hide fields based on answers)? Options: Yes, No
• Do forms require signatures, photos, attachments, or barcode captures? Options: Signature, Photos, Attachments, Barcode/QR
• Is offline form completion required when technicians have no connectivity? Options: Yes - full offline, Yes - limited fields only, No
• Which job status states and field mappings must sync back to the back-office system?
• Are there validation rules or regulatory fields that must be enforced before job close? Options: Yes, No

Implement Parts-on-Van Inventory Sync with Barcode Scanning

• Do technicians currently use barcode scanners or will smartphones be used for scanning? Options: Dedicated barcode scanners, Smartphone camera scanning, Both, No scanning today
• How many SKUs are typically stocked per van (average range)? Options: Less than 100, 100-500, 501-1,000, More than 1,000
• What is the acceptable sync latency for van inventory (real-time, hourly, end-of-day)? Options: Real-time, Near real-time (minutes), Hourly, Daily
• Do you require cycle counting, audit trails, or adjustment workflows on the mobile app? Options: Cycle counting, Audit trail/adjustments, No
• Are part numbers and barcodes standardized across your fleet, or do mapping rules apply? Options: Standardized, Require mapping/transformation, Mixed
• Describe any constraints (network, regulatory, or hardware) that could affect barcode scanning reliability.

Integrate ERP Parts Catalog and Auto-Replenishment

• Which ERP or backend inventory systems must be integrated? Options: SAP, Oracle, NetSuite, Microsoft Dynamics, Other
• What integration pattern is preferred for catalog & inventory data? Options: Real-time API, Scheduled batch (CSV/XML), Middleware/ETL, Other
• Do you want automated replenishment (PO generation) from van depletion events? Options: Yes - auto PO, Yes - draft PO for approval, No - manual replenishment
• What replenishment rules do you use (min/max, reorder point, vendor-managed, Kanban)? Options: Min/Max, Reorder point, Vendor-managed inventory, Kanban, Other
• Are part numbers consistent between field and ERP or is mapping required? Options: Consistent, Mapping required, Partial
• Describe any approval, audit, or compliance steps required for auto-generated replenishment orders.

Enable Technician Certification and Skill Validation on Mobile

• Do you currently track technician certifications and skills in a system today? Options: Yes - central system, Yes - spreadsheets, No
• Should the mobile app block assignment if a technician lacks required certification? Options: Block assignment, Warn but allow assignment, No block/warn
• Do certifications have expiration dates and automatic renewal reminders? Options: Yes - expirations & reminders, Yes - expirations only, No
• Do technicians need to upload proof (images/cert docs) from the mobile app? Options: Yes, No
• How many skill/certification categories and levels exist (provide ranges)? Options: Fewer than 10, 10-50, 51-200, More than 200
• Describe any regulatory or customer-specific qualifications that must be enforced on job dispatch.

Auto-Generate Parts Picklists and Van Replenishment Orders

• Do you want picklists generated per technician, per van, or per route? Options: Per technician, Per van, Per route, Per warehouse batch
• Should picklists include suggested substitutes or only exact SKUs? Options: Exact SKUs only, Include approved substitutes, Both with approval
• How frequently should replenishment orders be created (real-time, daily, weekly)? Options: Real-time, Daily, Weekly, On-demand
• Do picklists require warehouse/zone assignments and pick priorities? Options: Yes, No
• Who approves replenishment orders and what approval workflow is required? Options: Auto-approve, Supervisor approval, Procurement approval, Other
• Describe exceptions or manual override rules for picklist generation (e.g., urgent parts).

Capture Time, Travel, and Job Costs via Mobile GPS

• Should GPS capture be continuous, job-based (start/stop), or manual entry? Options: Continuous tracking, Job start/stop only, Manual entry by technician
• Do you want travel time and distance auto-calculated for cost reporting? Options: Yes, No
• Are geofencing rules required for job clock-in/clock-out? Options: Yes - required, Optional, No
• What cost granularity is required (labor only, labor+travel, full job cost including parts)? Options: Labor only, Labor + Travel, Labor + Travel + Parts, Full job cost with overhead
• Are there privacy or union constraints on GPS tracking we should be aware of? Options: Yes, No
• Describe any payroll or billing fields that must be populated from captured time and travel data.

Deploy Offline Asset History and Parts Lookup on Mobile

• Is full asset history required offline or only recent records? Options: Full history, Recent N months, Recent N jobs, No offline history required
• How many asset records should be available offline per device (approximate)? Options: Less than 1,000, 1,000-10,000, 10,001-50,000, More than 50,000
• Do offline lookups need images, schematics, or OEM manuals included? Options: Images, Schematics/OEM manuals, Parts list only, All of the above
• What offline sync frequency and conflict resolution policy do you prefer (last write wins, server wins, manual reconcile)? Options: Real-time when online, Scheduled daily, Scheduled weekly
• Are there storage constraints on devices that affect offline caches? Options: Yes - limited storage, No - ample storage
• Describe cases where offline asset access is mission-critical and must not fail.

Integrate CRM for Customer Context and Invoicing Handoff

• Which CRM(s) must be integrated for customer context? Options: Salesforce, Microsoft Dynamics, ServiceNow, Zendesk, Other
• Which data objects must sync from CRM to mobile (select all that apply)? Options: Contact, Account, Service History, Contracts/SLAs, Billing Info, Open Cases
• Is the CRM integration required to be bi-directional (updates from mobile back to CRM)? Options: Yes - bi-directional, Unidirectional (CRM -> Mobile), Unidirectional (Mobile -> CRM)
• Do you require invoice or job completion handoff to billing/ERP systems after job close? Options: Yes - automatic handoff, Yes - manual review then handoff, No
• What synchronization cadence is acceptable for customer/context data (real-time, near real-time, nightly)? Options: Real-time, Near real-time (minutes), Hourly, Daily
• Describe any custom fields or business rules in your CRM that must be respected during integration.

Launch Navigation Integration with Turn-by-Turn Directions

• Which navigation providers should be supported or preferred? Options: Google Maps, Apple Maps, Waze, TomTom, Other
• Do you require multi-stop route optimization or single-stop navigation only? Options: Multi-stop route optimization, Single-stop navigation, Both
• Is offline navigation required when technicians are in low-connectivity areas? Options: Yes - offline navigation required, No - online only
• Should customer ETA notifications be sent automatically with dynamic updates? Options: Yes - automatic ETAs, No - no ETAs, Optional per job
• Do technicians need the ability to select their preferred navigation app from the mobile device? Options: Yes, No
• Describe any routing constraints (vehicle type, restricted access, time windows) that must be applied.

• Order Form & Commercial Terms
• Statement of Work (SOW)
• Master Services Agreement (MSA)
• Service Level Agreement (SLA)
• Pricing & Payment Schedule
• Implementation Timeline & Milestones
• Roles & Responsibilities (RACI)
• Acceptance Criteria & KPI Targets
• Data Processing Agreement (DPA)
• Data & Integration Responsibilities
• Training & Change Management Plan
• Pilot & Phased Deployment Agreement
• Support, Maintenance & Escalation
• Change Order & Scope Management
• Termination, Exit & Data Return Terms

• Outcomes Confirmation (Executive Review)
• Lessons Learned & Root Cause Workshop
• Enhancement Prioritization & Roadmap
• Support & Continuous Improvement Handoff
• Quarterly Success Review (Recurring cadence)

• Ensure dashboards and alerting are operational and stakeholders have access.
• Consolidated Backlog Review
• Agree on a prioritized roadmap mapped to business outcomes and release windows.
• Define clear acceptance criteria for each enhancement to enable later validation.
• Commit owners and realistic timelines for delivery and verification.
• Publish the prioritized roadmap with acceptance criteria and owners to the shared channel.
• Create tickets/epics for top-priority items including test datasets and validation steps.
• Schedule demos/solution-experiences for major enhancements to prove future state before full roll-out.
• Shared Channel Setup and Ground Rules
• Put the shared communication channel into production with clear rules and membership.
• Agree and document an escalation matrix with SLAs and owners.
• One-sentence Current State Recap
• Create the shared channel, add invitees, and post the outcomes report and roadmap.
• Publish the escalation matrix and emergency contact list to the channel and internal wiki.
• Grant dashboard access to KPI owners and set initial alert thresholds.
• KPI Trend Review
• Validate sustained or improved KPI performance and confirm ongoing value delivery.
• Surface new issues or opportunities and queue them for the prioritization process.
• Decide on renewal/expansion readiness or additional remediation steps.
• Distribute the QBR deck including re-run proof outputs and updated ROI figures.
• Add agreed next-quarter initiatives to the enhancement backlog with owners and acceptance criteria.
• Schedule the next Quarterly Success Review and invite extended stakeholders.
• Confirm the project met the agreed acceptance criteria and obtain executive sign-off.
• Quantify and document the financial and SLA impact achieved.
• Agree monitoring baseline and cadence for ongoing measurement.
• Publish final Outcomes Report with raw data exports and ROI calculation within 3 business days.
• Collect executive sign-off (email/DocuSign) on acceptance criteria closure.
• Assign ongoing KPI owners and schedule the first post-signoff checkpoint.
• Current State Examples from Field
• Produce a prioritized list of root causes with estimated impact.
• Agree on immediate corrective actions and owners to address top operational risks.
• Define success criteria for each corrective action so results can be validated.
• Create an RCA report linking incidents to root causes, owners, and due dates.
• Implement top 3 quick wins (process or config) within 30 days and report impact.
• Plan pilot(s) for any change-management items affecting technician workflows.
• Recent Incidents & Resolutions
• Escalation Matrix & SLAs
• Consequence & Financial Impact
• Root Cause Analysis (5-Whys / Fishbone)
• Scoring Framework (Impact / Effort / Risk / Revenue)
• Proof: KPI Results vs Acceptance Criteria
• Proof: Re-run Scheduling Engine on Latest 90 Days
• Prioritize & Sequence Top Enhancements
• Monitoring, Dashboards, and Alerting
• Quantify Impact by Root Cause
• Validation: Tie Results to Customer Problems
• Identify Quick Wins vs Mid/Long-term Fixes
• Business Outcomes & Financial Update
• Change Request (CR) Process & Prioritization Pipeline
• Define Acceptance Criteria & Validation Steps
• Next Quarter Priorities and Expansion Triggers
• Sign-off, Commercial Next Steps, and Recommendation
• Assign Delivery Owners and Timelines
• Assign Owners, Timelines, and Success Criteria
• Support Enablement & Escalation Drills
• Agreed Monitoring Baseline & Next Checkpoints