Why does margin fall while revenue holds?

Revenue is confirmed once, at invoice. Cost accumulates across estimating, travel, time on site, materials, overtime, rework and credit notes, and most of it is recorded after the job is closed. A job type can therefore grow in volume, hold revenue steady and reduce group margin at the same time. The distinction only becomes actionable when delivered cost is assembled per job and compared with what was finally billed.

What is the smallest useful set of metrics to start with?

Four: estimate-to-actual labour variance by job type, travel time share by branch, rework or repeat-visit rate linked to the originating job, and unbilled completed work ageing. Those four separate estimating problems from delivery problems and billing problems. Add material variance and discount rate once the definitions are consistent across branches.

How do we know whether to reprice or to fix delivery?

Test persistence. If the variance holds across multiple crews and multiple branches doing the same work, the estimate or the price is wrong. If it is concentrated in one branch or one crew, delivery, scheduling or job readiness is the cause. Repricing a delivery problem raises price without recovering margin, and it usually costs volume.

How should unbilled work be handled without creating disputes?

Treat it as a process gap rather than a recovery exercise. Measure the ageing between job closure and invoice, identify where in the flow the additional work stops being captured, and fix the capture step. Retrospective billing of work agreed verbally weeks earlier damages the customer relationship more than the recovered value justifies.

Should crew-level cost variance be used in performance reviews?

Cautiously. Crew-level variance is useful for coaching and for identifying job readiness or skill-matching problems. Used as a ranking, it encourages under-recording of time and materials, which removes the very signal leadership needs. The reliable unit of accountability is the job type and the branch, not the individual.

Does Garuda replace FSM, dispatch, scheduling, CRM, ERP or payroll systems?

No. Garuda is a decision layer above those systems. It reads job, route, crew, branch, service and financial signals and presents a governed executive view of where margin is moving and who owns the response. It does not schedule jobs, dispatch crews, optimise routes, hold customer records or process payroll.

How Can Field-Service Companies Improve Job Profitability?

Direct answer. Job profitability improves when leadership can see the true delivered cost of a job against what was finally billed, at the level of job type, branch and crew, early enough to change the next hundred jobs rather than explain the last hundred. Revenue can hold steady while margin falls, because the erosion happens inside delivery: scope agreed loosely, actual labour running past estimate, travel absorbed into fixed prices, material variance unattributed, overtime used to protect the promise date, discounts applied at the point of sale, rework and repeat visits recorded as new jobs, and completed work that is never billed at all. Each of those leaves a trace in the systems a field-service business already runs. Read together by job type and branch, they separate an isolated bad job from a recurring loss pattern, name the owner and set the corrective action before month-end explains it.

Executive buyer: CEO, COO, CFO, Operations Director, Branch Manager, Service Delivery lead
Connected view: Estimate, schedule, crew, travel, materials, rework, billing, branch
Cadence: Weekly governed review by job type and branch, ahead of month-end close
Scope boundary: Leadership visibility layer, not an FSM, dispatch, scheduling or route optimisation system

Author: GritWiz Executive Research, Decision intelligence editorial team
Published: 2026-07-10
Updated: 2026-07-10

Job profitability metric framework for field-service leadership

A governed set, defined identically in every branch and read weekly by job type. Each group answers a different question, so a margin discussion can end with a cause and an owner rather than a variance.

Scope and estimate

Estimate-to-actual labour variance: Difference between estimated and actual on-site hours, trended by job type and branch.
Scope change rate: Share of jobs where delivered scope differed from quoted scope.
Repriced scope share: Share of scope changes that were formally repriced rather than absorbed.

Delivery cost

Travel time share: Drive time as a share of paid crew hours, by branch and route.
Material cost variance: Parts consumed against the expected bill of materials, by job type.
Overtime attributed to jobs: Overtime hours mapped to the job that caused them rather than to the payroll period.

Revenue realisation

Unbilled completed work: Work completed and closed in the field with no corresponding invoice line, by ageing band.
Discount rate at point of sale: Discount applied against list or contract price, by branch and authority level.
Credit notes against jobs: Post-invoice adjustments traced back to the originating job.

Rework and service quality

Rework rate: Jobs requiring corrective work linked back to the original job record.
Repeat-visit rate: Visits repeated for the same fault or customer request within a defined window.
First-time completion: Share of jobs completed on the first visit with no follow-up required.

Variation

