Obligation architecture and pre-award governance · Lesson 3

Choose governance tiers and decision rights by criticality

7 min read

Lesson objectives

  • Make a documented decision on choose governance tiers and decision rights by criticality with evidence and limits.
Reading tools

An organisation holds two maintenance contracts. One covers office devices that can be replaced within a day. The other keeps a data centre cool, supporting a service that cannot tolerate a long outage. If both contracts require a weekly committee with four approvals, the first may consume oversight effort without corresponding benefit. If the second receives only a monthly supplier email, an emerging interruption may be noticed too late. Governance means deciding who acts and reviews, on which evidence, and when. Its weight should match the consequence of failure and the uncertainty around delivery. More committees do not automatically mean better control.

Start with an operational tier rather than contract value alone. Consider outage consequence, ease of supplier replacement, subcontractor dependence, technical complexity, data sensitivity, and frequency of change. A low-value contract can be critical when replacement is slow at the moment of failure. Record the reason for the tier and its review date. Mobilisation may be riskier than stable delivery, and discovery of a sole critical subcontractor may change the tier later. UK government commercial guidance advocates management proportionate to complexity, value and risk in its stated context. The reasoning can inform our fictional design without being presented as a universal legal requirement.

After tiering, assign specific decisions instead of writing “the committee is responsible.” Who approves the mobilisation plan? Who accepts evidence of delivered service? Who can authorise a change in scope or cost? Who activates continuity arrangements if a supplier cannot deliver? The person who reviews a KPI may not have authority to amend the agreement. The person who approves an invoice may not be authorised to accept a continuity exposure. State decision limits by subject, threshold, and time. A fictional delegation might allow the contract manager to reschedule a visit within existing scope and budget while reserving changes in price or term for a commercial sponsor after specialist review. Such an example grants no authority in a real organisation.

For each decision, design a three-part path: author of the recommendation, decision holder, and escalation channel if the threshold is exceeded or a decision cannot be reached. If one person creates the evidence, accepts the result and releases payment, error or conflict becomes harder to detect. Small contracts may not support complete role separation, but can use compensating checks, such as an independent sample or a second approval for exceptional amounts. Critical contracts may need an empowered rapid meeting for outage decisions, while a monthly forum remains adequate for non-urgent improvement. The committee process should not delay a pre-authorised reversible continuity action.

Put a “decision gate” in the register instead of an empty approval column. A gate names its trigger, the evidence required, the alternatives, the threshold for escalation, and the decision to record. For example, if cooling at a critical site is interrupted for more than two hours, the operations lead activates an approved temporary-cover plan and alerts the contract manager. Ending the agreement would require a separate path and specialist interpretation of rights and effects. The distinction stops a team from treating a reversible operational precaution as though it were the same kind of decision as a major contractual change.

Governance outputs must change what people do. Minutes that say “performance discussed” do not tell a team what changed. A useful decision record links the decision to dated evidence, the rejected alternative and its reason, the implementation owner, the verification date, and a return trigger if the action fails. Without the assumption behind a decision, a later reviewer cannot tell whether execution failed or circumstances changed. Review tiers over time: an ordinary supplier may become critical if it becomes the only service provider for a new facility.

Lesson summary

A defensible answer gives the network higher initial attention because it stops receiving, has a four-hour manual ceiling, and an untested recovery claim. A trigger could be a 30-minute outage or repeated connection loss, adjusted to the organisation’s real continuity plan. Evidence would include outage start time, device condition, date of the last recovery test, remaining manual capacity, and supplier repair estimate. An authorised operations lead begins the approved manual or alternate process and alerts the contract manager. A purchase or extension outside current scope goes to the appropriate procurement and change authority after impact analysis. Monthly exception-based review may suit the more expensive training-room agreement because alternatives are quicker and the stated interruption consequence is lower. The review criterion is not whether the learner chose the word “weekly”; it is whether cadence, observable signal and actionable threshold fit the case.