Does this page name a winning or losing board-portal vendor?

No. It compares Prepared Board to legacy board portals as a category. Every Legacy cell is labeled typical category practice (verify with vendor). No commercial vendor is named as a loser.

Where do Prepared Board claims on this page come from?

Only from /facts and /agent-facts.json (doesToday and notLive). Strong / Partial / Not live ratings match what is live in product today. Every not-live item is listed verbatim.

Is Prepared Board claiming to beat every legacy portal on every criterion?

No. Document distribution and meetings are the historical strength of the category. Prepared's thesis is decision-record depth, citeable close, agent surfaces, investor proof share, and a full-record export on every tier (documents as metadata) — with identity still not production-live.

How should I compare a specific named portal?

Use /compare/how-to-choose-a-board-portal for evaluation criteria, then verify that vendor's trust center and product under NDA. This page will not invent their feature matrix.

Can we leave Prepared Board later?

Yes. An Owner, Admin, or Chair downloads the full board record as a ZIP from /app/export. /leaving-prepared lists what is and is not included. Lock-in should be decision quality, not captivity.

Category comparison

Prepared Board vs legacy board portals

Legacy board portals optimized for secure document distribution and meetings. Prepared Board is a decision operating system: prepare → decide with legitimacy → close with evidence → monitor follow-through → export the record (documents as metadata). This page compares categories, not a named vendor as a loser. Every Legacy cell is typical category practice (verify with vendor) — never an invented competitor feature quote.

Prepared Board ratings (Strong / Partial / Not live) and quoted excerpts come only from /facts and /agent-facts.json (as of 2026-10-10). No commercial vendor is named.

How to read this matrix

Strong — live in product today per agent-facts.json doesToday.
Partial — live with an honest limit (for example quorum is a seat count, not a legal opinion).
Not live — listed in notLive; do not upgrade from brochure language.
Legacy column never asserts a specific vendor's feature matrix. Verify under NDA.

Criteria matrix

15 criteria. Live investor and agent surfaces (full-record export, agent collaboration, sponsor proof share, portfolio digest, reserved matters, minutes-from-record) appear only because they are live today.

