THE MARGIN LEAKS HIDING IN PROJECT BUSINESSES

A project business can be busy, growing, and still lose money on jobs it thought were profitable.

The margin leak often starts before the contract is signed. Engineers spend time on plans. Someone pays for blueprints. An estimator works through revisions. A project manager starts answering questions. Meanwhile, the job number may not exist yet, or the time gets coded to overhead because nobody is sure where it belongs.

I was in a job-costing conversation recently where the company already had a cradle-to-grave job number. The system was capable of tracking the work. The gap was behavior. People were working on the job, but the costs were not always landing on the job.

One line from the conversation captured the problem: “If the date wouldn't have been there, then I wouldn't have been able to catch it.” A date exposed work that had already happened but was not connected to the project clearly enough for accounting to see.

That is the big idea. Project margin improves when the job has an owner, a budget, and a weekly rhythm from the moment the opportunity becomes real. The final job review matters, but it comes after most of the decisions that shaped the result.

PRE-CONTRACT WORK HAS NO HOME

Many teams start measuring a project when the contract is signed. The work often starts weeks earlier. Engineering, estimating, blueprint, and sales support time can accumulate before anyone has decided how to treat those costs.

The answer does not require every early conversation to become a permanent job. Open a job when the opportunity becomes real, capture the work against it, and close failed opportunities into estimating expense when they end. That gives the business a record of what it spent to win work and keeps those costs from vanishing inside overhead.

Opening jobs early creates a second discipline. Dead opportunities need a clean closeout. In one project-based business, roughly one quarter of opened job numbers never accumulated billed time. That kind of pipeline is manageable when the business can distinguish a real project from an inquiry that never became work.

THE BUDGET LIVES IN TOO MANY PLACES

Accounting should not have to search through folders to figure out which estimate represents the current plan. When three worksheets carry different labor, material, equipment, or subcontractor assumptions, the business has no stable starting point for a margin conversation.

The estimate needs to serve as the job intake record. Keep one approved version with the contract amount and four visible cost buckets: labor, materials, equipment, and subcontractors. When costs arrive, the team should know exactly which budget they are being compared against.

A margin report cannot answer whether a job is healthy when the original budget is scattered across folders and versions. The math may be correct. The question underneath it remains unsettled.

THE LESSON ARRIVES AFTER THE JOB IS CLOSED

Sales teams want to win work. Delivery teams want to complete it. Finance wants to understand what happened. Each goal makes sense, and the margin can still disappear between them.

In one review of larger jobs, several deliveries had been priced incorrectly. The business absorbed the loss because the mistake was not caught early enough. A short monthly review for large or unusual jobs gives the team a place to compare the estimate, actual cost, change orders, and final margin while the details are still fresh.

A completed job should produce more than revenue and a final margin. It should produce a better estimate for the next job.

The operating rhythm is simple. The hard part is assigning ownership and keeping the rhythm alive when the business gets busy.

1. OPEN THE JOB WHEN THE OPPORTUNITY BECOMES REAL. Create the job number when engineering, estimating, blueprint work, or meaningful project planning begins. Give someone responsibility for deciding when the opportunity is active, when it is lost, and where the early costs go. You need consistency and tracking all the way through.
2. CAPTURE PRE-CONTRACT COSTS. Make time and direct expenses easy to code against the job. Include engineering hours, estimating work, blueprint costs, and other meaningful effort. When an opportunity is lost, move the accumulated cost to estimating expense so the business can see what it spent to pursue the work.
3. KEEP ONE APPROVED BUDGET. Use the estimate as the intake record and preserve the current approved version. Show the contract amount and the budget for labor, materials, equipment, and subcontractors. If the scope changes, record the change instead of quietly replacing the original assumption.
4. REVIEW ACTUAL COST AGAINST BUDGET EVERY WEEK. The weekly job-cost report should give the project manager enough information to change the outcome while the job is active. It can show labor as a lump sum and exclude revenue when managers only need cost visibility. That protects payroll privacy while keeping the operating conversation useful.
5. HOLD A SHORT REVIEW AFTER LARGE OR UNUSUAL JOBS. Look at your jobs and set a threshold of when they rise to the level of needing a review. Big enough that they’re complex and not so small that you waste your teams time. At the start, maybe review all but quickly refine it so you can spend time on the jobs that matter. Ask what was estimated, what happened, what changed, and what should be priced differently next time. Require the project manager to explain the result to ownership and accounting.

A weekly job-cost report and a monthly WIP review serve different purposes.

The weekly report compares actual costs to budget by labor, materials, equipment, and subcontractors. It is designed for action. A manager can see that material costs are running ahead of plan, that hours are being spent outside the original scope, or that a subcontractor bill has arrived late enough to change the picture.

The monthly WIP review goes deeper into job status, invoicing, completion, and collection. It helps the business understand how project progress connects to revenue and cash. A job-costing system can show useful information, but the WIP review still depends on a close process people trust.

This is where reporting cadence changes behavior. A monthly report explains what happened. A weekly report gives the manager a chance to change what happens next.

If the field and accounting teams work from different versions of progress, the answer may sit upstream of the finance report. Project-based businesses often need a clean field-to-accounting handoff for job status, time, progress reports, and receipts. One engineering services firm solved that gap with a simple submission tool that routed field information into a queue accounting could manage. The technology mattered because it connected the operating work to the financial record.

The same principle applies to job reviews. A project manager should be able to see the budget, actual costs, open commitments, and known changes without asking accounting to rebuild the story every week.

Pull the last five completed jobs. For each one, compare the original estimate, actual cost, change orders, and final margin. Look for the largest unexplained gap.

Then ask where the gap first became visible. Was it pre-contract time that never reached the job? A budget change that lived in another worksheet? A cost that arrived after the manager thought the job was safe? A pricing assumption that nobody revisited?

Use that one job to design the first process change. Add the job-opening rule, clean up the estimate record, or start the weekly review. You do not need a perfect job-costing system before you begin. You need one clear owner and a rhythm that surfaces the problem while someone can still act.

Margin improves when the business learns before the next job, not when the owner discovers the miss after the books are closed.

If you want to find the gaps between operational work and financial reporting, book a Cash & Profit Diagnostic.