RIMAYSDigital safety and AI systems
Menu

Garis Panduan CDM Edisi 2026

Client Duty 2: Maintaining and Reviewing Management Arrangements

CDM 2026 · 8 of 52

Practical guidance for keeping project-management arrangements alive and reviewing them after change.

Ir. Ts. Dr. Mohamad Syamir bin Senin.3 min read
An illuminated acrylic installation showing project milestones, changes and review loops

Six-slide briefing

The guideline at a glance

Slide 1 / 6

01

CDM 2026

Regulation 4

Arrangements are a living system

They must be specific, proportionate, communicated, maintained and reviewed.

  • Clear owner
  • Controlled version
  • Relevant throughout

A static document is insufficient.

Use the buttons, dots or left/right arrow keys. This briefing summarises the guideline; the article and official source remain the detailed references.

CDM 2026 Series — Topic 8 of 52. This is general industry guidance and should be read with current legislation and DOSH directions.

Regulation 4 does not ask the client to create a document and file it away. The client must ensure project-management arrangements are maintained and reviewed throughout the project. The CDM Guidelines 2026 explain that arrangements should be project-specific, proportionate to size and risk, communicated to duty holders and kept relevant as conditions change.

Living project-management arrangements cycle
Figure 1 — Arrangements move through definition, delivery, review, change and verification.

Usable minimum content

A client brief can be the main control point. It should state project purpose and operational requirements, OSH risk-management expectations, realistic programme and budget, design direction and the client organisation’s point of contact. Arrangements should also explain:

  • how the team communicates, cooperates and coordinates;
  • how the client checks PCWD and PCWC duties;
  • assessment of appointees’ skills, knowledge, experience and organisational capability;
  • milestones, deliverables, decision owners and escalation routes;
  • commissioning and handover preparation.

Review triggers

Do not rely only on periodic review. Reopen arrangements after changes to scope, design, construction method, appointments, sequence, risk, site condition, dates, funding or operational requirements. Every trigger needs an owner, assessment date and reasoned decision.

Practical example — adopting IBS

Illustrative example for guidance; not an actual incident report. A Selangor residential project changes part of its structure from conventional construction to an Industrialised Building System (IBS). The change may benefit programme but introduces new interfaces for element weight, transport, storage, cranes, lifting points, installation sequence and temporary stability.

The client triggers a formal arrangements review. PCWD coordinates element design, connections, tolerances and residual risk; PCWC updates the CPP, lifting plan, logistics, exclusion zones and installation sequence. The client reviews mobilisation time, crane/storage budgets, installer competence and release milestones. Client brief, PCI, DRA and deliverables matrix are updated before the IBS package is released.

Compliance actions

  1. Issue a client brief with owner, version and effective date.
  2. Convert expectations into verifiable milestones and deliverables.
  3. Set periodic reviews and out-of-cycle change triggers.
  4. Require PCWD/PCWC reporting on status, gaps, changes and critical decisions.
  5. Record action, owner, due date and closure evidence.
  6. Confirm change reaches relevant PCI, DRA, CPP, method statements and S&H File.

Evidence to retain

  • client brief and version history;
  • communication, cooperation, role and deliverable matrices;
  • milestone schedule and acceptance criteria;
  • PCWD/PCWC reports, review minutes and site visits;
  • change register with time, funding, resource and risk impacts;
  • competence, decision, action and closure-verification records.

Common failures

  • client brief remains unchanged after a major change;
  • review becomes status reporting without decisions or actions;
  • the client delegates all monitoring to a project manager;
  • method change never reaches PCI, CPP or DRA;
  • milestones lack acceptance criteria;
  • actions close because a date expires rather than evidence being complete.

Checklist

  • [ ] Arrangements are project-specific and proportionate to risk.
  • [ ] Client brief, contact point and decision authority are clear.
  • [ ] Milestones and deliverables have owners and acceptance criteria.
  • [ ] Change triggers are defined.
  • [ ] PCWD and PCWC are monitored through reasonable steps.
  • [ ] Relevant documents are updated and distributed.
  • [ ] Actions close only after evidence verification.

Primary references

Consult current official texts. This article is general industry guidance, not legal advice.

Related articles