Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Transformation management and PMO

Contractual risk: the blind spot in the governance of major projects

In brief

A major project is first and foremost a portfolio of contracts, yet contractual risk can remain absent from a programme's risk map. This article explains why conventional governance does not capture it and proposes three actions and three indicators for bringing it into a PMO's steering.

Page contents

Ask a programme director to show you their risk map. You will find technical risks, schedule risks, budget risks, resource risks, sometimes currency risks. You will not always find a serious line on contractual risks. It is a paradox: a major project rests on a stack of contracts, and yet this is a dimension that governance can leave without any instrument.

At Management Square, we have been supporting large companies and public administrations in their project management and transformation initiatives since 2015. Our reading fits into one sentence: teams steer what they can see. Yet contractual commitments, once signed, become invisible. They sleep in a document management system, a SharePoint or a cabinet, and only reappear when they become expensive.

A major project is first and foremost a portfolio of contracts

Take a typical transformation programme in a large group: a main integrator, two or three software vendors, a cloud hosting provider, business-side project support providers, licence contracts, successive amendments, service level agreements. Such a programme can involve numerous active contractual documents, negotiated at different times, by different people, with clauses that do not always match one another.

Each of these documents contains precise commitments: delivery deadlines, late-delivery penalties, liability caps, reversibility conditions, intellectual property clauses, availability commitments, price revision mechanisms. These commitments are the legal translation of the project plan. When the plan drifts, they are what determines who pays, who repairs and who bears the consequences.

Standard project governance tracks milestones, workloads and deliverables. It does not always track the contractual material that frames them. The risk is then predictable: the clause is discovered at the time of the dispute, not at the time when it could have been useful.

Three situations a PMO may encounter

The forgotten penalty. Imagine that the integrator’s contract provides for late-delivery penalties capped at 7% of the annual amount. The project slips by four months. Nobody has notified the delays in the form required by the contract, within the required notification periods. When it comes to claiming the penalties, the legal department finds that the notification window has passed. The negotiating argument has disappeared, not for lack of a right, but for lack of follow-up.

The phantom amendment. Take a project whose scope evolves over the months. The changes are agreed in steering committee, recorded in minutes, sometimes in emails. The formal amendments, for their part, arrive six months late, when they arrive at all. The day the relationship becomes strained, the supplier performs the signed contract, not the committee minutes. The gap between the real project and the contracted project becomes a direct financial risk.

The unwanted renewal. Imagine a maintenance contract that renews tacitly every year, with a three-month termination window. The programme that was to replace the solution falls behind. Nobody is watching the date. The company is committed for another twelve months to a tool it wanted to decommission, and pays for two solutions in parallel. Multiplied across an IT department, this scenario represents as many avoidable costs.

These three situations have one thing in common: none of them stems from a lack of legal expertise. They stem from a lack of visibility. The information existed, in a signed document, but it was neither monitored nor linked to operational steering.

Why conventional governance does not capture this risk

The first reason is organisational. The contract belongs to legal or procurement, the project belongs to the business or the IT department. Between the two, responsibility for tracking commitments may be assigned to nobody. The project manager considers that the contract is “managed” since it is signed. The lawyer considers that performance is an operational matter. This no man’s land is precisely where the risk thrives.

The second reason is documentary. The contracts of a single programme are scattered across several systems and several versions. Reconstructing the exact contractual position with a supplier, amendments included, can take several days. No governance body can steer material that takes several days to reconstruct.

The third reason is methodological. Risk management frameworks, including the ISO 31000 standard on risk management, provide a generic approach, but applying them to contractual commitments requires an up-to-date inventory of sensitive clauses. Without this inventory, contractual risk remains an abstract category on the map, with no owner and no indicator.

What a structured approach to the contract lifecycle changes

A discipline has been built around this problem: contract lifecycle management. The idea is simple: treat the contract as a living object, from drafting to renewal, rather than as a document frozen at the moment of signature.

In practical terms, for a programme management team or a PMO, this approach brings four capabilities that conventional governance lacks.

A single repository. All the programme’s contracts, amendments and appendices included, are centralised, versioned and linked to one another. The question “what is our exact contractual position with this supplier?” gets an answer without manual reconstruction.

Commitments extracted and monitored. Sensitive clauses, such as deadlines, penalties, liability caps or termination windows, are identified and turned into alerts. Tracking contractual obligations and deadlines stops depending on the memory of a buyer or a lawyer and becomes a tooled process, with reminders before each critical date.

Verifiable compliance. Legal departments define acceptability rules, and each new contract or amendment is assessed against these rules before signature. Recent tools do this with assistance from artificial intelligence: Pactolane, for example, is a CLM platform designed for legal teams that assesses the compliance of clauses against internal playbooks and keeps a complete audit trail of approvals.

A common language between project and legal. When contractual commitments are visible in a dashboard, they can enter governance bodies on the same footing as milestones and budget. The steering committee can at last make decisions in full knowledge of the facts: this delay triggers that penalty, this change of scope requires that amendment.

Where to start: three actions for a PMO

There is no need to launch a major initiative to make progress. Three actions make it possible to move forward without waiting.

Inventory the programme’s active contracts. A simple census, with for each contract the key dates, amounts, penalties and termination windows, can reveal anomalies from the very first pass: duplicates, expired contracts still being paid, imminent renewals.

Appoint an owner for contractual risk. One person, within the PMO or working in tandem with the legal department, becomes responsible for monitoring commitments. Where this role does not exist, simply creating it can change the organisation’s behaviour.

Build a contractual review into existing bodies. Fifteen minutes per steering committee can be enough: deadlines within 90 days, gaps between actual scope and contracted scope, notifications to be sent. This routine turns the contract into a steering tool instead of an archived document.

Measuring in order to steer: three simple indicators

Like any risk, contractual risk only makes headway in an organisation if it is measured. Three indicators are enough to start, and each can appear in the PMO’s monthly report. The first is the coverage rate: the share of the programme’s active contracts whose deadlines and sensitive clauses are inventoried and monitored. The second is the average time taken to contract changes: the time between a steering committee decision and the signed amendment that formalises it. The longer this time grows, the more the gap between the real project and the contracted project becomes entrenched. The third is the value of rights exercised: penalties notified, service credits claimed, renewals renegotiated. This is the indicator that speaks to finance departments, because it translates contractual discipline into euros recovered or saved.

The contract as a steering instrument

The maturity of a project organisation is often measured by its ability to anticipate. Yet contracts are, by construction, the place where the future of the project is written in black and white: who must deliver what, when, at what price, and what happens in the event of a gap. Leaving this material outside the scope of governance means steering while ignoring the documents that bind the parties.

Companies that bring contractual risk into their governance can expect a double benefit: avoided losses, first, because penalties are notified in time and renewals are decided upstream; a stronger negotiating position, next, because the contractual history is documented and can be drawn on at any time.

In the course of our digital transformation and project governance assignments, this is a lever we recommend examining early: it requires neither reorganisation nor a major budget, only the decision to make visible what was invisible.

Management Square supports large companies and public administrations in securing their strategic projects: PMO, governance, risk management and compliance.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.