HVAC2026

Jobs and field reports for an HVAC installer

A single tool to track jobs, schedule interventions and produce field reports, replacing a general-purpose task manager pushed well past its purpose.

Board of twenty-four live jobs, in pre-sale columns (to handle, quote sent), delivery columns (to schedule, scheduled, in progress) then invoicing. Every card carries the customer, the town, the date, the type (repair, works, site), the priority, the amount, and for jobs in progress the time spent against the time sold. Above the board, a filter by type and a filter by origin. — Jobs pipelineDemonstration data

A repair job opened: the job's path along the top, from "to handle" to "done", then four figures: half a day sold on the quote, 0.2 days actually spent, the gap, and the amount. Below, the scheduled intervention with its report button, the task to handle, and the site's comment box. On the right, the customer with directions, then the type, origin, priority, due date and the state of the sync with the field-service software. — One jobDemonstration data

One day's schedule in two columns, from 11 am to 9 pm: every slot carries the intervention's name and its customer, the red line marks the current time, and an intervention just added shows in another colour. At the bottom, a sentence explains that a slot placed here is then moved in Google Calendar, and that the daily sync picks up its new date. — Day plannerDemonstration data

The same day on the map: interventions numbered in visiting order, linked by the computed route, with the driving time and distance between each. At the bottom of the list, the total: 5 h 52 on the road for 11 h 30 of interventions, and the share of the day spent driving, counted as unbillable time. — Route on the mapDemonstration data

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.

What changed, in numbers

tool, instead of four: 4 → 1tool, instead of four
entry per piece of information, instead of several: 1entry per piece of information, instead of several
of interventions with a report: 100%of interventions with a report

Let’s talk about your project

Describe what you are trying to build. We answer with an honest first read on feasibility and scope, even when the answer is that you do not need us.

Talk about your project