Entity management for corporate services firms: scale client portfolios without scaling admin linearly
Professional entity-service firms have a different operating model from in-house legal teams. The platform must organize Firm → Client → Portfolio → Entity while preserving client separation and repeatable service workflows.
Legal · Operations
Entiti · Operating guidanceReviewed September 2, 2026 · This page is for corporate secretarial, company secretarial and professional entity-administration firms.
Illustrative · Two permitted clients
Client context stays visible.
- 01Ashcombe GroupAshcombe Holdings Ltd · Evidence reviewNeeds review
- 02Northstar GroupNorthstar Services Ltd · Client responseWaiting on client
- 03Ashcombe GroupAshcombe Asia Pte. Ltd. · Baseline reviewIn progress
Start with the firm, then the client.
- FirmHarbor Corporate Services
- ClientAshcombe Group
- PortfolioAsia portfolio
- EntityAshcombe Asia Pte. Ltd.
The example contains only clients permitted within this illustrative scope.
Service scope and access are different.
- 01Client relationshipRelationship lead
- 02Entity informationInternal Entity Owner / Lead
- 03Prepared workAssigned preparer
- 04Material decisionAuthorized reviewer
A service assignment does not automatically grant access to all client data.
Client context
Keep every entity inside its client context.
The agency hierarchy is Firm → Clients → Portfolios → Entities. Use that structure consistently across onboarding, records, reporting and work.
- Establish client permissions before importing entities.
- Keep client and portfolio visible in cross-client views.
- Apply access rules to totals, filters, sources, exports and AI answers.
An accessible work queue
| Client | Entity | Owner |
|---|---|---|
| Ashcombe Group | Ashcombe Holdings Ltd | Jordan Smith |
| Northstar Group | Northstar Services Ltd | Alex Rivera |
Unauthorized clients must not appear in the queue or its counts.
Onboarding
Onboard the client, then establish the baseline.
A repeatable onboarding process starts with the relationship and service scope. Bring in the entity inventory next, reconcile source data and assign review ownership.
- Separate client creation, service scope and record authority.
- Resolve duplicate and conflicting sources within the correct client.
- Approve a manageable first portfolio before expanding.
Client context
- Responsible team
- Relationship lead
- Keep with the record
- Client scope and permitted access
Delivery
Manage the exception and its next step.
A shared work view helps teams coordinate across permitted clients. A useful row shows the entity, responsibility, deadline, status and blocker.
- Distinguish internal work from a dependency on the client.
- Use maker-checker review where policy or service risk requires it.
- Measure your own reporting effort, turnaround and unresolved work.
A blocker needs an owner
| Work | Dependency | Next step |
|---|---|---|
| Appointment evidence | Waiting on client | Request the missing record |
| Source conflict | Legal review | Confirm authoritative value |
| Prepared filing | Approval required | Route to authorized reviewer |
Targets and service commitments should come from the agreed client scope.
Questions by function
One entity context. Each team’s next question.
Use the same records and evidence to answer the question your team needs resolved.
Legal
Where does the client-specific authority sit?
Retain the source, reviewer and approval scope within the correct client.
Questions
The things teams ask first.
Answered plainly, including where the next step depends on local requirements, evidence or review.