Margin by job type: Delivered margin for each recurring job type, compared across branches.
Branch margin dispersion: Spread in delivered margin for the same job type between branches.
Crew-level cost variance: Cost variance by crew for comparable work, used for coaching rather than ranking.

Ownership

Owner assigned: Whether each surfaced margin pattern carries a named accountable role.
Action ageing: Time a surfaced pattern has remained open without a closed action or a documented decision.

From job execution to realised margin Estimate, schedule, delivery, closure and billing. Cost is created at every stage and revenue is confirmed only at the last one, which is why job margin is visible late unless each stage is read separately.

Estimate Scope agreed and priced. Owner: Estimating or Commercial lead. Signal: scope change rate and repriced scope share.
Schedule Crew, skills and route assigned. Owner: Branch Manager. Signal: travel time share and job readiness before arrival.
Deliver Work performed on site. Owner: Service Delivery lead. Signal: estimate-to-actual labour variance and material variance.
Close Job completed or a return visit created. Owner: Branch Manager. Signal: first-time completion and rework rate.
Bill Invoice raised against delivered work. Owner: Finance lead. Signal: unbilled completed work and discount rate.

Why job profitability declines while revenue looks stable

Revenue is recorded once, at invoice. Cost accumulates across the whole delivery chain: the estimate, the schedule, the drive, the time on site, the parts consumed, the second visit nobody planned for, the credit note issued a fortnight later. Revenue is therefore visible immediately and cost is visible late, which is why a branch can report a good month and a poor margin at the same time.

The second reason is aggregation. Group and branch reporting sums profitable and unprofitable work together, so a job type that loses money on every visit can sit inside a healthy total for several quarters. Leadership is not missing data. Leadership is missing the cut of the data at which the loss becomes a pattern with a name attached to it.

Scope accuracy: what was quoted and what was actually required diverge, and the gap is absorbed by the crew rather than repriced
Estimated versus actual labour: hours on site consistently exceed the estimate for specific job types, without the estimate ever being revised
Travel time: drive time between jobs is real cost that fixed-price and contract work rarely recovers
Material cost variance: parts consumed exceed the bill of materials, and the excess is not attributed back to the job
Overtime: used to protect a promise date, priced as though it were standard time
Discounts: applied in the field or at quotation without reference to the cost of delivering the work
Rework and repeat visits: logged as new jobs, so the original job still reads as profitable
Unbilled work: additional work performed, agreed verbally, never captured on the invoice
Job-type variation: two job types with similar revenue carry materially different delivery cost profiles
Branch variation: the same job type is estimated, scheduled and closed differently in each branch

What leadership usually sees too late

In most service networks, margin leakage reaches leadership as a month-end variance, several weeks after the jobs concerned were completed, invoiced and closed. By then the conversation is retrospective and the available levers are commercial rather than operational: raise price, cut cost, or push the branch harder. The operating cause has already produced its full effect.

Job-level margin is calculated after invoicing and credit notes, not while the job type is still repeating
Rework sits in a separate job record, so the true cost of the original job is never assembled
Unbilled work is only discovered when someone reconciles field records against invoices by hand
Discount authority is exercised locally and reviewed centrally, weeks later
Overtime is reviewed as a payroll line rather than as a job-cost line
Complaints and service recovery are handled by the branch and never connected to the margin picture
Branch variation is normalised because each branch defines job cost slightly differently

Which signals show job margin leakage early

The useful signals are the ones that move before the invoice does. Each is already recorded somewhere in field-service, scheduling, inventory, payroll or billing systems. The change is not new data collection. It is reading a small governed set weekly, by job type and branch, with definitions that are identical across the network.

Estimate-to-actual labour variance, trended by job type rather than by individual job
Travel time as a share of paid crew hours, by branch and route
Material variance against the expected bill of materials, by job type
Overtime hours attributed to jobs rather than to the payroll period
Discount rate and discount authority at point of sale
Rework rate and repeat-visit rate linked back to the originating job
Unbilled completed work ageing between job closure and invoice
Complaint and service-recovery volume concentrated on specific job types

How to separate an isolated job issue from recurring job-type leakage

The distinction determines the action. An isolated issue is a coaching or scheduling conversation. A recurring pattern is an estimating, pricing, contract or process decision, and treating it as a one-off means it repeats until the contract renews.

