Winning new business is exciting. A growing backlog signals opportunity, stronger revenue potential, and validation that your company is heading in the right direction.
Yet many CEOs of project-based businesses eventually ask the same question:
“If we’ve won so much work, why doesn’t our financial picture feel stronger?”
The answer often lies in misunderstanding two reports that are frequently discussed together but serve entirely different purposes: Work in Progress (WIP) and contract backlog.
It’s easy to see why they’re confused. Both relate to the same contracts, both are discussed during project review meetings, and both influence forecasts and strategic planning. However, each measures a different stage of a project’s lifecycle and answers a different business question.
When leadership treats them as interchangeable, important decisions can suffer. Hiring may happen too early, or too late. Revenue forecasts become overly optimistic. Cash flow expectations drift away from reality. Project issues remain hidden until they’ve already affected profitability.
For government contractors, engineering firms, architecture firms, and other project-based businesses, understanding the distinction isn’t just an accounting exercise. It’s an essential part of leading a growing company.
Two Reports, Two Different Questions
Every executive wants to know whether the business is positioned for success. The challenge is asking the right question.
A Work in Progress (WIP) report answers:
“How are our active projects performing?”
A contract backlog report answers:
“How much work have we committed to delivering in the future?”
Although both reports originate from customer contracts, they are designed for different purposes.
Think of a long-distance road trip.
Your current location tells you how far you’ve already traveled. Your destination tells you how much farther you have to go.
Neither piece of information is more important than the other. Together, they give you the complete picture.
The same principle applies to WIP and backlog.
What Work in Progress (WIP) Really Measures
Many business owners assume WIP simply means unfinished work. In reality, it provides much deeper insight into projects that are already underway.
A typical WIP report tracks information such as:
- Costs incurred
- Labor charged
- Revenue recognized
- Billings
- Gross margin
- Percentage of project completion
- Overbillings and underbillings
Viewed together, these numbers reveal whether projects are performing according to plan.
For executives, WIP becomes an early warning system.
A project may appear healthy because invoices are going out on schedule. But WIP may reveal labor costs climbing faster than expected or shrinking profit margins long before those issues appear on the financial statements.
Conversely, a project that seems behind schedule may actually be outperforming expectations financially.
Without reviewing WIP regularly, leadership is often making decisions with only part of the story.
Where ASC 606 Fits into the Picture
From a financial reporting perspective, WIP also supports revenue recognition under ASC 606, Revenue from Contracts with Customers.
Under current GAAP, signing a contract does not automatically create revenue. Revenue is generally recognized as a company satisfies its performance obligations under the contract.
For many government contractors and professional service firms, those obligations are satisfied over time as work progresses.
That’s why a newly awarded contract may immediately increase your backlog while having no impact on revenue or profit.
The work still has to be performed before it becomes part of the income statement.
This distinction is one reason finance teams pay close attention to WIP. It helps ensure revenue recognition reflects actual project progress rather than contract awards alone.
For most CEOs, however, the accounting standard isn’t the important takeaway.
The real takeaway is this:
Winning work and earning revenue are two different milestones.
What Contract Backlog Really Measures
While WIP focuses on today’s projects, contract backlog looks toward tomorrow.
Backlog represents the remaining value of work that has been awarded but not yet completed.
Unlike WIP, backlog isn’t intended to measure current profitability or earned revenue.
Instead, it helps answer questions such as:
- How much work is already under contract?
- When will projects begin?
- Will current staffing support future demand?
- How much capacity will be needed over the next six to eighteen months?
- Is business development replacing completed work?
Because backlog looks ahead rather than behind, it becomes one of the most valuable planning tools available to executive leadership.
A growing backlog generally reflects successful sales efforts.
But it should never be interpreted as guaranteed profitability or immediate cash flow.
Timing matters just as much as volume.
Why Strong Backlog Doesn’t Always Mean Strong Cash Flow
One of the biggest misconceptions among growing companies is assuming backlog automatically translates into financial strength.
Imagine a government contractor wins three significant contracts totaling $15 million.
The announcement is worth celebrating.
Yet those contracts may:
- Begin several months from now.
- Include phased funding.
- Require specialized employees before work starts.
- Contain milestone billing requirements.
- Generate collections well after payroll and subcontractor costs have been incurred.
The company may have excellent future prospects while simultaneously experiencing tight cash flow today.
Nothing is wrong with the backlog.
The mistake is expecting backlog to answer a question it was never designed to answer.
Cash flow depends on many additional factors, including billing terms, collections, project schedules, and working capital management.
Backlog is only one piece of that puzzle.
Five Business Decisions That Depend on Understanding Both Reports
Successful CEOs rarely rely on a single report.
Instead, they recognize that different reports support different decisions.
1. Hiring the Right Number of People
Current WIP may suggest existing teams have available capacity.
Meanwhile, backlog may show multiple large projects scheduled to begin within the next quarter.
Waiting until projects start to recruit engineers, project managers, or technical specialists can create staffing shortages that affect delivery schedules and customer satisfaction.
Looking at both reports together allows leadership to plan hiring before demand peaks.
2. Evaluating Project Profitability
Revenue growth doesn’t always mean projects are performing well.
WIP reveals whether actual costs align with estimates and whether margins are holding throughout the project lifecycle.
Backlog cannot answer those questions because the work hasn’t been completed yet.
If profitability is slipping, WIP usually provides the earliest indication that corrective action is needed.
3. Planning Future Capacity
Winning more work is only valuable if the organization can successfully deliver it.
Backlog helps leadership determine whether future commitments exceed available resources.
Questions worth asking include:
- Do we have enough project managers?
- Will specialized labor become a bottleneck?
- Are subcontractors available when needed?
- Can current systems support projected growth?
These decisions have little to do with accounting and everything to do with operational planning.
4. Forecasting Revenue
Forecasting becomes much more reliable when WIP and backlog are reviewed together.
WIP reflects projects already generating revenue.
Backlog identifies projects expected to contribute revenue in future periods.
Combining both reports produces a much more realistic forecast than relying on historical financial statements alone.
5. Identifying Business Risk
Every growing company faces risk.
The key is recognizing where it exists.
For example:
- High WIP combined with declining backlog may signal future revenue pressure.
- Strong backlog with limited staffing may indicate execution risk.
- Healthy WIP but shrinking margins may suggest estimating or pricing problems.
- Large backlog concentrated in one customer may expose the business to contract risk.
No single report reveals every issue.
Viewed together, they provide much greater insight into the company’s overall health.
A Real-World Government Contractor Example
Consider a technology contractor that receives a five-year federal contract valued at $20 million.
On the day the contract is awarded:
- Contract backlog increases by $20 million.
- WIP remains at zero.
- No revenue has been recognized.
- No project costs have been incurred.
Three months later, the company has mobilized its team, begun performance, and completed a portion of the work.
Now the picture changes.
WIP begins tracking project costs, labor hours, billings, recognized revenue, and project margins.
At the same time, backlog gradually decreases as contractual obligations are fulfilled.
Neither report is more important than the other.
One measures current execution.
The other measures remaining opportunity.
Together they provide leadership with a balanced view of both present performance and future commitments.
Looking Beyond Individual Reports
Many companies review WIP during accounting meetings and backlog during operations meetings.
While that approach is common, it often prevents leadership from seeing how the two reports influence one another.
Consider a business with an impressive backlog but declining WIP. That could simply mean several recently awarded contracts have not yet reached their start dates. It could also indicate delays in customer funding, contract modifications, or resource constraints that are preventing work from beginning.
Now consider the opposite situation. WIP is exceptionally strong, but backlog is steadily shrinking. Current revenue may look healthy, yet leadership should be asking whether enough new work is entering the pipeline to sustain growth over the next year.
Neither situation is necessarily a problem. The key is recognizing what the reports are communicating before small issues become larger ones.
The most effective leadership teams don’t review these reports in isolation. They connect them with other operational and financial indicators to understand where the business is headed.
Building a Better Executive Dashboard
As organizations grow, the number of reports available to leadership grows with them. The challenge isn’t finding more data; it’s identifying the information that supports better decisions.
For many project-based businesses, an executive dashboard should include more than WIP and contract backlog. It should provide a balanced view of current performance and future commitments.
A monthly executive review might include:
- Work in Progress by project
- Contract backlog by expected start date
- Gross margin trends
- Labor utilization
- Cash flow forecast
- Accounts receivable aging
- Proposal pipeline
- Contract win rate
Each report answers a different question.
Together, they tell the story of the business.
For example, strong backlog combined with low labor utilization may indicate that projects have not yet started. Strong WIP paired with aging receivables could signal that collections, not sales, are putting pressure on cash flow. Healthy margins alongside a declining proposal pipeline may suggest today’s profitability could become tomorrow’s slowdown.
Viewed individually, these reports provide useful information. Viewed together, they become business intelligence.
Turning Information into Better Decisions
Reports alone don’t improve a business.
Interpretation does.
A WIP schedule filled with accurate numbers has little value if leadership doesn’t recognize declining project margins. Likewise, an impressive backlog offers limited insight if no one evaluates whether the organization has the capacity to deliver the work successfully.
This is where financial reporting evolves into strategic decision-making.
Instead of asking, “How much revenue did we recognize this month?” leadership begins asking:
- Are our projects becoming more profitable or less profitable?
- Is our backlog growing in the right service lines?
- Will our staffing support next quarter’s workload?
- Are we pricing projects well enough to protect margins?
- What risks should we address before they affect financial performance?
Those questions move the conversation beyond historical reporting and toward proactive management.
Why the Distinction Matters More as Companies Grow
Work in Progress and contract backlog begin with the same customer contracts, but they tell two very different stories.
WIP focuses on the work already in motion, providing insight into project performance, earned revenue, and profitability. Contract backlog focuses on the work still ahead, helping leadership plan for future staffing, resource allocation, and growth.
Understanding that distinction changes the quality of executive decision-making. Instead of relying on a single number to measure success, CEOs gain a more complete view of where the business stands today and where it is headed tomorrow.
The strongest project-based businesses don’t choose between WIP and backlog. They recognize that each report answers a different question, and they use both to make smarter decisions about profitability, capacity, cash flow, and long-term growth. Want to learn more about WIP and backlog, visit Cheryl Jefferson & Associates.
