Job Costing for Subcontractors: A Practical Guide

Last updated: July 2026

Job costing for subcontractors answers one question: is this job going to make the money we bid it at, and is it doing that right now?

A company-level profit and loss statement cannot answer that for a commercial electrical, mechanical, concrete, drywall, roofing, or finishes contractor running many jobs at once. It can show whether the company made money overall. It cannot show whether job 412 is carrying job 407, whether one GC’s work is draining office time, or whether labor on a specific phase is already burning past the estimate.

That is why job costing has to happen while the work is still moving, not only after the accountant closes the books. Done after closeout, it explains what happened. Done during the job, it gives the office and field a chance to adjust labor, protect change-order revenue, update cost-to-complete projections, and price the next bid with fewer surprises.

For survey context on project-level profitability, read Profitability at the Project Level: Job Costing for Subcontractors. This guide is the practical version: how to structure the budget, capture the right costs, read the projection, and use the answer before the job is over.

For the broader project-management argument behind this guide, read What Project Management Actually Means for a Specialty Subcontractor. The short version: project management produces the inputs. Job costing turns those inputs into the answer.

Job costing for subcontractors is the practice of tracking each job’s labor, materials, committed costs, and approved revenue against the estimate, by cost code, while the job is still running. It is different from company-level accounting because it measures job-level profitability, not just overall company performance.

What You Need Before You Can Job Cost

Job costing starts before the first invoice lands.

The baseline is the estimate. If the estimate does not become the job budget, job costing turns into expense tracking with a job name attached. You can see money going out, but you cannot tell whether the job is performing against what you bid.

That budget also needs structure. In construction job costing, cost codes break the job into categories so actual costs can be compared to the estimate at a useful level of detail. A cost code might separate rough-in labor from trim labor, conduit from devices, slab prep from pour, or framing from finishing. The exact structure depends on the trade.

The practical rule is simple: the cost code structure should mirror how the job was estimated.

If the estimator built the bid by phase but the field codes costs by broad category, the comparison breaks. If the accounting system tracks labor, material, and equipment but the estimate was built by floor or area, the office will spend the whole job translating one structure into another.

Granularity is the tradeoff. Too few codes and problems hide inside big buckets until it is too late. Too many codes and the field stops coding accurately, which is worse. Most subs need a modest set of codes tied to how they estimate, schedule, and review work.

Consistency across jobs is what makes the data useful over time. The same codes used job after job create estimating feedback. The second year of consistent job cost tracking can tell a contractor which phases keep missing, which crews beat budget, and which work should be priced differently.

The Four Inputs: Labor, Materials, Commitments, and Revenue

A workable job cost report compares four inputs against the estimate: labor at a burdened rate, materials, committed costs, and revenue including approved change orders.

Labor at a Burdened Rate

Labor is usually the cost that decides the job because it is both large and hard to recover once it drifts.

Hours need to be coded to the right job and the right cost code close to when the work happens. A Friday timesheet reconstructed from memory may look clean in a report, but it is often a polished guess. That is dangerous because the number looks precise enough to trust.

The rate matters too. Job costing should use a burdened labor rate, not just the wage rate. A burdened labor rate includes the employer costs attached to labor, such as payroll taxes, workers compensation, insurance, benefits, and other labor burden. Costing a crew at wage rate understates the job every time.

For the full labor-rate breakdown, read Why Your Labor Costs Are Probably Wrong and What It’s Costing You on Every Job.

Materials

Materials look straightforward until the job starts moving.

An invoice may arrive days or weeks after delivery. Material bought for one job may get used on another. Stock from the shop may be pulled without a clean transfer. A PM may know the material is on site, while accounting has not seen the bill yet.

The fix is discipline around job assignment. Purchases, deliveries, transfers, and returns need to land on the right job and, where possible, the right cost code. Otherwise, one job looks better than it is and another looks worse for reasons nobody can see.

Committed Costs

Committed costs are costs the company has already agreed to but has not been invoiced for yet.

