Picture a signature headquarters two months from an opening date that has already been announced and committed to a board. The civil works are complete. The mechanical and electrical packages have been handed over and signed off. The audio visual, information technology, and extra low voltage package, the one that will make the building actually function as a place where people meet, present, communicate, and are kept secure, is reported by its specialist contractor at eighty-five per cent complete. The programme chart on the screen is reassuringly green across almost every line. The project team accepts the figure, because nothing in front of them gives them any basis on which to challenge it. Four months later, the building still has not opened. Every other trade finished on time. This one did not, and nobody in that room two months out had any way of knowing that it would not.
This is not an unusual story in our region. It is close to the median outcome on large technology packages, and the reason it keeps happening has very little to do with technology and almost everything to do with how progress is measured and reported.
Consider how these packages are actually contracted. Across this region, the audio visual, information technology, and extra low voltage scope of a building is awarded as a lump-sum, fixed-price package, either as one fully integrated scope under a single specialist contractor or as several coordinated packages running in parallel. Because the price is fixed at signing and any additions enter only through bounded variations, the client is not principally exposed to cost overrun. The client is exposed to schedule. And schedule exposure on this scope is severe, because the technology package sits on the critical path to building handover. A late handover means the asset cannot open on the date it has committed to. A hospital cannot receive patients. A hotel cannot accept guests. A headquarters cannot host its inauguration. A campus cannot begin its term. In each case the cost of the delayed opening, measured in lost revenue, idle staff, deferred service, and reputational damage, dwarfs the value of the technology package itself, often by an order of magnitude. The client carries that loss. The contractor pays a fraction of it back in liquidated damages, if any are recovered at all.
What makes this exposure worse than it appears is a feature peculiar to this scope. On the civil and the mechanical and electrical works, a project director can walk the site and see the progress with their own eyes. The columns are poured or they are not. The ducts are installed or they are not. The technology scope is different, because it is largely invisible by its nature. Cables run inside containment that is closed long before anyone can verify what is inside it. Devices sit in racks that have been installed but not yet configured. Control systems are written in code that cannot be inspected by walking a floor. Wall plates remain blank until the day they are commissioned. The moment the work finally becomes visible is the moment of commissioning, which is also the last possible moment to discover that it is not what was claimed. So this is the scope where the client simultaneously has the least independent visibility and the most schedule exposure. That combination is structurally dangerous, and it produces a disproportionate share of the late handovers in this market.
Other industries solved this problem a long time ago. Marine engineering, offshore oil and gas, defence, and major infrastructure decided decades back that visibility on schedule was not optional for any package of consequence, and they built their reporting around an instrument designed precisely to provide it. The instrument is the scope-loaded progress baseline, measured through what is known as earned value, and shown visually as a curve. In this region in particular, marine and offshore programmes routinely require their specialist contractors to submit weekly scope-weighted progress curves as a contractual deliverable, for the simple reason that the asset owner cannot afford the risk of finding out late. The instruments are not exotic. They are taught in every recognised project management qualification and described in every project controls curriculum. They are simply absent from the audio visual, information technology, and extra low voltage industry's own training, and absent from the contracts that this industry's clients are asked to sign.
The instrument itself is easier to understand than its reputation suggests. Imagine time running along the horizontal axis, week by week across the programme, and the cumulative value of the work, expressed in the currency of the bill of quantities, running up the vertical axis. The first line on the chart is the planned value. It is the baseline agreed at contract signing, and it shows how much scope value should have been completed by each week if the work proceeds to plan. The second line is the earned value. It shows how much scope value has actually been completed by each week, measured against agreed rules that define when a piece of work is allowed to count as done. The gap between the two lines, read at any week, is the true schedule status of the package, and because both lines are denominated in the same currency, that gap is a real number rather than an opinion.
What makes the measurement honest is the discipline beneath it. Every package in this scope contains three structurally different kinds of work that move at different times and to different rules. There is the supply of equipment, which earns its value when the equipment arrives on site. There is the installation, which earns its value as containment is built, cable is pulled and terminated, and devices are mounted. And there is the testing and commissioning, which earns its value as systems are configured, verified against specification, and accepted. These three streams typically carry roughly two thirds, one quarter, and one tenth of a package's value in that order. The reason this decomposition matters is that it forces honesty. A package reported as ninety per cent complete because the equipment is installed but no testing has begun is, on an honestly weighted curve, exactly ninety per cent complete, and ninety per cent is not enough to declare a room delivered. Without the decomposition, ninety per cent can mean whatever the person reporting it wishes it to mean. With it, the arithmetic tells the truth whether or not anyone wants to hear it.
From those two lines comes a single number that a chief executive, a project director, or a financier can absorb in seconds. It is the ratio of earned value to planned value, and it answers the only question that really matters, which is whether the work is keeping pace with the plan. A ratio of eighty-five hundredths in the fourth month does not mean the project is fifteen per cent behind in some vague sense. It means that at the current rate the package will finish meaningfully late, and the expected finish can be calculated, not guessed. That forecast, produced early, while there is still time to act, is the entire value of the instrument.
The natural question is why an industry full of capable people has not adopted something so useful. There are three reasons, and none of them is a failure of any individual. The first is that the industry's own training and certification, including the courses and reference texts most widely used by its project managers, do not teach earned value or scope-loaded progress curves as core control instruments. Most project managers in the sector have never been taught to build one or to read one. The second is that on the largest programmes, where a main contractor's project office may insist on a curve, it is too often produced as a compliance document, attached to a monthly report and then ignored, rather than used as a living early warning system. The third, and the most consequential, is that in the large segment of direct enterprise and government work, clients have not demanded the instrument, because they have not been taught what to ask for. Neither side of the table has had a commercial interest in a measurement that tells the truth, and so the truth has remained unmeasured.
Scope in this market changes constantly through variations, and a fair question is whether an instrument like this can absorb them. It can, and the way it does is itself instructive. A properly run earned value system handles variations through formal rebaselining at each approved variation order. The original baseline is preserved as a reference. A new baseline is built to include the approved change. Earned value going forward is measured against the new baseline. The chart then shows two things at once that no edited programme chart can show. The distance between the original baseline and the current one reveals exactly how much the scope has grown. The distance between the current baseline and the earned value reveals exactly how the work is performing against the latest agreed scope. Both truths remain visible. Neither is lost in the fog of an estimate that has been quietly revised twenty times.
It is worth being clear about whose instrument this really is. It is the client's. It gives the client verification of progress that does not depend on taking the contractor's word. It gives the client a forecast of the real handover date, derived from measured performance rather than from assurances, which is what allows the client to plan everything that depends on that date, the user onboarding, the opening event, the occupancy, the release of capital for the next phase. It gives the client an audit trail that will withstand a board, a regulator, a financier, or a government auditor. It gives the client the standing to intervene early, while recovery is still possible, instead of receiving a surprise at handover when it is not. And it gives the client a position of informed authority in every progress meeting, because a client who can read the curve cannot be told that a package is at eighty-five per cent without being able to ask the next question, which is what the earned value is, and what the ratio has been for the past three months.
In every mature capital industry, the client decided long ago that faith was not a sufficient basis on which to commit hundreds of millions to a programme. The audio visual, information technology, and extra low voltage industry in this region has not yet been required to make the same decision, because its clients have not yet thought to demand it. The question worth asking, before signing the next large technology contract, is not what the percentage complete will be reported as each month. The question is whether the instrument used to report it can tell the truth. A project is not managed by hope. It is managed by what can be measured, and the measurement is available to anyone willing to insist on it.