Built for consequence
Keep the approved project basis intact from mandate to use.
The method connects the business case, requirements, interfaces, delivery records and operational acceptance whenever work passes between disciplines, organisations or stages.
01 / What the method protects
Complex projects lose value between disciplines.
A sound business case can be detached from design decisions. A coordinated design can be weakened by procurement or implementation. A completed facility, system or change programme can still fail acceptance or operational use.
Built for consequence keeps the intended outcome, approved evidence, responsibilities and acceptance basis visible throughout the appointed role. It does not replace the client’s governance, contract, dutyholders or approval authority.
02 / The five controls
Five controls connect the original mandate to operational use.
Each control gives the next decision owner evidence that can be tested.
-
01
Consequence
State the outcome the project enables and what is exposed if it is late, ineffective or unavailable.
Record: consequence and outcome basis -
02
Evidence
Separate verified facts from assumptions, estimates, dependencies and required investigation.
Record: evidence and uncertainty register -
03
Interfaces
Name the owner, required input and decision for every material commercial, operational or technical dependency.
Record: interface and responsibility schedule -
04
Readiness
Set the tests, information, capability, training, transition and acceptance basis before completion.
Record: readiness and acceptance plan -
05
Change
Show whether scope, cost, programme or solution change weakens the approved outcomes or business case.
Record: impact and authority decision
03 / Governance
Apply the framework that belongs to the commission.
Each commission is structured around the client’s applicable governance and approval route. That may include the Five Case Model, RIBA Plan of Work or GovS 002 where relevant to the decision, asset and appointment.
The appointment records the approval route, required evidence and authority for each material decision.
04 / Appointment boundary
Integration does not blur authority.
The commission names M4Forge’s role, the disciplines provided or coordinated, the information basis, retained client and statutory duties, independent authorities, deliverables and acceptance conditions.
Start with the exposed decision
Which unresolved assumption or interface could prevent the intended outcome?
Identify the mandate, current phase, consequence and evidence the next decision maker needs.