Multi-Entity Board Software for Parent, Subsidiary & JV Boards

Target keyword: multi-entity board software
Intent: Commercial / category
Last updated: 2026-10-07
Reading time: ~11 minutes

---

The job to be done

Holding companies, operating subsidiaries, and joint ventures do not share one fiduciary board — even when the same people sit in every room. Duties run to each entity. Parent strategy, subsidiary creditor and minority protections, and JV parity rules collide in the same week. Packs leak across walls. Reserved matters get rubber-stamped. Dual-hatted directors vote without a recorded conflict process.

Prepared Board has no separate multi-entity product or board type: you run each entity as its own board inside one organization, with packs, documents, and minutes scoped to the board that owes the duty, a chair-maintained reserved-matters list that decisions can be tagged to, written-consent and related-party approval templates, and recorded conflicts and recusals on each decision. There are no intercompany-specific templates and no dedicated dual-hat workflow today; you use the general conflict, recusal, and related-party records. The goal is alignment without leakage — and fiduciary lines you can defend in diligence, insolvency, or partner dispute.

---

Who feels this pain most acutely

• Corporate secretaries and group GC running holdco plus three to twenty sub boards with overlapping directors
• Subsidiary chairs and local CEOs who need parent alignment without every pack becoming a group data dump
• JV co-chairs and partner nominees living inside reserved-matter matrices, parity votes, and deadlock procedures
• PE / private holdco operators who outgrew “one Drive folder per portco” when intercompany and SHA gates showed up
• Counsel asked to prove independent subsidiary process after the fact — when interests diverged and nobody recorded it

If your primary job is Fortune-scale entity GRC, ESG, and Diligent One–class enterprise graphs, say that out loud — that is a different buying motion. Prepared is for boards that need entity-clean decision records without a multi-year portal replacement.

---

Why multi-entity boards outgrow email, Drive, and a single portal tenancy

A single shared board portal tenancy with weak entity tags is how packs cross walls. Common failure modes:

1. Parent directors receive the full subsidiary book — including local HR, customer pricing, or minority-sensitive materials they did not need for the reserved-matter vote.
2. Subsidiary directors see parent M&A or financing drafts before the sub board has a role — or when antitrust / information-sharing rules say they should not.
3. Reserved matters (SHA, JV agreement, credit agreement) live in a PDF nobody maps to the agenda — so a capital call or related-party contract sails through without the right consent path.
4. Dual-hat directors (parent nominee on the sub; partner A designee on the JV) vote without a contemporaneous conflict / recusal record when interests diverge.
5. Intercompany dividends, guarantees, and service agreements lack resolutions recorded on the right entity's board — diligence and insolvency counsel reconstruct theater from email.

In Prepared the entity boundary is the board: memberships, packs, documents, decisions, and minutes belong to one board. There is no entity object above the board, no parent/subsidiary link between boards, and no ownership or consolidation graph today.

---

What Prepared Board includes for multi-entity, subsidiary & JV boards

How this maps to Prepared today

Stated limits

• There is no multi-entity board type or preset, no entity or ownership record above the board, and no consolidation, cap-table, or org-chart graph between boards.
• There are no parent-consent, two-JV-parent, or lender-notice consent types; Prepared does not read your SHA, JV, or credit agreement and does not decide whether a consent is legally required.
• There is no dual-hat or nominee field on the membership; record the dual hat in the COI attestation and the member's notes.
• There is no parity-vote mode, casting-vote rule per parent, or deadlock record; record deadlock procedures as reserved matters and decisions.
• There is no cross-board pack, shared document library, or one-click "share this to the parent board"; a document lives on one board.
• Pack magic links are per recipient, watermarked with the recipient's email, expire, and can be revoked by the chair. Offboarding also revokes that person's outstanding magic-link pack links on that board.
• Confidentiality levels and the privileged flag control who sees a document in Prepared; they do not create legal privilege or satisfy antitrust information-sharing rules.
• Nothing is formatted for statutory registers, local filings, or transfer-pricing files, and Prepared files nothing with any registry.
• SSO is not live today. Not legal advice.

Reserved matters: from PDF appendix to a consent cue on the decision

