1. Project Management
  2. Project Planning
  3. Before Building Systems Are Selected: Write Down the Owner’s Operating Needs

Before Building Systems Are Selected: Write Down the Owner’s Operating Needs

Turn everyday operating expectations into a clear project brief that the design and commissioning teams can review.

Before Building Systems Are Selected: Write Down the Owner’s Operating Needs

A building can contain the specified equipment and still be difficult for its owner to operate. Early planning should therefore describe how the building is expected to be used, maintained and handed over. These expectations give the design team a clearer target before systems are selected.

Distinguish the requirement from the solution

The Whole Building Design Guide’s commissioning documentation guidance distinguishes the Owner’s Project Requirements from the Basis of Design. The first sets out the owner’s goals and success criteria; the second explains the design team’s technical approach to meeting them. The guidance calls for early input from owners, users and operations staff, with updates as the project develops.

For an owner, the useful starting point is an operating need rather than a favorite equipment model. Describe who uses a space, when it is occupied and what the team must be able to control. Let the designers explain how the proposed systems address those needs.

Include the people who will run the building

Invite facilities staff and regular users to identify practical concerns. Ask about access for routine maintenance, staff experience with controls and the information needed when a fault occurs. Record differences between normal operations and occasional events instead of letting one schedule stand for every use.

Use the project’s communication arrangements to collect these comments in one place. Assign a person to resolve conflicting requests and confirm the accepted version of the brief.

Make success understandable

Ask the design and commissioning teams how each important requirement will be checked. A broad phrase such as “easy to maintain” should lead to specific discussions about access, instructions and training. Avoid inventing technical targets without professional input; identify the need and ask the team to propose a suitable, verifiable response.

Keep unresolved items visible with a responsible contact and decision date. This is particularly useful when a requirement depends on a tenant decision or an operating policy that has not yet been settled.

Carry the brief through handover

When requirements change, record the reason and ask which design or testing documents need revision. Before occupancy, review the agreed training, manuals and outstanding issues against the current brief. A concise record of operating needs gives the owner a practical reference for evaluating the finished building and discussing later changes with the project team.