Three tests usually settle it. First, does the variance persist across multiple crews doing the same job type? If it does, the estimate is wrong, not the crew. Second, does it persist across multiple branches? If it does, the pricing or scope definition is wrong, not the branch. Third, does it persist across periods? If it does, it is structural, and the corrective action belongs to whoever owns the estimate or the contract, not to the person who happened to be on site.

One crew, one job type, one period: coaching, job readiness or a specific site condition
Many crews, one job type, one branch: local estimating or scheduling practice
Many branches, one job type, several periods: pricing, scope definition or contract terms
One branch, many job types: branch operating discipline, capacity or supervision

What poor job profitability costs across time, effort, money and quality

The cost is rarely a single number. It is distributed across the operating week and only some of it appears in the profit and loss account.

Time: margin reviewed after close, corrective action delayed by a full cycle, excess drive time absorbed into every route
Effort: manual reconciliation between field records and invoices, repeated follow-up with branches, job-by-job investigation to explain a variance
Money: eroded job margin, unbilled completed work, avoidable overtime, material variance and discounting that was never costed
Quality: repeat visits, inconsistent delivery of the same job type between branches, service commitments missed while crews return to earlier work
Trust: customers who experience a second visit for the same fault, and account managers who cannot explain why
Leadership confidence: branch performance debated rather than governed, because the numbers are not defined the same way twice

Which owner should act, and what action should follow

A surfaced pattern without a named owner becomes a standing agenda item. The role that owns the correction depends on where the variance originates, not on who reported it.

Estimating or Commercial lead: revise the estimate, scope definition and price for the job type
Branch or Operations Manager: correct scheduling, job readiness, supervision and crew mix at the branch
Service Delivery lead: address rework causes, first-time-fix and repeat-visit patterns
Finance lead: close the unbilled-work gap, govern discount authority and confirm job-cost definitions
COO: decide whether a recurring job type is repriced, redesigned or exited

Where job margin leaks and what leadership feels later The right hand column is usually the first version leadership sees, weeks after the operating cause in the left hand column was already measurable.

Cause	Consequence
Scope agreed loosely and never repriced	Actual hours exceed the estimate on every repeat of that job type; the estimate is never corrected
Travel time absorbed into fixed-price work	Route density problems appear as a branch margin gap with no obvious cause
Material variance not attributed back to the job	Inventory shrinkage is debated centrally while the job type keeps losing money
Overtime used to protect the promise date	Service level is held, margin is not, and the trade-off is never made explicitly
Rework logged as a new job	The original job still reads as profitable and the recurring fault is never priced or fixed
Work completed but never invoiced	Revenue is lost silently; the branch is measured on activity that was never realised
Discount applied at the point of sale	Price falls below delivered cost for a job type nobody has costed recently
Same job type run differently in each branch	Group margin masks a single-branch problem until the quarter closes

Which reading tells you where the leakage sits Read the columns together before acting. Repricing a job type when the cause is job readiness raises price without recovering margin, and coaching a crew when the estimate is wrong changes nothing.

Points to an estimating problem

Labour variance persists across crews and branches
Scope changes are frequent and rarely repriced
Material variance repeats for the same job type
Margin gap is stable rather than volatile

Points to a delivery problem

Rework and repeat visits concentrated on specific work
First-time completion falling in one branch
Overtime rising without a demand increase
Complaints clustered on the same job type

Points to a billing problem

Completed work ageing without an invoice
Credit notes recurring against the same job type
Discount rate rising ahead of cost
Revenue stable while realised margin falls

From surfaced margin pattern to owned action The sequence a weekly leadership review should follow once a margin pattern appears, so the meeting ends with an owner and a review date rather than a variance discussion.

Surface Name the job type, branch and period where delivered margin is below the trailing reading.
Classify Decide whether the cause is scope, labour, travel, material, overtime, rework, billing or discounting.
Assign Attach one accountable role: Estimating, Branch Manager, Service Delivery, Finance or COO.
Act Approve the structural change: revised estimate, repricing, scheduling change, billing control or contract discussion.
Review Set the review date and the existing signal that will show whether the change worked.

Worked example: stable revenue, falling margin on one recurring job type

A multi-branch field-service company reports revenue in line with plan for three consecutive months. Delivered margin declines over the same period. Branch leaders report no unusual events, and the group review treats the movement as a mix effect.

