The Job Closeout Checklist That's Costing You Cash

The Most Expensive Jobs in Your System

The most expensive jobs in your system aren't the ones losing money. They're the ones that are done but not closed.

Work is complete. The tech packed up weeks ago. The customer is happy. But the job is still sitting open in your field service software because somebody hasn't reviewed the billing, or a PO never got receipted, or nobody documented the resolution. Meanwhile, the WIP stays on your balance sheet, the final invoice hasn't gone out, and the margin you think you earned is fiction.

I see this constantly. One HVAC contractor I work with asked their coordinator to pull a simple report: "What are the jobs that are complete but not closed, and what's missing?" The answer was dozens of jobs in limbo, some for months. Each one had a different gap: billing not finalized, procurement not reconciled, review status stuck in a queue nobody checks.

This is one of the biggest hidden cash flow drags in contracting. And it's entirely fixable.

The Closeout Gap

Here's what the data shows on closeout efficiency, the time between job completion and formal job close:

That gap between median and average tells the whole story. Most jobs close fast. But a small number of stale closeouts drag the average from 1.7 days to 14. Those aren't statistical outliers. They're real jobs with real costs trapped inside them.

Compare this to billing speed: the median time to first invoice is 2 days. So most contractors are invoicing quickly, but the formal closeout lags behind. Jobs get invoiced but never officially closed. That means the WIP never clears, the budget-vs-actual reconciliation never happens, and the job keeps accruing costs nobody notices.

Now layer on job duration data: 11.2% of jobs stay open past 90 days. Many of those aren't active work. They're completed jobs that never got through the closeout process. The work finished. The paperwork didn't.

What Unclosed Jobs Cost You

1. Trapped WIP on Your Balance Sheet

An open job carries work-in-progress. Labor, materials, subcontractor costs. All sitting as assets on your balance sheet until the job closes and the costs hit your P&L. If you have 50 jobs that are effectively done but technically open, you could be carrying six figures in phantom WIP that overstates your financial position.

This matters when you go to a bank for a line of credit. It matters when your bonding company reviews your financials. It matters when you're trying to understand whether last quarter was actually profitable. Trapped WIP makes every financial report a little less trustworthy.

2. Unbilled Work

Closeout and invoicing are supposed to be parallel tracks, but in practice, they drift. A job that hasn't been formally closed often has a billing gap. Maybe the final invoice was 90% of the contract value, and the remaining 10% is waiting on a change order that was never entered. Maybe the last progress bill went out two months ago and nobody sent the final.

The closeout process is what catches these gaps. Without it, the unbilled amount sits indefinitely. On one contractor's books, we found $87K in unbilled revenue across 34 unclosed jobs. All of it was billable. None of it had been invoiced because nobody had done the closeout review.

3. Cost Still Accruing

A job that's open in the system is a job that techs can log time against. And they do. A follow-up visit, a callback, a warranty check. The tech sees the job in the system, assumes it's still active, and logs their hours. Nobody flags it because the job is technically open.

This is how 40% of jobs end up exceeding budgeted hours. The original scope was profitable. But two months of post-completion time entries eroded the margin to zero. If the job had been closed on completion, that time would have been logged against a new job (warranty, callback, service agreement) where it could be tracked and costed properly.

4. Inaccurate Backlog Reporting

Your backlog number is one of the most important planning metrics in contracting. It tells you how much committed work you have ahead. But if your backlog includes dozens of jobs that are actually complete but not closed, the number is inflated. You think you have $2M in backlog. In reality, $400K of that is completed work that just hasn't been closed out. You're making hiring decisions, equipment purchases, and capacity plans based on a number that's 20% too high.

The 6-Point Closeout Checklist

This comes from a real contractor workflow, built by their project coordinator to answer one question: is this job actually done?

A job isn't truly closed until all six conditions are met:

Each check targets a specific failure mode:

Review Status catches jobs where the PM or supervisor never signed off on the work. If nobody reviewed the job, nobody verified the scope was completed, the hours were reasonable, and the customer was satisfied. This is especially critical on jobs where labor ran over budget.

Billing Status catches revenue leakage. "Fully Invoiced" means every dollar of contract value, including approved change orders, has been billed. Not "mostly invoiced." Not "we sent a progress bill." Fully invoiced.

