Ask any experienced project manager where problems on a large Malaysian project tend to surface, and the answer is rarely “in the middle of a package.” A piling contractor usually knows how to pile. A facade specialist usually knows how to install curtain walling. The trouble shows up at the edges: where the piling hands over to the substructure contractor, where the facade brackets meet the slab edge cast by someone else, where the building’s sewer line has to connect to a public system owned by another organisation entirely.
These edges are called interfaces. On projects split into several contracts, nominated subcontracts and authority works, interfaces multiply quickly, and each one is a place where responsibility can quietly fall between two parties. Interface management is the discipline of finding those edges early, deciding who owns what, and controlling them until the project is complete. It is less visible than programme or cost control, but it often decides whether they succeed.
Why interfaces are growing on Malaysian projects
Several features of the local industry make interfaces especially important.
Public projects are frequently procured in separate packages, for example enabling works, main building works, external works, and specialist mechanical and electrical works. Large infrastructure such as rail and highway schemes is typically divided into many civil, systems and station packages, sometimes coordinated through a project delivery partner arrangement. Private developers, meanwhile, often appoint specialist contractors directly for items like lifts, facade, kitchen equipment or IT systems, alongside the main contractor.
Then there are the utility and authority interfaces that almost every project has: power supply connections, water reticulation, sewerage, telecommunications, road access approvals and drainage discharge. These involve organisations that are not party to the construction contract at all, yet whose timing and technical requirements can hold up completion.
Add nominated subcontractors and suppliers under standard forms such as the PAM and JKR contracts, and a single building can easily have dozens of interfaces that cross contractual lines. Each one needs someone to say clearly: this is where my scope ends and yours begins.
Three kinds of interface
It helps to think about interfaces in three broad groups, because each needs a slightly different kind of attention.
Physical interfaces are where two pieces of work actually touch: a column base and its holding-down bolts, a waterproofing membrane and the drain outlet, a cable tray passing through a fire-rated wall, a road junction tying into an existing carriageway. The questions are about dimensions, tolerances, materials, sequence and who makes good afterwards.
Functional interfaces are where systems must work together even if they never touch: the fire alarm triggering the lift homing and the smoke extraction, the building management system reading data from chillers supplied under another package, or a station’s signalling depending on power from a separate contract. These usually show up late, during testing and commissioning, when they are most expensive to fix.
Contractual and organisational interfaces are about information, access and responsibility: who provides the setting-out data, who maintains the shared access road, who pays for the scaffold both trades use, and whose approval is needed before work can proceed.
Many disputes come from an interface that was understood physically but never agreed contractually, or agreed contractually without anyone checking that the systems would actually work together.
Learning from large international programmes
Internationally, formal interface management is well established on major rail, energy and infrastructure programmes, where hundreds of contracts must come together into a single operating system. London’s Crossrail programme, now the Elizabeth line, is often discussed in the industry as an example of how complex systems integration and the interfaces between civil works, systems and operations can drive delays when they are not resolved early. Offshore oil and gas and power plant projects have long used structured interface registers and agreements between contractors as a standard practice.
The lesson for Malaysian practitioners is not that every project needs the machinery of a megaproject. It is that the tools developed on those programmes scale down well. A mid-sized hospital, school, factory or mixed development can apply the same principles with a fraction of the effort.
The interface register
The core tool is an interface register: a living list of every significant interface on the project. A practical register records, for each interface:
A short description and location.
The parties on each side, and which of them is the lead.
The type of interface: physical, functional or contractual.
The information each party must provide to the other, and by when.
Any physical works, such as sleeves, embedments, openings or temporary supports, and who provides them.
Testing or inspection needed before the interface is closed.
Current status, open issues and the date it was formally closed.
The register should start during design and procurement, not on site. The best time to sort out an interface is before tender documents go out, because that is when scopes can be written so that boundaries are clear. Phrases like “by others” or “to be coordinated” in a specification are warning signs. Each one should point to an interface that is explicitly owned by someone.
Writing interfaces into contracts
Once packages are defined, scope documents should describe interfaces in plain terms. For each package, a short interface schedule can set out what the contractor receives from others, what it must provide to others, and the agreed handover condition. Drawings that show scope boundaries, often called demarcation or responsibility drawings, help avoid arguments later about who installs the last metre of pipe or the final layer of finishes around a fitting.
Where contractors appointed separately must cooperate, consider requiring them to agree interface agreements or coordination protocols among themselves soon after award, with the project manager or contract administrator overseeing them. This does not remove the employer’s responsibility for coordinating separate contractors, but it creates a documented basis for cooperation.
Managing interfaces on site
On site, interface management becomes routine coordination with a sharper focus. Useful habits include:
A regular interface review as a standing item in coordination meetings, working through open items in the register rather than discussing them only when something goes wrong.
Combined services and builder’s work drawings checked jointly by the trades involved, with sign-off before installation starts.
Joint inspections at the handover of an area from one contractor to the next, recording the condition of the work, any defects and outstanding items. A short signed handover form, with photographs, prevents arguments about who damaged what.
Early engagement with authorities and utilities, with their requirements and submission timelines built into the programme and tracked like any other interface.
Integrated testing and commissioning planning that maps which systems depend on which, so functional interfaces are tested in a logical sequence rather than discovered during final inspections.
The project manager’s role
Interfaces by definition belong to more than one party, which is exactly why they need a neutral owner. In most arrangements, that falls naturally to the project manager or the party appointed to coordinate on behalf of the employer. The role involves:
Making sure the interface register exists, is kept current, and is actually used.
Resolving disagreements quickly, before they become stand-offs that hold up work.
Escalating interfaces that depend on employer decisions, such as late design choices or direct appointments, so the employer understands the consequences of delay.
Keeping clear records. When something does go wrong, a well-maintained register and handover records make it far easier to establish responsibility fairly and reduce the scope for disputes.
It also requires a particular mindset. Contractors naturally focus on their own scope and their own risk. The project manager’s value is in looking at the whole system and asking, at every boundary, “who is looking after this bit?”
Start with the edges
Interface management does not need specialist software to begin. A well-structured spreadsheet, clear scope boundaries in the tender documents, and a disciplined review in each coordination meeting will catch most of the problems that otherwise appear as late surprises.
As Malaysian projects grow more complex, with more specialist packages, more digital systems and more authority requirements, the edges between packages will matter more, not less. For any project team, a good starting exercise is simple: list every place where your work meets someone else’s, and ask whether each one has a named owner. The gaps in that list are where your next delay is likely hiding.
The articles and technical notes published on this website are intended for knowledge sharing and professional discourse within the construction project management community. The views, opinions, and interpretations expressed are those of the respective authors and do not necessarily reflect the official policy, position, or constitutional stance of the Association of Construction Project Managers Malaysia (ACPM) or its Council.
The content should not be construed as legal, regulatory, or professional advice. Readers are encouraged to exercise their own professional judgement and seek appropriate advice where necessary