How to use the Drawing Glossary
Collect the abbreviations actually used in the current drawing or model issue and identify discipline conflicts before importing starter terms.
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.
- Set Glossary title, Region / terminology, project reference, issue and owner or checker.
- Search the Starter library and add only relevant terms, or use + Entry for a project-specific abbreviation.
- Complete Code, Meaning, Project context and any Caution or clarification, then set Draft, Adopted or Superseded status.
- Resolve duplicate codes with different meanings and incomplete entries before saving or producing the PDF.
Worked examples
These examples explain the set-up, expected output and review needed without changing the tool workspace.
Discipline conflict
- Set-up
- Add one code used differently by architecture and building services, recording both contexts and the ambiguity.
- Result
- The health check flags the conflict until the team adopts one meaning or replaces one code.
- Review
- Update the affected legends, models and sheets before marking the agreed term Adopted.
Issue-specific drawing legend
- Set-up
- Add only abbreviations present in the coordinated package and record where less familiar terms appear.
- Result
- The glossary remains short enough to review and can be issued with the drawing set.
- Review
- Search the final output for undefined codes and remove unused starter entries.
Suggested workflow
Place the tool in a controlled project or practice process rather than treating its output as an isolated verdict.
- Extract terms from the deliverable rather than beginning with a universal dictionary.
- Resolve ambiguous codes with every affected discipline and record the agreed context.
- Issue the glossary with the package and supersede terms deliberately when conventions change.
Check before saving or issuing
- Each code has one unambiguous meaning within its stated project context.
- Adopted entries are used consistently in the actual issue.
- Superseded terms remain identifiable without appearing current.
Common problems
- Conflict count remains above zero: search for duplicate normalized codes and compare their meanings.
- Glossary is full of unused terms: remove starter entries that do not appear in the issue.
- A term is clear to one discipline only: expand Project context or replace it with plain language.
Output
A controlled drawing glossary with duplicate, conflict and completeness checks.
Professional boundary
Meanings vary between practices and disciplines; agree ambiguous terms with the project team before relying on them.