Reserved matters are the contract that says this board cannot decide alone. Typical sources: shareholders’ agreements, JV agreements, investor rights agreements, and credit agreements. Examples include:

• Equity issuances, option pools, and changes to constitutional documents
• Material M&A, asset sales, and related-party / affiliate contracts
• Debt above thresholds, upstream guarantees, and intercompany loans
• Dividends and distributions outside an agreed policy
• CEO hire / fire and material compensation changes
• Business-plan approval, capital calls, and budget deviations (especially in JVs)
• Deadlock, ROFR, shotgun, and exit triggers

How Prepared Board treats them: the chair enters the reserved matters in Settings, each with the consent it needs (preferred investor, majority preferred, or board only), and tags decisions to them. A tagged decision shows a soft cue asking whether the consent was recorded, so you link a written consent or attach labeled evidence. The cue never blocks the vote or close, and Prepared does not decide whether a consent is legally required. There are no parent-consent, two-JV-parent, or lender-notice consent types today; note those in the reserved matter itself.

Wedge workflow: type the reserved matters from the SHA / JV agreement into Settings (Prepared does not read the agreement for you), tag the next reserved Decide item, and attach the consent before the vote.

---

Keeping parent and subsidiary packs apart

Fiduciary duties run to the subsidiary entity. Parent designation does not erase conflicts. Separate boards exist so that:

• Parent board packs carry group strategy, capital structure, and consolidated oversight — without dumping every OpCo customer file into the holdco book.
• Subsidiary packs carry local performance, local CEO evaluation, local compliance, and intercompany asks — without exposing peer-sub competitive detail or premature parent deal drafts.
• Observers and counsel get per-recipient magic links to that board's pack that expire and that the chair can revoke; ending a membership clears that person's per-document grants, but pack links are revoked on the pack, not by offboarding.

Separation comes from separate boards and document grants — not folder theater. A dual-hatted director may sit on both boards; they hold two memberships, receive two packs, and appear in two minute books. Document views are logged per board.

Cross-border groups add transfer-pricing evidence, local statutory directors, and data-residency sensitivity. Keeping each entity on its own board, with its own documents and archive, keeps counsel from reconstructing “which board saw what” from email headers six quarters later.

---

Dual-hat conflicts: nominee loyalty vs entity duty

Dual allegiance is normal in multi-entity structures — and still dangerous when undocumented:

• Parent nominee on a subsidiary facing a dividend, guarantee, or related-party services vote that favors the parent over sub creditors or minorities
• JV partner designees with equal slates approving capital calls, IP licenses, or exclusivity that favors one parent’s downstream business
• Shared executives (group CFO as sub director) evaluating related-party fees they helped design upstream
• Hospital / clinical JVs where nonprofit private-benefit and antitrust information-sharing rules tighten the room

Prepared Board handles this with its general conflict records, not a dual-hat module: the director discloses the dual hat on their annual COI attestation, the recusal is recorded on the decision, the related-party register lists it, and counsel's notes can sit at the Counsel confidentiality level or carry the privileged flag (which controls access in Prepared, not legal privilege). There is no dual-hat field on the membership today. Courts, partners, and insolvency practitioners care about contemporaneous process, not after-the-fact memos.

Common failures we help you avoid: rubber-stamping affiliate contracts with no brief; putting both parents’ commercial teams in the same unrestricted pack; minutes that say “discussion ensued” on a reserved matter; and actions that die in a holdco deck footnote with no OpCo owner.

---

Jobs to be done by seat

Parent / holdco chair and group GC

See reserved-matter consent status across the boards you sit on (counts only, per board). Keep group strategy on the holdco board. Demand Decision Briefs on intercompany and affiliate items. Leave with owned actions on the right entity's board — not a transcript of status across twenty OpCos.

Subsidiary chair, local CEO, and secretary

Publish a local pack with clear asks to the parent when reserved. Protect local HR and commercial detail. Produce minutes that show deliberation for the subsidiary’s interest when it diverges. Download the board's archive for local audits, lenders, and minority stakeholders (document metadata, not file bodies).

JV co-chairs and partner nominees

