Board and director management across a global entity portfolio
Board and director data becomes operationally useful when appointments, terms, authority, evidence and downstream actions are connected to the legal entities they affect.
Legal · Corporate Secretary
Entiti · Operating guidanceReviewed September 2, 2026 · Use this guide as an operating framework; appointment and resident-director rules vary by jurisdiction.
Ashcombe portfolio · 3 sample entities
Current roles across the portfolio.
- 01Ashcombe Holdings LtdUnited Kingdom · Morgan Lee, DirectorVerified
- 02Ashcombe Services LtdUnited Kingdom · Jordan Smith, OfficerNeeds review
- 03Ashcombe Asia Pte. Ltd.Singapore · Alex Rivera, DirectorVerified
One person record. Every connected role.
- MLMorgan LeeCurrent director · Ashcombe Holdings Ltd1 current role
- JSJordan SmithOfficer · Ashcombe Services Ltd1 current role
- ARAlex RiveraDirector · Ashcombe Asia Pte. Ltd.1 current role
An earlier appointment for Morgan Lee at Ashcombe Services ended September 18, 2026.
A role ends. Follow-up stays visible.
- Resignation receivedMorgan Lee · Ashcombe Services Ltd · September 18, 2026
- Corporate records reviewedKeep the effective date and appointment history.
- Authority still under reviewTreasury confirmation and separate POA evidence are required.
Appointments
Start with every role a person holds.
Record the person once and connect that person to each entity appointment. Keep current and historical roles together without flattening them into Director 1 and Director 2 fields.
- Capture role, entity, start date and end date.
- Link appointment evidence and review status to each relationship.
- Support people with several roles across multiple entities.
Current sample appointments · Switch the perspective
Every role belongs to an entity.
| Entity | Person | Role | Evidence |
|---|---|---|---|
| Ashcombe Holdings Ltd | Morgan Lee | Director | Verified |
| Ashcombe Services Ltd | Jordan Smith | Officer | Needs review |
| Ashcombe Asia Pte. Ltd. | Alex Rivera | Director | Verified |
Local requirements
Make local questions visible.
Board-composition requirements depend on the jurisdiction, legal form and facts. Keep the applicable rule and its source separate from the appointment record.
- Identify any composition or replacement question created by a change.
- Assign the review to someone responsible for the local requirement.
- Record the source, review date and decision basis.
Illustrative · Ashcombe portfolio
3 sample entities
Appointment evidence needs review.
The officer role is recorded, but the supporting document has not been verified.
- Review owner
- Corporate Secretary
- Source
- Appointment resolution
- Next step
- Obtain and verify evidence
Role changes
Close the work created by the change.
Record the effective date, identify affected entities and track each required follow-up through to evidence. Entering an end date is one step in the process.
- Confirm local approvals, filings and register changes.
- Review external authority, KYC and access where applicable.
- Preserve the old appointment and the completion trail.
Scope confirmed
- Responsible team
- Corporate Secretary
- Keep with the record
- Entity scope, dates and affected roles
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
What changed, and what evidence proves it?
Inspect the appointment, authority and effective-date history together.
Questions
The things teams ask first.
Answered plainly, including where the next step depends on local requirements, evidence or review.

