A quick tour of your field operations

• Tell us about the scope of your field operations, including number of districts, average daily jobs per district, and total technician headcount.
• Describe a recent quarter when first-visit completion dropped below 75 percent, what happened, and who flagged it first?
• Estimate your current average first-visit completion rate. Options: Below 60%, 60% to 69%, 70% to 74%, 75% to 84%, 85% to 94%, 95%+
• How does your team define and report first-visit success, and which dashboard or report is treated as the source of truth?
• Who on your leadership team owns field performance and would participate in pilot decision meetings? Options: VP Field Operations, Director Workforce Management, Head of Ops Excellence, Head of Product/Platform, Other (please name)

Where the current dispatch process fails

• What single failure in your dispatch process causes the biggest repeat truck roll cost today? Options: Incorrect skills assigned, Missing parts on truck, Wrong customer appointment window, Late technician arrival, Other (please explain)
• Walk me through the last time a technician arrived without the required part or certification, from dispatch to resolution.
• When that failure occurs, who on your dispatch or operations team is first to respond and what steps do they typically take? Options: Local dispatcher, Regional supervisor, Call center, Inventory control, Other (name role)
• How many repeat truck rolls does a typical district experience each month on average? Options: 0-5, 6-20, 21-50, 51-100, 100+
• List the downstream costs you track that result from repeat visits, for example customer credits, overtime, SLA penalties, or churn impact. Options: Customer credits, Overtime pay, SLA penalty costs, Lost revenue/churn, Dispatch admin time, Other
• If those repeat costs continue at current rates, would leadership support an external pilot to prove an alternative scheduling and dispatch approach? Options: Yes, immediately, Yes, with conditions, Maybe, needs more data, No, not right now

Where your data and integrations are most fragile

• Which integration gap would prevent an immediate pilot from accessing job, technician, or inventory data? Options: No API for inventory, No technician skill table export, Job feed is delayed, No access to GPS/telemetry, Unknown, Other (explain)
• Describe the systems that author parts inventory and technician skill tables and whether each exposes an API or only file exports.
• Who owns the API keys, data exports, or integration approvals for those systems and can they grant access within 30 days? Options: Yes, committed owner, Yes, but needs approval, No dedicated owner, Unsure
• Estimate the current accuracy of your parts-on-truck and technician-skills data. Options: Below 50% accurate, 50%–69%, 70%–84%, 85%–94%, 95%+
• Are there compliance, union, or legal constraints that could block sharing job, technician, or location data for a live pilot? Options: Yes, significant constraints, Yes, manageable with approvals, No constraints, Unsure
• Identify any contractual or regulatory barrier that would stop a 30-day live pilot before we scope integrations.

If the pilot proves the math, what changes for you

• If the pilot delivered a 25 percent reduction in repeat dispatches, which operational decision would you take first? Options: Scale to more districts, Change staffing model, Revisit SLA commitments, Negotiate commercial terms, Other (explain)
• Specify the top three metrics you will use to evaluate pilot success and the target improvement for each. Options: First-visit completion, Repeat dispatch reduction, Schedule efficiency (jobs/hour), Technician utilization, Customer SLA on-time rate
• What sample size of jobs and technicians does your team consider statistically meaningful for a district pilot? Options: Small sample (100–500 jobs), Medium (500–2,000 jobs), Large (2,000+ jobs), Depends on district variability
• Name the approvers, their roles, and the budget threshold that would trigger executive review for a rollout decision.
• Which internal approvals or budget holds would still prevent signing within 30 days even if the pilot reaches its targets?

Where you would run and scale a pilot

