How should I structure headings in a long Busabase document?

Use headings as a map, not as decoration. Stay shallow enough that the outline still fits on one screen, and split into another document when a branch becomes its own deliverable.

*Diagram · shallow outline vs when to split*

Practical heading levels

Keep sibling sections at the same level. Do not skip from H2 to H4 just for styling.

When to split into another document

Split when any of these is true:

• A section has its own audience, owner, or update cadence.
• The outline is deeper than ~three levels or longer than people will scroll to navigate.
• You want separate sharing permissions or Change Requests.
• The section is reused from multiple places (then it deserves its own doc and links).

Keep as nested headings when the parts are only meaningful inside this narrative (e.g. steps 1–5 of one procedure).

How to keep structure clear as it grows

1. Write the H2 list first (table of contents).
2. Add H3 only where a section has distinct sub-tasks.
3. Put tiny tips in bullets under H3, not new heading levels.
4. Link out to deep-dive docs instead of pasting them under H4.
5. After big edits, re-read only the outline: every H2 should still match the title’s promise.

How to verify

• Someone new can navigate from headings alone.
• No heading is a full paragraph; no section hides a second topic under a vague title.
• Related deep content opens as its own document with a clear back-link.

Boundaries

• Agents drafting long docs: ask them to propose the H2 outline for approval before filling sections.
• “Notes” that are really decisions belong in a Decision log Base or a short linked doc—not endless H4s.
• Formatting bold lines are not headings; use real heading styles so outlines and exports stay consistent.

If you share the rough section list, we can mark which ones should become linked docs.