Backlog and burn forecast for construction
Backlog value and backlog months by project and month, with weighted pipeline shown beside it but never counted as backlog.
The problem
Owners ask how much work is in hand and how long it will last, and the answer usually comes from a spreadsheet that mixes signed contracts with deals still in sales. Without a consistent burn rate, nobody can say when the team will run out of work or when to push for new wins.
What we build
We compute backlog from signed work in Procore (revised contract minus earned revenue), derive a burn rate from recent earned revenue, and express backlog in months. If your CRM is connected, weighted pipeline sits beside backlog by month, labeled as pipeline and never added to it.
How it works
- 1
Define backlog
Backlog is revised contract minus earned revenue, per project, using the same earned revenue as the WIP schedule so the two always tie.
- 2
Set the burn rate
Backlog months equals backlog divided by average earned revenue over the last three months; the window is a documented setting.
- 3
Add pipeline separately
HubSpot deals feed pipeline and weighted pipeline (amount times probability), shown next to backlog as total forward work.
- 4
Watch it by month
Backlog by month and by project shows whether new wins are replacing the work being burned.
- Procore
- HubSpot
- QuickBooks Online
- Microsoft Fabric
- Power BI
The value it creates
Forecasting
Backlog months gives a stated, repeatable view of how long current work lasts at the recent pace.
Early warning
A falling backlog-months line flags a coming gap while there is still time to win work.
Collective intelligence
Sales, operations and finance read one forward-work view instead of separate pipeline and job lists.
Proof
Related use cases
Frequently asked questions
Why not include likely wins in backlog?
Backlog should be signed work. Adding deals inflates it with work that may never arrive, so we show weighted pipeline beside backlog as 'total forward work' and keep the two figures distinct.
How is the burn rate calculated?
In the built version, average earned revenue over the last three months. A longer window smooths seasonal swings; we agree the window with you and document it.
Do we need HubSpot for this?
No. Backlog and burn come from Procore alone. The pipeline layer switches on when a CRM is connected, and other CRMs can follow the same pattern.
Next step
Which report or workflow would you like to improve?
Tell us what your team does today, which systems are involved, and what you want to change. We'll discuss whether there is a practical fit.
Prefer email? charley@buildflows.ai