• Where in your district footprint would you prefer to run a pilot first, and why is that location representative?
• Outline the priority sequence you would use to roll out districts over a three to six month period.
• Explain your team's capacity to support integration testing, field verification, and issue remediation during each district rollout. Options: Dedicated internal integration team, Shared engineering resources, Rely on external integrator, Limited capacity, need support
• Name the roles you would assign as district owners and the weekly time commitment you expect from them.
• List the contingency plans you would exercise when a district does not meet acceptance criteria. Options: Extend pilot, Increase training, Add mobile inventory, Pause rollout, Other (explain)
• Would limited technician participation in a district stop you from proceeding with that district's rollout? Options: Yes, pause rollout, No, proceed with mitigations, Depends on participation level, Unsure

Adoption risks and technician sentiment

• Could technician resistance to mobile tools and new workflows halt a pilot in a district? Options: Yes, likely, Possible but manageable, Unlikely, Unsure
• Share a recent example where a field change met resistance, what caused it, and how long it took to resolve.
• Quantify the percent of technicians who today have accurate parts inventories and current skill certifications reflected in your systems. Options: Below 40%, 40%–69%, 70%–89%, 90%+
• Select the training formats that have driven the best adoption historically, for example classroom, virtual, or in-field mentoring. Options: Classroom, Virtual instructor-led, On-the-job mentoring, Microlearning modules, Peer coaching
• Tell how field supervisors currently handle exceptions when a technician arrives without the right parts or skills, and who escalates those cases.
• Should 30 percent of technicians refuse to use the mobile tools in pilot districts, would you pause the pilot or continue with mitigations? Options: Pause pilot, Continue with mitigations, Scale training first, Unsure

The competitive set and internal alternatives

• For your current approach to win against an external vendor, what would have to be true about outcomes, cost, or risk?
• Enumerate the categories of alternatives you are evaluating, such as incumbent platform, internal build, managed service, or continued manual dispatch. Options: Incumbent platform, Internal build, Other vendor platforms, Managed service, Continue manual process, Unsure
• Has anyone inside your organization proposed an internal build instead of partnering, and what is that team's timeline? Options: Yes, active plan, Yes, exploratory, No internal proposal, Unsure
• Identify the performance or cost thresholds at which you would prefer to keep the incumbent rather than change to a new solution.
• Pinpoint the single advantage that would make you choose an internal build over engaging a partner.

Pilot design and acceptance criteria

• Would tying acceptance to first-visit completion change how you compare vendors and internal solutions? Options: Yes, it simplifies evaluation, Yes, but need multiple metrics, No, we prefer process metrics, Unsure
• Select the acceptance criteria you would require for pilot success. Options: First-visit completion target, Repeat dispatch reduction target, Schedule efficiency improvement, No increase in technician overtime, SLA on-time adherence
• Specify the minimum percentage improvement in first-visit completion you require to commit to rollout. Options: 5%–9%, 10%–14%, 15%–24%, 25% or more, Depends on cost savings
• Provide the titles and business owners who must approve pilot acceptance and the budget band that requires executive signoff.
• Specify the pilot duration in weeks that would convince your team to move to a phased rollout. Options: 2 weeks, 4 weeks, 6–8 weeks, 12 weeks, Other
• Should the pilot miss its agreed acceptance on first-visit completion, what fallback path would you prefer: extend, adjust scope, pause, or cancel? Options: Extend pilot, Adjust scope/targets, Pause and retrain, Cancel pilot

Data feeds, technical owners, and readiness

• Confirm which teams must grant API or file access for job, technician, and parts feeds and whether they are prepared to do so.
• Choose which systems must be integrated for the pilot, for example workforce management, inventory, CRM, scheduling, or GPS telemetry. Options: Workforce management, Inventory/parts system, CRM/OSS, Scheduling system, GPS/telemetry, Other
• Flag any systems that currently lack APIs and would require file-based transfers or manual exports.
• Share the name and contact of the technical owner who can provision access for each required feed.
• Absent automated access to parts inventory within 30 days, can the pilot proceed with agreed manual workarounds and who would authorize them? Options: Yes, proceed with workarounds, No, pilot requires automation, Conditional, needs exception, Unsure

Final logistics, blockers, and next steps

