Build the delay record before the EOT discussion starts.

What an EOT does—and what it does not do

An extension of time adjusts the contractual Time for Completion when the applicable mechanism and assessment support it. It is about time. It does not automatically settle loss and expense, prolongation cost, disruption or any other financial claim.

On a busy project, teams often use “EOT” to describe three different things: the delaying event, the contractor’s submission and the certificate or determination. Keep those separate. The site team records facts. The planning team analyses programme effect. The contract team handles notices and entitlement. The authorised contract administrator assesses the submission under the contract.

The useful question is not only “How many days did we lose?” It is “What happened, which activity did it affect, what did the logic show at that time, and what did the team do next?”

Start with the exact contract form and amendments

There is no universal Malaysian EOT notice period or procedure. First identify the form, edition, particular conditions, letters of award and amendments that actually govern the project.

JKR publishes PWD Form 203 (Rev. 1/2010) for contracts where drawings and specifications form part of the contract, and PWD Form 203A (Rev. 1/2010) where Bills of Quantities form part of the contract. CIDB publishes a separate Standard Form of Contract for Building Works 2022. PAM forms, design-and-build forms and bespoke contracts have their own wording.

The CIDB 2022 form treats defined events through its compensation-event procedure. When implemented, a compensation event may change the Contract Sum and/or Time for Completion; a time change is notified in a Certificate of Extension of Time under clause 32.6. That terminology should not be copied into a PWD, PAM or amended contract unless that contract uses it.

Before the job starts

• Build a one-page notice matrix listing the clause, trigger, deadline, addressee, delivery method and supporting particulars.
• Confirm who may issue instructions and who must receive contractual notices.
• Agree how programme baselines, updates and revisions will be named and retained.
• Keep proof of transmission. A draft in someone’s outbox is not a project record.

The seven-link delay record

1. Event opened. Give it a stable ID, a neutral description and a start date. “DE-014—access to Zone C not available” is more useful than “client delay”.
2. Source retained. Attach the instruction, RFI response, weather record, site photograph, inspection result, delivery information or access log behind the entry.
3. Notice issued. Follow the signed contract, state the known facts, reserve only what the contract and advice support, and keep delivery evidence.
4. Activities identified. Name the programme revision, activity IDs, work fronts, predecessors and successors affected.
5. Effect updated. Record what work stopped, slowed, resequenced or continued, with dates and actual resources.
6. Mitigation recorded. Note additional shifts, alternative access, resequencing, procurement action or other reasonable steps—and their outcome.
7. Event closed. Record the end date or continuing status, then cross-reference the submission, assessment and any certificate.

A short entry made each day is usually more reliable than a polished narrative reconstructed three months later. Preserve original timestamps and attachments even when a report is edited for clarity.

Connect the event to the programme that existed then

The programme is where a delay record becomes a time analysis. Use the current accepted or approved programme as required by the contract and project procedure—not a newly drawn bar chart created only for the claim.

Record the affected logic

Identify the activity ID, description, work front, planned dates, actual status, remaining duration, predecessors and successors. Explain whether the event affected a critical or near-critical path and how available float was treated. If the team resequenced work, show both the original logic and what changed.

Do not hide concurrent problems

If another contractor-responsible issue affected the same period or path, record it accurately and obtain professional advice on the contractual analysis. A reliable project file includes inconvenient facts; leaving them out makes the whole record easier to challenge.

Update prospectively, verify retrospectively

At the event date, record the likely effect using information available then. In later programme updates, compare the forecast with what actually happened. Keep each version. Overwriting last month’s programme destroys the audit trail.

Delay-event record checklist

Use this as an operational prompt, then adapt it to the contract and project procedure.

• Event ID, neutral title, location and responsible record owner.
• Start date, end date or “ongoing” status, with time where relevant.
• Instruction, access restriction, condition or other recorded cause.
• Contract clause and notice reference identified by the contract team.
• Programme name, data date, revision and affected activity IDs.
• Planned work versus actual work at the affected work front.
• Labour, plant, subcontractors and materials available or stood down.
• Wide context photos and close-ups with location, direction and caption.
• RFI, WIR, NCR, site instruction, drawing and meeting-minute references.
• Mitigation, resequencing and follow-up actions with owners and dates.
• Notice recipient, issue date and proof of delivery.
• Cross-reference to the EOT submission, assessment and certificate.

Common weaknesses that make the story harder to verify

• Labels instead of facts: “Employer delay” is a conclusion. Record the unavailable area, the planned activity and the instruction or access evidence.
• Photos without context: a close-up of wet ground proves little without date, location, direction and a wider view.
• No programme version: an activity reference is ambiguous if the programme revision and data date are missing.
• Silence on mitigation: record what was considered, attempted and achieved—even if the result was limited.
• Reconstructed daily records: a neat month-end diary created from memory is weaker than contemporaneous entries with original timestamps.
• Time and cost mixed together: keep the EOT time analysis clear and handle money under the relevant contractual procedure.

Make the daily record do useful work

A delay file is easier to maintain when supervisors already capture progress, constraints, resources and photographs in a consistent format. Continue with the Telegram site-reporting guide, or start from a practical daily site report template.