RPT 205 · Practitioner · Finance track · 12 min read

Cash Flow Forecast

The projection of cash coming in and going out over time, by project and company-wide, that tells a contractor whether it can fund the work it has already won.

Definition — what it is

A cash flow forecast projects the timing and amount of cash a contractor expects to receive and pay over a future horizon, built up from project-level billing and cost schedules and consolidated to the company. It models when pay applications will be billed and collected, when retainage will be released, and when payroll, suppliers, and subcontractors must be paid, to reveal whether the business will have the cash to fund its committed work. Its defining feature is that it is about timing, not profitability: a project can be highly profitable and still bankrupt the company that builds it if the cash goes out months before it comes in. It is not the same as the WIP schedule or the income statement, which measure earnings; the cash flow forecast measures liquidity, and the two routinely tell different stories in the same month.

Also known as: Cash Forecast, Cash Projection, Liquidity Forecast, Cash Flow Projection

Why it matters — what it protects

Construction is a business that finances its customers, and cash timing is the constraint that ends more contractors than unprofitability does. Payroll is due weekly and suppliers monthly, but pay applications are billed monthly, approved slowly, paid on net terms, and shaved by retainage - so a contractor routinely funds one to three months of work before the money returns. The cash flow forecast is the instrument that shows whether the company can survive that gap on the work it has already committed to.

The forecast is the difference between managing cash and reacting to it. A contractor that sees a shortfall eight weeks out can accelerate billing, negotiate terms, draw on a line of credit deliberately, or slow discretionary spend; a contractor that discovers the shortfall the week payroll is due is choosing between missing payroll and an emergency draw at punitive terms. The horizon the forecast buys is the whole value.

Cash flow is where retainage, billing terms, and payment behavior stop being contract abstractions and become survival math. Retainage withheld across a portfolio can equal a contractor's entire annual profit, sitting uncollected until closeout; a slow-paying owner or a front-loaded schedule of values changes the whole liquidity picture. The forecast is where these terms are modeled and their combined effect on cash is finally visible.

Lenders and sureties read the cash flow forecast to judge whether a contractor can fund its backlog. A company can have strong equity and a full backlog and still be uncastable if the timing of its cash cannot support the work program, and a credible, well-supported forecast is often what secures or preserves a line of credit. The forecast is as much an external credibility instrument as an internal management tool.

Lifecycle — how it moves

  1. Project cash modeling

    For each job, the schedule of values and cost schedule are laid across time to project billings and costs by period. The quality of the whole forecast rests here: a job modeled on an unrealistic billing curve or an optimistic schedule feeds error into the consolidation.

  2. Collection timing

    Billings are lagged by the realistic time to approve and pay a pay application, not the contract's stated terms, and retainage is held out until its projected release. Assuming contract terms instead of actual payment behavior is the most common way the inflow side is overstated.

  3. Disbursement timing

    Payroll, supplier, subcontractor, equipment, and overhead payments are scheduled by when they are actually due. Subcontractor payments are often modeled as pay-when-paid where the contract allows, which materially changes the outflow timing.

  4. Consolidation

    Project forecasts are combined with company overhead, debt service, tax, and distributions into a single company cash projection. The consolidation reveals whether jobs that are individually fundable collectively outrun the company's cash.

  5. Scenario and sensitivity

    The forecast is stressed - a slow-paying owner, a delayed retainage release, a lost or delayed award, a payroll spike - to find the fragile points. A single-line forecast that has never been stressed hides how quickly a plausible slip becomes a shortfall.

  6. Financing plan

    Projected shortfalls are matched to financing - line-of-credit draws, mobilization payments, billing acceleration - and the plan is validated against the facility's covenants and capacity. The forecast turns from a warning into a plan here.

  7. Actual-vs-forecast reconciliation

    Each period, actual cash movement is compared to the forecast to calibrate the model - how far off the collection lags and billing curves were. Forecasts that are never reconciled to actuals never improve and stay optimistic.

  8. Rolling update

    The horizon rolls forward as periods close and new awards, changes, and payment behavior are incorporated. A cash flow forecast is only useful while it is current; a stale one is worse than none because it is trusted.

