Manage interfaces between work packages

List the physical and organisational interfaces between packages: where one trade hands over to the next, where scopes touch and where a tolerance or a builder's-work detail crosses a boundary.

เหตุผล: Naming the interfaces is what turns a fuzzy boundary into a managed one. The interface nobody wrote down is the gap that becomes a variation and a delay when both sides deny it.

Give each interface an owner on both sides, the information each needs from the other and the date it is needed by, so the exchange is a commitment rather than a hope.

เหตุผล: An interface with one owner is an argument waiting to happen. Naming both sides and what each owes the other is what makes the handover actually work at the boundary.

Work the open interfaces in regular interface meetings, agree who does what by when at each boundary and minute the actions against the register.

เหตุผล: Interfaces close when the two sides sit down and agree, not when a register sits idle. The meeting is where the ambiguity at the boundary gets resolved before the trades reach it.

Close an interface only when both owners confirm the exchange is done and the physical detail is resolved, so a closed item really is closed.

เหตุผล: Closing on one side's say-so is how a gap reopens on site. Requiring both sides to agree is what makes the register a true picture of what is settled and what still bites.