SERVICE WORK VS NEW CONSTRUCTION. JOB COSTING.
Service and repair work is typically short duration, billed T&M or at a flat rate per call, and doesn't need percentage of completion WIP tracking. New construction runs long, runs phased, and depends on WIP to show overbilling and underbilling. A subcontractor doing both is running two different businesses inside one company, and the job costing has to reflect that. Force both through the same cost code and reporting structure and one of them, usually the service side, ends up misrepresented.
The reason sits in the underlying cost logic, well beneath the labels on the codes. Profit on a service ticket is labor and material against what was billed, settled in days. Profit on a construction job is cost to complete against a specific estimate, settled over months, and the only way to see whether billing is ahead of or behind progress is a WIP schedule. A code set built for mobilization, rough-in, and finish doesn't map onto a same day call, so service work gets crammed into whichever generic code is closest and the detail disappears. The fix is two tracks inside one system, not two accounting systems.
WHAT EACH ONE DOES.
| Capability | Service and Repair Work | New Construction |
|---|---|---|
| Typical duration | Hours to days | Weeks to months |
| How it bills | T&M or a flat rate per call, against a ticket | Percentage of completion against a specific estimate |
| Cost code structure | Ticket level codes by call type | Phase codes, mobilization, rough-in, and finish |
| WIP schedule | Generally not needed, no long timeline for cost to outrun billing | Required, it's the only way to see overbilling and underbilling |
| How profit gets measured | Labor and material against what was billed, ticket by ticket | Cost to complete against the estimate, month by month |
| How fast a problem surfaces | Within days, on the ticket | Only when someone reviews cost to complete |
| Overhead allocation | By the activity service work consumes | By the activity construction work consumes |
| What breaks when the two are blended | Ticket profitability disappears inside construction job reports | The overbilling and underbilling calculation is missed entirely |
| Financial statement rollup | Feeds one set of statements | Feeds the same set of statements |
Both tracks roll up into the same financial statements and the same overhead allocation, so the company still sees one coherent picture while each type of work gets tracked with the logic that fits it.
WHEN THE JOB IS DONE IN A DAY.
Service and repair work is short duration, ticket based, and billed T&M or at a flat rate per call. Job profitability on a service ticket is a straightforward comparison of labor and material cost against what was billed, and it resolves in days rather than months. There's no long construction timeline for cost to run ahead of billing, so there's no meaningful WIP position to track.
What service work needs instead is ticket level cost codes by call type and a T&M billing reconciliation, so you can see which kinds of calls earn and which ones don't. Applying WIP logic here adds complexity without telling you anything new. The risk on this side is size, because even a small share of revenue from service work can carry outsized damage if it loses money inside blended job cost reports built for construction jobs and nobody sees it.
WHEN THE JOB RUNS FOR MONTHS.
New construction runs for weeks or months, bills against a percentage of completion schedule tied to a specific estimate, and requires ongoing WIP tracking to show whether billing is ahead of or behind the work completed. The cost codes follow the phases of the job, mobilization, rough-in, and finish, because that's how the estimate was built and that's the only comparison that tells you whether the job is tracking.
Run the other direction and it breaks just as badly. Apply the T&M service billing logic to a new construction job and you miss the overbilling and underbilling calculation entirely, because T&M billing never needed a percentage of completion comparison. The two types of work require different cost tracking logic, not just different cost codes, and that distinction is the whole decision on this page.
WHERE WE COME OUT.
The fix isn't two accounting systems. It's two distinct cost code and reporting tracks inside one job costing structure, a service track with ticket level cost codes and T&M billing reconciliation, and a construction track with phase based cost codes and a full WIP calculation. Both roll up into the same financial statements and the same overhead allocation, so you get one coherent picture of the company while each side of the business gets measured the way it works.
Five things carry most of the weight. Separate cost code structures for service tickets and construction phases rather than one generic set. WIP applied only to jobs with a percentage of completion billing structure. T&M ticket profitability tracked ticket by ticket instead of blended into construction job cost reports. Overhead allocated across both types of work based on the activity each one consumes rather than a single blended rate. One set of financial statements at the top with both tracks feeding in correctly underneath.
The three beliefs we hear most are all the same mistake wearing different clothes. Construction cost codes for service tickets loses the detail that tells you which calls earn. A WIP schedule for everything adds work and tells you nothing on the service side. And service work being a small share of revenue isn't a reason to skip tracking it, because a small share that loses money is the kind of problem that hides best inside a blended report.
FREQUENTLY ASKED.