Invoice Status confirms the invoice was actually sent, not just generated. Plenty of contractors generate invoices that sit in a queue. The invoice exists in the system but was never emailed or mailed. That's not billed. That's a PDF nobody's seen.

Procurement Status closes the materials loop. If POs were issued for a job, were the materials received? If they were, did the receipts get posted? Open POs on a closed job mean materials costs that aren't reconciled, which means your job costing in QuickBooks is wrong.

Receipt Status is the accounts payable side. Were vendor invoices received, matched to POs, and posted? If materials were received but the receipt wasn't posted, you have a cost that exists in the real world but not in your books. Your job margin looks better than it is.

Resolution Notes are the qualitative check. What was the problem? What did you do? What was the outcome? This isn't just documentation for documentation's sake. Resolution notes are what allow the next tech to understand the job history, what allow the PM to explain scope changes, and what protect you in a dispute. A job closed without resolution notes is a job that will generate questions later.

How to Implement Weekly Closeout Review

Step 1: Run the Report

Every week, pull a list of all jobs where work is marked complete but the job status isn't closed. Sort by completion date, oldest first. This is your closeout queue.

For most contractors, this report doesn't exist by default. You'll need to build it, either in your field service software or by exporting to a spreadsheet. The filter is simple: job status = complete (or equivalent), AND job not in "closed" status.

Step 2: Assign the Review

One person owns the closeout queue. Not the PMs. Not the techs. A dedicated coordinator or office admin. Their job, every week, is to work through the queue and check each of the six items. If something is missing, they flag it and assign the fix to the right person (PM for review, billing coordinator for invoicing, purchasing for PO reconciliation).

Step 3: Set Time Thresholds

Any job that has been complete for more than 14 days without closing gets flagged yellow. More than 30 days, flagged red. More than 60 days, escalated to the controller or ops manager. These thresholds force action before jobs go stale.

Remember: the median closeout is 1.7 days. If a job has been sitting complete-but-not-closed for two weeks, something is broken in the process, and it won't fix itself.

Step 4: Track the Metric

Measure closeout time the same way you measure billing speed: days from job completion to job close, averaged across all jobs, reported monthly. Set a target (under 5 days is a reasonable starting point) and hold the team to it.

When you start tracking this metric, two things will happen. First, the obvious stale jobs will get cleaned up quickly since just looking at them creates urgency. Second, you'll find the systemic issues: the PM who never reviews jobs, the purchasing process that leaves POs open, the billing coordinator who batches invoices monthly instead of weekly. Those are the root causes. The weekly closeout review surfaces them.

---

The Bottom Line

The median contractor closes a job 1.7 days after completion. The average takes 14. The P90 is 36 days. That long tail of unclosed jobs traps WIP, hides cost overruns, leaves revenue unbilled, and inflates your backlog.

A 6-point closeout checklist (review, billing, invoicing, procurement, receipts, resolution notes) gives your team a concrete definition of "done." A weekly closeout review with time-based escalation thresholds ensures nothing sits in limbo for months.

If you don't have a closeout process today, start by running one report: all jobs marked complete but not closed, sorted by age. The list will be longer than you expect. The trapped cash will be more than you think.

Q: How does Level help with job closeout? A: We connect to your field service software and QuickBooks and build the closeout queue automatically. Every job shows its status across all six checkpoints, with aging flags at 14, 30, and 60 days. We include closeout efficiency as a KPI in your monthly financial review and flag the root causes of delays, whether it's a PM bottleneck, a billing gap, or a procurement issue. The first audit is free.

Q: What if our field service software doesn't track all six checklist items? A: Most modern platforms (BuildOps, ServiceTitan, Jobber) track billing status and invoice status natively. Procurement and receipt status depend on whether you're running POs through the system. If you're not, the checklist simplifies to four items: review, billing, invoice sent, and resolution notes. The key is having any defined closeout process, not perfection on day one.

Q: How much cash is typically trapped in unclosed jobs? A: It depends on job volume and average job size, but for a contractor running 1,000+ jobs per year with average job values of $5K-$15K, we commonly find $50K-$200K in trapped WIP and unbilled revenue during the first backlog cleanup. For larger commercial contractors with longer job durations, the number can be significantly higher. The stale backlog analysis is always the first step.