
In a company that works job by job, every paid hour should end up charged to a job. In practice it doesn't work that way: there is waiting around, travel, hunting for materials, rework and workshop time that gets charged to nobody. These unproductive hours never appear on an invoice, but you pay for them all the same, and they often explain why a company has plenty of work and still makes little money. In this article you will see where they tend to hide, how to measure them and what to do to reduce them.
What is an unproductive hour, and what isn't
Not every hour that isn't invoiced is unproductive. Compulsory training or maintaining your own tools is necessary. The useful distinction is this:
- Charged hours: those that appear on a work report linked to a specific job.
- Necessary internal hours: training, maintenance of vehicles and tools, safety meetings.
- Lost hours: waiting, rework, unnecessary journeys, looking for materials, downtime between jobs.
The aim is not to reach zero, which is impossible, but to know how many hours there are of each type and to get the lost ones down.
Where time tends to be lost
Every company has its own weak points, but there are places where lost hours almost always turn up:
| Where | How you notice it | What is usually behind it |
|---|---|---|
| Waiting at the client's site | The team arrives and can't start | Work permits, area not cleared, poor coordination |
| Materials | Trips to the warehouse or the supplier mid-shift | Materials badly prepared or ordered late |
| Travel | Many hours in the van for little work | Poorly planned routes, isolated short visits |
| Rework | Redoing what was already done | Unclear instructions, out-of-date drawings |
| Gaps between jobs | People in the workshop with no task assigned | Short-term planning, jobs that slip |
| Paperwork | Time spent filling in or looking for reports | Paper reports that are keyed in by hand |
How to measure them with work reports
Without data, unproductive hours are just a feeling. With data, they are a figure you can track month by month. The simplest method is to compare two numbers for each worker and for the company as a whole:
- Recorded hours: those of the working day, from clocking in to clocking out, minus breaks.
- Hours charged to jobs: those that appear on work reports with a job code.
The difference is the hours that have gone to no job. To find out where they went, it helps to have a few internal codes, treated as the company's own jobs: "workshop", "warehouse", "training", "vehicle maintenance", "waiting". Keep them few and clear; if there are twenty, nobody will use them properly.
A word of warning about honest reporting
If the team feels that logging a wait gets them into trouble, they will spread it across the day's jobs and it will vanish from the statistics. Explain that the aim is to find organisational failings, not to point the finger at anyone. A two-hour wait because of a missing permit at the client's plant is very valuable information: it helps you talk to that client or charge for the time.
What to do about each source of loss
Once you know where they are, the solutions are usually a matter of organisation rather than technology:
- Waiting: confirm with the client the day before that the area and permits will be ready. If waiting keeps recurring with a particular client, make a note of it and raise it in your next quote.
- Materials: prepare the materials for the job before setting off and check stock of the most common items. A warehouse with up-to-date valuation avoids emergency purchases.
- Travel: group visits by area and avoid sending someone out for a short task if it can be done on the next visit.
- Rework: make sure the job documentation (drawings, instructions, specifications) is on the operative's mobile and is the current version.
- Gaps: keep a list of useful internal tasks for slots with no assigned work, each with its internal code.
- Paperwork: sending the work report from the mobile on completion saves time for both the operative and the office.
How they affect the price of your quotes
Unproductive hours that cannot be eliminated entirely have to sit somewhere in the price. If you calculate the hourly cost by dividing by productive hours, you are already spreading them across jobs. If you divide by all paid hours, the hourly cost will come out lower than it really is and you will quote too cheaply.
Nor does it make sense to spread them by eye across the month's jobs. If a wait happened at a particular client's plant, it is a cost of that job and should appear against it: that way that client's margin reflects what it really costs you to work for them, and you will have arguments for reviewing the price or the terms.
For example, if a workforce records 1,000 hours in a month and only 820 go to jobs, each charged hour has to cover the cost of 1.22 paid hours. That ratio, monitored month by month, is one of the most useful indicators for a technical services company.
What GControl gives you
In GControl, work reports serve a dual purpose: the working time record of each worker, with the start, end and breaks of the working day clocked in from the app, and the breakdown of those hours by job and activity. With both sets of data in the same system, you can compare working-day hours with charged hours. The app also captures normal, overtime, public holiday, union, night-shift and leave hours, and any differences from the working day, and operatives can see on their mobile the documents attached to each job.
You can find it on the work reports page, and on the materials and stock page you will see how the warehouse is controlled. If all you need is time and attendance control for your workforce, with no jobs or costs, Infonet has Gesthoras.


