Skip to content

Keep the question
with the work.

A project conversation needs a common reference. Keep the document, the finding, and the decision in view so the next person can understand what is being asked—not reconstruct it.

Explore your team’s workflow

A better question
carries its context.

Illustrative review question—not a generated answer or an actual customer exchange.

Which drawing information supports this finding, and what still needs clarification before we respond?
Name the work
Identify the project and the specific report or drawing revision being discussed.
Point to the condition
Include the criterion, sheet location, or assumption that makes the question concrete.
State the decision
Explain whether the next step is a clarification, a design change, or a review of the requirement.
Illustrative connected view of a project model, drawings, and review evidence.
PROJECT QUESTION / CONNECTED CONTEXTIllustrative system view

A useful project question arrives with enough context to answer it.

Illustrative handoff path
01

Question

Does Door 104 establish the required clear opening?

02

Context pack

A2.1 · Door 104 · current drawing revision · applicable criterion.

03

Team response

The leaf size is scheduled. The clear opening at 90 degrees is still unresolved.

04

Decision record

Owner: architect · action: add or verify the dimension · status: open.

Illustrative exchange. A conversation preserves the basis and next action; it does not make the professional determination.

Use the conversation
that fits the question.

Team discussion

Messages, replies, mentions, and file attachments help colleagues share the material behind a coordination question.

Be explicit about the project, revision, and next step. An attached file is supporting material—not proof that every analysis workflow has incorporated it.

Report discussion

Report conversations are scoped to the compliance report they are opened against. Use that context to investigate the plan set’s findings.

Opening a different report changes the available conversation context. Do not assume a thread can see every report or every project document.

Explore report-based drawing review
Code-analysis discussion

Work through the premises and criteria of a code analysis. Keep the question tied to the relevant input, reference, or row under review.

Verify the response against the governing sources and project conditions before acting on it.

Explore Code Research & Analysis

Prepare the context.
Then ask the question.

The quality of a handoff depends on what the team can inspect. These are useful working practices, not promises of automated document control.

  • Identify the revision.

    A filename alone can be ambiguous. State which drawing issue or report the team should use and flag material that has been superseded.

  • Include the relevant source.

    Share the document or drawing detail needed for the question. Avoid separating a quoted requirement from the conditions that make it applicable.

  • Make the next step explicit.

    Say what needs checking and who should respond in the discussion. A conversation records the exchange; it is not an automatic assignment or approval.

Questions that move
a review forward.

Clarify evidence
“Is this result based on a stated dimension, a drawing condition, or missing information?”
Check a premise
“Which occupancy or sprinkler assumption is this criterion using?”
Coordinate a response
“Which sheet and detail need to be reconciled before this finding can be resolved?”

Illustrative prompts. Answers depend on the material available in the selected workflow and require review.