Project Pipeline for Construction Forecasting

A healthy order book starts before a contract is signed. Tender enquiries, quotations and negotiations all represent possible future work, but a list of their headline values is not yet a useful forecast. A construction project pipeline brings value, confidence and likely delivery dates together, giving commercial teams a consistent view of what may become revenue.

BuildQS Project Pipeline keeps prospects apart from live contracts while making the route from opportunity to project straightforward.

What is a construction project pipeline?

A construction project pipeline is a structured register of prospective and secured work. Each entry identifies an opportunity, its estimated contract value, its current stage, the likelihood of winning it and the period in which delivery is expected.

That is more informative than a tender log. A tender log can tell you that five bids worth £1 million are outstanding. A pipeline helps answer better questions: how much is secured, how much remains uncertain, when could the work happen, and which assumptions need review?

Why we built Project Pipeline in BuildQS

Many subcontractors track prospects in one spreadsheet and create projects in another system after award. Values are copied between files, dates become stale, and nobody is quite sure whether the latest tender revision reached the forecast. The same opportunity may appear under slightly different names, or stay in the pipeline long after it was lost.

Project Pipeline keeps that work alongside the BuildQS project workflow, without treating an unconfirmed tender as a live contract. The table records the project name and number, estimated value, stage, probability, start date and duration. The dashboard then organises those entries into total, secured and non-secured values, revenue periods and top opportunities.

This separation is deliberate. Prospects can change quickly, whereas live projects need controlled valuations, payment applications and retention records. Keeping the two states distinct avoids contaminating operational reports while preserving a clear conversion route when work is won. It also removes some of the copying and formula risks discussed in our comparison of BuildQS and payment application spreadsheets and the wider BuildQS versus Excel guide.

How probability-weighted forecasting works

Probability weighting reduces each estimated value according to the current chance of winning it:

Weighted value = estimated value × probability

BuildQS totals those results for the opportunities visible in the Pipeline Table. It also shows the unweighted total, prospect count and average probability. An unset probability counts as 100% in the weighted calculation rather than being excluded, so enter an explicit value when full weighting is not intended. Filters update these table KPIs.

A probability is a planning assumption, not a fact. Teams should use a repeatable policy, review it when evidence changes and avoid raising percentages simply to close a forecast gap. In BuildQS, marking an opportunity Won sets it to 100%, while Lost sets it to 0%. The working stages are Lead, Quoted, Negotiating, Won and Lost.

Timing is handled separately. Where an opportunity has a start date and duration, BuildQS spreads its estimated value evenly across the inclusive calendar months in that period. The dashboard groups this forecast by month or financial year and separates 100% opportunities as secured from the rest as non-secured. This is a simple revenue profile, not a detailed programme or payment schedule.

Worked example: a £240,000 opportunity

Suppose Riverside Office Refurbishment has an estimated value of £240,000 and a win probability of 60%. Its probability-weighted value is:

£240,000 × 60% = £144,000

That £144,000 belongs in the weighted pipeline KPI. If the expected delivery period is six inclusive months, the unweighted timing view spreads the £240,000 estimate evenly, showing £40,000 in each month. It does not spread £144,000 across those months. Keeping these views distinct lets you discuss likelihood and delivery timing without pretending either is a certified revenue figure.

How to use Project Pipeline in BuildQS

Project Pipeline is reached from the Projects navigation. It opens on a dashboard summary, with a separate Pipeline Table for maintaining individual opportunities. Feature availability depends on your current BuildQS plan and rollout access, so check the latest options on the pricing page.

1. Add the opportunity

Open the Pipeline Table and add a project projection. Start with a recognisable project name. Add your tender or enquiry number if your business uses one, so estimators and commercial managers can match the entry to the source documents.

BuildQS also supports spreadsheet import and export when you need to bring in an existing register or review the data outside the application.

2. Set value, stage and probability

Enter the current estimated contract value, choose Lead, Quoted, Negotiating, Won or Lost, and set a probability from 0% to 100%. Use the best current value rather than an early budget that has already been superseded by a quotation.

Agree probability rules within your team. For example, you might assign a low percentage to a qualified lead, increase it after submitting a compliant quote, and raise it again only when you have evidence of serious negotiation. Stage describes where the opportunity is; probability expresses confidence. They are related, but should not be treated as interchangeable until an opportunity is won or lost.

3. Add likely timing

Set the expected start and duration in months. BuildQS derives the end of the forecast period and allocates the estimated value evenly across each included month. An opportunity without dates remains visible in pipeline totals but cannot contribute to the time-based revenue view.

Use realistic mobilisation and delivery assumptions. If a client moves the proposed start date, update the pipeline promptly. Timing errors can make a healthy annual total look like enough work for a particular quarter when the likely delivery periods actually leave a gap.

4. Review the table and forecast

Use the dashboard to compare total, secured and non-secured pipeline, inspect revenue by month or financial year, and identify the highest-value opportunities. The Pipeline Table gives the detailed view, including probability-weighted value, average probability, stage filters and month-range controls.

Review both views regularly, including changed probabilities, dates and lost work. For broader liquidity planning, combine this forward-looking workload view with actual application and payment timing using our guide to cash flow forecasting for construction subcontractors.

5. Convert won work into a live project

When an opportunity is marked Won, BuildQS offers the option to create a live project from it. The conversion form carries the opportunity name, estimated value and dates into project setup, while asking for the client and contract details needed by the live workflow.

After conversion, the pipeline entry links to the created project and is no longer edited or deleted as an ordinary prospect. This preserves the history and prevents duplicate conversion. The live project can then hold its Master Valuation Schedule, applications, variations and retention information. It is a cleaner handover than retyping a won tender into an unrelated workbook.

What the forecast does and does not tell you

The pipeline is a decision aid. It shows the combined value of opportunities, the effect of your probability assumptions and a simple spread of estimated revenue over expected delivery months. It can expose workload gaps, excessive dependence on one tender, or a forecast that relies heavily on low-confidence work. An unset probability counts as 100%, so an incomplete entry can overstate the confidence-adjusted total.

It is not recognised revenue, a contract, a construction programme or a cash flow statement. The timing profile is spread evenly; it does not model front-loaded procurement, measured progress, retention, payment terms, certification delays or late payment. Weighted values are useful across a portfolio, but £144,000 of weighted pipeline does not mean 60% of a particular £240,000 job has been won.

Treat the result as one input to planning. Compare it with delivery capacity, margin expectations and cash collection. The relationship between time, cost and scope is covered in our guide to the iron triangle in construction. Keep assumptions dated, assign responsibility for updates and revisit the pipeline often enough that decisions are based on current evidence.

Prefer to walk through your workflow live first? Book a Demo

Frequently asked questions

Is weighted pipeline value recognised revenue?

No. It is the estimated value of each visible opportunity multiplied by its stated probability, then totalled. It is a portfolio planning measure, not turnover earned, work completed, an approved application or cash due. Recognised revenue should follow your accounting policy and actual contract performance.

What probability should I use for a tender?

Use a percentage supported by your own historical win rates and current evidence. A submitted quotation should not automatically receive the same probability in every market or with every client. Define internal bands, apply them consistently and adjust them when scope, competition, client intent or negotiation status changes.

Can I keep prospects separate from live projects?

Yes. Pipeline entries remain prospects until won work is deliberately converted. This keeps uncertain opportunities out of live project controls and payment application reporting while retaining one place to review future work.

What happens when an opportunity is won?

Setting the stage to Won sets probability to 100%. You can then create a live BuildQS project through the conversion action, complete the client and contract information, and continue into project setup. The original pipeline entry records its link to that project so users can open it without converting the same opportunity twice.