Your CFO closes the books on time every month. 

Revenue hits the target. Gross margin looks healthy. 

Then three months later, you true up completed jobs and discover half your enhancement work ran 8 points under budget. 

The monthly P&L wasn't wrong; it was fiction. 

Revenue recognition disconnected from production reality is where margin disappears on active jobs.

You invoiced $1.2M last month. How much of it was earned?

Ask most commercial landscaping CFOs what they invoiced in the previous month and they likely have an answer before you finish asking the question. But it’s usually harder for them to answer how much was earned. Financial credibility breaks down in the gap between the two.

The invoicing-versus-earnings gap is structural in landscape operations.

A $30M commercial landscaper runs $8M in enhancement and installation work annually alongside its recurring maintenance base. 

Monthly invoicing follows contract milestones: 30% on start, 40% at substantial completion, 30% on final. 

Though production doesn't track neatly to milestones:

• Crews start three jobs in week one.

• Materials installation completes on two jobs in week two.

• Punch-list work closes out on four jobs from the prior month.

In any given month, the company carries $1.5M to $2M in active work-in-progress spread across 40 to 60 jobs.

Without real-time WIP tracking, the controller reconciles job costs at completion, sometimes 8 to 12 weeks after the work started. 

During those weeks, monthly financials recognize revenue based on invoicing schedules rather than on what's actually been earned through production. The P&L shows a margin that may or may not exist.

The result is a recurring true-up cycle that erodes financial credibility.

A $180K enhancement job that appeared to be 28% gross margin on the second milestone invoice is actually 19% margin when final labor, materials, and subcontractor costs are reconciled eight weeks later. 

Multiply that across 40 active jobs, and the monthly P&L overstates gross profit by $60K to $120K every month until true-ups hit in a later period:

• Leadership makes decisions on inflated margins.

• The board reviews financials that will be restated next quarter.

• The CFO spends every month-end close defending numbers that will change when jobs close.

If you can't see WIP in real time, your monthly P&L is more guesswork than a reliable financial statement.

Revenue appears on the books because an invoice was issued. 

Costs exist in the field because crews are working and materials are being delivered. The gap between those two realities is a work-in-progress, and if the WIP balance is wrong, every number downstream from it is wrong too.

Why Landscape WIP Is Uniquely Hard to Track (and Uniquely Costly to Ignore)

WIP reporting is messy in every project-based business. 

Landscape operations add structural complexity, making the standard accounting approach inadequate.

1. Jobs span weeks to months, with costs hitting at different intervals

A single enhancement project might involve:

• Three weeks of crew labor.

• A materials delivery in week one that doesn't get invoiced by the supplier until week four.

• A subcontractor invoice that arrives 30 days after the work is complete.

If costs and revenue aren't matched in real time as production happens, the P&L becomes a series of timing mismatches that only reconcile when the job closes.

These circumstances don’t only appear in edge cases. They’re the default for any landscape company running project work alongside recurring maintenance. The crews are in the field today, completing work. The materials were delivered last week. The subcontractor bill will arrive next month. 

The client was invoiced at the second milestone two weeks ago. All of these transactions belong to the same job, but they hit the books in different periods unless the WIP system forces them into alignment.

1. Percent complete is subjective without production data

Most landscape companies estimate job completion based on the project manager's assessment. A PM walks the site, visually assesses progress, and reports that the job is 75% complete. But 75% complete by what measure?

• If the PM judges completion by visible progress, a job with extensive subsurface work or deferred punch-list items can appear farther along than it actually is.

• If the estimate assumes 400 crew hours and 280 have been logged, the job is 70% complete by production, regardless of the site's condition.

Subjective percent-complete estimates systematically overstate earned revenue.

PMs are optimistic. 

They see progress and believe the remaining work will go faster than it actually does. 

When WIP calculations rely on gut-feel completion percentages instead of hours-to-budget or cost-to-budget ratios, revenue recognition drifts ahead of production reality. A job reported as 75% complete (actually 60% complete) has overstated earned revenue by 15 points on that job. 

Multiply across dozens of active jobs, and the aggregate overstatement compounds into a material P&L distortion.

The cost of getting it wrong flows through the entire financial model

Misstated WIP doesn't stay isolated to a single line item. It flows into:

• Revenue recognition distorts gross margin.

• Gross margin feeds into job profitability reports used to price future work.

• Board reporting, EBITDA calculations, and covenant compliance for PE-backed landscape companies.

A $30M company with $2M in active WIP and a 10% reporting error has a $200K credibility problem every month. That error propagates through every financial decision made during the period.

The larger the company and the more project work in the mix, the more expensive WIP reporting errors become.

At $10M with limited enhancement work, a CFO can manually reconcile WIP at month-end and live with the lag. At $30M with $8M in project revenue and 60 active jobs, manual reconciliation is too slow and too error-prone to produce reliable financials. 

The infrastructure has to be operational, not accounting-driven.

What Real WIP Reporting Requires

Don’t think of WIP visibility as an accounting crackdown; think of it as an operational data discipline that requires production data to flow into financial systems in real time, not at month-end reconciliation.

Real-time cost capture at the job level

Labor hours, materials receipts, and subcontractor costs must flow into job records as they occur, not when someone remembers to enter them at month-end. 

Every day of delayed cost capture is a day the WIP balance is incorrect, which means every financial report produced during that lag is based on incomplete data.

Crew time tracking integrated with job costing is the foundation.

When crews clock in and out against specific jobs, labor costs hit the WIP balance immediately:

• When materials are received and assigned to jobs upon delivery, the materials costs update the WIP balance in real time.

• When subcontractor invoices are coded to jobs as they arrive, subcontractor costs flow into the WIP calculation without waiting for the month-end.

This isn't a reporting upgrade; it's an operational workflow change that makes cost data available when it matters.

Production-based percent-complete calculations, not PM gut feel

Replace subjective completion estimates with hours-to-budget or cost-to-budget calculations tied to actual production data:

• If a job was estimated at 400 crew hours and 280 hours have been logged, the job is 70% complete by production.

• If a job was budgeted at $85K in total costs and $61K has been incurred, the job is 72% complete by cost.

Both methods are defensible, auditable, and immune to optimism bias.

Shifting from subjective to objective percent complete eliminates the largest WIP estimation error.

PMs still provide qualitative input on job status, scope changes, and remaining work. 

However, the financial calculation for earned revenue uses production data, not opinion. 

When WIP is calculated from hours logged or costs incurred against budget, the revenue recognition model reflects operational reality instead of hopeful projections.

Variance alerts on active jobs, not post-mortems on closed jobs

The CFO shouldn't discover a margin problem when a job closes. 

WIP reporting should flag any job where actual costs exceed budgeted costs by more than 10% while the job is still active, so operations can intervene before the margin is gone.

Real-time variance visibility turns WIP from an accounting output into a management input.

If a $120K enhancement job is budgeted at 32% margin and actual costs at 60% completion are already at 75% of budget, the job is heading toward a 15-point margin miss. 

That signal should surface immediately, triggering an operational review while there's still time to course-correct:

• The scope has expanded, and a change order is warranted.

• Maybe the crew is inefficient and needs support.

• Maybe the estimate was wrong, and future bids need recalibration.

All of those interventions require early warning, which happens only when WIP tracking runs in real time.

What This Looks Like in Aspire

Aspire's integrated job costing and financial workflows deliver the operational infrastructure CFOs need to produce accurate WIP reporting without manual reconciliation.

Real-time cost capture through integrated time tracking and materials management.

• When crews complete work and log hours through Aspire's time-tracking system, labor costs are recorded directly in job records.

• Materials purchasing and receiving workflows assign costs to jobs at delivery, not at month-end data entry.

• Subcontractor management tools capture vendor invoices and code them to jobs as they arrive.

The result is a live WIP balance that updates daily as field activity happens, giving finance a current view of earned revenue and job profitability without waiting for reconciliation cycles.

Production-based percent-complete calculations are tied to estimating budgets.

Aspire's job-level dashboards show:

• Estimated versus actual costs.

• Hours logged against budgeted hours.

• Percent-complete calculated from production data rather than subjective PM assessments.

CFOs and controllers can see exactly how much work has been completed on every active job, how much cost has been incurred, and what the projected margin at completion looks like based on current run rates. 

Revenue recognition models use these production-based metrics to ensure that earned revenue reflects operational reality.

Variance alerts that surface margin risk while jobs are still active.

When actual costs on a job exceed budgeted costs by a defined threshold, Aspire's reporting tools flag the job for review:

• Finance and operations leadership see which jobs are trending over budget, by how much, and at what stage of completion.

• This enables real-time intervention, such as scope clarification, crew reallocation, change order generation, or estimating recalibration.

WIP stops being a backward-looking reconciliation exercise and becomes a forward-looking management tool.

Job-level profitability dashboards that show WIP in a financial context.

CFOs need to see WIP not just as a balance sheet line item but as a portfolio of active jobs with varying margin profiles. Aspire's dashboards present active WIP:

• By job, by service line, and by branch.

• Showing estimated margin, actual margin to date, and projected margin at completion.

Leadership can identify which jobs are performing, which are at risk, and where operational attention is needed, all from real-time production and cost data flowing through the platform.

If You Can't See Work in Progress, You Can't Trust Your P&L

Monthly financials are only as accurate as the WIP tracking behind them. 

If active job costs are reconciled at completion instead of captured in real time, every P&L between job start and job finish is a guess:

• Revenue recognition happens on invoicing schedules that may or may not align with production.

• Costs trickle in weeks after the work is done.

• The gap between those two realities produces financial statements that look clean but rest on assumptions that won't hold when jobs close and true-ups hit.

The true-up always hurts worse than the discipline of tracking WIP in real time.

A CFO who reconciles 40 jobs at quarter-end and discovers a $180K aggregate margin miss faces two problems. 

First, the financials for the prior three months were incorrect, which means every decision made based on those financials was based on incomplete information. 

Second, the correction hits all at once, creating a variance that's difficult to explain to leadership, the board, or PE sponsors. 

Real-time WIP tracking distributes that reconciliation across the period as jobs progress, eliminating surprise true-ups and producing financials that leadership can actually trust.

For landscape companies running meaningful project work alongside recurring maintenance, WIP visibility is the difference between financial reporting and financial credibility.

The operational infrastructure required to produce accurate WIP isn't complicated:

• Time tracking integrated with job costing.

• Materials management tied to job records.

• Percent-complete calculations based on production data, not subjective assessments.

Companies that build this infrastructure produce monthly financials that reflect operational reality. Companies that don't produce monthly financials will have to restate them when jobs close.

Book a demo to see how Aspire delivers real-time WIP visibility for landscape operations with job-level cost tracking, production-based revenue recognition, and variance alerts that turn WIP from an accounting exercise into a management system.