• Assuming pilot success, who on your side is enabled to fast-track deployment and commit the initial rollout budget?
• Choose the preferred timeline to start a district pilot. Options: Within 2 weeks, Within 1 month, 2–3 months, 3–6 months, Unsure
• Flag immediate blockers that would delay kickoff beyond your selected timeline, for example legal reviews, staffing, or data access. Options: Legal/contract review, Insufficient staffing, Missing API access, Budget approval, Union or compliance review, Other
• Outline the top three questions your leadership will ask before approving spend so we can prepare precise answers.
• Will a no-cost pilot data run that reproduces your last month's job and technician data make a signature within 30 days more likely? Options: Yes, significantly more likely, Yes, somewhat more likely, No, timeline unaffected, Unsure
• Pinpoint one condition that would make your team sign within a week after pilot success.

• Solution Experience — Scheduling & Dispatch Walkthrough

• Confirm the current state and its cost
• Customer confirms the demonstrated workflow eliminates the technician-skill and parts mismatch that drives repeat truck rolls.
• Provide the district job and technician dataset for the pilot, including job windows, required skills per job, parts-on-truck snapshots, and recent dispatch logs.
• Customer agrees on pilot success metrics tied to first-visit completion, repeat dispatch reduction, and schedule efficiency and accepts target thresholds for evaluation.
• Walk through a representative district scenario
• Run the dispatch engine on the provided dataset and deliver a pilot report benchmarking first-visit completion, repeat dispatch reduction, and schedule efficiency within seven business days of receiving data.
• Customer identifies remaining data gaps and integration blockers required to run a representative pilot.
• Proof: Run the optimized scheduling scenario
• Identify all current workforce and inventory integration endpoints and provide API or extract access details for each system to be used in the pilot.
• Review data and integration assumptions
• Confirm the pilot district, the pilot evaluation window, and the named district rollout owner for coordination and validation.
• Validate the future state

• Solution Experience — Scheduling & Dispatch Walkthrough
• Solution Experience Deck
• Solution Brief — Optimized Scheduling & Real-Time Dispatch

• meeting
• slides
• document

Change Context & Sponsors

• Who is the executive sponsor for this change (name and title)?
• Who is the operational sponsor in field operations (name and title)?
• Which district or regional leaders will act as local change sponsors (names and districts)?
• Who will have final sign-off authority for go-live in each district? Options: Regional Operations Lead, VP/Head of Field Operations, Director of Workforce Management, IT/Integration Lead, Other
• Are there internal stakeholders outside operations who must be engaged (legal, HR, union, compliance)? If yes, please list them and the required level of involvement.

Current Technician Experience and Tools

• How do technicians currently receive assignments and updates? Options: Paper schedule, Phone call / SMS, Email, Existing mobile app, Crew board / dispatch board, Other
• What devices do technicians use in the field (personal smartphone, company phone, rugged tablet, none)? Options: Personal smartphone, Company smartphone, Rugged tablet, Laptop / mobile workstation, No device provided, Other
• Are there known connectivity constraints in any districts that affect mobile app use (poor cellular, intermittent Wi-Fi)? If yes, which districts and how severe are the constraints?
• What current field tools or apps do technicians use on a daily basis (names or short descriptions)?
• On average, what is the technician population per pilot district and how many shifts or crews operate concurrently?
• How would you describe the general digital comfort level of your technicians? Options: Highly comfortable, Moderately comfortable, Somewhat uncomfortable, Not comfortable

Adoption Risks and Barriers

• Which of the following adoption barriers do you expect to be material for this rollout? Options: Lack of devices, Low digital literacy, Perceived surveillance or privacy concerns, Union or labor restrictions, Shift coverage constraints, Inaccurate parts or skills data, Integration downtime risk, Language barriers, Incentives misalignment, Other
• Are there specific districts, supervisors, or technician groups you expect will resist the change? Please name them and describe why.
• Have technicians been part of past technology rollouts? If so, what worked well and what did not?
• Do any collective bargaining agreements or local policies limit how you can monitor or change technician workflows? Options: Yes, No, Unsure
• Are there any regulatory or privacy constraints we should plan around when collecting usage data? Options: Yes, No, Unsure

