IPEXIQ · LEARN
Aligned with the CII Guide to EPCM Contracts

Interface Management for EPCM Projects

A practical register for engineering, procurement, and construction interfaces — the handover points where one party's deliverable becomes another party's input. Built to answer not just what needs to be tracked, but how to actually do it.

Why interfaces decide EPCM outcomes

In "A Guide to the Project Management of EPCM Contracts", the Construction Industry Institute (CII) identifies interface management as one of the highest-leverage activities on a project. EPCM organisations split work across many disciplines, contractors, vendors, and owner teams — and each split creates an interface where schedule, scope, and information must cross a boundary.

When those boundaries are tracked informally — in emails, side conversations, or a schedule note nobody opens — they fail silently. By the time the gap is visible on site, recovery is expensive.

The "we should" gap

Most PM guides — including the CII guide — tell you that you should manage interfaces. Few tell you how: what to write down, who owns the date, what the register should look like at 7am on a Monday.

Closing that "should → how" gap is a core principle behind every IPEXIQ tool. This app is the practical answer for interface tracking.

The core model

Every interface is a single record with two sides: a From party providing something, and one or more To parties needing it. Each side carries a forecast date. The variance between them tells you whether the interface is on track.

From → To
One supplier of information, drawing, equipment, or access — and the consumers downstream who need it to start their work.
Forecast dates
A single forecast date per side, updated as the project moves. The original plan is preserved for variance, but the forecast is what drives weekly conversations.
Responsible parties
A central party list (with contact email) populates every dropdown — so the register stays consistent and accountability is unambiguous.

How to actually run it

A practical workflow you can adopt this week — no consultant required.

01

Populate the Responsible Parties admin

List every organisation, discipline lead, or vendor that owns at least one interface. Each entry carries a name and email — and becomes a dropdown option everywhere else in the app.

02

Capture each interface as a single row

For every handover, record: the From side (who provides), the To side(s) (who needs it), and a one-line description on each. You'll typically end up with 30–150 interfaces on a mid-size EPCM project.

03

Set forecast dates and tick "Done" as they close

A single forecast date per side keeps the register fast to update. When the deliverable lands, tick "Done". The Summary tab shows variance — green when the To-side date sits after the From-side date (you have float), red when it doesn't.

04

Review weekly, not monthly

Open the Summary tab in your weekly project meeting. The compressed view (interface number, title, status, From & To forecast, variance) is built to scan in under a minute per row.

05

Export to markdown for archive or handover

The whole register exports as a portable markdown file. Re-import it on another machine, archive it with the close-out documents, or version-control it alongside your project records.

Where this fits in the CII guide

The CII Guide to the Project Management of EPCM Contracts calls out interface management across several chapters. This app maps to the practical artifacts each one asks for.

Project Execution Planning
A register that survives team rotation — every interface, owner, and date in one auditable place.
Contracting Strategy
Clear From/To parties make scope splits between EPCM, sub-contractors, and owner-furnished items unambiguous.
Schedule Integration
Forecast dates per side surface schedule pressure before it shows up as a missed milestone.
Risk & Change Management
Variance flags (early / on time / late) make interface slippage a quantified risk, not an anecdote.
Construction Readiness
"Done" ticks give construction a live view of which prerequisites have closed out.
Close-out & Lessons Learned
Markdown export preserves the full register for post-project review.
CII RS302-1 vs IR302-2

Research vs. Implementation

CII published two complementary documents on interface management. RS302-1 (the Research Summary) defines what good interface management looks like. IR302-2 (the Implementation Resource / Guide) tells project teams how to put it in place. Here's how they line up — and where this app sits.

RS302-1 and IR302-2 are publications of the Construction Industry Institute (CII). References here are for educational comparison; consult the source documents for full requirements.

Ready to register your interfaces?

Open the app, create your first register, and have your party list and first ten interfaces captured in under thirty minutes.

Launch the Interfaces App