Turn an EPC contract into an obligations register

Start with the executed agreement and its incorporated documents. Record the applicable document hierarchy, amendments and supplementary agreements. A clause extracted from an earlier draft can look perfectly reasonable and still be the wrong basis for action.

Review the contract by activity: submissions, access, approvals, payment, securities, insurance, notices, reporting, testing, completion and handover. For each activity, identify who owes the obligation and who receives the deliverable. Include important client and third-party dependencies as well as the contractor's own duties.

Do not turn every sentence into a task. Definitions, qualifications and linked clauses may need to sit beside an obligation as interpretation notes. A commercial reviewer should confirm the operative requirement before it becomes a deadline in the project system. The public works manual provides contract management context in section 7.2; the executed project contract remains the source for project-specific obligations.

A practical entry includes an obligation ID, source clause, responsible party, internal owner, trigger, required action, recipient, communication channel, time basis and required evidence. Add related obligations, current status and the person who validated the interpretation.

The trigger deserves careful wording. “After submission” may be too vague if the clause refers to receipt of a complete submission. Record the evidence needed to establish the trigger: acknowledged transmittal, accepted programme, access handover or another specified event. Preserve disputed trigger dates rather than silently choosing the most convenient one.

Keep an internal preparation date separate from the contractual deadline. The team may need three working days to prepare an inspection pack even when the contract's notice period uses calendar days. A system should show both dates and the assumptions behind the calculation.

Consider a fictional contract that gives a reviewer ten calendar days after receipt of a complete submission to respond. A separate provision requires a notice within seven calendar days after the contractor becomes aware of a specified delaying event. These periods are illustrative; they are not standard EPC rules.

Suppose a complete drawing submission is acknowledged on 2 September. On 8 September, the project learns that an access restriction will prevent the planned work. The drawing response clock and the possible delay notice clock have different triggers. Waiting for the drawing response deadline before examining the access notice obligation would confuse two separate duties.

The register should link these entries while preserving their distinct status. A sent reminder is not automatically a contractual notice. A notice acknowledgement is not acceptance of the underlying claim. Those distinctions belong in the record, where the next person can see them.

Site and engineering teams usually observe the trigger before the commercial team does. Give them a simple way to record an event and attach evidence without asking them to decide entitlement. The receiving owner reviews applicability, confirms the required action and assigns preparation and approval responsibilities.

If a trigger is uncertain, record the uncertainty and escalate promptly. An “under review” status should still have an owner and a next action date. It should not stop the system from showing that a potentially important period is running.

For outgoing communications, preserve the approved text, attachments, recipient details, transmission record and any acknowledgement. The register can then distinguish prepared, approved, issued and receipt evidenced. These are useful operational states even where the contract uses different language.

A supplementary agreement may change payment milestones or submission dates. Create a new effective version of the affected obligations, link the amendment and retain the previous version. Decide explicitly how the amendment affects obligations already triggered.

Do the same when a legal or commercial interpretation changes. Record who reviewed the issue, the revised interpretation and which open entries need reassessment. Editing a deadline without an explanation makes later review difficult and can conceal a missed action.

Responsibility changes also matter. When a package manager leaves, transfer open obligations to a named replacement. A group mailbox is useful for continuity but does not replace accountability. Periodically check that external recipient addresses and contractual communication channels remain current under the agreement.

The most useful weekly view shows unvalidated obligations, triggers awaiting confirmation, upcoming actions, issued communications without required evidence and disputed closures. An overdue list alone arrives too late and gives little help with prevention.

Close an obligation only when its defined evidence is present. For recurring obligations, close the individual occurrence and leave the recurring requirement active. A monthly report submitted in September does not complete the reporting duty for the rest of the project.

Test the register with three cases: a trigger on a non-working day, an incomplete submission and an amendment received after an obligation has started. Ask the authorised reviewer to confirm the intended treatment before automating date calculations. The test should expose ambiguity rather than bury it inside software settings.

The register earns its place when someone can open an event and understand the next required action without searching through months of correspondence. Its reliability comes from validated interpretation and preserved evidence, supported by reminders.

1. Extract the highest-consequence obligations from the executed contract first.
2. Validate triggers, recipients, channels and time calculations with the authorised reviewer.
3. Connect site events and submissions to their relevant obligations.
4. Review uncertain triggers and missing evidence alongside upcoming deadlines.
5. Preserve every amendment and interpretation change with its effect on open work.