Construction Estimating and Project Management That Stay Connected

• Construction estimating and project management are two functions that should be deeply connected but are often managed as if they are separate activities with a single handoff point at contract award. The estimate gets produced. The project gets awarded. The project management team picks up the number and tries to deliver within it. The link between the assumptions that produced the estimate and the decisions made during delivery is often weaker than either function would benefit from.
• Construction estimating and project management that stay genuinely connected throughout a project produce better outcomes than those that are managed in isolation. The estimate that informs the project management decisions. The project performance that informs future estimating. The assumptions embedded in the estimate that the project team understands rather than inherits as a budget with no explanation of how it was built.

Why the Gap Between Estimating and Project Management Matters

• The gap between how a project was estimated and how it gets managed creates specific and recurring problems that better connected processes would prevent.
• The project manager does not understand the estimated basis. The allowances that were made for specific activities. The productivity rates that were assumed. The risk items that were priced or excluded. Without understanding these assumptions the project manager cannot identify when actuals are diverging from the estimate basis or why. They manage against a budget without the context that would allow them to understand whether a cost variance reflects a genuine problem or an estimate assumption that has simply not been tested yet.
• The estimator does not receive feedback from project performance. The assumptions that consistently prove optimistic get made again on the next estimate. The risk items that consistently materialise get priced at the same level as items that rarely do. The productivity rates that reflect what the team achieves in ideal conditions get applied without adjustment for the specific site conditions of each project. Estimating accuracy improves only when project performance data flows back to inform future estimates.
• Procurement decisions are made without reference to the estimate. Material packages that were estimated at rates that no longer reflect the market get bought at current prices without anyone connecting the difference to the project margin. Subcontract packages that were estimated at rates based on a specific scope get awarded at rates that include variations the estimator did not price. These procurement outcomes affect project margin in ways that only become visible at the final account when the opportunity to manage them has passed.
• Programme assumptions in the estimate are not reflected in the project programme. The estimate assumed a twelve month programme. The project was planned to be a fourteen month programme. The preliminary costs associated with two extra months were never budgeted. The programme that the project is managed against does not connect to the duration assumptions that determined the preliminary costs in the estimate.

What Connected Estimating and Project Management Actually Looks Like

• Construction estimating and project management that are genuinely connected share the estimate basis and use it throughout the project rather than treating the estimate as a document that produces a number and is then filed.
• The estimated breakdown becomes the project cost plan. Not as a reformatted version of the estimate that loses the detail of how costs were built up but as the actual estimate structure presented in a form the project team can manage against. The allowances for each cost element visible. The productivity rates that were assumed accessible. The risk items that were priced and those that were excluded were documented.
• The programme that was assumed in the estimate is reflected in the project programme. Not necessarily as the controlling programme but as the reference against which the project programme is compared. Where the project programme differs from the estimate programme the cost implications of those differences are identified and accounted for rather than being discovered at final account.
• Procurement is managed against the estimate. Each package bought is compared to the estimated allowance for that package. Where market conditions have moved the estimate allowance is no longer achievable the commercial team understands the margin implication before the award rather than after it. Where scope has changed from what was estimated the difference is captured as a project risk item rather than being absorbed into the package cost without attribution.
• Project performance is tracked against estimated assumptions. Labour productivity compared to the rates assumed in the estimate. Plant utilization compared to the programmed that was estimated. Material consumption compared to the quantities that were taken off. These comparisons identify where the project is performing to the estimate basis and where it is diverging in ways that need management attention.

The Estimating Data That Should Flow Into Project Management