Criterion	Legacy board portals	Prepared Board
Decision-record depth Is a closed decision a first-class object with outcome, vote, recusal, and evidence — or mainly a document in a binder?	Typical category practice (verify with vendor): document repository + meetings focus; decision-record depth varies — some products stop at minutes and attachments rather than a per-decision object with vote, recusal, and closure evidence linked together.	Strong “A signed-in board can run meetings, decisions, votes, motions, a consent agenda, minutes” “the latest closed decision with evidence on the decision record”
Who voted, and who recused Can a successor chair open one decision and see named ballots or a certified tally, plus who recused?	Typical category practice (verify with vendor): votes and recusals are often captured in minutes text or a disclosure note; tying a named RECUSED state to a specific decision object varies by product.	Strong “If that decision stores Decision.outcome ADOPTED or DEFEATED (the same tokens as a certified VoteSession.result), the closed-record line says the vote was adopted or defeated.” “If that decision has a conflict still stored as RECUSED, the closed-record line names who recused.”
Evidence at close When the vote closes, is the evidence the board acted on attached to that decision — and is missing evidence said out loud?	Typical category practice (verify with vendor): evidence usually lives as pack attachments or shared files; whether close requires (or surfaces) missing closure evidence on the decision itself varies.	Strong “It lists each closed decision with its resolution text, its outcome monitors (target, metric, status, due date, and last report), its revisit date, its follow-up actions done, open, or overdue, and its closure evidence, and says so when any of these is missing.”
Quorum labeling Is quorum a seat count from attendance against board settings — labeled as a count, not a legal opinion?	Typical category practice (verify with vendor): attendance and quorum tools are common; whether the product refuses to present a statutory or ASPA-style opinion varies — verify labeling with the vendor.	Partial “On a meeting with attendance marked, the meeting header shows whether the seat count was met: Present or Remote versus the seats required by that board's quorum settings.” “The line says this is a count, not a legal opinion.” Not live: ASPA is not implemented. Quorum is a seat count from board settings plus Present or Remote attendance. It is not a statutory opinion, and there is no ASPA written-consent engine.
Document repository and board pack Can directors open one published pack version, and can a late change be distinguished from what was sealed?	Typical category practice (verify with vendor): secure document distribution and meeting packs are the historical strength of legacy board portals; depth of seal, watermark, and version control varies.	Strong “A published pack can be opened from a public pack link without an account.” “the last sealed meeting, the current pack” agent-facts.json does not claim a per-pack version history or a diff between pack versions, so this page does not either.
Follow-through after the vote After the gavel, do actions and outcome monitors stay on the decision — without inventing a 'target met' score?	Typical category practice (verify with vendor): post-meeting action lists are common; outcome monitors tied to a closed decision with overdue/due-soon surfacing and an explicit refusal to invent 'target met' scores vary — verify with the vendor.	Strong “It does not judge whether a target was met, because no stored field records that; it shows the last report as written.” “When an open outcome monitor is overdue or due within 30 days, the signed-in home names the decision title and due date”
Full-record export / switching cost If you leave, can you take a usable full-record archive without a hostage negotiation?	Typical category practice (verify with vendor): export and lock-in vary widely — some portals offer archives; others make exit slow or incomplete. Always verify what leaves with you and what stays behind.	Strong “An Owner, Admin, or Chair can download the organization's full board record as a ZIP from /app/export” “Document bodies, evaluation responses, secrets, pack/sponsor link tokens and token hashes, and other organizations' rows are not included;”
Agent collaboration Can a director or investor paste grounded board context into an outside agent — without the product inventing an agent identity or calling the agent?	Typical category practice (verify with vendor): agent surfaces (plain-text /agent URLs, Copy for your agent briefings grounded in board rows, /llms.txt and /facts) are rare in the legacy portal category — verify any AI claims with the vendor; brochure 'AI' is not the same as citeable context.	Strong “A published pack can be fetched as plain-text markdown for outside agents at /pack/{token}/agent” “Prepared does not call any AI model or push data to agents. A director can also connect their own AI assistant to the MCP server / agent API (read-only plus drafting questions; OAuth sign-in or a personal access token) when the chair allows it (/agents/connect).”
Observer privilege withholding Can an investor observer read the book without seeing privileged or recused material — enforced on the server, not only hidden in the UI?	Typical category practice (verify with vendor): observer or guest seats exist in many portals; whether privileged / executive-session / recused material is withheld server-side (including on agent and export paths) varies — verify with the vendor.	Strong “Investor observers hold an OBSERVER membership: they read the board book, sealed packs, decisions, and outcomes, but cannot vote, certify, or sign, and are never counted toward quorum.” “Privileged and executive-session materials, DocumentACL denials, executive-session agenda items, and items they are RECUSED from are withheld server-side”
Sponsor proof share Can a chair grant a named investor a revocable, expiring, audited link to decision-quality proof — without a board seat or the board book?	Typical category practice (verify with vendor): sharing a board book or PDF with an investor is common; a chair-granted, revocable, expiring, proof-only share that withholds privileged material and is not a board seat is uncommon — verify any 'investor portal' claim with the vendor.	Strong “A Chair, Admin, or Owner can grant a named sponsor (investor, LP, or parent organization) a chair-granted sponsor proof share from /app/board-proof: a revocable, expiring (default 90 days, max 365), scoped (proof only, or proof plus outcomes), audited read-only link to that board's Board decision quality proof.” “The sponsor never receives the board book, privileged or executive-session material, or individual votes”
Portfolio / cross-board digest If you sit on multiple boards, can you see decisions, monitors, and needs-attention across only those boards — without inventing outcome scores?	Typical category practice (verify with vendor): multi-entity or fund-of-boards views exist in some enterprise suites; membership-scoped digests with ranked needs-attention and an explicit no-score / no-target-met rule vary — verify with the vendor.	Strong “On the same /app/portfolio page, a cross-board decision digest covers only boards where the member holds an ACTIVE membership, for the last 30 days, the last 90 days, or since each board's last meeting.” “It does not compute a cross-board outcome score or say a target was met.”
Reserved matters / protective provisions Can a venture board tag financing or option-pool decisions that typically need preferred consent, and soft-cue when consent evidence is missing — without blocking the vote or pretending to read the IRA?	Typical category practice (verify with vendor): corporate secretarial workflows may track approvals; a soft reserved-matters tag with preferred-consent evidence cues that refuse to block the vote or invent IRA counsel varies — verify with the vendor.	Strong “Reserved matters / protective provisions tracker: a Chair, Secretary, Admin, or Owner maintains a reserved-matters list under Settings” “Board Go and the decision page show a soft cue — "Reserved matter tagged — preferred consent recorded?" — that does not block open vote or close.” agent-facts.json says Prepared does not read the IRA or decide whether consent is required; this page does not claim otherwise.
Minutes from the record Can minutes be drafted from attendance, quorum count, motions, votes, and recusals already on the record — with blanks for gaps, and without generative AI inventing text?	Typical category practice (verify with vendor): minutes tools and AI-assisted drafts vary; deterministic composition only from recorded rows with [fill in] gaps and an explicit not-AI rule is uncommon — verify any 'AI minutes' claim with the vendor.	Strong “On a meeting's minutes page, a Chair, Secretary, Admin, or Owner can click Draft from the record to compose an editable minutes draft only from recorded rows” “Missing fields become [fill in] placeholders; nothing is invented and the draft is not AI-written.”
Identity (SSO, SCIM, passkeys) Are SSO, directory sync, and passkeys production-live in the environment you will run — or only wired behind flags?	Typical category practice (verify with vendor): enterprise portals often market SSO and directory sync; what is actually enabled in your tenant (and whether passkeys work there) must be verified with the vendor — brochure copy is not a handshake.	Not live “Demo sign-in is email and password through NextAuth credentials.” Not live: Passkey sign-in (WebAuthn) is not live on preparedboard.com. It is built but switched off until it has been tested end to end. Not live: Enterprise single sign-on (SAML and OIDC) is built but not live on preparedboard.com. It turns on for an organization only once its identity provider is connected and its email domain is mapped. It signs people in to the board seats they already hold, never grants admin rights, and every sign-in is logged. Not live: SCIM directory sync is not live on preparedboard.com. It is built but switched off, so members are added by invitation. Not live: The onboarding checklist row labeled portal access verified (MFA) is a checkbox the board marks; it does not inspect accounts. Two-factor sign-in itself is live (authenticator app, optional per member, can be required per board by the chair).
Assurance packaging (independent audit, BYOK) Is an independent security audit report or BYOK actually available today — or a roadmap target?	Typical category practice (verify with vendor): many portals publish a trust center; whether an independent audit report or BYOK/CMEK is available to you must be verified under NDA with the vendor — never invent certification from a brochure.	Not live Prepared Board does not claim an independent security audit or live BYOK from marketing copy; see /facts. Not live: No independent security audit or certification yet. Not live: Customer-managed encryption keys (BYOK) are not live.

