Start with the outcome, then describe the systems
A useful mechanical, electrical and plumbing (MEP) brief explains what the building needs to do and what is changing. “Upgrade the office” is a starting idea. “Reconfigure two occupied floors, retain the shared plant and coordinate new partitions with air distribution and lighting” gives the project team something specific to assess.
At this stage, describe the requirement without prescribing an unverified technical solution. The responsible designers and specialist teams establish design suitability, system capacity and the approvals needed for the actual site.
Make the boundary visible
For each system, record what is included, what is retained and where the new work connects. A short interface table often reveals gaps that a long equipment list hides. Identify who provides equipment, who installs it, who makes each connection and who accepts the completed work.
- System and location: the asset, room or zone affected.
- Existing condition: available drawings, surveys and known limitations.
- Interface: the point where one party’s work meets another’s.
- Responsibility: the named party for design, installation, approval and acceptance.
Record the constraints that change the programme
An occupied site needs more detail than a completion date. List allowed working hours, access and storage limits, noise restrictions, equipment availability and the process for approving a service interruption. The team can then distinguish installation time from the time needed for access, review, procurement and restoration.
State unresolved information openly. “Existing panel schedule to be confirmed during survey” is more useful than treating the missing schedule as a settled fact. Keep a dated assumptions register and assign an owner to each question.
Define the evidence needed at completion
Agree the expected drawings, inspection records, equipment information and operating documents before pricing. Where testing or commissioning is included, identify the scope, acceptance responsibility and documentation requirement. A list of deliverables helps the client compare proposals on the same basis.
Commissioning frameworks connect verification to documented owner requirements. For a project brief, the practical lesson is simple: define the desired outcome and the evidence that will demonstrate it, then confirm the project-specific technical method with the appointed team.
A compact brief to prepare
Bring the following information to the initial discussion. It can be a single page with drawings and schedules attached. Keep confidential operational information within the project’s agreed document-sharing process.
- Location, building use, operating status and the change required.
- Available drawings and an equipment or system list.
- Scope boundaries, interfaces, exclusions and open questions.
- Access constraints, proposed dates and approval responsibilities.
- Required inspections, completion records and handover format.
References
General project planning guidance. Technical decisions and approvals depend on the site, agreed scope and responsible project team.