What Clients Should Decide Before MEP Coordination Begins

Coordination cannot resolve an undecided brief

A coordinated model can still describe the wrong building. Ducts may clear beams, pipes may avoid cable trays, and equipment may fit the plant room while the underlying assumptions about operating hours, occupancy, process loads, resilience, control, or maintenance remain unconfirmed. Geometry can reconcile known requirements; it cannot decide what the owner needs the building to do.

RIBA places detailed client requirements and the approved Project Brief before developed design, while ASHRAE's commissioning framework treats the Owner's Project Requirements as the basis for design, construction, acceptance, and operation [1][2]. These sources use different project languages, but they share a useful sequence: define intended performance and use, then develop and verify the technical response. MEP coordination should therefore begin with an owner-side decision record, not a request for every discipline to start routing.

MEP coordination becomes dependable when every important route can be traced to an owner decision and every owner decision has a route to acceptance.

Describe operation as scenarios, not averages

Record who uses each part of the building, when, for how long, and under which exceptional conditions. Include normal hours, setup and shutdown, cleaning, deliveries, seasonal change, events, partial occupation, tenant variation, after-hours work, emergency operation, and periods when only selected areas remain active. Occupancy totals matter, but diversity, simultaneity, movement, and local density often shape services more directly than a single peak number.

For each scenario, identify environmental expectations, critical equipment, water use, lighting and power needs, ventilation or extraction, acoustic limits, security boundaries, and operator presence. Mark whether the input is verified, assumed, provisional, or unknown. The design team can then state how each assumption affects plant capacity, zoning, distribution, control, metering, or space rather than burying it inside calculations that the client never sees.

Make owner equipment and process loads visible

List equipment the owner, tenant, kitchen, laboratory, workshop, IT team, security team, or specialist supplier will provide. For each item, record location, quantity, duty, power, heat, water, drainage, ventilation, data, controls, support, clearance, noise, vibration, delivery route, replacement route, and information maturity. A note saying 'equipment by others' is not a coordinated requirement.

Separate connected load from realistic operating demand, and ask qualified engineers to document the basis for any diversity or future allowance. Identify which loads are code-governed, manufacturer-defined, measured from an existing operation, or estimated. This is especially important where one late equipment choice can alter distribution, heat rejection, drainage, structural support, fire strategy, acoustic treatment, or plant space.

Choose resilience from operational consequences

Define which activities must continue through loss of power, water, cooling, ventilation, controls, communications, fuel, or a single item of plant. State the acceptable interruption, recovery sequence, safe state, manual fallback, redundancy expectation, stored capacity, and authority to reduce service. Avoid asking for 'full resilience' without defining the failure and consequence; different functions may justify different responses.

WBDG advises owners to identify business and occupant risks, system criticality, failure consequences, and mission impacts when setting project performance requirements [3]. This is planning guidance, not a universal engineering prescription. It supports a disciplined question: which system failure would stop a critical operation, create an unsafe condition, damage valuable contents, or prevent recovery—and what evidence will demonstrate that the chosen response works?

Decide how the building will be controlled and understood

Name the operating modes the controls must support, who may change setpoints and schedules, which alarms matter, how overrides expire, what happens during network loss, and which interfaces operators actually need. Define metering by decision: what energy, water, condition, demand, or tenant allocation must be understood, at what interval, by whom, and for what action. More points do not automatically produce better operation.

ASHRAE's controls guidance says successful building automation depends on clear owner requirements and specifications for equipment, performance, sequences, functionality, points, and network architecture [4]. Product and cybersecurity decisions require project-specific expertise. The owner's early task is to describe operational authority and information needs so the design can allocate sensors, controls, integration, access, retention, and acceptance accordingly.

Protect access, isolation, and replacement before space disappears

Ask facilities staff to review plant location, access routes, working clearances, isolation, drainage, lifting, consumables, hazardous tasks, cleaning, inspection, filter and component change, and the route for replacing the largest maintainable item. Show these zones in the same coordination environment as structure, ceilings, rooms, and services. An access volume that exists only in a maintenance manual is not available in the building.

Commissioning guidance distinguishes the Owner's Project Requirements from the design team's Basis of Design and carries requirements into reviews, testing, manuals, and training [5]. Use that chain for maintainability: owner need, design response, coordinated space, installed condition, inspection or test, operating document, and responsible role. Where access conflicts with saleable or usable area, the client should make the trade-off consciously rather than allowing the smallest route to win by default.

Set future capacity and acceptance evidence together

Future capacity should name a scenario, horizon, location, and enabling decision. It may mean spare electrical ways, capped connections, plant-space reservation, extendable controls, a second riser zone, adaptable distribution, or only enough information to make later intervention safe. A flat percentage added everywhere can consume cost and space without preserving the interfaces that change will actually need.

For each important requirement, choose how it will be accepted: design calculation, coordinated review, factory test, site inspection, pressure test, balancing record, functional test, integrated scenario, seasonal test, operator demonstration, training record, or measured performance in use. ASHRAE describes commissioning as phase-spanning verification against owner requirements, including acceptance, documentation, and operations training [2]. The exact scope must be set by the project's risk, appointments, codes, and contracts.

Use the E2W owner-side MEP input register

For every consequential decision, record: the requirement or scenario; affected spaces and systems; evidence source; current assumption; decision owner; specialist input required; latest safe date; consequence if unresolved; design response; acceptance method; and status. Organise the register around operation, occupancy, owner equipment, resilience, utilities, controls, metering, maintenance, security, future change, commissioning, and handover.

Review it at each design gateway with the project brief, equipment schedules, room data, plant and riser strategy, coordination model, cost plan, programme, risk register, and commissioning plan. The register is not a substitute for competent MEP, fire, controls, security, structural, architectural, cost, facilities, or regulatory advice. It is the owner's control surface: a way to prevent technical coordination from converting unanswered business questions into expensive physical assumptions.