What is not live in Prepared Board

Verbatim from agent-facts.json notLive. Weigh these before you switch — especially identity and assurance.

Passkey sign-in (WebAuthn) is not live on preparedboard.com. It is built but switched off until it has been tested end to end.
Enterprise single sign-on (SAML and OIDC) is built but not live on preparedboard.com. It turns on for an organization only once its identity provider is connected and its email domain is mapped. It signs people in to the board seats they already hold, never grants admin rights, and every sign-in is logged.
SCIM directory sync is not live on preparedboard.com. It is built but switched off, so members are added by invitation.
Stripe billing is built but not live. Checkout, the customer portal, signed webhooks, and plan gating turn on only once production Stripe credentials are connected; until then billing pages say Billing not live yet — contact sales, plans are not enforced, and nothing is charged. Seat meters are not built.
ASPA is not implemented. Quorum is a seat count from board settings plus Present or Remote attendance. It is not a statutory opinion, and there is no ASPA written-consent engine.
Prepared does not quote, bind, or broker D&O insurance and is not carrier-connected. /app/do-insurance is a board-declared binder/policy-date tracker with an in-app board-review attestation only — not an insurance application, not coverage advice, and not a verified coverage amount. An annual director questionnaire tracker at /app/questionnaires can record board-declared checklist attestations in-app.
No bank, treasury, or payment account is connected. Prepared does not move money or show a live balance.
There is no live filing feed to the IRS, a Secretary of State, county registry, or town clerk, and no Form 990 or state-charity e-file. /app/filings-window is a board-declared board-review window with an in-app attestation that the board reviewed a board copy — not IRS or state acceptance. Calendar filing rows remain reminders. Documents in a pack are board copies, not proof a filing was accepted.
Outbound email is not live in the demo. Delivery is reported only after a configured provider (Resend or Postmark) returns HTTP 2xx. Without those credentials, no send is claimed.
There is no Clear evaluation response action. A director can Retract a response. Clearing is not a product path.
The onboarding checklist row labeled portal access verified (MFA) is a checkbox the board marks; it does not inspect accounts. Two-factor sign-in itself is live (authenticator app, optional per member, can be required per board by the chair).
Customer-managed encryption keys (BYOK) are not live.
No independent security audit or certification yet.
Prepared does not auto-delete or auto-purge documents. /app/document-retention is a board-declared category schedule with an in-app Adopted / board-reviewed attestation only — template aid, not legal counsel, and not a compliance determination.
A paid recruiter tier (higher contact limits / commercial shortlists) is planned, not live. Billing checkout is built but not live until production credentials are connected.
Newsletter confirmation and issue send are not live — no email provider is connected. Signups stay PENDING; Approved issues are not emailed.
Uploaded files are not antivirus-scanned. PDFs pass strict structural validation (no encryption, JavaScript, embedded files, launch or form-submit actions) before storage; that is not a malware scan. Upload only files from sources you trust.
Database point-in-time restore covers the last 6 hours only; there is no longer-term or off-provider database backup yet, and uploaded files have no point-in-time restore.

