Powstania Warszawskiego 15
31-539 Kraków
Mechanical contractor job costing rarely fails in the accounting system. It fails on site, where hours, materials and extra work are recorded late, from memory or not at all. This guide shows where the cost of a mechanical job leaks between the plant room and the invoice, and what has to change for the numbers to be ready while the job is still running.
Mechanical contractor job costing works when every cost is recorded against the job at the moment it happens: hours by the technician on site, materials when they leave the van or the warehouse, extra work when the customer approves it. Most accounting systems can already report cost by job. The usual gap is capture, because data reaches the office days later on timesheets, paper forms and phone messages. A field app that records these four inputs against the job, offline if needed, and sends them to the office for approval closes that gap without replacing your accounting.
Take an ordinary job: replacing a pump set and controls in a commercial plant room. Most contractors can describe the cost of that job in three ways, and the three rarely match.
Hours for two technicians, the equipment, fittings and a commissioning visit. Written before the job, usually with care.
Hours from weekly timesheets, materials from supplier invoices that arrive weeks later, and extra work if somebody remembered to report it.
A second visit for a part, an hour lost waiting for access, fittings taken from van stock and a small extra repair agreed with the customer on site.
The difference between the second and the third number is where margin disappears. It is not fraud and rarely carelessness. It is data that never had a reliable place to be recorded at the moment it was created.
Each of the four inputs has its own weak point. Knowing which one hurts most in your company tells you where a first version of the software should start.
Notice that none of these is solved by a better report. Every one of them is solved, or not, in the field, by the person doing the work.
Job costing is an accounting task, but the data behind it is collected in the field. If recording a cost against a job takes longer on site than writing it down somewhere else, it will be written down somewhere else.
A working setup gives every input one owner and one moment. The technician should not have to think about costing at all, only about recording the work in the order it happens.
A timer started on the job, not a timesheet filled in later. It has to keep running when the phone screen locks or a call comes in.
Items taken from the van or picked up for the job, recorded with a few taps from a short list rather than typed.
A short description, photos and the customer's signature on the device, so the office can invoice it without a phone call.
Approval of hours and materials, and the expected subcontractor cost entered when the work is ordered, not when the invoice arrives.
Two practical conditions decide whether this works. The app has to function in basements and plant rooms without a signal, and it needs a place for every case the crew meets. We cover the first in offline first app development. The second is the one most often missed.
TimeFix is a time and job tracking app for technicians, built in Flutter, with photo documentation and a separate panel for team leads and the office. Two lessons from it apply directly to job costing.
First, the work timer had to keep counting when the technician locked the screen or placed a call from inside the app. That requirement was in no document and came out of real use. Second, before the app covered a given case, technicians started writing things in the notes app on their phones, and the data in the system drifted away from reality.
For costing, the second lesson matters most. Every case the app cannot record becomes a cost the office never sees.
Many mechanical contractors run service and installation under one roof, and the two cost differently. A service call is short, its cost is mostly labor and a few parts, and it should be complete the moment the job closes. A project runs for weeks, mixes crews and subcontractors, and needs a running total compared with the budget while there is still time to react.
A single tool built for one of these usually handles the other badly. That is the core reason mechanical contractors end up with spreadsheets between their systems, and the theme of our guide to mechanical contractor software. For job costing, the practical rule is simple: service jobs need speed of capture, project jobs need a daily running total.
You do not need a complete platform to see real job costs. A focused first version usually covers these elements, and nothing more.
That scope is what we describe as the first stage on our mechanical contractor app development page. Dashboards comparing job cost with the estimate come after the data is reliable, not before.
If your crews already record hours and materials against jobs in an off the shelf app, the data reaches accounting the same day, and the office does not retype anything, your job costing problem is a reporting problem. Fix the reports and keep the tools.
Custom software earns its place when the gap is in the field: when the tool cannot express how your service and project work runs, when technicians keep the real information outside it, or when you pay full licences for people who only need to record time, materials and photos. The same reasoning applies to HVAC service companies, covered in custom HVAC software development.
Job costing means tracking every cost of a job against that job: labor hours, materials, equipment, subcontractors and extra work, and comparing the total with the estimate or the contract value. For a mechanical contractor it covers both service calls and installation projects, which usually need different levels of detail.
Most accounting and ERP systems can report cost by job once the data is in them. What they cannot do is collect it on site. If hours, materials and extra work reach the office days later on paper or in messages, the report is late and incomplete no matter how good the accounting system is.
Daily is a good target for project work, because a crew that is running over hours shows it within the first days. For service calls the cost is usually complete when the job closes, so the important thing is that nothing is added from memory at the end of the week.
Not always. If an off the shelf field app records hours and materials against jobs and your crews actually use it, connect it to accounting and keep it. Custom software makes sense when the tool cannot record the way you work, for example service and project jobs in one company, or when technicians keep the real data in notes outside the system.
A first version built around one workflow, such as hours and materials against a job plus office review, typically takes 8 to 12 weeks from kickoff to the stores. Integrations and further workflows are added in later stages, each agreed in writing before it is built.
We price a fixed scope after a scoping call and a written scope document, so the number is agreed before development starts. This article does not quote figures. Current information is on our pricing page.
Thomas sets the company's long term strategy and direction, identifies market opportunities, and owns business development and client acquisition. He builds strategic partnerships that last beyond a single project. He works with clients from the first strategy conversation, so their business goals, not just their feature list, drive every decision.
Tell us where hours, materials and extra work get lost today. You get a straight answer on what a first version should record and what can wait.