Updates

What an update is

An update is a rich-text post you publish into your board's feed. Think of it as the evolution of the monthly investor email — except every board member reads it inside BoardHerald (not in an inbox), every read is tracked, and every edit shows in the history.

Typical cadences we see:

• Monthly investor updates — the core use case. Numbers, wins, asks.
• Weekly founder check-ins — shorter, rhythm-maintaining.
• Ad-hoc material — preparation for a board meeting, a fundraising status note, a hire announcement.

Composing

The editor supports headings, lists, inline emphasis, code, links, and block quotes — plain TipTap-style rich text without the distracting surface area of a full word processor. Paste from Google Docs / Notion and the structure comes across; what doesn't is images and comments, which you can add back from inside the editor.

Drafts autosave every few seconds. You can leave, come back a week later, and pick up where you left off. Only publishing makes the update visible to the board.

Publishing + notifications

Hitting Publish immediately:

1. Makes the update visible to every board member who has accepted the current NDA.
2. Sends a notification — in-app, email, and (if configured) an outbound webhook signed with your tenant's key.
3. Writes an update.published event to the audit log.

Reading

Board members land on an update page with the full content rendered through <BoardProse> — our accessibility-aware prose component. That means they can:

• Swap font family to Atkinson Hyperlegible, Lexend, or OpenDyslexic (from Profile → Accessibility).
• Step up font size (Small → Large → X-Large) and line-height (Normal → Loose → Very Loose).
• Switch the prose background to sepia or high-contrast for long-reading comfort.
• Tap the Listen button to have the update read aloud by a server-rendered neural voice (with browser fallback). Playback supports 1×–2.5× speed, six voices, and progressive streaming — the audio starts before the whole file is generated.

See Accessibility for the full controls and what each option does.

Acknowledgements

Board members click I've read this at the bottom of each update. The author sees an acknowledgement progress ring and the list of who has / hasn't yet confirmed. Acknowledgements are distinct from "opens": we track both, but ack is the one that matters legally and socially.

Unacknowledged? If you've configured the acknowledgement reminder cron (Settings → Reminders), members who haven't acknowledged after N days get an automated nudge email. Editing the update resets the cron — so a late correction doesn't look like an accusation.

Versioning + edit history

Every edit is tracked. The update's right rail shows prior versions; open any one to see exactly what was published when, and diff it against the current state. Members who had already acknowledged a prior version see a "re-acknowledge" prompt if the update has materially changed — you configure what counts as material in Settings → Updates.

Agent access

Any agent with the updates:read scope can list recent updates, fetch their content, and check acknowledgement state. Add updates:write and the agent can draft and publish on your behalf. See Agents — Capabilities for the full persona bundles.