Questions

Does this page name a winning or losing board-portal vendor?: No. It compares Prepared Board to legacy board portals as a category. Every Legacy cell is labeled typical category practice (verify with vendor). No commercial vendor is named as a loser.
Where do Prepared Board claims on this page come from?: Only from /facts and /agent-facts.json (doesToday and notLive). Strong / Partial / Not live ratings match what is live in product today. Every not-live item is listed verbatim.
Is Prepared Board claiming to beat every legacy portal on every criterion?: No. Document distribution and meetings are the historical strength of the category. Prepared's thesis is decision-record depth, citeable close, agent surfaces, investor proof share, and a full-record export on every tier (documents as metadata) — with identity still not production-live.
How should I compare a specific named portal?: Use /compare/how-to-choose-a-board-portal for evaluation criteria, then verify that vendor's trust center and product under NDA. This page will not invent their feature matrix.
Can we leave Prepared Board later?: Yes. An Owner, Admin, or Chair downloads the full board record as a ZIP from /app/export. /leaving-prepared lists what is and is not included. Lock-in should be decision quality, not captivity.

What to do next

Evaluation criteria without a matrix: How to choose a board portal
Alternatives boards actually use (email, spreadsheet, paper): /compare
Investor require pack: /for/investors
List prices (billing checkout not live): /pricing
Leave with your record: /app/export · Leaving Prepared
Try a board like yours — five seeded demos, no password typed.