That includes purchase orders, executed subcontracts, rentals, vendor commitments, and approved orders that have not hit accounts payable. In construction, committed costs are the difference between a real projection and a backwards-looking report.

Costs to date tell you what has happened. Committed costs tell you what is already going to happen.

A job can look under budget if the report only shows invoices received. Add the open purchase order, the committed rental, and the pending vendor bill, and the job may already be over. Cost to complete needs both actual costs and commitments.

Revenue and Approved Change Orders

The revenue side is the original contract plus approved change orders.

Pending change work should be tracked separately from approved change orders. The cost of changed work lands in the job the day the crew performs it. The revenue only exists when the change is approved.

That creates two opposite risks. A job can look like it is losing money because it is carrying change work that has not been approved yet. A job can also look fine while accumulating pending change work that may never become revenue.

Both errors create bad decisions. Track approved changes as revenue. Track pending changes as exposure. Keep the distinction visible.

For more on the change-order profit leak, read The Change Order Problem: Why Subcontractors Are Leaving Money on the Table After the Bid Is Won.

How to Tell Where the Job Will Finish

Costs to date tell you where the job has been. Job cost tracking becomes useful when it helps project where the job will finish.

That usually means looking at percent complete, cost to complete, and estimate at completion.

The cost-to-cost method calculates percent complete as costs to date divided by the current estimated total cost. It is common because it uses hard cost data. It also has a real weakness: costs do not always move in the same pattern as physical progress.

Budget spent is not work completed.

A mechanical contractor might buy major equipment early. A drywall sub might have material staged before installation catches up. A concrete contractor might spend heavily before the work is physically far along. In those cases, cost-to-cost percent complete can overstate progress if nobody adjusts the estimate at completion.

The field-observation method works from actual physical progress. A foreman or PM assesses what has been installed or completed. That can be closer to reality, but it depends on someone walking the job honestly and consistently.

The best practice is to use both views together. Let cost data show what has been spent. Let the field confirm what is actually complete. Then revise the current estimated total cost when conditions change.

Holding the original bid number as the estimated total cost after the job has changed produces a clean report with a false answer. Profit fade, where margin shrinks as the job progresses, often shows up when cost-to-complete estimates were not updated early enough.

Where Job Costing Breaks in Practice

A job costing system usually fails in predictable ways.

Late or memory-coded timesheets. The symptom is a labor report that arrives too late to act on. The cause is field data captured after the week has already blurred. The fix is faster time capture, simpler codes, and review while the crew still remembers the work.

Costs landing in overhead. The symptom is jobs that look better than the companyfeels. The cause is unassigned job costs buried in overhead or general expense. The fix is a monthly scan for uncoded costs and a rule that job-related spend needs a job.

Materials moving between jobs. The symptom is one job carrying material cost that another job consumed. The cause is field reality moving faster than paperwork. The fix is a simple transfer habit: when material moves, the cost moves too.

Change work performed before approval. The symptom is cost appearing before revenue. The cause is extra work getting done because the field has to keep the job moving. The fix is a separate pending-change log that tracks cost exposure until approval.

Retainage treated like cash. Retainage may be earned in the work performed, but it is withheld under the contract and often remains unavailable as cash until contract conditions are met. It is commonly 5 or 10 percent, though the actual amount varies by contract and jurisdiction. Treating retainage like available cash distorts the financial picture even when the job cost itself is accurate.

Estimated total cost never revised. The symptom is a job that looks fine until the end, then falls apart. The cause is a projection tied to the original bid after conditions have changed. The fix is a current estimate at completion, reviewed regularly.

Cost codes that do not match the estimate. The symptom is reports nobody trusts. The cause is actuals coded in a structure that cannot be compared to the bid. The fix is to align the budget, field codes, and accounting codes before the job starts.

Job Costing vs WIP vs Accounting

Job costing, WIP reporting, and construction accounting are related, but they are not the same thing.

‍

The one-line version: job costing tells you what a job is costing you. WIP tells you what you have earned versus what you have billed. Accounting tells the outside world what all of it added up to.

