Define the intended result.
Identify the systems, information and operator functions that matter. Explain what words such as “integrate,” “open” and “complete” mean for this project.

Integrated automation
Division 25 is the Integrated Automation division of MasterFormat, the system developed by the Construction Specifications Institute (CSI) and Construction Specifications Canada (CSC) to organize project information. On a project, it gives integration requirements a place to be defined, coordinated and connected to verification.
Try a practical example ↓The structure and the project
MasterFormat supplies the classification. The project team writes the actual requirements: what connects, how it should behave, who delivers it and what evidence supports acceptance. Read those requirements with the owner’s criteria, drawings, agreements and related specification sections.
Division 25 and MSI are connected ideas. Division 25 organizes specification content. MSI describes an integration role and its work. The project still has to define that role’s scope and authority.
Identify the systems, information and operator functions that matter. Explain what words such as “integrate,” “open” and “complete” mean for this project.
Check how integration relates to plumbing, heating, ventilation and air-conditioning (HVAC), electrical systems, communications and general project requirements. Resolve gaps or conflicts through the agreed clarification process.
Define the required points, names, units, relationships, recording intervals and access. Agree on how missing or unreliable data will be identified.
Connect responsibilities with review, readiness, testing, issue resolution, records and operator training. Establish the acceptance criteria before the team needs to demonstrate them.
Try the thinking
An illustrative draft specification contains that sentence. You are reviewing it before procurement. Which action gives the team a clearer starting point?
Choose where you would begin. Open each option to compare the reasoning.
The extra word does not identify the meters, destination, functions, data or acceptance evidence. Stronger wording helps only when the team can understand what it requires.
This addresses the missing detail. Identify the meter schedule, required points and units, communication interfaces, recording needs, access, responsible parties and agreed acceptance evidence. Coordinate these requirements with the related documents before pricing.
The commissioning provider can help identify gaps and review verification needs within its scope. Assigning missing design or delivery requirements at the end creates uncertainty. Resolve the intended scope with the responsible project parties early.
What you practice producing
Take one intended function and build a requirement-to-evidence record. Identify the source requirement, the responsible parties, the conditions for the check, the expected result and the record the owner receives. Advanced sessions can use an approved specification and interface matrix.
Use the MasterFormat edition selected for the project and the actual project specifications. Teaching shorthand and a company’s preferred section structure may differ from official titles. A section number by itself does not establish a technical requirement.
CSI’s MasterFormat overview
WBDG / SpecsIntact: MasterFormat divisions
Build your understanding
Practice reading integration requirements, identifying gaps and connecting the intended result to useful evidence. Start with the fundamentals or bring an approved project example for deeper team training.
Help shape BPV
Tell us what connected, where you got stuck or what is missing for your role. Your questions help identify the next lesson to develop.
You can review and send your feedback in your email app.