Money spent and work done on a construction project can tell two different stories. I am Dr Sepehr Abrishami. I once set up a design office of my own, and now, as a researcher and the host of Reimagining AEC, I want to show what changes when a building information model, rather than a set of spreadsheets, sits at the centre of cost management. Let me begin with a month-end meeting. It is illustrative rather than a real project. A contractor is building a new station on a light rail extension. The structural concrete for the station box is one work package, with a budget of one million pounds. At the meeting, the package manager reports that six hundred thousand pounds has been spent. The planner says the programme expected four hundred thousand pounds of work to be done by now. The client's representative asks one thing. Is this package in trouble? Nobody in the room can answer. Six hundred thousand pounds spent could mean the package is running fast and costing what it should. It could mean it is on time and badly over budget. It could mean both problems at once. Spending, on its own, tells you how much money has left the account. It tells you nothing about what that money bought. The missing figure is how much of the work has been built, measured in a way everyone agreed in advance. So the question for this episode is this. How does a project team know, at any point in the job, whether it is on cost and on programme, and what does BIM contribute to making that answer trustworthy? By the end, you will be able to set out a progress monitoring strategy built on a structured work breakdown, apply earned value management to judge cost and schedule performance, evaluate how quantity, progress and cost data are collected from site, and explain how a model-based workflow brings these together into one reporting system. We will take it in five parts. First, two definitions and the case for working from a model. Second, how the model connects to estimating, budgeting and control. Third, how progress is measured, from a single wall up to the whole project. Fourth, earned value itself, which answers the client's question. Fifth, where the data comes from, and what a working system looks like on a large programme. Our station box will come back at each stage. Start with project controls. A project is a temporary endeavour, with a defined budget and a defined end date. Project controls is the process that keeps it on track. It controls scope and time, so the work is delivered to programme, and it controls budget, so the work stays within the funds available, without compromising quality. Organisations invest in it for four reasons, which come down to two. During the job, it lets managers monitor performance month by month rather than discovering the outcome at the end, and it makes a named party responsible for corrective action when something slips. After the job, and alongside it, it gives stakeholders accurate, timely reporting on earned value and cost performance, and it captures historical data that improves the next estimate. Our month-end meeting failed on the first of these. The monitoring existed, but it could not produce a judgement. The second definition is building information modelling, or BIM. BIM is the process of creating and managing a digital representation of a built asset, in which each object carries information as well as geometry. A wall, a column, a foundation, a reinforcement bar, each one records what it is as well as where it is. The current international standard, the ISO 19650 series, frames BIM as the management of that information across the whole life of the asset, from planning and design through construction and into operation. The value is twofold. The model gives a clear three-dimensional view of the asset before anything is built, which matters because clients and operators cannot always read a two-dimensional drawing. And it links that geometry to structured data, so the same model serves architecture, engineering design, detailing and fabrication, and, for our purposes, project management and cost control. The clearest argument for working from a model is the cost of poor coordination, and three real cases from site make it. In the first, a lighting structure was never coordinated with the building beneath it, so the two were built overlapping each other. In the second, a bridge was built out from both ends, and the levels did not agree, so a step was left where the two halves met. In the third, a pipe run clashed with a structural column nobody had planned around, and someone cut through the column on site to make the pipe fit. Each one is expensive rework, and the last compromised the structure itself. Each one is a clash a coordinated model would have caught. Resolved in the model, a clash costs a change of geometry. Resolved on site, it costs time, money and sometimes structural integrity. Timing matters as much as coordination. Picture two curves across the life of a project, running from preliminary design through detailed design, construction documentation and construction, to operation. The first curve is your ability to influence cost and performance. It starts high in preliminary design and falls steadily as decisions become fixed, until in operation there is little left to influence. The second curve is the cost of making a design change. It starts low and climbs, slowly through design and then steeply once construction is under way. A traditional drafting workflow peaks late, in construction documentation, when changes are already becoming expensive. A BIM workflow moves effort earlier, into design, where influence is high and change is cheap. The lesson for cost is direct. The more information we capture during design, and the more consistently we hold it in the model, the fewer expensive changes we face later. That reasoning explains the benefits usually claimed for BIM, which reduce to three ideas. Errors are caught before they reach site, through better visualisation, clash detection and more accurate information, which also cuts waste and safety risk. Everyone works from one shared model rather than disconnected drawings, which improves collaboration and lets work be sequenced more accurately, so processes and programmes get shorter. And the data carries forward into operation, so the operator inherits a data-rich model with service life and maintenance information in the objects, which lowers operational cost and improves asset management. None of this follows from buying software. These benefits come from disciplined information management. One more piece of vocabulary. BIM is often described in dimensions. Three D is the geometric model. Four D adds the schedule, so the construction sequence can be seen over time. Five D adds cost, by linking quantities and rates to model objects, so that value engineering options can be tested, and it is the dimension this episode is about. Six D is usually associated with sustainability and energy analysis, and seven D with facility management across the operational life. Beyond three D, the dimensions are not formally standardised, and different countries and vendors define them differently. The more rigorous concept, and the one the standards now use, is level of information need, set out in ISO 7817-1 of 2024. It defines exactly what geometry, data and documentation are needed for a given purpose at a given stage. For a cost workflow, that is a firmer basis than a dimension number, because it tells the modeller what the quantity surveyor will need from each object. So the foundations are in place. Project controls asks for a regular, objective judgement of performance. BIM offers a single, information-rich model from which that judgement can be drawn, provided the information is managed with discipline. The next step is to connect the model to cost management itself. Cost management has three tasks, and BIM changes each of them differently. Cost estimation is the prediction of cost from measured quantities. BIM generates those quantities directly from the model objects, so the take-off is faster, more consistent and traceable back to the geometry. In UK practice the measurement rules are the New Rules of Measurement published by the Royal Institution of Chartered Surveyors, or RICS, and the International Cost Management Standard gives a common classification for reporting cost, including life cycle cost. Cost budgeting is the allocation of the estimate across the work breakdown structure and the organisational breakdown structure. BIM ties each budget line to the objects it pays for and to the party responsible for them. Cost control is the ongoing comparison of performance against that budget. This is where BIM makes the largest difference, because progress can be measured object by object and fed back close to real time. That is what makes reliable earned value possible, and it is exactly what our month-end meeting lacked. Those three tasks sit inside an integrated framework, which is easiest to follow as three zones that information passes through in turn. The first zone is design and engineering. It produces the BIM model, the drawings and the specifications, and it runs document and change control, so every revision is registered. The second zone is the model and commercial zone. Here the model feeds quantity take-off and the bill of quantities, which in turn drive procurement and material control. The planning schedule, the programme, sits in this zone too. The third zone is project controls. It combines the modelled quantities, the programme and actual data from site to produce what management needs, which is the cost and progress reports, the payment certificates and the earned value assessment. The essential feature is that estimating, planning, procurement and progress all draw on the same model and the same breakdown structure, rather than on separate systems reconciled by hand. Day to day, that framework runs as a loop rather than a line. It starts with coordinated drawings and disciplined documentation, so any variation updates the model and passes through change control. From the model, the team takes off quantities and builds the bill of quantities. That produces a material take-off, which feeds procurement, so materials are bought and expedited before they cause delay. When suppliers return shop drawings, those come back into the model, which keeps the take-off accurate. On site, model data is combined with the schedule to produce a three-week look-ahead, the short-term plan that manages the work. The model stays the single source of truth throughout. On top of the loop sits a cost control strategy, a sequence in which each step depends on the one before. It begins with a proper work breakdown structure, because everything else hangs from it. Quantities then come from the three-dimensional model, so they are traceable, and a detailed estimate is built from that take-off. The plan and the budget are integrated, and the budget is laid out along the organisational breakdown structure, so that every work package and every subcontractor has a responsible manager. Progress is then measured at object level, actual costs are collected against consistent cost codes, and a single reporting approach brings cost, time and progress together. Follow that sequence and the result is a project controls system based on earned value management, which gives management what it needs to make prompt, evidence-based decisions. Skip the first step, and nothing that follows can be added up. For our station box, this means the concrete package is not a single line in a spreadsheet. It is a set of objects in the model, each with a quantity, a budget, a place in the programme and a manager who answers for it. That brings us to progress, and to the work breakdown structure, often shortened to WBS. Progress has to be measured somewhere specific and then rolled up, and the WBS defines where. Here it has seven levels, best walked from the top down using our station. Level one is the phase, which is engineering, construction, commissioning or maintenance. Our package sits in construction. Level two is the main area, here the station itself. Level three is the sub-area or discipline, here structural, alongside mechanical and electrical. Level four is the stage, a set of activities that complete one type of work, such as the reinforced concrete walls. Level five is the critical path activity that the planner schedules. Level six is the object, a specific item defined in the model, for example one shear wall on the east side of the station box. Level seven is the set of operations needed to complete that object, which for a concrete wall means fixing reinforcement, erecting formwork, pouring, striking the formwork, curing and a quality control release. The principle is to measure at the lowest sensible level, and then aggregate consistently all the way up. Measurement uses rules of credit, agreed with the client before work starts. At operation level, each operation carries a weight that reflects its share of the effort, and the weights add up to one hundred per cent. For a concrete wall, one example set gives erecting formwork thirty-three per cent and pouring forty per cent, so together those two account for nearly three-quarters of the wall. Fixing reinforcement is worth ten per cent, the quality control release another ten, and the remaining seven per cent is split between striking the formwork at five and curing at two. As each operation finishes, the wall earns its weight. Once the reinforcement is fixed and the formwork is up, our shear wall stands at forty-three per cent. At object level, the wall is reported as either complete or not complete, which removes subjective judgement about the item as a whole. From there, progress rolls up. At activity level it is a weighted average, based on quantities or man-hours. Above that it rolls up on man-hours, with a correction for equipment-intensive work, such as earthworks, where man-hours understate the effort. The important consequence is that one progress percentage feeds both the cost calculation and the planning calculation, so the two cannot tell different stories. From that percentage, the team computes earned man-hours and, for each commodity, the cost performance index, which is where the next part begins. By this stage, the station box has a progress figure that is objective, traceable to individual walls and slabs in the model, and agreed with the client. That is the missing number from the month-end meeting. Earned value management, or EVM, rests on three quantities. Planned value is the value of the work the programme said would be done by now. Actual cost is what has been spent. Earned value is the budgeted value of the work that has been done, which is the measured progress multiplied by the budget. From these come two indices. The cost performance index, or CPI, is earned value divided by actual cost. The schedule performance index, or SPI, is earned value divided by planned value. Both read the same way. Above one is good, meaning under budget or ahead of programme. Exactly one means on plan. Below one means over budget or behind programme. Now return to the station box. Suppose the measured progress, rolled up from every wall and slab, puts the package at fifty per cent complete. Fifty per cent of a one million pound budget gives an earned value of five hundred thousand pounds. The team has spent six hundred thousand pounds. The CPI is five hundred thousand over six hundred thousand, which is about nought point eight three. For every pound spent, the package has delivered about eighty-three pence of work. It is over budget. The programme expected four hundred thousand pounds of work by now. The SPI is five hundred thousand over four hundred thousand, which is one point two five. The package is ahead of programme. So the answer to the client's question is precise. The package is not late. It is ahead. Its problem is cost, and the earned value report will show which commodity, discipline and area is driving it. Had the team spent four hundred thousand pounds rather than six hundred thousand to reach the same point, the CPI would be one point two five, and the package would be making a saving. An SPI below one would call for one of two responses, recovering the programme or warning the client. Two ratios, but together they combine scope, time and cost into an objective reading of project health. That is why the technique is set out in the Project Management Institute's Standard for Earned Value Management, published in 2019, and why it is used so widely on major projects. Every number in that calculation depends on the progress measurement from the previous part. If the fifty per cent were a guess, the CPI and the SPI would be guesses too. That brings us to the data. Earned value is only as good as the data behind it, and on a live site that data arrives in three streams, quantity, progress and cost. Quantity comes in two forms. The budgeted quantity comes from the estimate, the bill of quantities and the material take-off. The actual quantity comes from the as-built model. Progress comes from site measurement against the agreed rules of credit, operation by operation. Cost divides by how directly it relates to the scope. Direct costs build the scope, which means labour, plant, subcontractors and materials, tracked through time cards, store issues and payment certificates. Indirect costs support the work without being part of it, the office, fees and management staff, tracked through invoices and payroll. Accruals cover ongoing items such as services, materials under measure and mobilisation. The principle across all three streams is the same. Each must be collected against the same breakdown structure and the same cost codes, or the streams cannot be combined. Disciplined collection is not a clerical detail. It is the foundation of the whole system. To see how this comes together in practice, consider a BIM-based project controls system used on a large programme of works. The specific software is not the point, but the structure is. In that system, the model provided an intelligent representation of every object. Progress updates came from site, applied through the rules of credit. The quantity surveyors' take-off updated the model with actual quantities, so the model reflected what had been built. An integrating platform, called C3D in this case, held these together, so that one model, kept current, linked what was designed, what was measured and what was built. That is the condition for trustworthy five D cost information. Around the model, the controls system brought four streams into one place. A time sheet system gave actual hours against each cost code. The master schedule gave planned value. Progress, measured through the quantity surveying and BIM route, gave earned value. The model gave quantities and object detail. These were integrated for each individual project and then rolled up into the master project, to generate a set of standard reports, including a quantity, unit rate and progress report, an earned value report and a bill of quantities report. Two of those reports show why the discipline is worth the effort. The weekly progress report lists each area and discipline in turn. For each one it gives the planned, updated and actual percentage complete, for the week and cumulatively, the variance between plan and actual, and a three-week look-ahead. The earned value report sets out, for each work package, the budgeted, earned and actual man-hours side by side, and computes the SPI and the CPI for each. A manager reading either report can see which disciplines are behind, which are overspending, and where to intervene. That is the month-end meeting as it should have gone. Research is pushing this further. Radman and colleagues, in 2025, link BIM with Microsoft tools to automate earned value for electrical and instrument works, and integration with business intelligence tools such as Power BI is moving the indices towards near real-time reporting. Adoption is still developing, and every one of these tools depends on the object-level data described in this episode. Let me draw this together. The question was how a project team knows, at any point, whether it is on cost and on programme, and what BIM contributes to that answer. The answer is earned value, measured from the model. A team knows where it stands when it can compare three numbers, planned value, earned value and actual cost, and BIM makes the middle number trustworthy by tying progress to objects that everyone can see and count. Three things are worth carrying into your own work. First, anchor progress monitoring to a structured work breakdown structure, measured at object level with rules of credit agreed before work starts, because a progress figure nobody can trace will not survive a dispute. Second, read earned value through its two indices together. A CPI of nought point eight three with an SPI of one point two five describes a very different problem from the reverse, and calls for a different response. Third, treat the model as the single source of quantities and object-level progress, and the three data streams from site as part of the same system, all managed under ISO 19650, with level of information need defined to ISO 7817-1. Without that discipline, five D is a label rather than a control system. For further reading, start with the PMI Standard for Earned Value Management, the RICS New Rules of Measurement and the International Cost Management Standard. ISO 19650 Parts 1 and 2, and ISO 7817-1, set out the information management that underpins it all. For recent evidence, Das, Khursheed and Paul, in 2025, report case studies on the impact of BIM on project time and cost. The episode on 4D BIM covers the schedule side of the model in depth, and the episode introducing BIM sets out the ISO 19650 framework. I am Dr Sepehr Abrishami, and this episode of Reimagining AEC ends on a check rather than a summary. Pick a project you know from the office, the site or a research dataset, see whether its records let you work out a cost performance index today, and if they do not, find the missing stream, because that is where the control system fails.