Obligation architecture and pre-award governance Review questions Integrated summary: Obligation architecture and pre-award governance Before award, the learner turns a promised service outcome into a defined obligation, action owner, acceptance record and calculable indicator. Buyer, supplier and shared duties become a dependency chain with named acceptance and escalation decisions. The learner compares governance effort for critical and ordinary sites using outage consequence and replaceability, rather than contract value alone. A causal risk description distinguishes a proposed control from one tested in operation before estimating residual risk. In the worked service case, the learner creates linked register rows for obligation, owner, source, period and denominator, and tests a platform ticket closure against confirmed restoration. The module ends by separating an unresolved contractual right from an evidence-based operational follow-up decision.
Review questions Test your understanding with these questions. Marking and saved results are available with a free account.
Question 1 Which rate should be reported with a qualification? 75% with no note 75% if all five were late, or 80% if the early report is reclassified 100% because every site opened Question 2 Which event still needs evidence? Whether an earlier partial list existed Whether another supplier exists in the market Why the visit did not start after pass issue and when the site was available Question 3 What is the limit of the urgent decision? Activate authorised cover and send any price change to its separate authority Implicitly change price because the incident is urgent Wait for a price committee before protecting service despite approved cover Question 4 How should the buyer-owned spare be counted before its test? Two usable because ownership is known One usable and one unverified until the check passes Zero because the two parts are held separately Question 5 What is the status of two time-zone-mismatched reports? All seven are fully valid because the files arrived Ignore independent data because the supplier reported daily Record 7/7 receipt, hold comparability of two, and investigate clocks and the missing alert Question 6 What makes a handover pack useful? An operative-document index, launch decisions and open gaps tested with the price question A larger folder with every email undifferentiated Delete negotiation emails so older versions disappear Question 7 Which test covers the service end to end? Login test alone A trial ticket from site to technician and confirmed restoration with handoff times Counting technician accounts Question 8 What follows from a replacement invoice? Pay both because identifiers differ Always reject the newer one because the first is older Link versions, establish cancellation or any payment of the first, then match new lines Question 9 Which subcontractor dependency needs testing? The bid name closes exposure The substitute's pass, tool, travel time and actual task trial The total count of subcontractors Question 10 What makes conditional launch reversible? Add expiry, observation owner, rollback trigger and duty test Rely on the word temporary because everyone understands it Remove critical tickets until testing is done Question 11 Which balancing rate can be calculated? Subtract seven from 45 and call it response compliance Treat every reopening as proof of false first closure Show 7/50=14% ordinary reopenings and 4/45≈8.9% among timely ones under separate labels Question 12 What separates incident and risk here? Both are closed past incidents Yesterday's delay is an event; future stockout is a linked risk needing a trigger Both establish a legal breach Question 13 What early action follows increased use? Confirm order, lead time and stock condition, and investigate higher use before labelling risk low Keep low risk because four is greater than one Buy unlimited stock without authority Question 14 What shows whether corrective cover worked? Success is proved because late tickets were zero Failure is proved because extra crew was idle Critical response remains untested in live service; trial duty readiness and observe later real incidents Question 15 What does the quarter comparison need? Declare complete improvement from the rate alone Request outage hours by site and incident and the new site's start date before attributing cause Declare complete deterioration because hours rose Question 16 What does the supplier reply fail to prove? It proves final price because capacity means acceptance It suggests possible capacity but not buyer price approval or delegation It removes the need for a change log Question 17 What is the cost difference under the exercise assumptions? Incumbent is 500 cheaper Both cost 14,000 Other is 14,000 versus incumbent 14,500, subject to service constraints Question 18 Which date governs measuring the ticket? The 1 November effective date, while recording the system-rollout lag The 3 November configuration date because technology creates the right The 10 October approval date because decision came first Question 19 Which information resolves the conflicting accounts? Monthly visit count alone The operative response-start definition, how app time is created and what remote support did The opinion of the higher-ranking party Question 20 How should August night service appear in comparison? August daytime fell to 80% Delete night cases to preserve 90% Both daytime rates are 90%, night is 50%, and new overall August is 80% with a scope-change marker Question 21 When does the backup-readiness clock start? On quotation date On the original supplier's first delay After stated inputs arrive, with their preparation time counted too Question 22 Which knowledge-transfer test fits the gap? Map current and previous pump identifiers and have the new team read its history before readiness acceptance Accept because the file has many assets Change the pump ID at random until a result appears Question 23 How should the 45,000 saving be described? Realised savings to book immediately A preliminary estimate conditional on bridge, rights, quality and capability A 45,000 loss because mobilisation is large Question 24 What is the final invoice state? Paid because arithmetic is right Rejected because a person is absent Arithmetic review complete; approval pending the holder or formal deputy Question 25 Which conclusion avoids inventing a class rate? Overall is 90% and both late cases are critical; critical-class rate cannot be computed from these facts Critical rate is certainly zero of two Critical rate is 90% because overall is 90% Create a free account to mark your answers and save your progress.