Most family disputes about inheritance don't begin with shouting. They begin with a sibling who quietly thought "I'm not sure about that," didn't say so, and watched the decision get made. Months later, when the consequences land, the unspoken reservation surfaces — and what could have been a five-minute conversation becomes a five-year resentment.
Heriteo's decision model is built around a stubborn observation: families don't lack goodwill, they lack a structured place to record nuance. A quiet "yes," a polite "if that's what everyone wants," and a genuine "I have concerns" all look identical in a family WhatsApp group. They shouldn't.
From intention to decision: why the distinction matters
Heriteo separates two things most spreadsheets confuse. Intentions are individual, often private, sometimes uncertain — what each heir wants to see happen. We've covered the intention model in detail in why every heir's voice (including silence) is data. Decisions are proposals for the whole family — a specific outcome on a specific object, drafted by an admin, sent for validation by the heirs.
The transition from intention to decision is the most consequential moment in the whole process. It's the moment a private preference becomes a public proposal. Doing that in a structured way — rather than via a phone call to one sibling and a text to another — is what prevents the slow-motion misunderstandings that kill estate plans.
The four-state decision lifecycle
Every decision in Heriteo moves through the same four states: Draft → Pending → Resolved → Executed.
Draft
The admin heir is shaping a proposal. The decision specifies one outcome — Assign, Sell, Donate, or Dispose — with relevant details: a recipient, a buyer, a donation target, sale amounts, taxes, fees, notes. While in Draft, the decision is invisible to the rest of the family. This is the workspace where the proposer thinks, revises, and double-checks.
Pending
The decision is published to the family. Every heir can see it. This is the validation window — the explicit space for the family to say what they think, in writing, before anything is acted on.
Resolved
The family is aligned, validations are in, and the decision moves toward action. The Resolved state captures who resolved it and when, and it freezes the proposal so the executor can act on a stable record.
Executed
The action has actually happened — the object has been delivered, sold, donated, or disposed of. Heriteo records who executed and when. Outcomes can carry their own data: Sale captures amount, taxes, fees and buyer name; Assignment captures the recipient Person; Donation captures the target organisation; Disposition captures notes.
The lifecycle isn't there to make the family feel like they're using software. It's there to make sure that the difference between "we're going to do this" and "we did this" is visible — at the moment it matters and ever after.
Three positions, not two: Acknowledge, Support, Object
Most validation flows offer two options: yes or no. That's the wrong shape for family decisions, because it forces every heir into a stance — and quiet support gets confused with reluctant agreement gets confused with active enthusiasm.
Heriteo's validation positions are explicitly three:
Acknowledge
"I see this. I have no objection. I am not particularly active in this decision." A genuine, useful position — most decisions in a household will reasonably attract more Acknowledges than Supports, and that's fine. Acknowledge says the family is informed without being unanimous.
Support
"I'm actively in favour." This is the position that matters when a decision is contested or sensitive. A Support is a thumb on the scale, not a passive nod. It records that the heir wants this outcome, not just that they tolerate it.
Object
"I have concerns I want to register before this proceeds." Crucially, Object is not a veto. It is a recorded reservation, ideally with a comment explaining the concern. The proposer reads it, considers, and decides whether to revise the decision, hold it open, or proceed — and that response is itself recorded.
The reason this matters: most "fights" about inheritance are actually unrecorded Objects. A sibling thinks "I'm not sure about this" but says nothing because the moment to say something didn't exist. Months later, the unprocessed objection surfaces as a complaint, and the rest of the family thinks "well, why didn't you say so at the time?" Object is the slot in the conversation where they could have.
Why an objection is data, not a problem
Families that use Heriteo for any length of time learn quickly that an Object position is one of the most useful events in the whole workflow. It surfaces a hesitation before action. It invites a conversation. It often improves the decision — either because the proposer revises in light of the comment, or because the family now has a chance to talk through the concern together.
The worst outcome is not a decision with three Objects. The worst outcome is a decision with five silent Acknowledges and a sibling who is privately seething. The former is in process; the latter looks fine and is, in fact, broken. We've explored the broader dynamic in how to avoid inheritance disputes before they happen — the consistent pattern is that disputes come from invisibility, not disagreement. Validation is one half of dividing an estate peacefully; the practical method for the division itself is laid out in how to split family heirlooms without fighting.
The role of comments — and why they should be specific
Every validation in Heriteo can carry a free-text comment. It is one of the most under-used and most powerful affordances in the product, and the reason is simple: a position without a comment leaves the proposer guessing.
"Object" with no comment is an irritation. "Object — I'd prefer this go to my brother because of his daughter's musical interest" is a piece of information that almost always changes the decision constructively. The same is true of Support: "Support" is a click; "Support — Marie has been clear about wanting this, and it would honour her mother to confirm it" is a sentence that might matter to the executor twenty years from now.
For decisions involving heirs who don't live nearby, this written nuance is even more valuable. We covered the patterns that work for distant family members in engaging distant heirs.
Resolve and execute as separate steps
One subtle but important detail: Heriteo treats Resolved and Executed as two distinct states. A decision that the family has aligned on isn't yet a decision that has happened. Sales take time to close; donations need recipients to confirm; assignments sometimes wait for a transition event.
Recording who resolved a decision, when, on what evidence, and then separately recording who executed it and when — this is the thing that makes the family record trustworthy a decade later. An executor who has to act on a parent's decisions five years after they were made is grateful for the timestamps; the family discovering an old decision was never executed is grateful for the gap being visible rather than silently lost.
How this looks in Heriteo
In practice, an admin heir drafts a decision on an object, choosing the outcome and filling in the relevant fields. They publish it; the family receives a notification. Each heir can validate from their own view — Acknowledge, Support, or Object — with an optional comment. The decision page shows the full set of validations as they come in.
When the family is aligned, the admin moves the decision to Resolved. When the action happens — the keys handed over, the cheque deposited, the object donated — the admin moves it to Executed and fills in the outcome data. Both transitions carry an authoritative timestamp and the user who performed them. The audit trail is automatic; the trust the trail produces is not.
A practice round before it matters
Don't wait for a real decision to learn the workflow. Pick a low-stakes object — a piece nobody has strong feelings about — and run a full Draft → Pending → Resolved → Executed cycle on it as a family. The mechanics become familiar before the emotional ones arrive.
- Draft the decision in private; revise until the proposal is your honest first attempt.
- Publish to Pending; resist the urge to lobby individual heirs by phone.
- Use all three positions — Acknowledge, Support, Object — and require comments on Objects.
- Read the comments before responding. Most are constructive, not adversarial.
- Mark Resolved only when the family is genuinely aligned, not when you're impatient.
- Mark Executed when the action actually happens — and keep the gap honest.
Family decisions don't fail because heirs disagree. They fail because the disagreement had no structured place to live. Three positions, four states, a comment field, two timestamps — that's enough infrastructure for a family to say yes, push back, change its mind, and move forward. Without a fight, and without anyone having to swallow a reservation that should have been said out loud.