Training and Skill Development

• Which training modalities do you prefer for technicians during pilot and rollout? Options: Onsite instructor-led, Virtual instructor-led, On-demand video modules, In-app guided steps and tips, Printed job aids, Train-the-trainer model
• Who will own training delivery (internal training team, field supervisors, vendor trainers, blended)? Options: Internal training team, Field supervisors, Vendor trainers, Blended model, Other
• What is a realistic training time budget per technician for initial onboarding (minutes or hours)? Options: <30 minutes, 30-60 minutes, 1-2 hours, Half day, Full day, Multiple days
• Which topics must be included in training to reduce adoption risk (select all that apply)? Options: How scheduling decisions are made, Parts and skills validation, Privacy and data use, App navigation and tasks, Escalation and exception handling, Safety and compliance
• How will you validate training effectiveness after sessions (quiz, supervised shifts, usage threshold)? Options: Knowledge quiz, Observed field verification, Training completion certificate, Minimum usage threshold, Supervisor sign-off, Other

Communication and Engagement Plan

• Who will own the communications plan for technicians and supervisors?
• Which channels do you regularly use to communicate with technicians? Options: Email, SMS / text, In-app notifications, Supervisor briefings, Toolbox talks, Printed notices, WhatsApp or group messaging, Other
• What is the preferred cadence for pre-launch communications to field teams? Options: Weekly, Biweekly, Monthly, Two weeks before go-live, Ad hoc
• What core messages should be emphasized to reduce resistance (efficiency gains, reduced repeat work, less overtime, privacy safeguards)? Please list the top three.
• How will you capture and respond to technician feedback during pilot and rollout? Options: In-app feedback, Supervisor reports, Regular feedback sessions, Anonymous survey, Dedicated support hotline, Other
• Who will manage an FAQ and escalation list for common concerns, and how will updates be distributed?

Incentives, Measurement, and Governance

• Which adoption and behavior metrics will you track during pilot and rollout? Options: App adoption rate, Active daily users, Training completion rate, First-visit completion rate, Repeat dispatch rate, Schedule adherence, Technician satisfaction score, Parts accuracy rate
• What target change in adoption metrics would you consider a success at pilot completion (give one clear numeric target)?
• Will you use incentives or recognition programs to encourage adoption? If yes, briefly describe the approach. Options: Yes, No, Undecided
• How often will sponsor and stakeholder reviews occur to assess adoption progress? Options: Weekly, Biweekly, Monthly, At pilot milestones only, Other
• Who is the escalation owner for adoption issues that require cross-functional intervention (name and role)?

Pilot Design, Support, and Rollout Readiness

• How many technicians and which districts will be included in the initial adoption pilot?
• What is the planned duration of the pilot (weeks or months)? Options: 1 week, 2-4 weeks, 1-3 months, 3-6 months, Other
• What level of go-live support do you expect during the pilot (onsite support, remote support, supervisor-led)? Options: Onsite support, Remote support, Supervisor-led, Combination, Minimal
• What acceptance criteria tied to adoption must be met before expanding beyond pilot (list up to three measurable criteria)?
• Are there any logistical requirements for rollout day one we should plan for (device distribution, SIM provisioning, training sessions)? If so, list them.
• Who will be the named owner responsible for technician adoption after rollout (name and role)?

• Deploy Dispatch Optimization Engine
• Provision Technician Mobile App
• Integrate Parts Inventory System
• Sync On‑Truck Inventory and Replenishment
• Import Technician Skills and Certifications
• Connect Workforce Management System Endpoint
• Enable Real‑Time GPS Rerouting and ETA
• Activate Real‑Time Rescheduling
• Configure SLA Appointment Window Enforcement
• Migrate Historical Job and Technician Records
• Run Pilot District Optimization Instance
• Train Technicians and Dispatchers on Platform