Anatomy — the data it carries

Forecast horizon and interval
How far ahead and in what buckets - usually weekly near-term for liquidity, monthly further out for planning. The near term is where survival is decided.
Projected billings by project
Expected pay-application amounts by period from the schedule of values. The gross inflow before timing and retainage.
Collection lag
Realistic days from billing to cash, per owner. Modeling contract terms instead of actual behavior is the classic overstatement.
Retainage held and release timing
Cash withheld from each billing and when it is projected to return. Across a portfolio this can equal a full year's profit sitting idle.
Payroll disbursements
Direct and indirect labor by pay cycle - the most rigid and frequent outflow, and the one a shortfall hits first.
Supplier and subcontractor payments
Outflows by due date, often modeled pay-when-paid where contracts allow, which shifts the timing significantly.
Equipment and overhead
Rent, ownership costs, and company overhead that continue regardless of project cash. The fixed drain between inflows.
Debt service and financing
Loan payments and projected line-of-credit draws and repayments. The financing that bridges timing gaps.
Net cash flow by period
Inflows less outflows each period. The core output showing surplus or deficit before the running balance.
Cumulative cash position
The running balance against available cash and credit. Where the shortfall date becomes visible.
Minimum cash / covenant threshold
The floor below which the company breaches a covenant or cannot operate. The line the cumulative position must not cross.
Scenario assumptions
The billing curves, collection lags, and award timing behind the forecast. Making them explicit is what lets the forecast be stressed and improved.

Failure modes — how it breaks

Contract terms instead of payment behavior

Collections are modeled on the net-30 the contract states rather than the net-55 the owner actually pays, so every inflow lands weeks early in the forecast. The projected balance stays comfortably positive while the real balance heads toward a shortfall the model never sees.

Retainage ignored or mis-timed

Retainage is either not withheld in the model or assumed to release at substantial completion when it really trickles in over months after closeout. A large chunk of projected cash never arrives when the forecast says, and the retainage that funds nothing sits as the difference between profit and liquidity.

Profit mistaken for cash

Management reads the WIP or income statement, sees the company is profitable, and assumes cash is fine - when the profit is tied up in unbilled work, receivables, and retainage. Profitable growth is one of the most common ways a contractor runs out of cash, because every new job consumes cash before it returns any.

Front-loaded billing that reverses

The schedule of values is front-loaded to pull cash forward early, which helps the near-term forecast and then leaves the back end of the job cash-negative when there is billing left but little cost. The forecast that ignores this shows a false comfort that reverses exactly when retainage is also being held.

Never stressed

The forecast is a single deterministic line that has never been run against a slow payer, a delayed award, or a payroll spike. It looks fine until one plausible event happens, and then the company discovers the shortfall it could have seen coming had it stressed the model.

Stale and trusted

The forecast is updated quarterly but decisions are made from it weekly, so it no longer reflects new awards, changed schedules, or a payment slowdown. A stale forecast is worse than none because it carries the authority of a number while describing a world that no longer exists.

No reconciliation to actuals

Forecast cash is never compared to actual cash, so the model's systematic biases - always optimistic on collection, always late on retainage - are never corrected. The same errors recur every cycle and nobody knows the forecast cannot be trusted until it misses badly.

Metrics — how it is measured

Projected minimum cash position

The lowest cumulative balance over the horizon and when it occurs. The single most important output - how close the company comes to the floor.

Days of cash on hand

Cash and available credit divided by average daily outflow. Translates the balance into survival runway.

Forecast accuracy

Actual cash against forecast cash by period. Measures whether the model can be trusted and where it is biased.

Collection lag actual vs. assumed

Real days-to-cash against the model's assumption, by owner. The main driver of inflow error.

Retainage receivable

Total retainage withheld and awaiting release, with aging. Often a contractor's largest and slowest-moving asset.

