Minutes stop being a backlog
Packs assemble from live data, minutes are drafted from the recording, and approval runs forward-only to a signed, versioned record.
What the family expects, and where it lives
A family office is held to institutional standards on a fraction of institutional headcount, and the standard that matters is discretion. Each expectation below is carried by a module that records the decision as the work happens.
| What has to hold | Where CoreAdmin evidences it |
|---|---|
| Know at any moment which structures the office administers and who holds each role | Entity recordsOne golden source for structures, counterparties, roles and statuses that every other workflow keys against, so two records can never disagree about who the client is. |
| Require a second named person on every payment and sensitive change | Four-eyes approvalsThe second approver is required by construction, cannot be the first, and the sign-off chain is recorded automatically rather than reconstructed from email. |
| Let each adviser, family member and staff member see only what they are entitled to | Access controlTiered permissions decide who sees what, segregation-of-duties conflicts are defined centrally, and every access change is logged append-only. |
| Produce a signed, versioned minute for every trustee or board decision | Board meetingsPacks assembled in hours, minutes drafted from the recording, and a forward-only approval chain to a signed record. |
| Reconstruct any decision years later, with the evidence that supported it | Audit reportsEvery workflow retains its named actions and supporting evidence, so a decision can be explained to a beneficiary or a court without archaeology. |
| Show a bank or counterparty who is authorised to instruct on each structure | Entity recordsRoles and authorities are held against the structure itself, not in a signatory list someone maintains separately, so the answer given to a bank matches the answer given to the auditor. |
| Give the principals one current view of tasks, approvals and risk | Management dashboardsOne live view across the structures the office administers, so nothing depends on one person being reachable to answer a question. |
Every row is an append-only record. Entries are added, never quietly rewritten, so the register and the underlying file cannot drift apart.
Three places the difference shows up first
Nothing waits on one person
Tasks, approvals and risk sit in one live view, so a principal gets an answer without a key colleague having to be available.
Records stop living in inboxes
Structures, counterparties and roles move out of personal drives into one source that every workflow reads from.
The detail, when you want it
The operating reality this was built for
- The family expects institutional-grade governance, but the office runs on a fraction of institutional headcount.
- Approvals happen in email and key decisions depend on one or two people being available.
- Entity records, minutes and evidence are spread across spreadsheets, inboxes and personal drives.
- Discretion is non-negotiable: information must reach exactly the people entitled to it, and no one else.
What CoreAdmin runs for a family office, module by module
Entity records. One golden source for structures, counterparties, roles and statuses that every other workflow keys against, so records can never disagree about who the client is.
Approvals and four-eyes control. Payments and sensitive changes require a second named person by construction, with the sign-off chain recorded automatically.
Board meetings and minutes. Packs assembled in hours, AI-drafted minutes from a recording, and a forward-only approval chain to a signed, versioned record.
Management dashboards. One live view of tasks, approvals and risk across the structures the office administers.
Evidence and audit reports. Every workflow retains its named actions and supporting evidence, so any decision can be reconstructed years later without archaeology.
Access control. Tiered permissions decide who sees what, segregation-of-duties conflicts are defined centrally, and every access change is logged append-only.
How it lands alongside the systems you already use
CoreAdmin starts with the workflow that hurts most, often approvals or entity records, and grows from there. It sits alongside the systems and advisers the office already uses. Every AI-assisted step goes to a named person for decision, and the audit trail is produced as a by-product of the work.
How discretion is enforced rather than promised
Permissions are tiered per module and per record, not granted wholesale by job title. A conflict between two duties is defined once, centrally, and then the platform refuses to let one person hold both.
Every access change is written to an append-only log, so the question "who could see this, and from when" has an answer that does not depend on anyone's memory. Read more about how the platform is secured on the security page.
Where the AI stops and a named person starts
AI drafts, extracts and summarises. It never approves. Each decision is attributed to the individual who took it, alongside the version of the policy that applied at the time.
Where a second pair of eyes is required, the workflow will not complete without them, and the second reviewer cannot be the first. That is enforced by the platform rather than described in a procedure.
See it against one of your own workflows
Bring a live process to a focused 30-minute session: a distribution approval, an entity record or a board pack.