Hospital trusts + ICSs
Multi-committee governance with explicit delegation cascades, chair rotation, and obligation tracking across clinical, financial, and operational portfolios.
← PortikoPreview
01.3 — Quorum
Committee governance,
continuous across chair handovers.
Quorum is the system of record for institutional governance. Schemes of delegation, decisions, minutes, obligation calendars, authority-scope enforcement — built so a new chair inherits institutional context, not a folder of PDFs. Tenancy is institutional-identity (Person, Role, Committee, Membership), not flat workspaces.
- Status
- Preview
- For
- Multi-committee institutions
- Tenancy
- Institutional-identity
- Pricing
- TBD
A — Who Quorum is for
Built for institutions where governance continuity matters.
Quorum is calibrated for organisations that run governance through named committees — where decisions are bound by Terms of Reference, where authority is delegated explicitly, and where the next chair has to be able to pick up where the last one left off.
Large group practices + federations
PCN-level or federation-level governance over multiple constituent practices, with delegated authority and shared committee structures.
Pilot programmes + research consortia
Time-bounded governance arrangements with formal delegation, scheduled obligations, and ratifiable decisions across stakeholder groups.
B — How it works
Four pillars: identity, authority, continuity, discharge.
Quorum is organised around the four things every committee governance system has to get right: who exists institutionally, what they can decide, how those facts persist across time, and how obligations get discharged. Each pillar maps to specific surfaces.
01
Identity
Persons, Roles, and Role-Holdings — institutional identity, distinct from system identity. The person who is the Medical Director is recorded as the same person across every committee they sit on, and across every time-bounded role they have held.
02
Authority
Schemes of Delegation declare who can decide what. Committees have Terms of Reference. Outcomes that cite SE-entries are scope-checked at the point of binding — authority can be exercised, not asserted.
03
Continuity
Memberships are time-bounded. End events name the doctrinally distinct reasons a Membership ends. Closed Memberships persist; the next chair sees the history, not a clean slate.
04
Discharge
Obligations are registered against committees with target windows; forward projection sorts by deadline; overdue is computed mechanically. Discharge requires the outcome, not a checkbox.
C — Modules
Eight modules, one institutional record.
Each module corresponds to a load-bearing governance primitive. The append-only chronology underneath every module is the institutional memory — closed memberships persist, superseded minutes are visible, deleted obligations never were.
- 01
Committees
Top-level committees and sub-committees, with Terms of Reference and approval flow.
- 02
Persons + Roles
Institutional identity register: Persons, Roles, and time-bounded Role-Holdings.
- 03
Memberships
Persons bound to Committees in declared Membership Types for an effective period.
- 04
Schemes of Delegation
Structured delegations from source bodies to recipients, with limits, reservations, sub-delegation terms.
- 05
Meetings
Per-meeting flow: agenda → items → quorum state → outcomes → minutes → approval.
- 06
Outcomes
Named decisions citing the source-of-authority Scheme entry; binding outcomes scope-checked at commit.
- 07
Minutes
Approved minutes supersede prior versions; the approval event is the binding point, not the document.
- 08
Obligations
Forward-projected obligation calendar with overdue computation and discharge tracking.
D — What Quorum shows
Two real surfaces from the running app.
Captured against the running Quorum app, against the same code pilot partners sign in to. The sign-in surface is the closed-pilot gate; the landing surface declares the substance — governance obligation continuity for healthcare institutions.
E — Honest notes
Things worth saying explicitly.
Quorum is not a meeting-scheduler.
It does not run calendars, send invites, or replace whatever scheduling tool your committees already use. It records the institutional consequences of those meetings — decisions, minutes, outcomes, obligations.
Quorum does not write minutes.
Minutes are authored by named secretaries. Quorum tracks the approval point, the supersession chain, and the binding-outcome citations — but the substance is yours.
Authority scope is enforced, not advisory.
Outcomes that cite an SE-entry are scope-checked at commit. If the cited Scheme entry does not authorise the binding outcome, the commit refuses. Authority is exercised, not asserted.
Quorum is preview, not GA.
Engineering-verified (482 tests passing); not yet partner-deployed. Pilot-track access is by application.
F — Access
Pilot by application.
Quorum — pilot access
By application
Pricing follows pilot validation.
- · Founder-level support during pilot
- · Manual onboarding of your committee graph + scheme of delegation
- · Single-tenant deployment with institutional-identity tenancy
- · Direct influence over the GA governance surface
- · Preferential GA pricing when published
Pilot partners commit to approximately three hours per month of feedback time across the first three months — a committee-graph walkthrough at month one, a delegation-cascade review at month two, an obligation discharge audit at month three.
Apply for pilot accessG — Common questions
Frequently asked.
- Why is Quorum not just a meeting-scheduling tool?
- Meeting schedulers track who is meeting and when. Quorum tracks the institutional consequences of those meetings — the schemes of delegation that govern what they can decide, the chronology of who was present in what capacity, the obligations that flow from each decision, and the authority scope that determines whether a binding outcome is actually binding. The schedule is incidental; the governance memory is the substance.
- Why does Quorum reject the `org_id` pattern?
- Multi-tenant SaaS treats organisations as flat boundaries — every row carries an org_id, and tenancy is enforced by query scope. Quorum's tenancy is institutional-identity (Person, Role, Committee, Membership). A person can sit on committees in different institutions; a role can be held by the same person across different organisations. The institutional graph is the tenancy boundary, not a flat org_id.
- Is Quorum for a single organisation or multi-institution use?
- Both. A single multi-committee organisation (a hospital trust, an ICS) can use Quorum to manage its own committee graph. A federation can use Quorum to manage governance across multiple constituent institutions sharing some committee structures and not others. The institutional-identity tenancy supports both without requiring a switch.
- Is Quorum available now?
- Quorum is preview status — engineering-verified (clean typecheck, 482 passing tests across 41 files, runtime smoke verified on `portiko-quorum.vercel.app`) but not yet partner-deployed. Pilot-track access is by application.