Map promised outcomes to measurable obligations and acceptance evidence
7 min read
Lesson objectives
- Make a documented decision on map promised outcomes to measurable obligations and acceptance evidence with evidence and limits.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
Imagine an organisation responsible for 40 buildings signing a maintenance contract whose stated purpose is to keep sites operational. Procurement can complete the award successfully while the contract manager, one month later, cannot answer a basic question: what must the supplier demonstrate before a service is accepted? The gap is deeper than a missing tracking sheet. The desired outcome has not yet been translated into obligations, measurement boundaries, and acceptance evidence. In this lesson we build the first rows of a governance register that will develop throughout the program: outcome, obligation, actor, evidence, and decision.
An outcome is the effect the buyer wants, such as continued operation of critical sites. An obligation is a defined act or deliverable expected of a party under the hypothetical contract documents. An indicator describes how performance is observed; it does not by itself create a new contractual duty. A control is a step that prevents, detects, or helps correct error, such as withholding approval of a maintenance invoice until visit records have been reconciled with closed service calls. These distinctions matter. A good-looking dashboard can coexist with weak evidence and a continuing operational exposure.
Begin with a short map of the service, rather than copying contract clauses in their printed order. Ask who depends on the service, what failure would change the outcome, and which deliverable can be tested. The case has critical and ordinary sites, emergency incidents, and preventive maintenance. A single average response time would obscure important differences: many simple tickets could hide one delayed critical incident. Define incident class, measurement period, the event that starts and stops the clock, and legitimate exclusions. These are design assumptions for the case, not universal legal rules.
Next, convert the outcome into a manageable obligation unit. Record the responsible party, action, subject, due date or recurrence, acceptance criterion, required evidence, and person authorised to accept it. For example: “Within five business days after each month begins, the supplier submits the previous month’s preventive-visit log for critical sites, and the site manager checks a sample against access records.” Five days is a case assumption; an actual contract must supply its own deadline. If the signed text merely asks for “appropriate maintenance”, a contract manager cannot invent a binding standard. Record the ambiguity and seek commercial or legal interpretation of the executed version, or an approved change if needed.
Then design the evidence chain. A supplier system may record when a fault was opened and closed, but closing a ticket does not establish that equipment was operating again. Add independent acceptance evidence proportionate to the consequence of failure: site confirmation, a test reading, or a sample inspection. Verification need not be equally intensive everywhere. Every incident at a critical facility may justify direct confirmation; routine low-impact tasks may use a defined sample with exception escalation. UK government contract-management guidance calls for proportionate management, clear roles, a management plan, and performance monitoring in its own context. We use those as design ideas, not as law for every learner.
Do not collapse both parties’ duties into one responsibility field. Suppose the supplier must dispatch a team within four hours, while the buyer must grant site access. A late arrival does not automatically prove supplier fault, nor does restricted access automatically excuse every delay. Preserve the timeline: report logged, acknowledgement sent, team arrived, access granted, and service restored. This shows the cause that a simple status flag conceals. The contractual effect of that cause may need specialist interpretation. The register’s immediate job is to retain facts and distinguish observed events from assumptions.
Lesson summary
Reference answer: the first row concerns the supplier’s report before 09:00, supported by a timestamp. The second concerns the site lead’s safety acceptance, supported by the inspection record and approval time. The fifth day cannot be classified as a late supplier report because 08:50 precedes the deadline. Investigate the delayed safety inspection rather than mixing the two indicators. The data intentionally conflict: “five late reports” cannot include an 08:50 report under the stated rule. Ask for the list to be corrected before fixing a rate. If five reports really were late, 15 of 20 were on time, or 75%. If the listed fifth day was the only false late classification, four were late and 16 of 20 were on time, or 80%. Full credit requires spotting the conflict and presenting these conditional results, not choosing an unsupported single rate. This is an exercise in data quality as well as obligation design.