For a construction accounting view of WIP, see CFMA’s discussion of WIP schedules, underbilling, overbilling, and margin fade.

Costing by GC, Not Just by Job

Job costing should not stop at the job.

A specialty subcontractor should also roll job results up by general contractor. Which GCs’ jobs are consistently profitable? Which ones look good at bid time but create coordination problems, change-order friction, slow payment, or extra office work?

Two jobs with the same bid margin are not equal if one GC approves changes in a week and pays in 30 days while another disputes everything and pays in 90. The second job costs more to run and more to finance.

This is where job costing loops back to preconstruction. Profit-by-GC becomes bid and no-bid intelligence. It tells the office which invitations deserve estimating time, which relationships need risk priced in, and which jobs may not be worth chasing at all.

For the bid-side view, read Bid Management Software for Subcontractors.

How Subs Actually Run This

Subcontractors usually run job costing through one of three approaches.

1. A job costing spreadsheet can work at low job counts. It is flexible, cheap, and familiar. It breaks when manual entry gets stale, versions multiply, formulas change, or field data arrives too late for the spreadsheet to guide decisions.
2. Accounting software with job costing is strong for cost capture and the financial record. It can track costs by job, which matters. The gap many subs hit is operational: getting field hours in quickly, coding them correctly, carrying the estimate in as the budget by cost code, and reflecting committed costs before invoices arrive.
3. Project management software with job costing built in is strongest when it connects field data, job budgets, change tracking, and actual costs in one workflow. Depth varies widely by product. Some tools track a simple budget-versus-actual number. Others go deeper into cost codes, commitments, labor, and change orders.

The right question is not which category sounds most advanced. Ask how many jobs you are running, how fast field data needs to reach the office, whether the estimate becomes the budget, and whether the cost report can still change the outcome while the work is underway.

For the software distinction, read GC Software vs. Subcontractor Software: What’s the Difference?.

FAQ

What is job costing in construction?

Job costing in construction means tracking the costs of a single job against that job’s estimate, usually by cost code. For subcontractors running several jobs at once, it shows which jobs are making money while there is still time to adjust labor, costs, change orders, or billing.

What’s the difference between job costing and WIP reporting?

Job costing tracks what a job is costing against its budget as an operational tool. WIP reporting compares earned revenue to billed revenue across active jobs for accounting, lenders, and sureties. Job costing feeds WIP, but they are not the same report.

Can you do job costing in QuickBooks?

Yes, QuickBooks can track costs by job or project, which covers part of the job costing workflow. The gaps many subs hit are field-hour capture, cost-code detail, estimate-to-budget comparison, committed costs, and construction-specific change tracking. Many contractors pair accounting software with an operational system.

What are cost codes and how many should I use?

Cost codes divide a job into categories so actual costs can be compared to the estimate. Use enough codes to see where the job is drifting, but not so many that the field codes work inaccurately. The right structure mirrors how you estimate and schedule the work.

Why do my jobs look profitable until the end?

Usually the projection is missing something. Common causes include committed costs not counted until invoices arrive, an estimated total cost that was never revised, labor coded late from memory, or change work performed before approval. Each makes the job look better than it really is.

How often should job costs be reviewed?

Review job costs frequently enough to act. Weekly is a practical rhythm for active commercial jobs, with labor coded within days rather than at month-end. A report that arrives after the crew has moved on is still useful history, but it is no longer a decision tool.

Closing

Job costing for subcontractors is the discipline of comparing the estimate to what the job is actually consuming while the job is still running.

Done after closeout, it explains what happened. Done during the job, it helps a sub protect margin, choose better work, and price the next bid with fewer surprises.

For the parent article, read What Project Management Actually Means for a Specialty Subcontractor. For the GC/sub software distinction, read GC Software vs. Subcontractor Software: What’s the Difference?. For labor costing detail, read Why Your Labor Costs Are Probably Wrong and What It’s Costing You on Every Job. For the bid-side loop, read Bid Management Software for Subcontractors.

Last updated: July 2026