Analysing real-world construction projects

Theory is essential, but real-world experience is where Quantity Surveyors truly sharpen their skills. In this topic, we’ll explore how to analyse real-world construction projects to understand how cost capture, control, and management are applied outside the classroom.

By learning from real projects—both successful and problematic—you’ll build a stronger foundation for decision-making, problem-solving, and professional judgment.

Why Analyse Real Projects?

Looking at real-world case studies helps you:

  • Bridge the gap between theory and practice
  • Understand practical constraints like programme pressures, client expectations, and changing scopes
  • Learn from mistakes (without paying the price!)
  • Identify best practices for cost management
  • Build confidence in tackling similar situations in your own career

Each project presents unique challenges—from budget overruns and contract disputes to innovation in cost-saving strategies. The more projects you study, the sharper your instincts become.

What to Look for When Analysing a Project

Whether you’re reviewing a completed project or working on a live one, there are several key aspects to examine:

1. Project Overview

  • Type: Residential, commercial, infrastructure, etc.
  • Scope and size
  • Location and duration
  • Delivery method (Design & Build, Traditional, etc.)

2. Contractual and Procurement Arrangements

  • Contract type used (JCT, NEC, etc.)
  • Procurement strategy (e.g. single-stage tender, negotiated, framework)
  • Client expectations and constraints

3. Cost Management Strategy

  • Initial budget vs final account
  • Use of cost planning and forecasting tools
  • Application of contingencies
  • Use of BIM or cost management software
  • How variations were handled

4. Challenges Encountered

  • Unforeseen ground conditions
  • Design changes
  • Inflation or material shortages
  • Delays and disruption
  • Disputes and claims

5. Lessons Learned

  • What worked well (e.g. early contractor involvement, transparent reporting)
  • What could have been improved (e.g. unclear instructions, poor communication)
  • How cost overruns or disputes were resolved
  • Recommendations for future projects

Example Case Study 1: City Centre Mixed-Use Development

Project: £40M mixed-use development in Manchester
Contract Type: JCT Design and Build 2016
Procurement Route: Two-stage tender
Duration: 18 months

Key Points:

  • BIM used for cost planning and clash detection
  • Early design freezes helped control variation risk
  • Cost overruns occurred due to unexpected ground contamination (£500k over original budget)
  • Final account settled amicably due to clear valuation procedures and good record-keeping

Lessons Learned:

  • Early engagement with the supply chain reduced risk
  • Importance of allocating a realistic contingency for groundworks
  • Collaboration between QS, architect, and client reduced conflict

Example Case Study 2: School Refurbishment Project Gone Wrong

Project: £5M refurbishment of a secondary school
Contract Type: NEC Option A
Procurement Route: Single-stage lump sum
Duration: Planned 9 months, completed in 14

Key Issues:

  • Poor design information at tender stage
  • Numerous client-led variations during construction
  • Poor communication between QS and contractor
  • Disputed final account: £900k difference in valuations
  • Required third-party adjudication

Lessons Learned:

  • Importance of a well-defined scope before tendering
  • Clear variation process and approval hierarchy must be agreed early
  • Early warning mechanisms in NEC contracts must be used effectively
  • Accurate, timely record-keeping is non-negotiable

How to Practise Analysing a Project

To develop your skills, try working through the following tasks using either real project documentation (with permission) or simplified project packs provided in training:

  1. Review the original budget and final account.
    • What caused the increases or savings?
  2. Track how variations were managed.
    • Were the changes recorded, priced, and approved promptly?
  3. Identify risk allowances and how they were used.
    • Were provisional sums and contingencies sufficient?
  4. Evaluate how the QS communicated with stakeholders.
    • Was cost information clear, timely, and evidence-based?
  5. Make your own list of lessons learned.
    • What would you do differently on a future project?

Pro Tip: Use a Project Analysis Template

You can create your own project review template to use whenever you study a project. Include fields like:

  • Project Name and Summary
  • Contract and Procurement Details
  • Budget vs Final Cost
  • Key Cost Risks and Outcomes
  • Variation Management Process
  • Cost Reporting Methods
  • Final Lessons Learned

This helps ensure consistency in how you gather insights—and it looks great in a professional portfolio or APC preparation file.

Summary

Analysing real-world projects is one of the best ways to develop practical cost management skills. From managing scope creep to dealing with difficult contractors, these case studies expose you to the realities of life as a QS.

Every project tells a story. Your job is to learn from it—so that when it’s your turn to lead, you’re prepared, proactive, and one step ahead.