Joel LeeIf your shop runs custom jobs, you've felt this before: month end is ten days out, you pull up your open job list, and you have no fast way to know which ones are healthy and which ones are bleeding margin. Knowing how to see which open jobs are at risk before month end close is not a reporting question. It's a data structure question. The answer depends entirely on whether your job records capture quoted versus actual costs as work progresses, not just at close.
What "at risk" actually means for an open job
An open job is at risk when its actual cost trajectory, if continued to completion, will produce a margin lower than what was quoted. That definition matters because it moves the conversation away from "did we hit budget" and toward "what will this job actually yield." A job can be within budget today and still be at risk if two-thirds of the work is done and the remaining scope is the most labor-intensive part.
The three main drivers of margin erosion on custom jobs are labor overruns, unplanned material costs, and scope changes that were absorbed without a change order. All three have early signals. The problem for most shops is that those signals are buried in timesheets, purchase orders, and email threads, and no one aggregates them until the job is closed.
The data you need, and where it usually lives
To catch at-risk jobs early, you need four numbers per job, updated continuously: estimated labor hours, actual labor hours to date, estimated material cost, and actual material cost to date. Those four numbers let you calculate a simple cost-to-complete projection. If the projected total cost exceeds the quoted cost at current burn rates, the job is at risk.
For most engineer-to-order and make-to-order shops, those numbers live in at least three separate places. Estimated hours and material costs are in the quote or the BOM. Actual labor hours are in timesheets or a time-tracking app. Actual material costs are in purchase orders or the accounting system. The aggregation almost never happens automatically. Someone has to pull it together, and in most shops, that only happens at job close.
Connecting job costing to your accounting system is one piece of this, but the accounting integration alone doesn't give you job-level margin visibility during production. You need the job record itself to carry the comparison.
A decision rule you can apply this week
Here is a practical filter you can run on your open job list right now, without building a new system. Pull every open job that meets any of these three conditions: actual labor hours are above the estimate, a purchase order exists for a material line that was not in the original BOM, or a scope change was requested but no revised estimate was issued. Any job that meets one condition is worth a five-minute review. Any job that meets two or more conditions needs a conversation with the foreman or project lead before the end of the week.
This filter doesn't require software. It requires that someone has access to timesheets, open POs, and the original quote at the same time. The real value of building a system around this is making that access automatic, not reserved for whoever has time to hunt through three tabs.
Assigning job ownership from engineering to shop floor matters here because a job without a clear owner is a job where nobody is watching the cost signals. Ownership and visibility have to be set up together.
How labor cost overruns show up before invoicing
Tracking labor cost overruns on custom fabrication jobs before invoicing is a matter of comparing time entries against the labor estimate at a task or phase level, not just at the job total. Job-total comparisons are too coarse. A job can be within budget at the total level while one phase, say, fit-up or final inspection, is running 40 percent over because of rework. By the time the overage is visible at the total level, most of the labor has already been spent.
The phase-level labor review
Break each job's labor estimate into at least three phases: pre-production (engineering, procurement, setup), production (fabrication, assembly), and post-production (inspection, finishing, shipping prep). Track time against each phase separately. When actual hours in any phase exceed the estimate for that phase by more than 20 percent, flag the job for review before moving to the next phase. This catches the overage while there is still time to adjust scope, add resources, or issue a change order.
What to do when you find a labor overrun mid-job
A mid-job labor overrun has three possible responses: absorb it and protect the delivery schedule, issue a change order if the overrun traces to customer-requested scope, or reduce scope elsewhere to recover margin. The wrong response is to do nothing and hope the remaining phases come in under estimate to compensate. In custom manufacturing, remaining phases almost never come in under estimate when earlier phases ran over. The rework or complexity that caused the early overrun usually persists.
Tracking material cost variance during production
Material cost variance against estimate during production is the difference between what the BOM said materials would cost and what purchase orders and receipts show they actually cost. This variance has two components: price variance (the supplier charged more than the quote) and quantity variance (more material was used or ordered than planned).
Price variance is usually visible the moment a PO is issued, if someone is comparing PO prices to the estimate. Quantity variance becomes visible when materials are issued from inventory or when additional POs are raised mid-job. Both types of variance should trigger a job review, because either one can turn a quoted 30 percent gross margin into a 15 percent margin by the time the job ships.
The most common failure mode here is that material purchases are tracked in the accounting system but not linked back to the job record in a way that's visible to operations. The accountant knows the PO was issued. The shop manager doesn't know it was 12 percent over estimate. That gap is where material margin erosion hides until month-end close.
Building real-time job margin visibility for engineer-to-order work
Real-time job margin visibility for engineer-to-order manufacturers means having a single view, updated at least daily, that shows each open job's current estimated margin versus its projected margin based on costs incurred to date. This is different from a job cost report run at close. The point is to see the projection while there is still time to act.
Our systems scoping sprint is designed to map exactly this kind of workflow: where your cost data lives, what your job record structure looks like, and what the shortest path is to surfacing at-risk jobs before they close. The build is almost always simpler than shops expect, because the data already exists. It's the aggregation and the alert logic that's missing.
The failure mode to recognize early
The most common early warning sign that a job is going to miss margin is not a cost overrun. It's a job that enters production without a finalized bill of materials or a confirmed labor estimate. When a job starts before the estimate is locked, every cost incurred during production is being compared to a moving target. By month-end, the cost data exists but the baseline to compare it against is ambiguous. The job may look fine on paper because the estimate was adjusted upward to match actuals, rather than actuals being measured against the original estimate. If your closed job reports consistently show margins close to estimate but your cash position tells a different story, this is likely what's happening.
What a working at-risk job report looks like
A practical at-risk job report for a custom shop has one row per open job and five columns: job number, quoted margin, projected margin based on costs to date, primary risk flag (labor, material, or scope), and the name of the person accountable for the job. It is sorted by the gap between quoted margin and projected margin, largest gap first. It is reviewed weekly, not monthly. The jobs at the top of the list get a conversation. The report does not need to be built in expensive software. It needs to be built on reliable data.
See how we approach these builds
Frequently asked questions
How do I know if a job is going to miss margin before it closes?
Compare actual labor hours and material costs incurred to date against the original estimate, then project those burn rates forward to completion. If the projected total cost exceeds the quoted cost, the job is at risk. The earlier in production you run this comparison, the more options you have to recover margin through scope adjustment or a change order.
What's the earliest signal that a custom job is in trouble?
The earliest signal is usually a job that enters production without a locked estimate or a finalized bill of materials. When the baseline is unclear at the start, cost overruns accumulate without a clear reference point, and the problem only becomes visible at close when it's too late to act.
How often should we review open job margins during production?
Weekly is the right cadence for most custom shops. A monthly review only catches problems after month-end close, when the job may already be invoiced. A weekly review gives you at least two to three decision points during a typical three-to-six week job where you can still adjust scope, issue a change order, or reallocate resources.
Do we need new software to track job margin in real time?
Not necessarily. Many shops already have the underlying data in timesheets, purchase orders, and their accounting system. The missing piece is usually the aggregation: a structured way to pull those numbers into a single job view on a regular schedule. Whether you need new software depends on how fragmented your current data sources are and how many open jobs you're managing at once.
What's the difference between a job cost report and a real-time margin view?
A job cost report is typically run after a job closes and shows what actually happened. A real-time margin view shows projected margin on open jobs based on costs incurred so far, updated continuously during production. The job cost report is useful for estimating future jobs. The real-time view is what lets you catch and correct margin erosion before the job ships.
If this sounds like a handoff your manufacturing operation keeps fighting, bring us the specific workflow. Start a free scoping sprint. We'll map the people, data, tools, and decisions involved, and you'll leave with a comprehensive build plan whether or not you work with us.
