A client-friendly explanation of mechanical, electrical and public-health coordination, with emphasis on space, interfaces, access, controls and commissioning. This guide is written for clients and non-specialist decision-makers who need a clear framework for asking better questions, commissioning the right evidence and understanding where specialist input is essential.
Define the servicing strategy early
The practical point is that establish heating cooling ventilation power water data and life-safety needs. In client terms, this should be translated into an explicit decision, owner and evidence requirement rather than left as an informal expectation. Align systems with occupancy and resilience should be tested against the brief and the constraints already known. If the project team cannot explain the assumption in plain language, the assumption is not yet controlled.
A useful review asks three things: what is known, what is still uncertain, and what decision becomes harder if the uncertainty remains. Reserve major plant space deserves particular attention because it can affect more than one workstream. Test utility capacity before detailed design should therefore be recorded early enough for designers, contractors and the client to respond without avoidable rework.
For a building services decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes define the servicing strategy early a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Protect routes and service zones
Good project control begins by making allocate risers ceiling zones and horizontal distribution visible. That does not mean producing more paperwork; it means ensuring the relevant people can see the requirement, understand its consequence and act at the right time. Coordinate with beams and fire compartments then becomes part of the project logic rather than an isolated technical discussion.
The same discipline applies to maintain required falls for drainage. Teams should state the evidence they will use to confirm the position and the date by which it is needed. When avoid relying on site teams to resolve impossible geometry is also considered, the client can compare options on a consistent basis and avoid decisions that appear cheaper or faster only because important consequences were omitted.
For a building services decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes protect routes and service zones a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Coordinate equipment with the building
At this stage, plan structural loads and plinths is best treated as a managed choice rather than a background detail. The team should establish the baseline, identify interfaces and document who has authority to approve a change. Provide acoustic and vibration treatment can then be reviewed in the same decision framework, with cost, time, safety, quality and operational consequences shown together.
This approach is especially valuable where coordinate louvers intakes and exhausts. A short, evidence-led discussion before commitment is usually more useful than a long explanation after work has started. Maintain safe access for replacement should be carried into the next design or delivery gateway so that the project does not quietly revert to an outdated assumption.
For a building services decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes coordinate equipment with the building a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Manage penetrations and fire stopping
Clients do not need to perform every technical task themselves, but they do need confidence that identify wall and floor penetrations systematically. The appointment, brief or control process should make that expectation unambiguous. Coordinate sleeves and builders work also needs a route for escalation when information conflicts or a decision cannot be made within the working team.
In practice, use tested fire-stopping solutions appropriate to the construction is where seemingly separate disciplines often meet. A coordinated review should examine those interfaces before downstream work relies on them. Inspect before ceilings close access completes the control loop: define what acceptable looks like, obtain the relevant evidence and retain the record in a form that will still make sense at handover.
For a building services decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes manage penetrations and fire stopping a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Integrate controls and specialist systems
The practical point is that define interfaces between BMS lighting security fire and process controls. In client terms, this should be translated into an explicit decision, owner and evidence requirement rather than left as an informal expectation. Agree cause-and-effect requirements should be tested against the brief and the constraints already known. If the project team cannot explain the assumption in plain language, the assumption is not yet controlled.
A useful review asks three things: what is known, what is still uncertain, and what decision becomes harder if the uncertainty remains. Coordinate network and power dependencies deserves particular attention because it can affect more than one workstream. Avoid late integration after individual packages are complete should therefore be recorded early enough for designers, contractors and the client to respond without avoidable rework.
For a building services decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes integrate controls and specialist systems a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Commission from systems to whole-building operation
Good project control begins by making create pre-commissioning checks visible. That does not mean producing more paperwork; it means ensuring the relevant people can see the requirement, understand its consequence and act at the right time. Balance test and demonstrate services then becomes part of the project logic rather than an isolated technical discussion.
The same discipline applies to test controls in realistic modes. Teams should state the evidence they will use to confirm the position and the date by which it is needed. When record results and defects against acceptance criteria is also considered, the client can compare options on a consistent basis and avoid decisions that appear cheaper or faster only because important consequences were omitted.
For a building services decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes commission from systems to whole-building operation a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Handover for operators, not archives
At this stage, provide clear asset data and set points is best treated as a managed choice rather than a background detail. The team should establish the baseline, identify interfaces and document who has authority to approve a change. Train facilities staff can then be reviewed in the same decision framework, with cost, time, safety, quality and operational consequences shown together.
This approach is especially valuable where label systems consistently. A short, evidence-led discussion before commitment is usually more useful than a long explanation after work has started. Plan seasonal or post-occupancy fine tuning where the project needs it should be carried into the next design or delivery gateway so that the project does not quietly revert to an outdated assumption.
For a building services decision, the useful question is not simply whether this topic has been discussed, but whether the discussion changed the project information. The project record should show the chosen position, any alternatives rejected, the assumptions that remain open and the trigger for revisiting them. That makes handover for operators, not archives a working control rather than a retrospective narrative. It also gives future team members enough context to understand why a decision was made instead of repeating the same investigation.
Client review checklist
Before moving to the next project stage, use this short review to test whether the core decisions are actually controlled:
- Define the servicing strategy early: Establish heating cooling ventilation power water data and life-safety needs.
- Protect routes and service zones: Allocate risers ceiling zones and horizontal distribution.
- Coordinate equipment with the building: Plan structural loads and plinths.
- Manage penetrations and fire stopping: Identify wall and floor penetrations systematically.
- Integrate controls and specialist systems: Define interfaces between BMS lighting security fire and process controls.
Not every item will apply with the same weight to every project. The value of the checklist is to expose assumptions early, allocate them to a competent person and make the consequences visible before commitment.