Master plans with building annexes for Macquarie Park corporate campuses

The master holds anything that should be identical everywhere: what a clean workstation means, how amenities are assessed, the reporting format, the escalation path, the induction requirements and the policy on periodic work. These are decisions the campus makes once. Repeating them in six documents guarantees they will diverge, usually because one was updated and the others were not.

The annexe holds what genuinely varies: the zone list, the frequencies, the access route and hours, the storage location, any surface or equipment particular to that building, and the local contacts. An annexe should be short enough to be readable in a few minutes, because it is the document a supervisor actually carries when covering an absence in an unfamiliar building. It is also the document most likely to be handed to someone at short notice, so length works against it. Anything that applies to every building on the campus belongs upstream in the master, where it is maintained once.

Campuses often force uniformity that costs money without improving anything. A building housing laboratories or a data facility has requirements that an ordinary office building does not, and applying either one's specification to the other is wasteful in one direction and inadequate in the other. The annexe structure allows genuine difference without abandoning the shared standard.

The reverse problem is equally common. Where two office buildings on the same campus have drifted to different frequencies for no reason other than history, the master and annexe structure makes that visible immediately. Comparing six short annexes against a common framework surfaces the anomalies in a way that comparing six full contracts never does.

Review effort should follow risk and change rather than the calendar. A building with a stable population and unchanged use may need an annual look at its annexe. One undergoing refurbishment, a tenancy change or a headcount shift needs attention when the change happens. Setting review triggers per building keeps the campus manager's time on the buildings where something is actually different. A trigger-based approach also gives the campus manager a defensible answer when asked why one building has not been reviewed recently: nothing about it has changed.

The master document needs its own review, but less often and for different reasons. It changes when a standard changes, when an induction requirement is updated or when the reporting format needs to move. Keeping those decisions in one place means they are made once for the campus and applied everywhere, rather than negotiated separately building by building.