Deploy Dispatch Optimization Engine

• Where will the optimization engine be deployed (hosted by us, run in your cloud, hybrid)? Options: Hosted by us, Run in your cloud, Hybrid / discuss
• Which dispatch constraints must the engine enforce for your districts (select all that apply)? Options: Technician skill certification, On‑truck parts availability, Customer SLA appointment window, Drive‑time limits, Overtime caps, Union rules or local labor constraints
• How many concurrent scheduling requests peak per minute in a typical district? Options: Less than 10, 10-50, 51-200, 200+
• What response‑time SLA for optimization decisions do you require (max latency to produce a reassignment)? Options: <5 seconds, 5-30 seconds, 30-120 seconds, >2 minutes
• Which integration endpoint will provide job and technician feeds to the engine (REST API, message bus, file drop)? Options: REST API, Message queue (event stream), SFTP / file drop, Database replica / direct DB access, Other
• Describe the acceptance criteria that will confirm the optimization engine is delivering value in a pilot district (include target first‑visit completion %, target repeat dispatch reduction %, and schedule efficiency metric).

Provision Technician Mobile App

• Is there an existing technician mobile app that must be replaced or integrated? Options: Replace with new app, Integrate with existing app, Phased: integrate then replace
• Which mobile device types are used by technicians in the pilot district (select all that apply)? Options: Android rugged phones, iOS phones, Rugged tablets, Mixed/other
• What on‑truck app features must work offline for technicians (parts lookup, barcode scan, job details, signature)? Options: Parts lookup offline, Barcode scan offline, Job details offline, Customer signature offline, All of the above
• Name the owner of distribution and mobile device management (MDM) for technician devices and their contact method.
• Provide the authentication method to be used for technicians and any corporate directory required (SAML, OAuth2, local credentials). Options: SAML / SSO, OAuth2, Local credentials, Other
• Describe the training and change management measures required for technicians to accept the mobile app, including any union agreements or device‑usage policies.

Integrate Parts Inventory System

• Which inventory system is the canonical source for on‑truck and depot SKU data (ERP, WMS, or custom DB)? Options: ERP, Warehouse Management System (WMS), Custom database, Other
• What inventory update cadence do you require for the dispatch engine to rely on (real‑time event, 5 minutes, hourly, daily)? Options: Real‑time (event driven), Every 5 minutes, Hourly, Daily
• Which export or API formats does your inventory system provide for SKU, location and quantity (REST API, SOAP, CSV/SFTP, DB replica)? Options: REST API, SOAP, CSV / SFTP export, Database replica, Other
• How are parts distinguished on trucks versus central depots in your schema (separate SKU codes per location, same SKU with location attribute)? Options: Separate SKU per location, Same SKU with location attribute, Need mapping assistance
• Are serialized assets tracked by serial number in the inventory feed or only by SKU and quantity? Options: Serial‑numbered tracking, SKU/quantity only, Mixed model
• What data accuracy threshold for on‑truck inventory is acceptable before enabling optimization (for example 95% SKU‑level accuracy)? Options: >=99%, 95‑98%, 90‑94%, <90% — remediation required

Sync On‑Truck Inventory and Replenishment

• Which replenishment model do you operate for truck stocking (pull‑based after use, scheduled restock, min‑max thresholds)? Options: Pull‑based (after use), Scheduled restock, Min‑max thresholds per route, Other
• How are replenishment events triggered today (manual depot request, mobile scan on return, automated reorder from ERP)? Options: Manual depot request, Mobile barcode scan, Depot scan on return, Automated reorder from ERP
• Name the team responsible for physical reconciliation of returned parts and damaged items. Options: Field technicians, Depot inventory team, Third‑party vendor, Not defined
• Which inventory fields must synchronize from the truck feed to the platform (SKU, lot/serial, expiration date, quantity, condition)? Options: SKU, Lot / Serial, Expiration date, Quantity on hand, Condition / damaged
• What maximum delay between a technician consuming a part and the platform reflecting that consumption is acceptable? Options: Real‑time, <5 minutes, <30 minutes, End of day
• Are automated replenishment thresholds required for pilot trucks tied to depot lead times and route schedules? Options: Yes, No, Pilot only

