Exit
Take your record with you
A board should be able to leave with its full decision record. Lock-in comes from the quality of that record, not from captivity. This page says what you can take, in what format, and what is not included. Matches what we publish on /facts.
What you can take
A signed-in Owner, Admin, or Chair of the organization downloads one ZIP from /app/export. The ZIP is format prepared-board-record-export-v1. Every row is read from that organization's database at download time. No other organization's rows are included.
- boards — Each board of the organization included in this export, with its procedure settings.
- people — Board memberships: who sits on each board, their role, voting status, and term.
- committees — Committees of each board and their charters.
- meetings — Every meeting: when, status, pack status, quorum flag, and minutes status. Minutes text is in record.json and in the minutes/ folder.
- attendance — Who was marked Present, Remote, or Absent at each meeting.
- agenda_items — Agenda items per meeting, in order, including consent-agenda flags.
- decisions — The decision record: status, outcome, rationale, resolution, closure evidence, revisit date, and the supersede chain.
- motions — Motions made on decisions, with mover and seconder.
- vote_sessions — Each vote held on a decision: method, result, tally, and certification time.
- votes — Every individual ballot: who voted, how, and when.
- consent_signatures — Signatures on unanimous written consents.
- recusals — Decision-specific conflicts and recusals (DecisionConflict).
- conflict_disclosures — Standing conflict-of-interest disclosures and annual attestations filed with each board.
- actions — Action items: owner, due date, status, evidence, and formal close.
- monitors — Outcome monitors on decisions: what to measure, target, due date, last report. (Decision revisit dates are in decisions.revisitAt.)
- documents — Document metadata only (title, file name, type, confidentiality, links). File bodies are not in this export.
- calendar — Board calendar milestones (filing reminders, AGM, budget, evaluation). Reminders only — not proof anything was filed.
- activity_log — The audit / activity log: who did what, to which record, and when. Metadata is allowlisted for export (no token hashes or raw tokens).
Format
README.md— plain-words schema, export timestamp, organization name, and row counts.manifest.json— the same information for software (schema, counts, column list).record.json— every table in one JSON file. This is the complete copy.csv/<table>.csv— one CSV per table (UTF-8). A few long-text columns stay in record.json and minutes only.minutes/<meeting>.md— one Markdown file per meeting whose minutes text is stored.diligence_snapshot.md— diligence_snapshot.md — same markdown as Diligence snapshot on /app/diligence (Copy snapshot for your agent), included when the exporter's role can open diligence (Chair, Admin, or Owner — the same roles that can download this ZIP). One file per exported board. Fundraising / investor leave-behind. Not a securities disclosure, not legal advice.board_proof.md— board_proof.md — same markdown as Board decision quality proof on /app/board-proof (Copy proof for your agent), included when the exporter's role can open board-proof (Chair, Admin, or Owner — the same roles that can download this ZIP). One file per exported board. Investor / LP leave-behind. Not a securities disclosure, not legal advice.
The download is recorded in that board's Activity log as “Export completed.” Nothing is emailed. There is no live sync, no live import into another product, and no live integration that pushes this file anywhere.
Not included
- Document file bodies. The documents table lists every document's metadata and says whether a body is stored (hasContent, contentLength). Download any document you need from Documents in the app before you leave.
- The counsel privilege-safe note on decisions (privilegeSafeNote). It is left out of every export on purpose.
- Board evaluation responses. They are anonymous by design and are not exported per person.
- Pre-meeting questions and answers. The Trust Center archive (JSON) carries shared Q&A snippets.
- Pack read receipts, document view logs, notifications, and the skills matrix.
- Invitations, pack magic links, integration connections, SSO / SCIM / passkey settings, passwords, and sessions. Secrets and access tokens are never exported.
- Audit / activity-log metadata is allowlisted per action before export. Share-link token hashes, raw link tokens, passwords, and secret-material field names are never included. Meeting video join links are reduced to their host (the link itself is the way into the meeting), and passcode / token / signature query parameters and user:password in any other URL are redacted. Sponsor-share rows keep sponsor name, email label, scope, expiry, and token prefix only — never the share token or its hash. Sponsor share table rows themselves are not exported.
- Meeting join links and the legacy attendeesJson field (the attendance table is the record of who was there).
- This export's own activity entry. It is written right after the file is built, so it appears in Activity and in your next export.
Who can download
Only an active Owner, Admin, or Chair of the signed-in organization. Directors, secretaries, counsel, observers, and guests cannot download the full record. The Trust Center still offers a smaller single-board JSON archive for the same roles.
Related: /facts, /trust, /app/export.