Sustainability in projects

Sustainability reaches a project as a set of obligations and constraints that have to be identified, designed for and evidenced, in the same way as any other requirement. Whether an organisation ought to go further than it is obliged to is a decision taken well above the project. What a project manager owes is an accurate account of what has been committed to and whether it is being met.

Three dimensions, not one

DimensionWhat it coversA project exampleHow it usually arrives
EnvironmentalEnergy and emissions, materials, waste, water and landA platform migration carrying a ceiling on the energy the new environment may draw, reported quarterlyRegulation, and the disclosure regimes built on it, passed down the supply chain as a contract clause
SocialLabour conditions across the supply chain, health and safety, accessibility of what is built, the effect on the community around a site, and the effect on the people whose jobs the project changesEvidence that no supplier in the chain uses forced labour, and an interface tested against a named accessibility standard before releaseContract clauses and supplier codes of conduct, and public procurement scoring it explicitly under a social value heading
EconomicWhether the result stays viable to run once the project has gone, meaning who can operate it and what it costs to keep runningA system only one specialist can operate, carrying a licence renewal the receiving department has never budgeted forOrganisational commitment, expressed through the business case and the whole life cost examined at a gate

Environmental covers energy and emissions, materials, waste, water and land. It is the dimension everyone thinks of first and the one most likely to be measured, which is also why it absorbs attention the other two need.

Social covers labour conditions across the supply chain, health and safety, the accessibility of whatever is built, the effect on the community around a site, and the effect on the people whose jobs the project changes. Public procurement often scores this explicitly under a social value heading, so on a public sector bid it carries marks rather than goodwill.

Economic asks whether the result remains viable once the project has gone. Something that can only be operated by one specialist, or that carries a running cost the receiving department cannot afford, is unsustainable in a way that has nothing to do with emissions.

A project reporting only on the first of these is describing a third of its position, and the third column of that table is why. Each dimension arrives by a different route, so a project that watches only the regulator will miss the two that come through procurement and through its own organisation's commitments.

As a constraint and as an objective

A constraint is a boundary the project stays inside while delivering something else. A migration with an energy ceiling, a build with a waste diversion target, a procurement rule requiring suppliers to hold a labour standard. Constraints belong in the requirements, in the design reviews and in the gate criteria, and they are tested like any other requirement.

An objective is when the sustainability outcome is the reason the project exists and the thing its funding was justified by. A programme to cut a site's emissions by a stated amount has that reduction as its benefit, with an owner, a baseline and a measurement date.

The distinction decides where the requirement lives and who watches it. Treating an objective as though it were a constraint is the more damaging error, because it demotes the purpose of the project to a box that gets ticked, and the first schedule pressure will find it.

Whole life rather than delivery phase

The impact of the delivery phase is usually a small fraction of the total. A building's operating emissions across decades dwarf those of its construction. A system's energy and running cost across its service life dwarf the project's budget. Decommissioning, disposal and data deletion sit at the far end and are frequently nobody's line item.

Whole life thinking matters because it changes decisions taken during the project. A cheaper component with a higher energy draw is a saving on the project and a cost on the operating budget, and the two sit with different people. That is a decision for whoever holds the whole life cost, which is why it is raised at a gate rather than settled inside the team, and why the business case is the right place for the comparison.

Most of the whole life impact is fixed early, when the material, the architecture or the supplier is chosen. By the time there is a finished thing to assess, the options that would have moved the figure have already closed, which puts the useful conversation at the design stage.

Obligations that arrive through the contract

The route into a project is changing. Large organisations subject to a disclosure regime need data from everyone in their supply chain, and they get it by writing it into their contracts. What reaches a supplier is therefore a clause requiring emissions figures per delivery, a supplier code of conduct to sign, evidence of checks on forced labour, or a right for the customer to audit.

Two consequences follow for delivery. The obligation binds you through commercial law rather than through the regulator, so the escalation route and the penalty are contractual. And the data collection has to be designed in from the beginning, because figures of this kind cannot be reconstructed at the end of a project from records nobody kept.

What this means in practice

Treat it as a requirements source and a risk source with an owner, and the work becomes ordinary. Establish which obligations bind this specific project, from legislation, from the contract, from the parent organisation's own commitments. Write them as testable requirements with acceptance criteria rather than as aspirations in a charter. Put the whole life question on the agenda at the points where design decisions are actually taken. Keep the evidence as it is produced, since these obligations are audited on records in exactly the way other compliance obligations are.

Common misconceptions

Sustainability on a project means reducing carbon.

Environmental impact is one of three dimensions. Social obligations cover labour conditions in the supply chain, accessibility and the effect on people whose work the project changes. Economic sustainability asks whether the result stays viable to run once the project has gone.

These requirements come from regulation.

A growing share arrive through the contract instead. A customer subject to a disclosure regime needs figures from its suppliers, so the obligation lands in your contract as a reporting clause or a supplier code, and it binds you whether or not the regulation applies to your organisation directly.

Where this is examined
PMP
Business Environment, 26 per cent of the exam.
Related material
Book
How Big Things Get Done, On early decisions that fix the cost of everything that follows.
Concepts