> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/cadd/note-cadd.md).

# Leader Note

A **Leader Note** is a text annotation with a leader arrow pointing from the text to the feature being annotated. Use it for callouts that need to attach to specific geometry — material callouts on a section, dimension references, construction notes pointing to specific locations, revision callouts.

For free-floating text without an arrow, use Text instead.

## Content

**Text:** The note content. Multi-line is supported for longer callouts.

**Size:** Font size in real units.

**Arrow Size:** Size of the leader arrow head. Larger arrows for top-of-sheet callouts; smaller for dense detail areas.

**Text Align V:** Vertical alignment of the text relative to its anchor point: Top, Middle, or Bottom.

## Placement

A leader note has two anchor points — the text position and the leader's tip (where the arrow points). Drag either to reposition.

For multi-segment leaders (where the arrow needs to bend around other geometry), drag the leader's intermediate handle to add a kink.

## Styling

**Color / Thickness:** Color and weight of the leader line and arrow.

**Level:** Layer assignment.

## Notes

For material callouts (e.g., `Class A Concrete`, `ASTM A572 Gr. 50`), keep the text concise — long material specs belong in a notes block, not on a leader.

For revision callouts referencing a Revision Cloud, use a small Note inside the cloud or with its leader pointing at the revised area, plus a revision-block reference somewhere on the sheet.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openbrim.org/templates/cadd/note-cadd.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.