Give every authority a job and a stop line.

The exact organisation varies, but the control logic should not. For every important fact, name one primary authority, the contributors it needs and the decisions it must not make alone.

A tool is never an authority by itself. Revit, an IFC repository, a CDE, Maximo, an OPC UA server, a data platform and a digital twin can all hold important records. Authority comes from the owner’s operating model: mandate, competence, source, approval and consequences.

Mandate inflation often looks like helpfulness.

Overreach rarely announces itself as overreach. It arrives as efficiency: “We already have the model,” “the platform can store it,” or “someone needs to decide.” The short-term gap is closed. A weak foundation is embedded.

The most dangerous specialist is not the one who knows too little. It is the one whose authority expands faster than their awareness of what they do not know.

This standard must also apply to the owner, the architect and the systems engineer. Cross-disciplinary responsibility does not mean pretending to possess every discipline’s depth. It means recognising the right authority, forcing boundary decisions into the open and refusing unsupported certainty.

Govern the handoffs, not just the boxes.

A role chart is not enough. The owner needs a decision chain for every critical information class, especially where several domains contribute to the same object.

For critical objects, an authority register should state at minimum: information class, primary authority, contributors, authoritative source, validation rule, approval role, effective lifecycle stage and escalation path.

The house is not strongest when one discipline owns every brick. It is strongest when each brick is controlled by the right authority and every interface has a named decision owner.