Give the design team a brief that reveals the unknowns.

Lead with the project decision

Write the municipality, property type and proposed work. State whether you need an initial assessment, review of an alteration, a defined repair scope or recovery of missing records. Explain the decision that is blocked and the intended project timing as context.

Example: “Commercial tenancy renovation in Edmonton. Current drawings are partial. We need the sprinkler-design review scope before the ceiling plan is finalized.” That is a useful request without inventing technical design values.

Build the document index

Attach only documents needed through an appropriate project channel. The public enquiry can begin with a broad description of what is available.

Describe changes without designing the solution

• New partitions, ceilings or room uses.
• Storage products, packaging and arrangements.
• Installed equipment and connected-trade changes.
• Heating or enclosure changes.
• Access and occupied-building constraints.

Ask the design team what further information it needs. The brief should explain the proposal rather than choose sprinkler spacing, demand, pipe size or an equipment configuration.

Request the professional scope explicitly

Ask who will establish the applicable requirements, what site verification is needed and what deliverable results. Identify whether connected alarm, supply, structural or other specialist questions need separate roles.

NRC’s adoption overview explains why jurisdiction and adopted requirements matter. A current manufacturer document can inform a product question without settling the governing code or project approval. Keep those roles distinct.

Make assumptions and decisions visible

Use one list for unknowns and another for confirmed project decisions. Give each a responsible person, supporting document and drawing revision. When an answer changes the proposal, update the brief and preserve the earlier assumptions.

Ask the team to identify prerequisite decisions for procurement, construction and handover. This is a coordination record, not a design calculator or an authority submission by itself.

Work through a first brief with incomplete drawings

Consider a fictional building alteration with a current architectural proposal and partial existing sprinkler records. The owner wants a price but has not established the design-review scope. Begin with the proposed change, available documents and the information that is missing. Ask the responsible professional to explain what verification and additional input are needed before a firm project basis can be established. A concise brief can make the uncertainty reviewable without pretending that the owner’s floor-area estimate or component count supplies a design.

Label each attachment by source and status. The architectural plan may describe the current proposal; the old sprinkler plan may be useful history; a recent service report may identify a finding without addressing the alteration. Ask the team to explain how those documents will be used and what they do not establish. Record the response in the brief’s unknowns list. If the assessment scope requires another qualified role, identify it and the interface rather than assuming the first provider’s quotation includes all building questions.

Use the initial discussion to request a deliverable, not simply a yes-or-no answer. Ask what record will describe the assessment, which proposal revision it represents and what remains outside its scope. Keep the professional fee or commercial proposal linked to that deliverable. The resulting engagement is easier to review because the owner can see what information it is buying and what decision that information supports. It also reduces the chance that a preliminary conversation becomes an unsupported instruction to start installation.

Copyable engagement request: “Please propose a defined design-review or assessment scope for [property/change], represented by [proposal revision]. We have [existing records] and lack [identified information]. Explain what verification, supply information and connected professional input are needed, which deliverables your engagement will provide and what remains excluded. Identify the decision the resulting record will support and the appropriate local pathway questions.” Replace the brackets with actual references and send the complete attachments requested by the team. Keep the fee proposal tied to those deliverables, rather than treating a preliminary conversation or a general site visit as a complete design engagement.

Use the brief throughout the project, not only at booking

Create a brief version whenever the material proposal changes. Retain the date, drawing revision and reason for the change. If the owner changes storage, use, ceilings or equipment, identify that difference explicitly and ask the coordinator which reviews need an update. A running project description should not overwrite the assumptions behind an earlier design answer. Keeping versions lets the team understand whether a new question is additional work, an unresolved original item or a clarification of information that was already supplied.

Turn confirmed responses into a decision index. Each entry should identify the question, responsible issuer, supporting document and affected scope. Keep open questions separate from answers and connect them to the next responsible action. The owner can use this record to coordinate procurement and access while the qualified team determines the technical requirements and sequence. Avoid assigning a generic readiness score. The record is more useful when it shows precisely what must be resolved before the next commitment than when it produces a number with no professional basis.

At handover, connect the brief’s decisions with the delivered record package. Note which proposed changes were completed, which were withdrawn and which remain outside the accepted scope. Include the final issuer documents and open-item list rather than leaving the original enquiry as the only summary. This gives the future manager a readable account of why the work was undertaken and where its evidence is held. The brief remains an administrative aid; it never replaces the governing design, professional verification or actual authority decisions.

Send the first request with a clear next step

Use the project brief tool to organize the summary, then review it before sharing. A useful final sentence is: “Please confirm the assessment scope, information still needed and the record you will deliver.”

The enquiry desk is a non-emergency introduction route. It does not dispatch an emergency crew, promise contractor availability or approve the proposed design.

References and scope

1. Provincial and territorial code adoption — Canadian Board for Harmonized Construction Codes. Explains adoption and enforcement responsibilities. Provincial tables carry different reference dates; obtain current information from the responsible authority. It is not a ruling for a particular building. Link reviewed 2026-10-02.
2. Provincial and territorial ministries — National Research Council Canada. Starting points for the responsible jurisdiction. Confirm local authority and current requirements. Link reviewed 2026-09-30.
3. Sprinkler fitter — trade description — Red Seal Program. Trade scope; does not establish a specific company’s qualifications or provincial licensing. Link reviewed 2026-09-30.

Review dates identify source-link checks, not professional certification or a building-specific determination. Confirm current jurisdiction and exact-model requirements for actual work.