Agree parity and deadlock procedure in the JV agreement and list them as reserved matters before the room invents process (Prepared has no parity-vote mode). Use per-document grants so one parent's IP and customer data are not opened by the other parent's designees. Document capital calls and related-party services as structured decisions.

Independents and statutory / minority directors

Receive materials you are entitled to — on the entity you serve — without being seated on peer-sub or parent boards. Know when you are the independence valve on a reserved or related-party item.

---

Wedge workflow: multi-entity setup in about fifteen minutes

1. Create the entity boards — holdco, each OpCo or JV as its own board with jurisdiction and cadence.
2. Invite each director to each board they sit on — same people, separate seats; note who is a parent nominee or partner designee on their COI attestation.
3. Enter the SHA / JV reserved matters in Settings — then tag Decide items to them.
4. Keep packs on their own board — parent and sub packs never merge because they live on different boards; restrict sensitive documents further with committee or per-director grants.
5. Start intercompany asks from the written-consent template — dividend, guarantee, shared services, or IP license between meetings.
6. Publish — directors open packs via magic link per board (sign-in today is email + password; passkeys are not production-live). Prep Score gives each meeting a 0–100 readiness number, and read receipts show which directors have opened the pack.

What to aim for: no materials shared with the wrong entity's board; reserved-matter decisions documented with their consent; dual-hat disclosures on file before related-party votes; and a new sub or JV board set up in hours, not quarters. These are goals for your board, not measured Prepared results.

---

Agenda design across the entity graph

Prepared has five agenda item kinds. Use them so the room knows what “good” looks like:

1. Decide — resolution-ready (intercompany contract, dividend, capital call, CEO change, reserved SHA item).
2. Inform — local KPI / compliance with variance narrative, on that entity's board.
3. Discuss — strategy that does not require merging packs across parents.
4. Consent — routine local approvals batched so airtime goes to judgment and reserved matters.
5. Executive — CEO assessment or conflict-sensitive deliberation; executive-session agenda items are withheld from observer and guest seats.

A sample subsidiary quarterly: call to order and minutes; consent; local CEO narrative; financials vs local plan; one intercompany or reserved Decide item with brief and consent; risk / compliance flash; dual-hat conflict check; actions with owners on that entity's board.

Do not confuse group management reporting with subsidiary board packs. Flash packs can be denser operationally for the holdco. The fiduciary pack must support the entity’s decision and record.

---

Compared to folders, single-tenancy portals, and enterprise GRC

We are honest about fit. If you must buy Diligent-class multi-entity + ESG + GRC as a single Fortune vendor, that RFP is not our wedge. If you need parent/sub/JV boards that counsel will defend and directors will actually use every quarter, this is the path.

---

Expansion path

• Private Company — institutional hygiene for a single OpCo board. See private company board software.
• PE portfolio — observer seats, owned actions, and the portfolio view across portcos. See PE portfolio board software.
• JV depth — parity voting modes, a deadlock log, and a clinical quality overlay are not built today; record deadlock procedures as reserved matters and decisions.
• Listed parent — the Public company or Pre-IPO preset, committee charters, the director questionnaire, and the insider-trading policy acknowledgment (an in-app record, not eSign); not a separately billed module.
• Full enterprise graph — consolidation links between entities are not built today; boards sit side by side under one organization.

One operating system and one record as the entity surface grows. On a sale, spin, or partner exit, download that board's archive; you keep your own document files, since exports list them as metadata only.

---

Practical checklist for your next multi-entity cycle

• Each legal entity has its own board record (not one mega-folder)
• Dual-hat directors have separate memberships and conflict disclosures on file
• Reserved matters from SHA / JV / credit docs are listed and tagged on Decide items
• Parent and subsidiary packs live on their own boards — no accidental cross-shares
• Intercompany and affiliate items carry Decision Briefs and resolution text
• Minutes show deliberation for the entity that owes the duty when interests diverge
• You know which export counsel gets: the single-board archive, or the full-record ZIP across every board you chair

If more than two boxes are chronically red, you do not have a “cadence” problem — you have an entity-boundary operating system gap.

---

Related guides and landings

• Conflict of interest policy
• How boards make decisions
• Consent agenda
• Board portal comparison
• Private company board software
• PE portfolio board software