Interface redrawn from the real mechanic, with neutral data. It is not a screenshot of the client’s system.
Where it started
Tracking lived in a general-purpose task manager, topped up with emails, a shared calendar and an intervention tool. The same information was entered three times, and the link between a job, its interventions and its invoicing existed only in the owner’s head.
What we built
A model that takes the trade’s own vocabulary: the job is the parent entity, the intervention its child, and site work, breakdown call or refurbishment are merely job types. Reports are filled in the field — maintenance routines, readings, photos. External sources feed the application rather than the reverse: calendar, intervention software, down to equipment notifications arriving by email and parsed automatically.
What changed
One entry, at the moment the information exists. The owner sees the true state of his jobs without reconstructing it, and the assistant schedules, tracks equipment and invoices from the same screen.
The work is described without naming clients: the trade, the order of magnitude and what was built — never the identity.