Advisory Board Software for Advice Without Fiduciary Confusion
Target keyword: advisory board software
Intent: Commercial / category
Last updated: 2026-10-07
Reading time: ~8 minutes
The job to be done
Advisory boards create enormous value — and enormous confusion — when they start to look like fiduciary boards. Advisors get “board” in their title, receive packs, debate strategy, and sometimes believe they voted. Founders blur lines. Investors ask who actually has authority. Counsel winces.
In Prepared, Advisory is a board type you pick at onboarding. It keeps the same agenda, pack, and decision record as every other board, and changes the wording around it so the body reads as what it is: advice to management, not board approval.
Why advisory boards break ordinary board portals
Most board software assumes directors, quorum, motions, and votes. Force advisors into that mold and you get:
- Votes that read like approvals and imply authority advisors do not have.
- Liability confusion about who owes fiduciary duties.
- Observer / advisor / director role soup on one board.
- Minutes that read like corporate board minutes for a body that cannot bind the company.
- Onboarding friction that kills the informal value of advice.
Advisory board software should make the non-fiduciary nature hard to miss, in the app and in the wording of the record.
Who sees what
Advisory boards use the same access model as every Prepared board. Confidentiality levels (open, board, committee, executive session, counsel), per-document grants, and per-recipient magic links that show the recipient's email as a watermark and that you can expire or revoke (there is no device-based access control today). Executive-session materials are hidden from the CEO, the Counsel role, and observers by default, and Executive session and Counsel documents never appear in a magic-link pack view. Observers can read the board book but never vote, certify, or sign, and never count toward quorum.
How this maps to Prepared today
| What an advisory body needs | What Prepared actually does |
|---|---|
| A board set up as non-fiduciary | Pick Advisory at onboarding, or apply the Advisory board preset under Settings → Board type preset (Admin, Secretary, Chair, or Owner; the change is written to the audit log). The preset counts quorum against members in office, counts recused members toward quorum, does not require seconds, does not require unanimity for written consent, and uses a 5-day pack lead time. |
| A cue nobody can miss | Every in-app page for an Advisory board shows the banner “Advisory board — recommendations only; not a fiduciary governing body”, and Settings shows a Non-fiduciary badge. The banner is hidden when you print, and it does not appear on magic-link pack views, uploaded files, or exports, so screenshots of those carry no advisory label. |
| Recommendations, not votes | On a decision page the Votes card is titled Recommendations, Open vote becomes Open recommendation balloting, and the written-consent card is titled Advisory written recommendation. The underlying flow is the same one fiduciary boards use: frozen motion text, roll call or voice, and the same attendance-quorum gate. Prepared relabels balloting on Advisory boards; it does not block it. |
| An agenda | Advisory boards get no default agenda template; pick one when you create the meeting or build the agenda yourself. |
| Annual dates | Two calendar milestones: an annual advisory recommendations review (June 15) and advisor COI / independence attestations (January 31). Milestones have no owner field, so create an action item when someone must own a deadline. |
| Follow-ups owned by management | Ordinary action items with an owner and due date. Nothing marks them as management commitments rather than board actions; say so in the title or note. |
| Advisor conflicts | The same COI disclosure and recusal flow as other boards. The January 31 milestone is a reminder date, not a separate advisor attestation workflow. |
| Records | Chair, Admin, or Owner can download the board's JSON archive from Trust and a full-record ZIP at /app/export. Both are document metadata only; file bodies are not in the export. Drafted minutes and exports do not add advisory wording, so put “advisory, non-binding” in the minutes text yourself. |
Guide: /guides/how-boards-make-decisions.
Stated limits
- There is no separate Advisor Workspace product, edition, or add-on; Advisory is a board type preset with defaults and relabeled wording.
- There is no per-person “advisor” or “non-voting” badge. To keep someone from voting, give them the Observer role.
- There is no “advice not decision” watermark on documents or packs; the only watermark is the recipient's email on a magic-link pack view.
- An Advisory board is its own board. It cannot be attached to a fiduciary board, and there is no way to share selected fiduciary-board materials into it; upload the excerpt to the advisory board yourself.
- There is no one-click path that converts an advisor into a fiduciary director. Invite them to the fiduciary board as a Director when the seat is real.
- Sign-in today is email and password; passkeys, SSO, and SCIM are not production-live. See /facts.
- Labels and banners describe the body in Prepared; they do not decide whether anyone owes fiduciary duties. Not legal advice.
Jobs to be done
Founders and CEOs
Gather advice from operators, domain experts, and customers without creating a shadow board that thinks it hired or fired you. Run the advisory circle as its own board in Prepared so it never shares a decision log with the fiduciary board.
Advisors
Know exactly what is being asked: react, challenge, introduce, or review — not “approve.” The decision page says Recommendations, and the banner says the body is non-fiduciary.
Fiduciary board and counsel
Advisory sessions live on a separate board, carry the recommendations-only banner in the app, and use recommendation wording on decision pages. When an advisor should join the fiduciary board, that is an explicit invite to a different board.
Chief of staff / board ops
Stand up an advisory circle with the Advisory preset, its two calendar dates, and the same pack and action tools you already use.
Advice versus decision — a bright line
| Advisory body | Fiduciary board |
|---|---|
| Advice, challenge, network | Care and loyalty duties |
| Recommendation balloting (relabeled; same quorum math) | Quorum, motions, resolutions |
| Recommendations-only banner in the app | Decision Briefs and recorded votes |
| Management owns follow-ups | Board actions and resolutions bind |
The banner and wording keep the line visible in the app; the advisory charter and how you write minutes keep it visible everywhere else. The same philosophy shows up in LPAC versus IC distinctions in our capital-structure research: never imply a consent or advisory body is a corporate fiduciary board.
Where advisory boards show up
- Venture-backed startups testing domain experts before offering a board seat
- Private companies running customer or technical advisory councils
- Nonprofits assembling fundraising or program advisors — distinct from the fiduciary nonprofit board
- Hospitals and universities with advisory councils attached to operating units (confidentiality still matters)
Practical hygiene for advisory programs
- Charters state non-fiduciary status in plain language
- The board uses the Advisory board type so the banner shows
- Minutes and recommendation text say “advisory, non-binding” in words, since printouts and exports carry no banner
- Compensation / equity advisor agreements tracked in your own records
- Conflicts disclosed when advisors have competitive or vendor interests
- Moving to director is an explicit invite to the fiduciary board, with onboarding
Try the closest demo
- Harbor Advisors (Advisory board) —
a sample board (see /sample-decision)/password123— one seeded recommendation decision so you can see the banner and the Recommendations wording.
Or /#try-a-board.