Forecast construction project cash gaps

Direct answer

For this review, explain cash gap as timing mismatch between cash out and cash collected, then show forecast by project phase.

Why this question comes up

Contractors pay labor/materials before progress billing and retainage cash arrives. This guide turns that concern into a review that can be repeated with a defined period, consistent inputs, and a visible trail back to the records.

Records to gather

• Schedule of values with billing milestones per project
• Retainage percentage and release conditions
• Subcontractor and supplier payment terms
• Change orders — approved, pending, and disputed
• Payroll and equipment costs by project and week
• Historical days from application for payment to cash received

Review workflow

1. Recognise the structural gap. Construction pays labour and materials weekly or monthly while collecting on billing cycles that often run 60–90 days behind, with a portion retained. The gap is inherent, not a failure.
2. Model retainage explicitly. Retainage held at 5–10% across several active projects is a substantial sum unavailable until release conditions are met — often long after practical completion.
3. Forecast by project and in aggregate. A single project can be cash-positive while the portfolio is not, and the timing of overlapping projects is what creates the squeeze.
4. Treat pending change orders as uncertain. Work performed against an unapproved change order is cost incurred with no billing right yet. Do not forecast it as revenue.
5. Time subcontractor payments against collection. Pay-when-paid terms, where enforceable, shift timing materially. Where they are not enforceable, you carry the gap.
6. Look ahead at least a full billing cycle. A 13-week horizon is usually the minimum for a business on 60-day collection.

What a useful answer should include

• Weekly cash position by project and in aggregate
• Retainage held, by project, with expected release timing
• Pending change orders separated from approved
• Subcontractor payment timing against expected collection
• The lowest projected position and the week it occurs
• Historical collection lag used, not contractual terms

Common failure modes

• Forecasting on contract terms. Actual days to payment are the only reliable basis.
• Omitting retainage. It accumulates quietly across projects into a large locked-up balance.
• Counting unapproved change orders as revenue. Cost is real; the billing right is not yet.
• Project-level view only. The squeeze comes from overlapping project timing, which is only visible in aggregate.

Community context

The linked community posts show why people search for this topic and which parts create confusion in practice. They are anecdotal. Use the reference sources and your organization’s policies for accounting treatment, tax, compliance, and final decisions.