Custom development
Field crews were opening five or six systems before starting work, and a logging flow was telling them it had saved data when it had saved nothing.
01Key numbers
02The situation
Field technicians checked five to six different systems every morning to find out where they were going and what they were doing.
Assets left site with no removal tracking at all. Converting a hand-drawn map to a digital one took more than thirty hours. 82% of orders were not fully estimated.
Recognise this in your own org?
03What we built
One board pattern, proven once and then applied seven times, plus the mobile paths the desktop build had quietly broken.
The same board family covers task, work order, purchase order, order, dispatch, production and development work, including a real Gantt view. A new board is a configuration of a proven pattern rather than a new build with new bugs.
The desktop flow uses a table component that does not render in the mobile app at all. Rather than degrade the desktop experience, there is a mobile-safe path. If it does not work on the phone, it is not done.
Crew staffing had lived in a spreadsheet, so the replacement had to behave like one. The scheduler supports Excel-style typing directly into cells rather than a record page per assignment.
In-org training is served from a static resource and was recorded by logging in as an actual field user. An admin walkthrough shows a screen the field crew will never see.
Contract value excludes tax. Amounts are as entered, in mixed currencies, and are not converted.
We will demonstrate any of these live, on the real org,.
The activity flow listed an order’s work orders and looped over them. 42 active orders had zero work orders. Field staff saw "0 of 0 items", pressed Next, and were shown a success screen. An empty selection looped zero times straight into a confirmation. It is fixed with a stop screen, a minimum row selection, and back-dating so missed days can be self-logged.
04Outcome
The morning routine moved onto one board family, and the sign-in problems behind it were diagnosed rather than guessed at.
Order intake, field mobile, time logging and kanban totals were each verified by logging in as the named user who does that job.
Keep reading
The client told us the tax was calculating by product instead of by province. We tested that against all 2,335 order line items and it was not true. Six other defects were, and we priced each one.
Every order had an address and none had coordinates. Once they were mapped, one account turned out to be 20% of the book and the default view was hiding another 35%.
Tell us what is broken. You get a written read on it within one business day, before any money changes hands.