Every query should reference a drawing, revision and location; its answer must not automatically alter the document released for execution.
Index
A technical answer sent through messaging loses context when nobody can identify which drawing detail prompted the question.
The rule that changes the scope
Every query should reference a drawing, revision and location; its answer must not automatically alter the document released for execution.
Project tools may support comments; a custom portal is justified when questions cross organizations with different response responsibilities.
One query may receive an answer without changing the design; another may require a formal drawing revision. Those paths must be distinguished during procurement. The execution owner should find valid guidance through the referenced element rather than search the entire conversation. Include withdrawal of an incorrect answer: superseded guidance remains in history but no longer appears as the current instruction for the team performing the work.
Specify operational deliverables
- Capture the drawing excerpt and technical question without relying on filenames.
- Distinguish an answer received, clarification requested and conclusion accepted by the responsible team.
- Connect any drawing revision to the question that initiated the change.
Test the exception before acceptance
In a hypothetical scenario, the author answers using a later revision; the team must notice that difference before applying the instruction on site.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Share an anonymized question, the referenced drawing and the current response sequence.