Raw

**Extend Fieldbook to North and Islands in Q1, provided we restructure onboarding before go-live and resolve critical system integrations.**

Fieldbook is live in four regions, delivering strong operational gains and positive economics. However, adoption lags in two regions reveal a training bottleneck, and unresolved system gaps cause rework and data errors that threaten scalability. Extending to North and Islands is viable if we replicate the successful adoption model and clear technical debt before launch.

**1. Economic and operational gains justify extension**

*   **Productivity and efficiency improve significantly.** Completed jobs per technician rose from 4.6 to 5.3, and average travel time between jobs fell 18%. Same-day emergency insertion is now automatic with a median response time of 4 minutes.
*   **Cost savings are realized across key metrics.** Overtime spending dropped 12% quarter over quarter, and fuel cost per job decreased 9%, consistent with reduced travel times.
*   **Payback is achievable within the current quarter.** The rollout paid back running costs within the second quarter in Central and East. Economics for North and Islands remain favourable if adoption pace matches these regions; a repeat of the slower West pattern would delay payback by at least two quarters.
*   **Licensing costs are predictable.** Extension adds £13,500 per month in licences, offset by continued efficiency gains.

**2. Adoption risks are manageable through training restructuring**

*   **Current training model creates bottlenecks and hidden costs.** Regional coordinators scheduled classroom courses only once per region, leaving late hires and absentees to learn second-hand. In West, 34 of 118 technicians never attended any session.
*   **Improvised shadowing erodes productivity.** Coordinators in South and West arranged shadowing to fill gaps, consuming an estimated 380 technician-hours of lost route time.
*   **Support volume confirms training dependency.** Password resets and login problems account for 44% of support tickets, concentrated among technicians who missed classroom sessions. Attendance at weekly webinars correlates strongly with regions that missed classroom slots.
*   **Restructuring onboarding eliminates these risks.** Replicating the Central and East adoption pace—where full adoption was reached within six weeks—requires ensuring every technician receives direct training before going live. Winter travel for classroom training in North and Islands is necessary and justified.

**3. System integrations must be fixed to prevent scaling errors**

*   **Missing asset register feed causes field errors.** Fieldbook does not receive service history from the legacy asset register, leaving technicians without prior site knowledge. This forces calls to the back office and leads to incorrect part replacements; audited jobs showed a 9% error rate where parts already replaced under warranty were swapped again.
*   **Invoicing code mismatch generates manual rework and data disputes.** Job-completion codes in Fieldbook do not match the invoicing system, requiring the billing team to re-key roughly 300 records per week. This introduces transcription errors caught by customers and creates a 2–4% weekly variance between Fieldbook reporting and invoicing counts, forcing manual reconciliation.
*   **Search limitations create duplicate customer records.** Technicians create duplicate records when the search screen matches only exact postcodes. The support desk merges approximately 70 duplicates per week manually, and affected customers have split job-history views until resolution.
*   **Solutions exist but require immediate action.** The vendor provides a configurable mapping table for invoicing codes and supported connectors for both the asset register and invoicing system. IT confirms these integrations are straightforward but were excluded from the original deployment scope. Both must be scoped and implemented before North and Islands go-live.
*   **Program governance must enforce early fixes.** Every negative pattern observed in this review was visible by week four of the Central go-live, yet no mechanism existed to convert early field observations into program-level fixes. New regions require a process to apply lessons immediately rather than repeating delays.