Example

Example discovery report

A finished report for an invented project, Fieldwise: a mobile app for a field-service company. It is built from the same stages and shown exactly as the report in the app. Open any row, switch the pages, and download it as PDF, Word, PowerPoint or Markdown. All names and figures are made up.

Start your own, free

Stakeholders

Marta Kowalska
Chief Operating Officer, Northline Services
Project sponsor. Approves budget and scope and decides between building on the dispatch system and replacing it.
Daniel Osei
Head of Field Operations
Owns the visit process and the 120 technicians. Wants fewer missed visits and no more paper forms.
Priya Nair
IT Lead
Owns the dispatch system and its API. Controls the release calendar the project depends on.
Tomasz Brandt
Dispatch Supervisor
Assigns about 400 visits a day by phone and spreadsheet. Main user of the dispatcher board.
Lena Fischer
Customer Service Manager
Handles complaints about missed visits. Needs signed proof of work for disputes.

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

All goals
3 goals
GoalSuccess metricsNext target date
Reduce missed and repeated visits
Customers get the visit they were promised, the first time.
2 metricsJun 28, 2027
Remove double entry
Results are recorded once, at the customer, and never typed again.
2 metricsApr 29, 2027
Technicians adopt the app
The app is the way visits are closed, not an extra step.
1 metricMay 29, 2027
Key performance indicators
3 KPIs
KPINowTrendTargetOwner
First-time fix rate82%↑ 2pt90%daniel.osei@northline.example
Average visits per technician per day3.3↑ 0.13.8daniel.osei@northline.example
Customer satisfaction after a visit4.1↑ 0.14.5lena.fischer@northline.example

User experience

Users & actors
3 actors
ActorGoalsPain 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.
User Journeys
2 journeys
Technician closes a visitTechnician4 steps
Dispatcher reassigns a declined visitDispatcher, Technician3 steps
User Flows
2 flows
Visit assignmentApprovedUsed in Dispatcher reassigns a declined visit
Offline syncIn reviewUsed in Technician closes a visit

Requirements

Loading…

Architecture

Diagrams
3 diagrams
System contextFlowchart
Covers REQ-001, REQ-002, REQ-005
Offline syncSequence
Covers REQ-003
Visit lifecycleState
Covers REQ-001, REQ-004

Loading…

UI screens

Screens
4 screens
Day list
Covers REQ-001
Visit detail
Covers REQ-001, REQ-006
Close visit
Covers REQ-002, REQ-007
Dispatcher board
Covers REQ-004, REQ-008

Roadmap, milestones & estimates

Milestones
4
Estimate
16–22 person-weeks
General release
29 Apr 2027
Nov
Dec
Jan
Feb
Mar
Apr
M-1
30 Dec 2026
M-2
28 Feb 2027
M-3
30 Mar 2027
M-4
29 Apr 2027
IDMilestoneStatusReqsEstimateTarget
M-1Foundation and dispatch connectorOn track34–6 pw30 Dec 2026
M-2Technician app with offline syncNot started57–9 pw28 Feb 2027
M-3Dispatcher board and alertsNot started33–4 pw30 Mar 2027
M-4Pilot in two regionsNot started12–3 pw29 Apr 2027
Assumptions
4 assumptions
  • 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…