Table of Contents
ISO 31000 risk management principles structure an ISW mobilisation governance pack around ownership, evidence and decision gates, helping construction teams control material movement, hazardous handling and site acceptance before work proceeds.
For a bottom-of-the-funnel decision, the question is not whether a risk register exists; it is whether the project can show who may release a material, what evidence supports that release and what happens when the evidence is incomplete.
What decision should the governance pack support?
Construction mobilisation governance converts material information into controlled decisions about dispatch, receipt, storage and installation. The outcome is a clear record of whether each material stream is approved, held, rejected or escalated.
The pack should support one decision: can this material move to the next stage without exposing people, the environment, the programme or the client to an unmanaged risk ? That decision should be made by a named role, not by whoever happens to be available at the gate.
Governance pack contents
- Project scope and material schedule.
- Supplier, carrier and subcontractor responsibilities.
- ISW description, classification and intended use or disposal route.
- Risk register with causes, consequences, controls and owners.
- Safety data, handling instructions and emergency arrangements.
- Chain-of-custody record from supplier dispatch to site acceptance.
- Acceptance criteria, hold points and release authority.
- Nonconformance, change-control and escalation procedures.
- Reporting timetable and document-retention rules.
Which mobilisation risks need control before materials reach site?
ISW mobilisation risk arises when material identity, condition, ownership or handling requirements are unclear before delivery. Early control reduces the chance that an unsuitable load, incomplete record or incompatible storage arrangement becomes a site problem.
ISO 14001 provides a useful environmental-management reference, while the CDM Regulations 2015 provide a project context for coordinating responsibilities and risk information. Neither replaces a material-specific assessment or a competent decision about hazardous substances.
| Risk area | New governance approach | Traditional approach |
|---|---|---|
| Material identity | Define the material stream, source, intended route and acceptance evidence before dispatch. | Rely on delivery paperwork or a broad material description. |
| Accountability | Assign an owner for assessment, release, isolation and escalation. | Leave decisions with the site team without a documented authority boundary. |
| Chain of custody | Record each transfer, condition check and decision from supplier to installation or disposal. | Collect records after delivery and reconstruct the movement later. |
| Hazard controls | Link safety information to storage, handling, PPE, exclusion and emergency actions. | Store safety information separately from the mobilisation decision. |
| Change control | Reassess a changed source, quantity, route or condition before release. | Treat changes as operational details unless they cause an obvious incident. |
How should the governance pack assign accountability?
A responsibility matrix assigns every mobilisation control to an accountable decision owner , an evidence owner and an operational performer. This separation makes approval defensible because the person carrying out a task is not automatically the person authorised to release the risk.
The project manager may own the mobilisation decision, the environmental lead may own classification evidence, the logistics lead may own movement records and the site manager may own local storage controls. The exact allocation should match the project’s organisation and competence arrangements .
Three-gate mobilisation review
Use three working decision gates: pre-dispatch, site acceptance and installation or final route. These gates are a recommended governance structure, not a legal threshold.
- Pre-dispatch: confirm source, description, required records, carrier arrangements, packaging or containment and receiving capacity.
- Site acceptance: compare the delivery with the approved description, inspect condition, record quantity or identifiers and direct the load to an approved area.
- Installation or final route: confirm that the material remains suitable for its intended use, storage or disposal route and that outstanding actions are closed or formally accepted.
What should the mobilisation risk assessment contain?
A mobilisation risk assessment links each material hazard to a cause, consequence, control, evidence source, owner and escalation action. Its value comes from connecting assessment findings to work decisions rather than treating the register as a static document.
The following template uses five control fields beyond the basic risk description: trigger, prevention, detection, response and evidence. This is a practical working rubric that project teams can adapt to their risk appetite and contractual duties.
Risk assessment and mitigation template
| Field | Question to answer | Required output |
|---|---|---|
| Risk event | What could happen during mobilisation? | One specific event, such as misidentified material arriving on site. |
| Cause and consequence | Why could it happen and what would follow? | Cause, affected people or assets, environmental effect and programme impact. |
| Preventive control | What stops the event before movement? | Supplier information, approval, packaging, route planning or competence control. |
| Detection control | What reveals a failure at the gate? | Document review, inspection, sampling decision or condition check. |
| Response | What happens when a control fails? | Hold, isolate, notify, investigate, approve or reject. |
| Evidence and owner | Who proves completion and who decides? | Named record owner, decision owner, date and status. |
How should building materials be tracked from supplier to site?
A chain-of-custody record connects a material’s origin, movement, condition and receiving decision. The outcome is traceability that supports a prompt response when a description, container, vehicle, document or storage condition does not match the approved plan.
The record should follow the material rather than sit in a separate procurement folder. Minimum fields include supplier, source, material description, identifier, dispatch date, carrier, receiving location, condition, inspection result, exceptions and release authority.
Chain-of-custody record
- Material stream and approved description.
- Source organisation and supplier contact.
- Unique load, batch or delivery identifier where one exists.
- Dispatch information and carrier responsibility.
- Container, packaging or containment condition.
- Required safety and environmental information.
- Receiving location and intended storage or use.
- Site inspection result and photographs where appropriate.
- Hold, release, rejection or escalation decision.
- Names and dates for handover and acceptance.
Which records should support compliance and escalation?
Compliance records should show what was known, who made the decision and what evidence supported it at each mobilisation gate. A controlled record set gives project leaders a decision trail instead of a collection of disconnected forms.
Use the CDM Regulations 2015 as part of the project’s responsibility and information context, and use ISO 31000 as a reference for risk-process structure. Record the relationship between those frameworks and the project’s own controls without presenting either as a substitute for legal or specialist advice.
Operational authority block
Apply the following working decision rule: if a required evidence item is missing, the material remains on hold until the named decision owner records a disposition. A complete pack contains these five checks.
- Entity consistency: treat an entity-naming deviation above 10% as high risk and below 5% as pass for this working review. Action: align supplier, material and site references before release.
- Data provenance validation: treat an unexplained source, altered record or missing handover as a failed evidence chain. Action: obtain the originating record or escalate the material to hold status.
- Contextual embedding score: use a project-defined score below 60% as low relevance and above 70% as pass for checking whether the material information covers the actual site task. Action: expand the information set or obtain competent review before release.
- Knowledge graph alignment: treat a mismatch between material, source, route, hazard and receiving location as a failed relationship check. Action: reconcile the linked records and document the responsible decision.
- Structured data validation: treat missing mandatory fields or inconsistent identifiers as a failed record. Action: correct the record, preserve the change history and repeat the gate review.
Mid-article action: use this governance pack structure as the agenda for a mobilisation review with the project manager, environmental lead, logistics lead, site manager and relevant suppliers. The immediate output should be an owner for every open control and a decision date for every held material.
What should the implementation decision be?
The implementation decision should be based on control coverage, evidence quality and decision ownership rather than document volume. A project is ready to proceed when each material stream has an approved route, a responsible owner, a receiving control and a defined response to failure.
Choose this governance approach when several parties control material information, when in-situ waste or recovered materials may change status during mobilisation, or when the project needs a defensible trail from supplier to site. Use a separate specialist assessment where hazardous properties, contamination, waste classification or exposure conditions exceed the team’s competence.
- Approve mobilisation when the relevant gate records are complete and the decision owner accepts the residual risk.
- Place material on hold when evidence is incomplete, identifiers conflict or site conditions do not match the plan.
- Reject or reroute material when its condition, description or intended route cannot be brought within the project’s control criteria.
- Escalate repeated failures through the project governance route rather than closing them as isolated paperwork issues.
Next step: turn the pack into a controlled project document, populate it with the actual material schedule and run a gate review before the first mobilisation activity . The result should be a signed decision trail that the delivery team can use at the point of work.
Frequently asked questions
What should a contractor provide before mobilisation?
A contractor should provide the material schedule, supplier details, safety information, delivery sequence, storage plan, responsible persons and escalation contacts. The governance pack should connect each item to an owner and an acceptance decision.
How does this approach work with CDM Regulations 2015?
The governance pack supports the management of construction risks by making responsibilities, controls, information and escalation routes visible before work starts. It does not replace the project’s construction phase plan, design risk management or specialist legal advice.
How should a business measure governance pack performance?
Measure whether required records arrive before decision gates, whether rejected materials are isolated, whether changes are logged and whether corrective actions close on time. These measures show control performance without treating document volume as proof of safe mobilisation.
When is a separate specialist assessment needed?
A separate specialist assessment is appropriate when materials may contain hazardous substances, when contamination is suspected, when waste classification is uncertain or when handling conditions exceed the project team’s competence. The governance pack should record the specialist input and the resulting control.
What is the difference between a risk register and a governance pack?
A risk register records threats, owners, controls and status. A governance pack connects the risk register to decisions, evidence, acceptance gates, reporting routines and escalation routes so mobilisation activities can be authorised or stopped on defined grounds.
What should happen when a delivery fails acceptance criteria?
The delivery should be placed on hold, physically separated where appropriate, recorded as a nonconformance and referred to the named decision owner. Release should follow documented evidence and approval rather than an informal instruction from the delivery team.
