Drawing
Add context without obscuring the drawing
Use concise annotations to explain information that geometry, hatches, and line hierarchy cannot communicate alone.
Give every annotation a purpose
An annotation should answer a likely reader question. If it repeats obvious geometry or established graphic conventions, it may add noise rather than clarity.
- Identify an element or condition that would otherwise be ambiguous.
- State a requirement that is not encoded in the visible geometry.
- Connect a note clearly to the part of the drawing it describes.
- Use consistent terminology across related views.
Protect the reading order
- 01
Establish the drawing hierarchy
Finish the main line and hatch decisions before placing detailed notes.
- 02
Place high-priority information first
Reserve the clearest positions for annotations that affect interpretation.
- 03
Keep references unambiguous
Make the relationship between a note and its target easy to follow.
- 04
Review at reading size
Check spacing, contrast, and overlap without relying on a highly zoomed view.
Write for scanning
- Lead with the identifying term or action.
- Prefer one clear instruction over several compressed ideas.
- Use the same name for the same object throughout the drawing set.
- Avoid unexplained abbreviations unless they are an agreed project convention.
Review annotations after model changes
When a source section changes, an annotation can remain readable while becoming inaccurate or pointing to the wrong context. Review meaning and placement, not only whether the text is still visible.