Line utilization vs. capacity

Projected draw against the facility limit and covenants. Shows whether the financing plan is actually feasible.

Net cash burn / generation rate

Cash generated or consumed per period across the portfolio. Reveals whether growth is funding itself or draining the balance.

The AI shift — what actually changes

Conversational

The forecast stops being a spreadsheet you rebuild each month and becomes something you interrogate. You ask when the cash position dips closest to the floor, which owners' slow payment is driving it, how much of the gap is retainage not yet released, and what a two-week owner-payment slip does to the balance - with the billing schedules and payment history cited so the answer is grounded in behavior, not contract terms.

Generative

Cash narratives and financing plans are drafted from the model: a commentary explaining the projected low point and its drivers, a financing plan matching draws to shortfalls within covenant limits, or a lender-ready cash package that lays out assumptions, scenarios, and the plan to stay above the floor - written for the audience that will act on it.

Orchestrated

The forecast stops being disconnected from the systems that drive cash. Billing projections are built from the current schedules of values, collection lags are calibrated from each owner's actual payment history, retainage release is modeled from real contract terms and closeout timing, and shortfalls are matched to line capacity and covenants so the forecast, the AR aging, and the financing plan tell one consistent story.

Autonomous

The routine motion runs continuously: the rolling forecast updated as billings, awards, and payments post, collection lags recalibrated from actual receipts, forecast reconciled to actual cash to correct bias, scenarios re-stressed as conditions change, and any projected approach to the minimum-cash floor flagged early - while humans own the financing decisions, approve every line draw, and decide how to close any projected gap.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Treasury review to confirm the company can fund the next quarter of committed work.

Build our 13-week cash flow forecast from current project schedules of values and cost schedules, consolidated to the company. Model collections on each owner's actual payment history, not the contract terms, and hold and release retainage on real timing. Show me net cash by week and the cumulative position against our minimum-cash floor and line-of-credit capacity. Tell me the projected low point, the week it occurs, and the primary drivers. Then stress it three ways - our two slowest-paying owners each slip two weeks, a payroll spike from the new self-perform crew, and a delayed award we were counting on - and tell me which scenario breaches the floor first.

What good output looks like: A behavior-based 13-week forecast with the low point, drivers, and stress-test breaches identified against the floor and line capacity - not a single optimistic cash line.

Follow-ups:

  • How much of the projected gap is retainage that has not released yet?
  • If we accelerate billing on the two largest jobs, how much does the low point improve?
  • What line draw, and when, keeps us above the floor in the worst scenario?

Generative — The bank wants a cash package supporting a request to increase the line of credit.

Draft the cash flow narrative for our lender package supporting a request to increase our line of credit. Using the 13-week and 12-month forecasts, explain our cash cycle - how long we fund work before collection, the effect of retainage, and our billing profile - describe the projected low points and what drives them, and lay out the financing plan that keeps us above our covenant threshold in both base and stressed cases. Be explicit about the assumptions behind collection timing and state where we have calibrated them to actual owner behavior. Keep it measured and specific, in the register a credit officer expects, and do not understate the risk of the slow-payer scenario.

What good output looks like: A model-grounded cash narrative with explicit, calibrated assumptions, base and stressed scenarios, and a covenant-aware financing plan - credible to a credit officer.

Follow-ups:

  • Add a paragraph quantifying our retainage receivable and its expected release schedule.
  • Produce the one-page executive summary that leads the package.
  • Rewrite the assumptions section to preempt the question of why we are not just billing faster.

Orchestrated — You want the cash forecast, AR aging, and financing plan to stay one consistent story.

Reconcile our cash flow forecast with the AR aging and the financing plan. Recalibrate each owner's collection lag from its actual payment history in the aging, rebuild the retainage release schedule from the real contract terms and projected closeout dates, and rebuild the billing projections from the current schedules of values. Then recompute the consolidated forecast, identify the projected low point and its drivers, and match any shortfall to available line capacity within our covenants. Flag where the aging shows an owner paying materially slower than the forecast assumes, and where retainage that the forecast counts on is stuck. Tie each adjustment to the record and flag anything uncertain.