• Specific data generated during estimating should flow directly into the project management process rather than being left behind when the estimate is complete and the project begins.
• Quantities. The material quantities taken off during estimating are the reference for procurement and for tracking material consumption during delivery. A concrete quantity that was estimated and then re-measured for procurement rather than using the estimated quantity represents double work. A material consumption that exceeds the estimated quantity without anyone identifying the variance until the project is complete represents a missed opportunity to investigate and manage the difference.
• Productivity assumptions. The output rates assumed for each trade, for plant operations and for specific activities determine how the project is programmed and what the labour and plant costs should be. These assumptions should be documented during estimating and available to the project manager rather than being implicit in the programme that the estimate produced.
• Subcontractor allowances. The rates and scopes that were used to estimate each subcontract package are the reference for subcontract procurement. Where the awarded subcontract differs from the estimate in rate, scope or programmed the difference should be identified and managed rather than absorbed into the project cost without attribution.
• Risk register. The risk items identified during estimating that were priced or excluded should become the starting point for the project risk register. Risks that were priced at a specific allowance need to be tracked against that allowance. Risks that were excluded need to be monitored for whether they materialise and whether they create a commercial claim.

The Project Performance Data That Should Flow Back to Estimating

• The connection between construction estimating and project management works in both directions. Just as estimate data should flow into project management, project performance data should flow back to inform future estimating.
• Actual productivity rates achieved on different activity types in different ground and weather conditions. Actual material quantities compared to measured quantities and the reasons for any difference. Actual preliminary costs compared to the estimate and the reasons for any significant variance. Actual subcontract costs compared to the allowances and what drove the differences.
• This performance data accumulated across projects builds the database of actual experience that makes future estimating more accurate. Not because every project is the same but because patterns in how specific types of work performed in specific conditions become visible when the data is captured and reviewed rather than being lost when each project closes.
• The feedback loop that connects project performance to estimating accuracy is one of the most valuable things a construction business can build and one of the least commonly developed. The businesses that build it produce estimates that consistently reflect their actual performance better than those whose estimating relies on industry benchmarks and individual estimator experience without the grounding of their own performance data.

Technology That Supports the Connection

• Construction estimating and project management that stay genuinely connected benefit from technology that supports that connection rather than requiring manual translation between systems.
• Estimating software that produces output in a form that feeds directly into project cost management rather than requiring reformatting and re-entry. The estimate structure that becomes the cost plan. The quantities that become the procurement reference. The programme assumptions that become the project programme baseline.
• Project management software that captures actual performance in a form that can be compared to estimate assumptions rather than just tracking costs against budget headings that have lost their connection to how the budget was built. Actual productivity tracked against the rates that were estimated. Material consumption tracked against the quantities that were taken off. Plant utilisation tracked against the programme that determined the plant cost in the estimate.
• Reporting that shows estimate versus actual at the level of detail that allows the reasons for variances to be understood rather than just the fact of the variance. A cost overrun on a subcontract package that is attributable to a scope increase that was not in the estimate is a different management issue from one that is attributable to the estimate rate being wrong. The reporting that distinguishes between these provides better information for both current project management and future estimating.
• EZY PLANO is a platform built for construction businesses that want their project management connected to how their projects were planned and estimated rather than managing against a budget that has lost its connection to the assumptions that produced it. Supporting the information flow between estimating and project delivery that keeps the two functions genuinely connected throughout the project lifecycle rather than separated after the estimate is complete.

Questions Worth Asking

How do we make the estimate basis accessible to the project team without it being misinterpreted as a management document rather than an estimating document? 

• Document the key assumptions separately from the detailed estimate build-up. The productivity rates assumed. The programmed basis. The risk items included and excluded. These assumptions in a format that the project manager can use as a management reference are more useful than the full estimate detail which was designed for estimating rather than for management.

How do we capture project performance data in a way that is actually useful for future estimating without creating significant additional administrative overhead? 

• Focus on capturing the data that will actually be used rather than capturing everything that might be relevant. Productivity rates on key activity types. Subcontract cost compared to allowance and the reason for significant variances. Preliminary cost compared to estimate and the programme-related reasons for differences. 

How do we connect our estimating and project management systems when they are currently separate platforms? 

• Identify the specific data that needs to flow between them and establish a defined process for that transfer even if it is manual initially. The quantities that become procurement references. The programme assumptions that become project programme baselines.