Import Technician Skills and Certifications

• What canonical source contains technician skills and certifications (HR system, learning management system, operations CSV)? Options: HR system, Learning Management System (LMS), Operations CSV maintained by team, Other
• Which certification attributes must the scheduler consume (certification type, expiry date, authorized task list)? Options: Certification type, Expiry date, Authorized task list, Certification issuer
• How often are certifications renewed or requalified in your organization? Options: Annually, Every 2‑3 years, On demand / as needed, Unknown
• Provide the mapping between your current skill taxonomy and the platform schema or indicate whether mapping should be performed during onboarding.
• Are there documented supervisor overrides or shadow certifications dispatchers may apply in the field? Options: Yes — supervisor overrides allowed, No — hard certification enforcement, Some roles allow overrides
• Which completeness threshold for skills data must be met prior to enabling optimization (for example 100% of active technicians with skill entries)? Options: 100%, >=95%, >=90%, Other

Connect Workforce Management System Endpoint

• Which WFM endpoint will supply technician schedules, time off and shift constraints (REST API, roster file via SFTP, DB replica)? Options: REST API, Roster file via SFTP, Database replica, Other
• What specific fields in the shift feed are mandatory for scheduling (shift start/end, skill tags, work zone, break rules)? Options: Shift start/end, Skill tags, Work zone / region, Break rules, Planned off time
• How are emergency or on‑call assignments represented in your WFM feed today? Options: Separate on‑call flag, Ad‑hoc shifts in WFM, Not represented — manual only
• Who is the technical owner for the WFM integration and what is their contact method?
• What cadence do you require for shift updates to be synchronized to the scheduling engine (real‑time, 15 minutes, hourly, daily)? Options: Real‑time, Every 15 minutes, Hourly, Daily
• Is read/write access to the WFM required to post completed work and time punches, or is read‑only sufficient for the pilot? Options: Read‑only, Read and write required, Pilot: read‑only then write

Enable Real‑Time GPS Rerouting and ETA

• Which telemetry source supplies live technician locations (in‑app device telemetry, fleet telematics provider, phone OS location)? Options: In‑app device telemetry, Fleet telematics provider, Phone OS location only, Other
• What location‑ping update frequency do you require to support rerouting and ETA calculation? Options: Every 5 seconds, Every 30 seconds, Every minute, On significant movement only
• Which privacy, collective‑bargaining or union rules constrain live location usage (no live tracking, anonymized aggregation, consent required)? Options: Full live tracking allowed, Aggregated / anonymized only, Consent required by technician, No live tracking permitted
• How should ETA and reroute notices be surfaced to customers and dispatchers (select all that apply)? Options: SMS to customer, Dispatcher console alerts, In‑app technician notification, IVR customer updates
• What maximum acceptable ETA error margin do you need for SLA enforcement (for example +/- 5 minutes)? Options: +/- 1 minute, +/- 5 minutes, +/- 10 minutes, +/- 15 minutes
• Which monitoring metrics will you require to validate rerouting performance (on‑time arrival rate, average ETA variance, missed ETA events)? Options: On‑time arrival rate, Average ETA variance, Missed ETA events, Number of reroutes triggered

Activate Real‑Time Rescheduling

