JOURNAL / DELIVERY PLANNING
Build an interface register before procurement
A project package rarely exists in isolation. Structure, envelope, services and operations meet at interfaces that need clear responsibilities and current information.
01
Describe the boundary precisely
An interface is where information, physical work or responsibility connects one package to another. A useful entry identifies the location, affected systems and the question requiring a decision. For example, equipment may need a support, opening, service connection and maintenance clearance supplied by different parties. Simply naming the two contractors does not resolve that relationship.
The register should make the missing information understandable to the people who must respond, with references to the current drawings, specifications or vendor information. Begin with the decisions that connect workstreams. Record the question, the information owner, the required input and the point at which the answer is needed.
02
Allocate information as well as work
Record who supplies the relevant data, who reviews it, who installs each element and who accepts the completed interface under the actual appointments. These roles may differ. Coordination should not be mistaken for authority to approve every technical discipline. Where the required professional or contractual responsibility is unclear, identify it as an unresolved action rather than assigning it casually in a spreadsheet.
The register supports the project’s appointments; it does not replace them or create engineering credentials.
03
Connect the register to procurement dates
An unanswered question can affect an order long before installation begins. Identify when the information is needed and the work or purchase depending on it. Review the status with the responsible parties before a deadline becomes a site problem. Distinguish a target response date from a confirmed decision.
If procurement proceeds with an assumption, make its authority and implications explicit through the agreed process. The register should expose risk rather than make an incomplete package appear fully coordinated.
04
Keep the decision and its reference together
When an issue is resolved, record the accepted response and the document revision carrying it. A meeting note may explain the discussion without being the instruction the contractor is entitled to build from. Confirm how the decision reaches the appropriate current information. Withdraw superseded references from the working set and communicate the change to affected packages.
Closing an entry without an identifiable outcome can make the register look tidy while leaving the original interface unresolved in practice.
05
Use a manageable review rhythm
Focus each review on decisions with an approaching dependency, unresolved responsibility or material effect on the scope. An enormous list of minor issues can obscure the items that need client or specialist attention. Assign clear action owners and revisit overdue responses. The register is a coordination tool, not a measure of personal performance by the number of rows closed.
Its value lies in helping the appointed project team act on the information before the affected work or procurement commitment proceeds.
06
Carry relevant decisions into handover
Some interface decisions affect operation, maintenance access or future alterations. Identify which accepted records need to reach the owner and how they connect to the installed work. Preserve the relevant information without giving the facilities team an unexplained working spreadsheet as its only handover. This illustrative method does not certify a coordinated design or eliminate project risk.
It provides a disciplined way to ask which responsibilities and technical decisions remain open before procurement, installation and acceptance. Keep the register focused on actions rather than administrative volume. A useful entry explains what must be resolved and who is responsible for progressing it.
General planning guidance, not a property assessment, installation specification, legal advice or an accepted project proposal. Confirm relevant decisions with the appropriately appointed professionals.