Your WIP schedule knows what is going wrong before your P&L does— if you know what to look for. The seven patterns in this checklist are the ones most AEC CFOs discover too late, after the damage has already moved into the income statement.
The problem isn't awareness. Most AEC CFOs know that underbillings grow into collection risks and that stale cost-to-complete estimates produce phantom profits. The problem is cadence. A monthly review tells you what already happened. A Monday morning review gives you time to do something about it— and the hidden costs of deferred financial reviews compound faster than the calendar suggests.
CFMA (the Construction Financial Management Association, the industry's primary professional body for construction financial management) frames the stakes this way: "Overbillings and underbillings are not optional disclosures; they tell the CFO, the surety, and the bank whether the company is being funded by its customers, or quietly funding its customers out of working capital."7 As Reach CPA documents, "Profit rarely disappears all at once but leaks out through small, reasonable-sounding decisions that no one stopped to price."13 At 2–4% net margins1, every percentage point on every job is load-bearing.
Here are the seven patterns to look for each Monday:
- Underbillings aging past 60 days
- Job borrowing (overbilled cash from new projects funding old ones)
- Stale cost-to-complete estimates
- Profit fade on active projects
- Jobs showing 100%+ completion
- Inconsistent percent-complete methodology
- Retainage receivable exceeding trailing net income
Why Monday, Not Month-End
A monthly WIP review tells you what happened. A Monday morning review gives you time to do something about it.
By the time month-end close reveals a problem on a specific job, the corrective window has already narrowed. The project manager has committed to subcontractors. Labor is booked. The schedule is set. Monday timing has a specific value: it sets the week's accountability conversations before anything else gets locked in. You catch the problem in week three instead of at the quarter close— and there is a real difference between those two moments.
BaseBuilders recommends weekly WIP reviews by project, especially for jobs that are 60% or more complete, because that's when project managers still have operational levers to pull.3 BCS ProSoft's escalation framework5 makes the timing logic explicit: a one-month margin dip warrants investigation; a second consecutive month requires action; multiple declining cycles demand principal-level escalation. You can only run that framework on a weekly cadence.
The threshold: weekly review is most critical for firms with ten or more active projects above $500K contract value. Monthly is the accepted minimum below that. But even there— a problem found in week three is a conversation. A problem found at month-end close is a restatement.
| Cadence | What You Learn | Window to Act |
|---|---|---|
| Monthly | What happened last month | Narrow; PM has already committed |
| Weekly | What is developing this week | Wide; PM still has operational levers |
Measuring the ROI of financial process improvements starts with whether you're catching problems early enough to correct them. Cadence is the leverage point.
Red Flag 1: Underbillings Aging Past 60 Days
Underbilling that ages past 60 days stops being a timing issue and becomes a collection risk. At 90 days, the industry data puts your recovery odds at 30–50%.2
The distinction matters. Some underbilling is legitimate: you're billed up-to-date by contract terms and the next billing cycle hasn't arrived. That's not a flag. The flag is aging unbilled work— an approved scope that went unbilled, an unapproved change order absorbed into the base contract, a phase that quietly closed without a final invoice. Monograph calls it plainly: "Chronic underbilling is the most common engineering-firm disease: the work outruns the invoicing, receivables look fine, and the firm quietly finances its clients."2
Monograph's realization rate benchmarks2 are specific:
| Age of Unbilled Work | Realization Rate |
|---|---|
| 0–30 days | 85–95% |
| 31–60 days | 70–85% |
| 61–90 days | 50–70% |
| 90+ days | 30–50% |
Past 90 days, you are statistically likely to recover less than half what you're owed. BaseBuilders puts it directly: "high write-off risk, recovery options narrowing."3 CFO Advisors goes further: "Persistent aggregate underbilling is the single most reliable early warning of contractor distress."1
This is particularly acute in architecture and engineering firms, where fixed-fee projects and phase-based billing make it easy for scope additions to slide through unbilled. If a job has been underbilled for more than one full billing cycle without a documented reason, escalate it to the principal that week.
Red Flag 2: Job Borrowing— The Slow-Motion Failure
Job borrowing happens when overbilled cash from new projects is used to cover cost overruns on old ones. The signature is a growing overbilled position at the portfolio level while gross margins on closed jobs keep falling.
This pattern is easy to miss job-by-job because each project may look fine individually. The warning is in the aggregate. Civil CFO puts it clearly: "If your overbilled position keeps growing and your gross margin on closed jobs keeps falling, you're not doing healthy front-loading. You're job borrowing."4 The consequence: "job borrow— when overbilled cash from new jobs is funding cost overruns on old jobs— is the slow-motion failure that takes down contractors that on paper look strong."4
Three conditions distinguish healthy front-loading from job borrowing:
- Healthy overbilling: 2–5% ahead of earned revenue at the portfolio level1; normal on individual jobs in early phases
- Front-loading: overbilling concentrated in early-phase work where billing legitimately leads cost
- Job borrowing: overbilling growing portfolio-wide while recently closed jobs show declining gross margins
ChatFin AI flags overbilling exceeding 15% of contract value as a threshold requiring immediate investigation.9 The bonding implication is harder to recover from than the cash implication. Inaccurate WIP schedules— including unsupported overbilling— are among the top causes of bonding declines, and CFMA notes that most contractors discover this only when they try to increase their single-job limit and get turned down.7 By then, the pattern is years old.
Red Flag 3: Stale Cost-to-Complete Estimates
When a project carries the same estimated cost to complete (ETC) for two or more months while labor keeps posting, the WIP schedule is reporting phantom profit. The real loss will appear at project close— and it will be larger than it needed to be.
The mechanism is straightforward. An unchanged ETC inflates percent complete, overstates earned revenue, and produces reported gross profit that does not exist. BCS ProSoft documents the pattern: "A project may carry the same ETC for several months while labor continues to post, masking margin erosion. This is particularly acute after 70% completion when remaining fee flexibility diminishes."5 At 70%+ complete, there's nothing left to absorb the overrun. Vessel Advisors states the logical conclusion: "Cost-to-complete estimates exceeding remaining contract value guarantee job losses regardless of original budget."10
This is where "you can't read the label from inside the bottle" matters most. Project managers are structurally too close to their own work to objectively assess remaining cost— the optimism bias is well-documented, and AI platforms flag EAC anomalies that manual review routinely misses.9 Field teams must own ETC, but the CFO must enforce the update discipline.
ChatFin AI flags EAC (Estimate at Completion) increases exceeding 10% without approved change orders as a threshold requiring investigation.9 On large programs, the stakes of a small error compound fast: a 1% WIP error on a $4 billion program can shift recognized revenue by $40 million.6
Three questions to ask about any ETC on your Monday list:
- When was this ETC last updated? (More than one billing cycle: flag it.)
- Has labor posted against this job since the ETC was last revised?
- Does this ETC exceed the remaining contract value? (If yes, the job is in loss position.)
Red Flag 4: Profit Fade on Active Projects
A single month of declining estimated gross profit on a project warrants investigation. A second consecutive month requires action. Multiple declining cycles demand principal-level escalation.
Profit fade is a pattern, not an event— estimated gross profit percentage declining across successive WIP cycles. And it's invisible without month-over-month comparison. JMCO illustrates it: "a job sliding from 15% to 8% gross profit can remain invisible without rigorous scrutiny."11 Against CFMA's 26% average gross profit benchmark12, a job at 15% is already running lean. A slide to 8% represents more than half the margin gone— but without a weekly scan looking specifically for the trend, neither number by itself triggers a conversation.
The BCS ProSoft escalation framework5:
- Month 1 decline: investigate— is this a one-time scope adjustment or a pattern?
- Month 2 consecutive decline: action required— PM accountability conversation this week
- Multiple cycles declining: principal escalation— this project has a structural margin problem
The underlying mechanism is usually what Reach CPA describes as "small, reasonable-sounding decisions that no one stopped to price."13 Each unpriced scope addition, each late revision, each PM meeting that ran long was rational at the time. Compounded over a project, they eat the fee.
Red Flag 5: Jobs Showing 100%+ Completion
Any job showing more than 100% complete on your WIP schedule is a direct red flag— and it is not a system error. It means either your original cost estimate was wrong, your team stopped updating it when actuals exceeded it, or both.
CFMA is direct: jobs over 100% complete indicate "inability to properly estimate costs or failure to update estimates when actuals exceeded original."7 The same flag applies to gross margins that look suspiciously high— both are data quality problems that distort the entire WIP schedule.
The bonding risk is concrete. Inaccurate WIP schedules are among the top causes of bonding declines7, and surety underwriters treat jobs over 100% complete as evidence of broader estimate discipline failure. Most contractors don't discover this until they apply for a larger single-job limit and get turned down.
When you find a job at 100%+ on Monday:
- Investigate the ETC history: when did actuals exceed the original budget, and why wasn't the ETC updated?
- Check for unprocessed change orders that should have adjusted the contract value upward
Fix it before month-end close, not after. Correction after the close carries prior-period adjustment implications.
Red Flag 6: Inconsistent Percent-Complete Methodology
Your WIP schedule uses cost-to-cost on one fixed-fee design-build project and elapsed time as the proxy on a nearly identical contract in the next division over— with no documentation explaining why. Auditors notice this. Bonding companies notice this. Under ASC 606, consistency across similar performance obligations isn't optional.
Beancount.io documents the standard: "ASC 606 requires consistent application of the chosen method across similar performance obligations in similar circumstances."8 And: "Switching methods between projects or periods raises red flags with auditors, bankers and bonding companies."8 This isn't a preference— violation without documentation creates audit exposure and makes WIP schedules difficult for surety underwriters to evaluate.
The legitimate exception: different contract types may use different methods. T&M projects and fixed-fee projects don't have to use the same methodology. The problem is mixing methods on similar contracts without explanation, or using elapsed time as a completion proxy on fixed-fee deliverable work. A GC using cost-to-cost on one IDIQ contract and milestone billings on a structurally identical sister contract— with no documented rationale in either file— is the pattern that surfaces in audit.
Three warning signs of methodology inconsistency:
- The same job type uses different percent-complete methods in different periods with no documented reason
- Fixed-fee architecture or engineering projects use elapsed time rather than deliverable milestones
- No written documentation explains why a specific method was chosen for a contract type
For context on governance patterns more broadly, see our AI governance framework for AEC operations— the methodology documentation discipline here maps to the same process-rigor principles.
Red Flag 7: Retainage Receivable Exceeding Trailing Net Income
When your retainage receivable exceeds your trailing twelve-month net income, cash flow management is your primary job— not strategy, not growth.
Retainage is the piece of each progress billing the owner holds back until final project completion. Standard terms run 5–10% per invoice. On a $10 million project with 10% retainage, $1 million doesn't reach the bank account until the job closes.1 CFO Advisors documents what that adds up to across a portfolio: "retainage float can represent 15% to 20% of annual revenue sitting in someone else's account."1
| Project Value | Retainage Rate | Locked Amount | Release Condition |
|---|---|---|---|
| $10M | 10% | $1,000,000 | Final completion + owner acceptance |
| $5M | 5% | $250,000 | Substantial completion per contract |
| $25M | 7.5% | $1,875,000 | Per-phase per contract terms |
The threshold that changes the CFO's job description: when retainage receivable exceeds trailing twelve-month net income, active retainage management— scheduling recovery milestones, tracking retainage aging, negotiating release timing— becomes the primary function.1 Vessel Advisors flags "significant holdbacks on completed work that remain uncollected" as a sign of execution problems.10 That's the version to catch before it shows up in a fractional CFO conversation about what went wrong.
The Monday Morning 30-Minute Review
A 30-minute Monday morning review of your WIP schedule catches most of these patterns before they become crisis conversations. Here is one way to structure it.
This is a pattern scan, not a full WIP rebuild. The output is a list of calls— not a report.
- Start with the aggregate position. Check the portfolio-level overbilled/underbilled balance first. Note the direction: growing, shrinking, or stable. Growing underbillings at the portfolio level is this week's primary signal.
- Sort by completion percentage. Focus on jobs between 60% and 95% complete. That is the highest-risk zone— enough runway to act, not enough buffer to absorb surprises.
- Age the underbillings. Any unbilled work older than 30 days needs a note. Anything older than 60 days needs a conversation this week, not next month.
- Check ETC update dates. When was each cost-to-complete estimate last revised? Any unchanged ETC on an active job for more than one billing cycle is a flag, regardless of how the job otherwise looks.
- Flag methodology outliers. Any job using a different percent-complete method than its peers should have a documented reason in the file. If it doesn't, add it to the list.
- Set the week's conversations. The output of the Monday review is not a report. It is a list of project managers to call before Friday.
The WIP schedule is only useful if someone is reading it with the right questions in mind, on the right cadence. The questions are above. The cadence is Monday.
AI and the WIP Review— Faster Pattern Detection, Same Process Prerequisites
AI platforms for construction finance can flag the patterns in this checklist automatically— but only when the underlying process inputs are reliable. AI automating bad cost-to-complete estimates from project managers is just inaccurate data faster.
Most AEC firms shopping for AI-powered WIP monitoring have the wrong problem. The manual review process isn't working yet, and adding AI to a broken process makes it break faster— you get the same wrong answers on a tighter timeline. Build the Monday morning habit first. Then consider what automation adds.
What AI platforms actually do in this space: ChatFin AI9 flags overbilling exceeding 15% of contract value, EAC increases exceeding 10% without approved change orders, and underbilling growing for three or more consecutive periods. The efficiency gain is real when the data is clean— monthly WIP prep drops from 40–60 hours with legacy processes to 8–12 hours with AI assistance.9
Three thresholds AI platforms commonly auto-flag:
- Overbilling exceeding 15% of contract value
- EAC increase exceeding 10% without approved change orders
- Underbilling growing for 3+ consecutive periods without a documented billing plan
If your firm is evaluating AI-assisted WIP monitoring and you're unsure whether your current data quality and process infrastructure supports it, that readiness assessment is the right first step. Our AI implementation services for AEC firms include exactly that evaluation. For the broader decision logic on applying AI to your financial operations, the AI decision framework for founders covers the sequence directly.
Your WIP schedule has always known what was coming. The Monday morning habit is what makes that knowledge actionable before it becomes a problem you're managing instead of one you prevented.
FAQ
What is job borrowing in construction?
Job borrowing happens when a contractor uses overbilled cash from new projects to cover cost overruns on old ones. Its signature is a growing portfolio-level overbilled position while gross margins on recently closed jobs keep declining. Civil CFO calls it "the slow-motion failure that takes down contractors that on paper look strong."4 The distinction from normal front-loading is the portfolio pattern over time— not the overbilling on any single job.
How often should AEC firms review WIP?
Weekly review is recommended for firms with active projects over $500K, especially those 60% or more complete.3 Monthly is the accepted minimum for smaller or less active portfolios. The advantage of weekly is that project managers still have operational levers to pull when problems surface in week three rather than at month-end close. The Monday morning review in this article is designed to run in 30 minutes and produce a call list, not a formal report.
When does underbilling become a serious problem?
Underbilling aged past 60 days should be escalated to the principal. At 90 days, Monograph's data2 shows realization rates fall to 30–50%, meaning you recover less than half the unbilled amount on average. Any underbilling growing for three or more consecutive periods without a documented billing plan is a red flag regardless of age.
What WIP ratio indicates cash flow problems?
High-performing AEC firms maintain WIP ratios below 1.2. Firms with ratios above 1.5 frequently show cash flow difficulty.2 Both benchmarks originate from CFMA data.
What does 100%+ completion on a WIP schedule mean?
A job showing over 100% complete means actual costs exceeded the original budget estimate and the cost-to-complete was never updated to reflect that. CFMA treats this as a direct red flag7 requiring investigation— not a data entry error to correct without understanding why the ETC went stale.
References
- CFO Advisors, "Construction Company Cash Flow Management: WIP Schedules, Progress Billing, and Retainage (2026 Guide)" (2026)— https://cfoadvisors.com/blog/construction-company-cash-flow-management-2026
- Monograph, "Engineering Firm WIP Reports: Where Profit Becomes Cash" (2025)— https://monograph.com/blog/engineering-firm-wip-reports
- BaseBuilders, "WIP Management for Architecture & Engineering Firms: How to Protect Revenue Between Delivery and Billing" (2025)— https://www.basebuilders.com/articles/wip-management-for-architecture-engineering-firms
- Civil CFO, "WIP Schedule Explained: Overbilling, Underbilling" (2025)— https://www.civilcfo.com/blog/wip-schedule-construction-overbilling-underbilling
- BCS ProSoft, "WIP Reports for A&E Firms: Catching Margin Fade Before It Hits the P&L" (2025)— https://www.bcsprosoft.com/wip-reports/
- SWK Technologies, "The $40M Cost of a 1 Percent Construction Project WIP Error" (2025)— https://www.swktech.com/construction-project-wip-error/
- CFMA, "WIP Accounting: Critical and Often Misunderstood" (2024)— https://cfma.org/articles/wip-accounting-critical-and-often-misunderstood
- Beancount.io, "The Construction WIP Schedule: Percentage-of-Completion Accounting Under ASC 606" (2026)— https://beancount.io/blog/2026/05/15/construction-work-in-progress-schedule-percentage-of-completion-asc-606-overbillings-underbillings-contractors-bonding-banks-guide
- ChatFin AI, "AI for Construction Finance CFOs: Job Cost, WIP Schedules, and Percentage of Completion 2026" (2026)— https://chatfin.ai/blog/ai-construction-finance-cfo-job-cost-wip-percentage-completion-2026/
- Vessel Advisors, "The WIP Schedule Tells the Truth— Are You Reading It? A Fractional CFO's View" (2025)— https://vesseladvisors.com/resources/article/wip-schedule-fractional-cfo.html
- JMCO, "What Your WIP's Warning Signs Actually Mean" (2025)— https://www.jmco.com/articles/construction/what-your-wips-warning-signs-actually-mean/
- CFMA, "CFMA's 2024 Construction Financial Benchmarker Executive Summary" (2024)— https://cfma.org/articles/cfma-s-2-24-construction-financial-benchmarker-executive-summary
- Reach CPA, "Fee Erosion in AEC Firms: Early Warning Signs + What to Do This Month" (2025)— https://www.reachcpa.ca/post/fee-erosion-in-aec-firms