• Which operational events should automatically trigger real‑time rescheduling (job completed early, job running late, customer cancel, traffic incident)? Options: Job completed early, Job running late, Customer cancel, Traffic incident, Technician breakdown
• What guardrails should limit reshuffling of an individual technician's day (max reassignments per day, minimum notice window)? Options: Max 1 reassignment per day, Max 2 reassignments per day, Minimum 15‑minute notice, Minimum 30‑minute notice, Custom
• Who on your operations team may approve manual overrides to automated rescheduling decisions? Options: Dispatch supervisor, Regional manager, On‑call scheduler, No manual override allowed
• What time window relative to appointment start should disallow automatic rescheduling (for example within 30 minutes)? Options: Disallow within 15 minutes, Disallow within 30 minutes, Disallow within 60 minutes, Allow until appointment start
• Which operational metrics will you monitor to evaluate automated rescheduling behavior (reschedules per day, SLA retention, technician impact)? Options: Reschedules per day, SLA retention rate, Technician schedule churn, Average reassignment lead time
• Which logs and audit trails must be retained for each automated reschedule event and for how long (reason code, actor, pre/post assignments; retention 6 months / 1 year / other)? Options: Reason code, Actor ID, Pre/post assignments snapshot, Retention: 6 months, Retention: 1 year, Other

Configure SLA Appointment Window Enforcement

• Which SLA types must be enforced in the pilot (first‑visit completion, four‑hour appointment window, committed arrival time)? Options: First‑visit completion, Four‑hour appointment window, Committed arrival time, Other
• What tolerated SLA breach threshold should trigger escalation (for example 90% of appointments within window)? Options: >=99%, >=95%, >=90%, Custom
• How should SLA breaches be recorded and reported (automated alerts, weekly reports, audit log, dashboard)? Options: Automated alerts, Weekly reports, Audit log entry, Dashboard metric
• Which customer notification templates must be used when an appointment shifts outside the SLA window? Options: Standard delay notice, Premium SLA notification, Custom templates provided by you, No customer notification
• Are penalty calculations required in SLA reports for contractual review (yes/no/pilot only)? Options: Yes — include penalty calculations, No — report only, Pilot: report only then decide
• Identify the primary data source to validate SLA compliance (job end timestamps, GPS arrival event, customer confirmation) and any secondary sources. Options: Job end timestamps, GPS arrival event, Customer confirmation, Dispatcher log

Migrate Historical Job and Technician Records

• What time range of historical job and technician records is required for pilot analysis (3 months, 6 months, 12 months)? Options: 3 months, 6 months, 12 months, More than 12 months
• Which historical data fields are required for side‑by‑side comparison (job outcome, parts used, technician ID, travel time, time on site)? Options: Job outcome, Parts used, Technician ID, Travel time, Time on site
• What format will historical exports be provided in for import (CSV, Parquet, database replica)? Options: CSV, Parquet, Database replica, Other
• Name the validator responsible for data completeness and state the acceptance threshold required prior to import (for example 98% job‑id match).
• Are personally identifiable information (PII) or customer contact fields required for the pilot dataset and how should they be masked or consented? Options: PII included and consented, PII excluded, PII masked before export, Discuss options
• Is backfill of historical technician skill records required alongside job records for the pilot? Options: Yes — full history, Only current skills, Partial history, No

• current_state
• stakeholders
• decision_readiness
• gaps
• desired_state
• success_criteria
• stakeholders
• current_state
• decision_readiness
• desired_state
• success_criteria
• gaps
• stakeholders
• desired_state
• decision_readiness
• success_criteria
• current_state
• gaps
• current_state
• gaps
• decision_readiness
• desired_state
• success_criteria
• decision_readiness
• decision_readiness
• decision_readiness

• Subscription Agreement & Order Form
• Data Processing Agreement (DPA)
• Pilot Acceptance & Results Sign-off
• Statement of Work (Deployment Services)
• Integration & Data Access Agreement
• Operational Readiness & Handover Agreement
• Service Level Agreement (SLA)

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• Acceptance Gate — Pilot Evaluation (around day 90)
• Ongoing Operational Review (monthly during rollout)
• Quarterly Outcomes and Operations Review