Symptom Revenue stable at group level; delivered margin below the trailing average, with no single branch obviously responsible.
Hidden operating signal One recurring job type shows actual labour running consistently past estimate, rising travel time share on the routes it sits on, and rework linked back to the same fault category.
Service consequence Customers on that job type experience a second visit more often, and promise dates are being held by overtime rather than by schedule design.
Margin consequence Every repeat of the job type erodes margin, and the erosion scales with volume, so a commercially successful job type is the one damaging the result.
Metric that reveals it Estimate-to-actual labour variance and rework rate by job type, read together with travel time share and margin by job type across branches.
Responsible owner Estimating lead for the estimate and price, Service Delivery lead for the rework cause, Branch Manager for scheduling and job readiness.
Immediate action Revise the estimate and scope definition for the job type, address the recurring fault cause, and review route design where that work is concentrated.
Leadership decision required Decide whether the job type is repriced, redesigned or restricted, with a named owner, a review date and a success signal before month-end close.

The company acts on the operating cause while the job type is still repeating weekly, rather than explaining a margin variance after the quarter has closed.

Illustrative example based on recurring patterns in multi-branch field-service operations. Not a specific client attribution. No figures are presented as benchmarks.

Leadership checklist for improving field-service job profitability

If more than two of these cannot be answered clearly at the weekly leadership review, the visibility layer is the constraint, not the branch.

Which job type is losing margin?
Is the issue scope, labour, material, travel, rework or billing?
Is the leakage isolated to one crew or recurring across the network?
Are services being delivered but not billed?
Is discounting masking the real cost of delivery?
Is overtime protecting a promise date that the schedule should have protected?
Which branch or crew needs attention, and for which reason?
Which owner is responsible for the corrective action?
Is the issue visible before month-end review?

Executive FAQ

Why does margin fall while revenue holds?: Revenue is confirmed once, at invoice. Cost accumulates across estimating, travel, time on site, materials, overtime, rework and credit notes, and most of it is recorded after the job is closed. A job type can therefore grow in volume, hold revenue steady and reduce group margin at the same time. The distinction only becomes actionable when delivered cost is assembled per job and compared with what was finally billed.
What is the smallest useful set of metrics to start with?: Four: estimate-to-actual labour variance by job type, travel time share by branch, rework or repeat-visit rate linked to the originating job, and unbilled completed work ageing. Those four separate estimating problems from delivery problems and billing problems. Add material variance and discount rate once the definitions are consistent across branches.
How do we know whether to reprice or to fix delivery?: Test persistence. If the variance holds across multiple crews and multiple branches doing the same work, the estimate or the price is wrong. If it is concentrated in one branch or one crew, delivery, scheduling or job readiness is the cause. Repricing a delivery problem raises price without recovering margin, and it usually costs volume.
How should unbilled work be handled without creating disputes?: Treat it as a process gap rather than a recovery exercise. Measure the ageing between job closure and invoice, identify where in the flow the additional work stops being captured, and fix the capture step. Retrospective billing of work agreed verbally weeks earlier damages the customer relationship more than the recovered value justifies.
Should crew-level cost variance be used in performance reviews?: Cautiously. Crew-level variance is useful for coaching and for identifying job readiness or skill-matching problems. Used as a ranking, it encourages under-recording of time and materials, which removes the very signal leadership needs. The reliable unit of accountability is the job type and the branch, not the individual.
Does Garuda replace FSM, dispatch, scheduling, CRM, ERP or payroll systems?: No. Garuda is a decision layer above those systems. It reads job, route, crew, branch, service and financial signals and presents a governed executive view of where margin is moving and who owns the response. It does not schedule jobs, dispatch crews, optimise routes, hold customer records or process payroll.

Sources and further reading

How Garuda supports field-service job profitability visibility

Garuda connects job, route, crew, branch, service and financial signals from the systems a field-service business already runs, surfaces the exceptions that need leadership attention with consequence and context, supports ownership and follow-up on each surfaced pattern, and lets executives ask operational questions across those connected systems. Garuda does not replace FSM, dispatch, scheduling, CRM, ERP, payroll or technician applications, and it is not a route optimisation engine.

See How Garuda supports field-service job profitability visibility

Related analysis

Assess where field-service job margin visibility is delayed

Walk through where estimate, labour, travel, material, rework, billing and branch signals are reaching leadership after the margin has already moved. See Garuda in action during the same session.

Assess where field-service job margin visibility is delayed