- About you
- About them
- How we can help
Has someone close to you died?
Then you may need probate rather than a will — a different journey, with its own kind of care. We'll point you somewhere genuinely useful instead of pretending this page is it. PROPOSAL
Thank you for being here for them. Who are they to you?
A first name is fine — it just makes the next steps feel human.
Helping someone sort their will is one of the kindest jobs there is. Plenty of people arrive here doing exactly what you're doing — you're in good company, and we'll look after you both.
Where does David live?
The law that shapes a will follows the person it's for — so this one question decides how we can help.
We've set this to England & Wales from where you saw our ad. If David lives somewhere else, just change it below — no problem. PROPOSAL
Only so we can suggest people you could sit down with in person.
Why two location questions?
They do different jobs. Where David lives sets which law applies to the will. Where you live just helps us find help near you. You could be in Glasgow while David is in Hale — that works fine.
David stays in charge. You're the helping hands.
You can gather, tidy and prepare — and nothing becomes final unless David agrees to it. That protects you both.
David's say-so. We'll ask David to confirm they're happy for you to help — and they can pause or stop it at any time, no questions asked. We ask because it keeps David in genuine control. PROPOSAL wording
Acting for David — let's keep you on safe ground.
Caring for someone who can't decide for themselves is a big responsibility. We only unlock what your authority covers, so you can never put a foot wrong here.
Options shown for England & Wales — this list follows where David lives. config, not code
Add a copy of the document — a PDF or a clear photo is fine.
It saves you typing, and it's the proof a will writer will ask for anyway. PROPOSAL
You're in the right place — and so is David.
Here's how we've understood things. If anything's off, just step back and change it — nothing is locked in.
You can gather, check and prepare drafts. David approves anything that matters, and can pause your access at any time.
for myself · supported helper · deciding together · attorney / deputy
Next you tell us about the estate. If it looks straightforward we say so, and show free charity wills alongside the paid routes, with no default. If it does not, we show the paid routes and say a firm should advise. Free to look around. No card details, and we never charge anything without asking you first.
We can't arrange a will for David where he lives yet
We only work where we truly know the law, which is England and Wales at launch. We'd rather tell you that plainly than pretend.
In the meantime, a local solicitor or notary where he lives is the right first step — a genuinely good place to start. PROPOSAL
One email when we open where David lives. Nothing else, ever.
That email doesn't look quite complete — could you check it for us?
Built on INHERIT v2
This demo is built on INHERIT v2 — an open standard for describing an estate. We show you honestly which parts of this screen the standard can hold today, which are planned, and which are still gaps.
- Supported now1 entriesThe standard already has a place for this today.
- Supported now · shared core6 entriesSupported by the part of the standard shared across our brands.
- Planned11 entriesA change proposal covers this. Where we can check the standard’s own record, we show its status.
- Gap — needs planning0 entriesOn the screen, but no change proposal covers it yet. These still need planning.
- Not a standard concept7 entriesPage furniture, or something we decided the standard should not hold.
25 traced entries on this screen, from two overlapping traces
Each entry comes from either the screen’s feature list or the data the screen displays. The two traces overlap, so one feature can appear twice: these are entries, not a count of distinct features.
Planned
intake.authority-outcomeICP-0070 Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule
Planned
intake.bereavement-routeICP-0070 Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule
Planned
intake.capability-scopeICP-0070 Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule
Planned
intake.capacity-triageICP-0070 Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule
Planned
intake.co-decision-modeICP-0070 Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule
Planned
intake.confirm-with-subjectICP-0070 Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule
Planned
intake.paid-helper-safeguardICP-0070 Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule
Planned
intake.relationship-captureICP-0070 Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule
Planned
intake.remuneration-facetICP-0070 Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule
Planned
intake.reserved-acts-stopICP-0070 Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule
Planned
intake.situation-summaryICP-0070 Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule
Supported now
intake.poa-evidenceIn the standard as: Common · Media
Supported now · shared core
companion.consent-captureShared core: shared-core#companion.consent-capture
Supported now · shared core
jurisdiction.ad-prefillShared core: shared-core#jurisdiction.ad-prefill
Supported now · shared core
proxy.authorisationShared core: shared-core#proxy.authorisation
Supported now · shared core
referral.routeShared core: shared-core#referral.route
Supported now · shared core
steward.acting-for-anotherShared core: shared-core#steward.acting-for-another
Supported now · shared core
steward.entry-modeShared core: shared-core#steward.entry-mode
Interface onlyActive viewer app-role → capability tokens
Interface: ext.roles.tokens
interface configuration, not something the standard holds
Interface onlyAuthorityBasis modes self→Owner / supported→Steward / substituted→Proxy
Interface: ext.intake.authority_basis_modes
interface configuration, not something the standard holds
Interface onlyJurisdiction options (E&W / Scotland / ROI)
Interface: ext.intake.jurisdictions
interface configuration, not something the standard holds
Not a standard concept
jurisdiction.honest-declineWhy not: per-territory "not available where they live yet" copy — brand copy, not a standard concept; Rich released it from solicitor sign-off 27 Aug 2026 (decision #14)
declined by Josh Thayre
Not a standard concept
jurisdiction.notify-meWhy not: waitlist email capture on the decline branch — marketing / CRM, not a standard concept; behaviour settled by Rich 27 Aug 2026 (decision #14)
declined by Josh Thayre
Not a standard concept
jurisdiction.testator-gateWhy not: the testator's jurisdiction checked against MFI's launch territory list — brand launch config (SSOT brand-architecture.md §1.7), not a standard concept; behaviour settled by Rich 27 Aug 2026 (decision #14)
declined by Josh Thayre
Not a standard concept
jurisdiction.visitor-locationWhy not: the visitor's own location, used only to rank in-person proximity to a will writer (TT-1007, the MFI location-aware header) — brand-layer header and matching behaviour, never eligibility; the standard carries the jurisdiction value, not where a visitor is browsing from
declined by Josh Thayre
The 29 change proposals this demo relies on
A change proposal (ICP) is a tracked request to extend the standard. These are the ones behind the “Planned” features across all 33 screens — and the few already adopted and built. Where the standard has a written proposal we show its status from the standard’s own record; where it does not, we say so rather than guess.
- ICP-0001 · TT-657 — Port v1 consumer-estate surface into v2 (retracted in the standard)
- ICP-0002 · TT-658 — IHT 36% reduced charity rate (approved in the standard)
- ICP-0006 · TT-663 — Marketplace & dealer model (tracked; no written proposal yet)
- ICP-0007 · TT-664 — Valuation lifecycle enrichment (tracked; no written proposal yet)
- ICP-0008 · TT-665 — Delegation, stewardship & marketplace integrity (tracked; no written proposal yet)
- ICP-0013 · TT-672 — Condition grading (tracked; no written proposal yet)
- ICP-0014 · TT-673 — Collector records bundle (tracked; no written proposal yet)
- ICP-0015 · TT-674 — Legal-assurance model (pending in the standard)
- ICP-0016 · TT-681 — Professional engagement & marketplace data model (approved in the standard)
- ICP-0019 · TT-684 — Executor / personal-representative appointment & powers model (pending in the standard)
- ICP-0021 · TT-686 — Wishes, directives & plan-assessment primitives (pending in the standard)
- ICP-0022 · TT-1029 — Post-death estate-administration & will-lifecycle domain (approved in the standard)
- ICP-0024 · TT-1031 — Nomination / expression-of-wish — non-testamentary transfer route (approved in the standard)
- ICP-0026 · TT-1033 — Free-text→structured multi-entity extraction (approved in the standard)
- ICP-0027 · TT-1034 — Living-Monitoring change-event model (approved in the standard)
- ICP-0028 · TT-1040 — Couple / mirror-vs-mutual wills modelling (approved in the standard)
- ICP-0029 · TT-1954 — Insurance-cover model (approved in the standard)
- ICP-0030 · TT-1069 — Catalogue item-import adapter (approved in the standard)
- ICP-0033 · TT-1131 — Executor pre-death readiness facet (approved in the standard)
- ICP-0034 · TT-1132 — E&W IHT spouse exemption (tracked; no written proposal yet)
- ICP-0044 · TT-1143 — Steward/authority-grant remuneration facet + paid-helper undue-influence safeguard (tracked; no written proposal yet)
- ICP-0046 · TT-1144 — Multi-opinion / consensus valuation shape (approved in the standard)
- ICP-0047 · TT-1145 — Compute faith fixed-shares (approved in the standard)
- ICP-0052 · TT-1292 — Funeral & farewell domain (tracked; no written proposal yet)
- ICP-0054 · TT-1174 — Asset-side external-registry enrichment (tracked; no written proposal yet)
- ICP-0055 · TT-1175 — Asset enrichment facets: maker/external-id (tracked; no written proposal yet)
- ICP-0061 · TT-687 — Heir collaboration & asset-claim resolution (tracked; no written proposal yet)
- ICP-0062 · TT-688 — Collections & asset disposition (tracked; no written proposal yet)
- ICP-0070 · TT-969 — Steward / AuthorityBasis — who may act for whom, with what authority, scope and consent, and the legal-effect confirmation rule (tracked; no written proposal yet)
Checked against a pinned copy of the standard’s change-proposal register (73 proposals, standard at main@f63ca72e116d), and against the standard’s own record of what it has adopted (29 written proposals, 176 computed rules). Sample estate — demo data, no sign-up.