Commissioned client work · Client pilot · dry-run testing
Entrusted
Quiet stewardship of generosity.
Dignity for the people asking, clear authority for the people deciding, and a traceable record of every step.
A trust operations and governance progressive web app commissioned by a client. It places a structured, respectful process between requests for support and the people responsible for funding them — consistent decisions within delegated limits, with oversight and a full history.
Enquire about Entrusted
Who it helps
- Family and community trusts
- Administrators and executors
- Oversight and governance roles
- Beneficiaries requesting support
Connected capabilities
Everything a request needs, from first submission to archived record.
Intake and verification
Beneficiary profiles are checked at intake so later decisions rest on verified context.
Evidence and timelines
Each request carries its documents, context and a timeline everyone with access can follow.
Delegated limits and exceptions
Executors decide within their authority; anything outside policy or caps escalates to the Overseer.
Recurring obligations
Scheduled support such as fees or allowances, with schedule changes recorded.
Payment records and proof
Payments made outside the app are recorded manually, with proof uploaded against the request.
Audit, notifications and support
Audit history and exports, request notifications with a retry queue, role permissions and technical support access.
Five roles, one journey
- Beneficiary
- Sees their own requests, evidence and status.
- Administrator
- Checks intake and asks for missing information.
- Executor
- Reviews within delegated authority, schedules approved support, records manual payments and proof.
- Overseer
- Sets policy and caps, handles escalations, governance and audit.
- Technical
- Diagnoses issues, manages tickets, read-only inspection — no financial decisions.
Request lifecycle
- 1Draft
- 2Submitted
- 3Admin review / Needs information
- 4Executor review
- 5Overseer (if exception)
- 6Decision
- 7Scheduled
- 8Payment record
- 9Archived
Representative journey
An education-support request
A fictional example of how a request moves through Entrusted:
- 01Beneficiary requests school-fee support
- 02Administrator asks for the fee statement
- 03Executor decides within policy
- 04Manual payment recorded with proof
- 05Traceable timeline kept for oversight
What's next
- Proof-of-payment matching
- Bank integration, always with human review
- Reusable onboarding for multiple trusts
Where it stands
Delivered for client onboarding and workflow dry-run testing. Payments are recorded, not moved, by the app. No real client records are shown.
See our bespoke PWA serviceInterested in Entrusted?
Tell us about your interest or how you might like to be involved.