Stakeholders
Background
The company
Northline Services installs, repairs and maintains heating systems for homes and small businesses in three regions. About 120 technicians complete roughly 400 visits a day.
How work is done today
- Dispatchers assign visits by phone and in a shared spreadsheet, then re-enter them in the dispatch system.
- Technicians write the result of each visit on a paper form.
- Office clerks re-type the forms into the dispatch system every evening, about four hours a day in total.
Earlier attempts
In 2024 Northline trialled an off-the-shelf field-service app. It was dropped after three months because it could not work without mobile coverage and had no connection to the dispatch system.
Constraints
- Budget approved for a first release: up to 24 person-weeks.
- Customer personal data must stay in the EU.
- The dispatch system is maintained by IT and changes only in monthly releases.
Executive summary
Northline loses an estimated 9% of visits to scheduling errors and late paperwork, and spends four hours every evening re-typing paper forms. A two-week audit of 800 visits confirmed both figures.
Fieldwise is a mobile app that gives every technician their day, works without coverage and writes the result of each visit straight to the dispatch system. Dispatchers see declines and delays as they happen.
Recommendation
Build a first release for two regions in about 14 to 19 person-weeks, on top of the existing dispatch API, and measure the result over three months before rolling out to the third region.
Decisions needed now
- Approve building on the dispatch API (ADR-001) and ask IT to expose two missing endpoints in the next release.
- Confirm whether a ticked box is enough as customer confirmation or a signature is required.
Problem statement
Dispatchers and technicians cannot share an up-to-date view of the day, because visits are assigned by phone and recorded on paper. As a result about 9% of visits are missed or repeated and the office spends four hours every evening re-typing results.
Who is affected
- Customers, who wait for a technician who does not arrive, or pay for a second visit.
- Technicians, who start the day without the equipment history of the visit.
- Dispatchers and clerks, who spend their time moving data between systems.
Evidence
A two-week audit of 800 visits, 41 customer complaints in the last quarter and interviews with 12 technicians and 4 dispatchers.
Goals & success metrics
| Goal | Success metrics | Next target date | |
|---|---|---|---|
Reduce missed and repeated visits Customers get the visit they were promised, the first time. | 2 metrics | Jun 28, 2027 | |
Remove double entry Results are recorded once, at the customer, and never typed again. | 2 metrics | Apr 29, 2027 | |
Technicians adopt the app The app is the way visits are closed, not an extra step. | 1 metric | May 29, 2027 |
| KPI | Now | Trend | Target | Owner |
|---|---|---|---|---|
| First-time fix rate | 82% | ↑ 2pt | 90% | daniel.osei@northline.example |
| Average visits per technician per day | 3.3 | ↑ 0.1 | 3.8 | daniel.osei@northline.example |
| Customer satisfaction after a visit | 4.1 | ↑ 0.1 | 4.5 | lena.fischer@northline.example |
User experience
| Actor | Goals | Pain points |
|---|---|---|
TE Technician Visits customers and does the work | See the day at a glance. Close a visit in under two minutes. | No equipment history on site. Coverage drops in cellars and rural areas. |
DI Dispatcher Assigns visits and reacts to changes | Know where every technician is in the day. Reassign a declined visit quickly. | Learns about a decline by phone, late. Keeps a spreadsheet next to the dispatch system. |
OC Office clerk Checks results and prepares invoices | Receive complete, readable results. | Re-types paper forms and chases missing fields. |
Requirements
Loading…
Architecture
Loading…
UI screens
Roadmap, milestones & estimates
| ID | Milestone | Status | Reqs | Estimate | Target |
|---|---|---|---|---|---|
| M-1 | Foundation and dispatch connector | On track | 3 | 4–6 pw | 30 Dec 2026 |
| M-2 | Technician app with offline sync | Not started | 5 | 7–9 pw | 28 Feb 2027 |
| M-3 | Dispatcher board and alerts | Not started | 3 | 3–4 pw | 30 Mar 2027 |
| M-4 | Pilot in two regions | Not started | 1 | 2–3 pw | 29 Apr 2027 |
- The dispatch API stays stable during the project and IT exposes the two missing endpoints in the next monthly release.
- Two technicians and one dispatcher are available for a weekly 30-minute test session.
- A photo is at most 5 MB and a visit has at most six photos.
- The first release covers two of the three regions; the third follows after the pilot review.
Risks, blockers & open questions
Loading…