The PMC Firm / Module 01
One spine, many mandates
Every mandate on the same records, with a governed workspace per client and per-project access enforced at the database — so two developers never see each other's programme.
- Partner
- Practice head
- IT / admin
For a firm. The constraint on a PMC practice is rarely demand — it is how many mandates a partner can personally hold in their head. Standard records, standard registers and enforced separation of duties move part of that load into the system, which is the only way the fifth mandate is as well run as the first.
What it holds
Client workspaces
An organisation layer per client with its own projects, parties, users and entitlements. Your staff move between them; your clients cannot.
Per-project authorisation
A user scoped to one mandate cannot read or act on another — checked on every route and enforced with row-level security, not by hiding a menu item.
Module entitlement per mandate
Each project carries only the modules its appointment covers, so a planning-only mandate does not present cost screens nobody is engaged to run.
Acting-for mode
The same platform used on the employer's side of the table or the contractor's, with the mode recorded on the project — because a firm that does both should not be running two systems.
What the firm gets
- A new mandate provisioned in an afternoon, to your standard
- The same registers on every project — comparable, auditable
- Staff who move between mandates without relearning anything
What it will not allow
- Cross-mandate visibility, at any role
- A module used on a project it is not engaged for
- A client login reaching another client's workspace