Change Management Plan: [Mobile Field Service]
Organisation | [Allbright Utility Services] |
Project | [Replace paper job sheets with the FieldGo mobile app] |
Executive sponsor | [Name, Director of Operations] |
Change manager | [Name] |
Go-live | [Phased: North region 1 March 2027, South region 3 May 2027] |
Version | [1.0, December 2026] |
1. The change
[Field engineers currently receive jobs on printed sheets each morning and return completed paperwork at the end of the week. From March 2027, all 320 engineers will receive, update and close jobs on a tablet app, capture photos and customer signatures digitally, and order parts from the van. Dispatchers will schedule and reassign jobs in real time.]
2. Case for change
[Paperwork errors cause 11% of jobs to be invoiced late or wrongly; $1.4m in delayed cash each month.]
[Customers cannot be told an accurate arrival time; complaints about missed appointments rose 24% in 2026.]
[Engineers spend about 45 minutes a day on paperwork and phone calls to the office.]
[The regulator requires digital safety records from January 2028.]
What success looks like: [95% of jobs closed in the app within 4 weeks of go-live; paperwork time cut by 30 minutes per engineer per day; missed-appointment complaints down 40% by year end.]
3. Change impact assessment
Group | Size | Today | Future | Degree of impact |
|---|---|---|---|---|
[Field engineers] | [320] | [Paper sheets, weekly paperwork drop] | [Tablet app; real-time updates; digital signatures] | [High] |
[Field supervisors] | [28] | [Allocate work at morning briefings] | [Monitor live dashboards; coach on app use] | [High] |
[Dispatchers] | [22] | [Phone engineers to reassign jobs] | [Drag-and-drop scheduling; automated customer texts] | [High] |
[Billing team] | [14] | [Key in job sheets] | [Review exceptions only] | [Medium] |
[Customers] | [About 40,000 a month] | [Four-hour appointment window] | [Arrival text with live ETA] | [Low] |
[IT service desk] | [12] | [No field-device support] | [Support 340 tablets] | [Medium] |
4. Stakeholder analysis
Stakeholder | Influence | Interest | Current position | Desired position | Approach |
|---|---|---|---|---|---|
[Director of Operations (sponsor)] | [High] | [High] | [Committed] | [Committed and visible] | [Monthly sponsor actions; site visits] |
[Regional managers] | [High] | [Medium] | [Neutral] | [Committed] | [Involve in rollout planning; adoption targets in objectives] |
[Field supervisors] | [Medium] | [High] | [Sceptical] | [Committed] | [Super-user role; early training] |
[Engineers’ union representatives] | [High] | [High] | [Concerned about tracking] | [Supportive] | [Consult on location-data policy early] |
[Senior engineers (30+ years’ service)] | [Medium] | [Medium] | [Resistant] | [Accepting] | [Peer champions; extra hands-on support] |
[Billing team] | [Low] | [High] | [Positive] | [Committed] | [Regular updates; process redesign workshops] |
5. ADKAR readiness assessment
Scores 1 (low) to 5 (high), from surveys and focus groups in November 2026. The first score of 3 or below is the barrier point.
Group | Awareness | Desire | Knowledge | Ability | Reinforcement | Barrier point |
|---|---|---|---|---|---|---|
[Field engineers] | [3] | [2] | [1] | [1] | [1] | [Awareness / Desire] |
[Field supervisors] | [4] | [3] | [2] | [2] | [1] | [Desire] |
[Dispatchers] | [4] | [4] | [2] | [2] | [1] | [Knowledge] |
[Billing team] | [4] | [5] | [2] | [2] | [1] | [Knowledge] |
What this tells us: [Engineers do not yet understand why the change is needed, and some fear it is about monitoring them. Communications and the sponsor must address the reasons and the location-data question before training starts.]
6. Sponsorship roadmap
When | Sponsor action |
|---|---|
[Jan 2027] | [Launch video and depot roadshow: why we are changing and what it means for engineers] |
[Jan 2027] | [Publish agreed location-data policy with union representatives] |
[Feb 2027] | [Attend first training sessions in each depot] |
[Mar 2027] | [Go-live day visits to North depots; thank early adopters by name] |
[Monthly] | [Review adoption dashboard with regional managers and remove blockers] |
7. Communications plan
Audience | Message | Channel | Sender | Timing |
|---|---|---|---|---|
[All operational staff] | [Why we are changing; what is and is not changing] | [Video, depot briefings] | [Sponsor] | [w/c 11 Jan 2027] |
[Engineers] | [What the app does for you; how location data is and is not used] | [Toolbox talks, FAQ card in vans] | [Supervisors] | [Jan–Feb 2027] |
[Engineers] | [Your training date and device collection] | [Text and email] | [Project team] | [2 weeks before training] |
[Dispatchers] | [New scheduling process; cutover plan] | [Team meetings, workshop] | [Dispatch Manager] | [Feb 2027] |
[Customers] | [New arrival texts] | [Website, text message] | [Customer Service] | [At go-live] |
[All] | [Progress, quick wins and fixes] | [Fortnightly bulletin] | [Change manager] | [From go-live, 12 weeks] |
8. Training plan
Group | Format | Duration | Timing | Proficiency check |
|---|---|---|---|---|
[Super-users (2 per depot)] | [Classroom and field trial] | [2 days] | [Jan 2027] | [Complete 10 test jobs] |
[Engineers] | [Depot hands-on session plus in-van practice mode] | [4 hours] | [2 weeks before go-live] | [Close 3 practice jobs unaided] |
[Supervisors] | [Dashboard and coaching session] | [1 day] | [3 weeks before go-live] | [Run a live dashboard review] |
[Dispatchers] | [Classroom and simulation] | [2 days] | [3 weeks before go-live] | [Schedule a simulated day] |
[Billing] | [Workshop on exception handling] | [Half day] | [2 weeks before go-live] | [Process 20 test invoices] |
9. Resistance management
Likely resistance | Root cause | Response | Owner |
|---|---|---|---|
["The app is for tracking us"] | [Fear of surveillance] | [Agreed data policy: location only during working hours, not used for discipline without a separate process] | [Sponsor, HR] |
["I’m not good with tablets"] | [Low confidence] | [Peer champions, extra practice sessions, simple quick-reference card] | [Super-users] |
[Supervisors keep paper as backup] | [Fear of failure on day one] | [Clear paper cut-off date; offline mode demonstrated] | [Regional managers] |
10. Reinforcement
[Weekly league table of app adoption by depot, celebrating improvement rather than shaming]
[Recognition for super-users and early adopters at monthly meetings]
[Paper job sheets withdrawn four weeks after go-live in each region]
[App use added to supervisor objectives for 2027]
11. Success metrics
Metric | Baseline | Target | Measured |
|---|---|---|---|
[Jobs closed in app] | [0%] | [95% within 4 weeks of go-live] | [Weekly] |
[Engineer proficiency check passed] | [n/a] | [100% before go-live] | [At training] |
[Paperwork time per engineer per day] | [45 min] | [15 min] | [Survey at 8 weeks] |
[Invoices raised within 2 days of job] | [61%] | [90%] | [Monthly] |
[Engineer sentiment: "the app helps me do my job"] | [n/a] | [70% agree] | [Pulse survey at 12 weeks] |
12. Roles and responsibilities
Activity | Sponsor | Change manager | Project manager | Line managers | Super-users |
|---|---|---|---|---|---|
Case for change | A | R | C | I | I |
Communications | A | R | C | R | I |
Training delivery | I | A | C | C | R |
Resistance management | A | R | I | R | C |
Adoption tracking | A | R | C | R | I |
R = Responsible, A = Accountable, C = Consulted, I = Informed.
13. Approval
Sponsor: [Name] Date: [Date] Change manager: [Name] Date: [Date]