• Update the operational issue tracker with owners, target fix dates, and verification steps for each open incident.
• If acceptance is conditional or failed, list remediation tasks with owners and committed completion dates.
• Confirm the incumbent system wind-down plan is complete or scheduled, including data archive/migration and user fallback closure.
• Publish the acceptance decision record and evidence package to the shared workspace and attach the named signatory's decision.
• Open remediation tickets for any unmet criteria and schedule checkpoints to verify closure before district rollout.
• Execute the incumbent decommission or retention-read-only steps and confirm archive completeness in the shared log.
• Trend review vs Pilot Evaluation targets
• Ensure first-visit completion rate and repeat dispatch rate continue trending toward the Pilot Evaluation targets or have an agreed remediation plan.
• Maintain a prioritized operational backlog with owners and due dates for fixes and enhancements.
• Validate the integrity of parts and skills data that feed the scheduling engine for the coming month.
• Re-confirm success criteria and owners
• Publish the prioritized enhancement backlog and schedule investigative spikes for top requests before the next review.
• Run and share the month-over-month data quality report for inventory and skills feeds to confirm source system health.
• Quarterly outcomes vs Pilot Evaluation targets
• Validate that aggregated first-visit completion rate and schedule efficiency meet or have a clear path to meet the Pilot Evaluation targets.
• Capture and codify top operational learnings that should be applied to remaining district rollouts.
• Ensure the shared channel and escalation rules are current and that high-impact enhancements are scheduled with owners and timelines.
• Publish the quarterly outcomes report comparing aggregated metrics to the Pilot Evaluation targets and circulate to stakeholders.
• Document the top 3 operational learnings and update the rollout runbook to apply them to future districts.
• Refresh the enhancement backlog priorities and schedule the next release window for high-impact items.
• Confirm the production deployment and integrations are functioning for live jobs in the pilot district.
• Document and assign remediation owners and target dates for any critical blockers discovered during go-live.
• Verify early adoption signals exist and capture any immediate training or support actions required.
• Publish the go-live validation checklist and remediation log to the shared workspace.
• Execute priority fixes for critical blockers and report status in the shared channel within 72 hours.
• Schedule the First Measurement Review for weeks 4-6 post go-live and circulate required data extracts.
• Present outcome data vs targets recorded in the Pilot Evaluation stage
• Determine whether first-visit completion rate and repeat dispatch rate are trending toward the targets recorded in the Pilot Evaluation stage.
• Agree a prioritized set of corrective actions, each with an owner and target resolution date, to close any gaps before the acceptance gate.
• Confirm data sources and fixes required to ensure subsequent measurements are reliable.
• Deliver a root-cause findings memo that links each metric gap to specific data or operational causes.
• Implement agreed corrective actions and update the remediation log with progress at least weekly until the acceptance gate.
• Prepare the dataset and dashboard views that will be used for the Acceptance Gate meeting, aligned to the Pilot Evaluation targets.
• Restate numeric acceptance criteria from the Pilot Evaluation stage
• Produce a documented acceptance decision against the Pilot Evaluation stage targets, with evidence for each criterion.
• Root-cause diagnosis for metric gaps
• Present metric-by-metric outcomes
• Deployment and integration validation
• Operational learnings and process changes
• Open operational issues and ticket burn-down
• Enhancement request backlog and prioritization
• Data quality and telemetry check
• Outstanding issues and enhancement roadmap
• Document pass/fail per acceptance criterion
• Early adoption and usage signals
• Shared channel and escalation path confirmation
• Critical blockers and defects triage
• Formal acceptance decision and signatory capture
• Agree corrective actions and timeline to acceptance gate
• Data integrity and inventory sync check
• Incumbent system wind-down confirmation
• Immediate remediation actions and next steps
• Next-month action plan
• Agree remediation items and rollout sequencing