How to use the Drawing Conventions
Identify the project information protocol, regional context, consultant requirements and the drawing or model outputs on which each convention must remain legible.
The workspace starts blank. Load example temporarily fills the controls with demonstration data; reload or use the tool’s New or reset action, where provided, before entering live information.
- Choose Region, then complete the register Title, Issue, project information protocol and information manager or owner.
- Search the starting library and include only conventions relevant to the project deliverables.
- Set each item to To review, Adopted, Exception or Not applicable and assign a responsible person.
- Record protocol, template, test or review Evidence and document any approved project deviation before saving the register.
Worked examples
These examples explain the set-up, expected output and review needed without changing the tool workspace.
Overhead-line convention
- Set-up
- Select the overhead-element convention, identify the affected plan types and record the office template or plotted test as evidence.
- Result
- The adopted treatment has an owner and a traceable basis for the project issue.
- Review
- Print or publish a representative drawing at the intended scale and confirm it remains distinct from demolition, hidden and center lines.
Consultant symbol conflict
- Set-up
- Mark the shared symbol To review and describe how the architectural and services meanings conflict.
- Result
- The agreed replacement or discipline-specific exception is recorded instead of silently changing one drawing.
- Review
- Coordinate legends, templates and affected issued sheets before marking the item Adopted.
Suggested workflow
Place the tool in a controlled project or practice process rather than treating its output as an isolated verdict.
- Collect applicable office, client, CDE and consultant conventions at project mobilization.
- Resolve conflicts through representative drawing tests and recorded ownership.
- Issue the adopted register with templates and review it when deliverables or information standards change.
Check before saving or issuing
- Every Adopted item has evidence that can be reproduced in the project environment.
- Exceptions state the reason, affected deliverables and approval.
- The register issue matches the templates and legends used for the drawing package.
Common problems
- The register is too long to govern: include only conventions that affect the project and mark deliberate exclusions.
- A status is Adopted without evidence: attach the protocol, template reference or plotted test used to approve it.
- A convention works on screen but not in print: test the actual sheet scale, lineweight table and output process.
Output
A governed drawing convention register with provenance and conflict checks.
Professional boundary
Coordinate conventions with client, consultant, statutory and CDE requirements rather than assuming one office rule is universally applicable.