The problem is not just bad reporting. It is bad cost visibility.
A lot of businesses have job profitability reports that look reasonable on paper but do not line up with reality.
The report says a job made money. The bank balance, workload and staff pressure suggest otherwise.
That usually happens because the report only includes the costs that are easy to attach directly to a job, such as labour hours booked against the job and materials purchased for it. What gets missed is everything around the job that still consumed time, people and cost.
That might include:
- travel time
- quoting time
- scheduling and rescheduling
- supervisor involvement
- customer updates
- procurement
- variations and approvals
- rework
- mobilisation time
- incomplete paperwork chasing
- non-billable site visits
- workshop prep
- end-of-day admin
- staff time between jobs
- payroll processing tied to operational complexity
If those costs are invisible, inconsistently captured or left sitting in a general overhead bucket with no allocation logic, the profitability report is not really showing job profitability. It is showing partial direct cost recovery.
That distinction matters because businesses make operational decisions from these reports. If the numbers are wrong, pricing, staffing and scheduling decisions will be wrong as well.
Direct costs are only part of the picture
Direct job costs are the easiest part to understand.
These are costs you can clearly point to and say, "that was for this job". Usually that includes:
- labour performed on the job
- materials used on the job
- subcontractor costs for the job
- equipment hired specifically for the job
The problem is that many service, trade and field businesses have a large amount of effort that supports jobs without being recorded as direct job activity.
That support effort is still real. It still consumes wages, vehicles, management attention and admin capacity. But because it does not fit neatly into a single line item on the job, it often disappears from reporting.
This is where indirect cost visibility matters.
Indirect costs are not fake costs or accounting abstractions. They are the operational cost of getting work delivered. If you ignore them, profitable-looking jobs can simply be jobs that are under-measured.
The hidden categories that usually distort profitability
When people talk about overheads, they often think only about broad fixed costs like rent or insurance. Those matter, but the more dangerous distortions often come from operational time that sits between clearly billable activities.
A few common examples:
Travel and dead time
A technician might spend 5 hours on site and 2 hours travelling. If only the 5 site hours are costed to the job, the job report understates labour cost.
This becomes even more important when jobs are geographically spread, scheduled inefficiently or require multiple visits.
Admin linked to jobs but not booked to them
Office staff may spend time:
- creating work packs
- confirming customer access
- chasing missing details
- ordering parts
- rebooking attendance
- processing completion documents
- resolving invoice questions
If that time is treated as generic overhead with no visibility, the job appears cleaner than it really was.
Supervisor and management involvement
Some jobs run smoothly. Others consume repeated manager intervention, technical review or escalation time.
If your reporting treats both jobs as equally profitable because only field hours are counted, it hides a major operational difference.
Non-billable field time
This might include:
- returning to site to fix documentation issues
- waiting for access
- site induction time
- setup and pack-down
- time spent between small jobs
- attendance that does not result in chargeable work
If the business pays for it, it belongs somewhere in the visibility model.
Internal support activities
Dispatch, scheduling, estimating support, stock handling and customer communication may all be essential to delivering a job. They may not belong as direct cost lines on every job, but if they are never allocated in any consistent way, job profitability becomes misleading.
Why "we know overhead exists" is not enough
Many businesses already know these costs exist. The problem is that knowing they exist is not the same as handling them properly in reporting.
A common situation looks like this:
- direct labour and materials are tracked against jobs
- wages for admin, supervisors and support roles sit elsewhere
- travel time is sometimes recorded and sometimes not
- non-job time is lumped into broad timesheet codes
- end-of-month profitability is reviewed as though it represents real job performance
In that setup, the report often creates false confidence.
The business starts treating the visible margin as operational truth. Then it makes decisions like:
- keeping prices too low because jobs appear more profitable than they are
- accepting awkward work that consumes disproportionate coordination
- overscheduling teams because travel and support time are not visible
- underestimating admin headcount required to support growth
- blaming field staff for margin issues caused by process design
The real issue is not that overhead exists. The issue is that there are no explicit rules for how indirect cost should appear in decision-making.
The goal is not perfect accounting. It is better operational decisions.
This is where many businesses either overcomplicate the problem or avoid it completely.
At one extreme, they try to create a level of allocation detail that nobody can maintain. At the other, they avoid allocations because they do not want to be "inaccurate".
Neither approach helps.
You do not need false precision. You do need consistent logic.
A useful profitability model should help you answer practical questions such as:
- Which jobs or job types consume more support effort than expected?
- Are small jobs genuinely profitable once travel and handling time are considered?
- Does a certain customer create disproportionate admin overhead?
- Are some crews less profitable because of performance, or because they are assigned the most fragmented schedules?
- Is your quoted margin enough to absorb the real delivery model?
That is an operational reporting problem, not just an accounting one.
What good allocation logic actually looks like
Good allocation logic means deciding, in advance, how indirect time and overhead will be made visible.
It is not about pretending every dollar can be perfectly traced. It is about creating a reporting model that is deliberate, repeatable and understood.
A practical framework usually starts with four questions.
1. Which indirect costs should be visible at job or job-type level?
Not every overhead needs to be pushed into every job report.
Start with the categories that materially affect operational decisions. Often that includes:
- travel time
- scheduling and coordination time
- supervision
- quoting or pre-delivery effort where relevant
- workshop prep
- non-billable field time
- support labour linked to job volume or complexity
The aim is to include the categories that explain why a job that looked fine on paper still strained the business.
2. Can the cost be captured directly, allocated by rule, or left at business level?
There are usually three levels of treatment.
Captured directly
If a cost can reasonably be attached to a specific job, do that.
Examples:
- technician travel recorded against the day’s jobs
- supervisor time logged to a problematic project
- return visit for defect resolution booked to the relevant job
Allocated by rule
If direct capture is impractical, use a consistent allocation method.
Examples:
- dispatch/admin support allocated by number of jobs
- supervisor cost allocated by labour hours
- vehicle overhead allocated by field hours or travel hours
- branch overhead allocated by revenue, labour hours or crew capacity
Left at business level
Some costs may remain outside job-level reporting if allocating them adds more noise than value.
That is fine, provided the boundary is clear. The problem is not that every overhead is not allocated. The problem is when nobody knows what is included and what is excluded.
3. What is the purpose of the report?
This matters more than people think.
If the report is meant to support pricing decisions, then indirect delivery costs need stronger visibility.
If it is meant for branch performance, a different allocation view may be more useful.
If it is meant for accountant-prepared financial statements, the structure may be different again.
One business can legitimately need more than one profitability view. Trouble starts when one incomplete report gets used for every decision.
4. Can the rule be followed consistently?
A slightly imperfect rule that is used every week is far more useful than an ideal model that falls apart after two months.
If staff cannot realistically capture the underlying data, the reporting logic will decay. The system has to match how the operation actually works.
Common allocation methods that are practical without pretending to be perfect
There is no universal formula, but there are a few sensible approaches depending on the cost type.
Allocate by labour hours
Useful when support effort broadly scales with the amount of work delivered.
This can work for:
- supervision
- some admin support
- general operational overhead linked to workforce activity
Allocate by number of jobs or visits
Useful when the handling cost is driven more by job count than by job duration.
This is often relevant for:
- scheduling effort
- customer communication
- dispatch workload
- invoice processing for high-volume small jobs
A business doing many short service calls often experiences more coordination cost per revenue dollar than a business doing fewer large jobs.
Allocate by travel hours or kilometres
Useful where geography materially changes cost to serve.
If some jobs are consistently remote or fragmented across locations, hiding that cost leads to bad quoting and poor scheduling decisions.
Allocate by revenue
Sometimes useful for broad financial visibility, but often weaker for operational decision-making.
Revenue does not always reflect effort. Two jobs with the same sell price may create very different workload.
Allocate by job type, customer type or service model
This is often more useful than trying to force every job into the same logic.
For example, a reactive service call model, a planned maintenance model and an installation model may each need different assumptions about non-direct effort.
The important thing is not choosing the most sophisticated method. It is choosing methods that reflect how cost is actually created in the business.
Why timesheets, clock events and job statuses matter more than people expect
Allocation logic only works if the underlying operational signals are usable.
This is where many reporting projects fail. The business debates margin formulas but does not fix the process that generates the data.
If you want reliable visibility, you need to know things like:
- when a person started travelling
- when they arrived on site
- when the job was completed
- whether they were waiting, reattending or blocked
- whether paperwork was complete
- whether the job was ready for invoicing
- whether a supervisor had to intervene
That does not mean turning every worker into a full-time data-entry clerk. It means deciding which events matter and designing a practical way to capture them.
For example:
- a field worker changes status to travelling, on site, completed or return visit required
- timesheet categories distinguish productive job time from travel, workshop, standby and admin
- office teams have simple codes for scheduling, quote support or job rework
- incomplete close-outs trigger a visible exception instead of disappearing into email
Without this structure, overhead allocation becomes guesswork layered on top of messy source data.
Poor system design often creates the very non-job time you are failing to measure
Another reason these reports mislead people is that the business treats non-job time as unavoidable background cost, when much of it is actually caused by broken workflow.
For example:
- technicians call the office because job information is incomplete
- jobs need repeat visits because photos or approvals were missing
- admin staff chase timesheets because there is no clear completion process
- supervisors intervene because ownership is unclear
- payroll teams fix coding errors caused by inconsistent job references
That support time still needs visibility in reporting. But it should also raise a deeper question: is the operation generating avoidable overhead?
This is where systems thinking matters. Some indirect cost is part of doing business. Some indirect cost is created by poor handovers, weak process rules or disconnected systems.
If all of it is simply spread across jobs with no analysis, you miss the chance to improve the underlying workflow.
What bad allocation logic does to quoting, staffing and scheduling
When indirect costs are hidden or inconsistent, the damage usually shows up in decision quality.
Quoting gets distorted
You may think a type of work is healthy because direct labour and materials look fine. But if that work consistently creates:
- extra coordination
- more travel
- more supervision
- more customer communication
- more small non-billable attendances
then your quote rates may be too low even if the visible job margin looks acceptable.
Staffing decisions become reactive
If non-billable time is invisible, management often concludes the business simply needs "more productivity" from field staff.
Sometimes the real issue is that too much of the day is consumed by travel, fragmented scheduling, poor information flow or support bottlenecks.
Without allocation logic, the business can misdiagnose a system problem as an individual performance problem.
Scheduling looks efficient when it is not
A day can appear fully booked while still being commercially poor.
If the schedule creates excessive travel, multiple handovers, waiting time and scattered low-value visits, utilisation may look high while profitability remains weak.
Good scheduling decisions require more than job count and labour hours. They need some visibility of the indirect cost created by the schedule itself.
Avoid false precision
One of the biggest mistakes is acting as though a complex spreadsheet automatically creates better truth.
If you allocate support labour to four decimal places but the underlying time capture is inconsistent, the report only looks precise.
A better approach is to be explicit about what the numbers mean.
For example:
- direct job margin
- operational job margin including allocated support labour and travel
- broader contribution view including selected overhead categories
That gives decision-makers a more honest picture than a single "profit" number that hides major assumptions.
You are not trying to simulate perfection. You are trying to create reporting that is reliable enough to support better decisions.
A practical way to improve profitability visibility
If your current reporting feels disconnected from reality, a useful approach is:
- List the indirect time and overhead categories that materially affect delivery.
- Separate them into direct-capture, allocate-by-rule, or business-level-only categories.
- Define a small number of allocation rules that fit how the business actually operates.
- Tighten the operational data capture needed to support those rules.
- Review profitability by job type, customer type or service model, not just individual jobs.
- Check whether the newly visible cost points to workflow problems that should be fixed, not merely allocated.
This usually produces far better insight than endlessly adjusting gross margin formulas after the fact.
What trustworthy job profitability reporting looks like
Good job profitability reporting does not claim that every overhead dollar has been perfectly attributed.
It does something more useful.
It makes clear:
- what is included
- what is excluded
- how indirect cost is treated
- which assumptions are being used
- where the biggest non-direct cost drivers sit
- whether margins are good enough for the delivery model behind them
That kind of reporting helps you make better decisions about pricing, work mix, resourcing, scheduling and process improvement.
If your profitability reporting consistently says jobs are fine while the business still feels squeezed, the gap is often not mysterious. It is usually sitting in the time and overhead nobody has decided how to treat.
If your workflow spans field teams, office staff, multiple systems and inconsistent status data, mapping the cost flow properly is often the first step before changing reports or adding automation. That is the kind of operational reporting design 5M Consulting helps businesses work through when the numbers no longer match how the business actually runs.