What good output looks like: A forecast reconciled to real payment behavior and retainage timing, consistent with the AR aging and financing plan, with drivers and uncertainties surfaced and records cited.

Follow-ups:

  • Which slow-paying receivables should collections prioritize to protect the low point?
  • If the stuck retainage does not release on time, when do we breach the floor?
  • Draft the internal note reconciling why cash and profit diverge this quarter.

Autonomous — Standing policy for keeping the rolling cash forecast current and honest.

Maintain our rolling 13-week cash forecast continuously under these rules. As billings, receipts, awards, and payments post, update the forecast and recalibrate each owner's collection lag from actual receipts rather than contract terms. Model retainage held and released on real contract and closeout timing. Reconcile forecast cash to actual cash each week and report the bias so the model self-corrects. Re-run the standing stress scenarios as conditions change, and flag early - at least four weeks out - any projected approach within a defined buffer of the minimum-cash floor or line capacity. Never initiate a line draw, never change payment timing to a vendor, and never commit to a financing action without my approval, and route every projected floor approach to me with the drivers.

What good output looks like: A continuously reconciled, self-calibrating cash forecast with early floor warnings and a short action queue, where every financing decision stays with a person.

Follow-ups:

  • Show me this week's forecast-to-actual variance and where the model was biased.
  • Which scenario now breaches the floor soonest, and what is the earliest week I must act?
  • Draft the financing action for the projected shortfall for my approval.

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

  1. Level 0 - Bank balance

    Cash management is checking the bank balance and reacting to shortfalls when they arrive. There is no forward view and every crunch is a surprise.

  2. Level 1 - Static forecast

    A cash forecast is built periodically in a spreadsheet from billing and cost plans, but on contract terms and without stress testing, so it is optimistic and quickly stale.

  3. Level 2 - Behavior-based and stressed

    Collections are modeled on actual payment behavior, retainage on real timing, and the forecast is stressed against slow payers, delayed awards, and payroll spikes with a financing plan attached.

  4. Level 3 - Assisted

    The forecast is built from live schedules of values and payment history, reconciled to actuals to correct bias, and floor approaches are flagged for review.

  5. Level 4 - Operated

    The rolling forecast stays current and self-calibrating inside guardrails - updating, reconciliation, stress-testing, and early floor warnings - while humans own every financing decision and line draw.

Common questions

How can a profitable contractor run out of cash?

Because profit and cash are different things separated by timing. A profitable job still requires the contractor to pay labor weekly and suppliers monthly while billing monthly, waiting net terms for payment, and having retainage withheld until closeout - so the cash goes out long before it comes back. When the company grows, every new job repeats this cash drain, and fast, profitable growth can consume cash faster than the completed jobs return it. The income statement says the company is winning while the bank balance says it is drowning, which is exactly why the cash flow forecast is a separate instrument.

Why model actual payment behavior instead of contract terms?

Because owners pay when they pay, not when the contract says, and the gap between the two is where cash forecasts go wrong. An owner on net-30 terms who consistently pays in 55 days will, if modeled on the contract, put every collection into the forecast almost a month early, and across a portfolio that error is enough to hide a real shortfall. Calibrating each owner's collection lag from its actual payment history in the AR aging is the difference between a forecast that warns you and one that lulls you.

How is the cash flow forecast related to the WIP schedule?

The WIP schedule measures earnings - it recognizes revenue and margin based on work performed - while the cash flow forecast measures liquidity, the actual timing of money in and out. They draw on the same projects but answer different questions, and they routinely diverge: a job can be earning strong margin on the WIP while consuming cash because its billings lag its costs and retainage is being held. A contractor needs both, because the WIP tells it whether the work is profitable and the cash forecast tells it whether it can afford to keep doing the work.

Read this article as markdown · Browse all 110 objects