Trust Document Intelligence

The problem

Governing terms live in paper. The distribution standard, the successor trustee chain, the power of appointment, the retention clause, the perpetuities savings language: all of it sits in a scanned instrument in a document management system, and a version of it sits, re-keyed by hand, in the trust accounting system. Nobody can prove the two agree.

When a beneficiary asks why a distribution was denied, or an examiner asks how the account was coded, the answer is a trust officer's memory and a folder. Re-keying is where fiduciary risk enters. Not in the reading, but in the copying, and in the twelve years since the amendment nobody indexed.

What it reads

Document types the system ingests. Each is versioned in sequence so a superseded term never silently governs.

Trust instruments

Revocable and irrevocable, including the full amendment and restatement chain.

Amendments and restatements

Tracked in sequence, with effective dates, so a superseded term never silently governs.

Wills and pour-over wills

Including testamentary trust provisions.

Certifications of trust

The abbreviated instrument counterparties actually accept.

Powers of attorney and healthcare directives

Durable, springing, and limited.

Entity agreements

LLC operating agreements, family partnership agreements, and buy-sell provisions held inside trusts.

Court orders and settlement agreements

Modifications, reformations, non-judicial settlements, decanting instruments.

Beneficiary designations and elections

Including tax elections attached to the account.

What it proposes

The system produces a structured abstract of governing terms. Each field is extracted language with a citation back to the source. Nothing below is a conclusion. It is a proposed abstract for human review.

Parties and structure

Trust name, execution date, governing law and situs
Settlor or grantor; revocable or irrevocable; grantor or non-grantor for income tax
Current trustee, co-trustees, successor trustee chain, and the conditions that trigger succession
Trust protector or directed party, and the scope of the direction
Beneficiary classes: current income, remainder, contingent, with the language that defines membership

Distribution authority

The distribution standard as written, verbatim, with its citation — ascertainable (health, education, maintenance, support) versus absolute or sole discretion
Mandatory income provisions, unitrust or total-return conversions, annuity or fixed-sum payments
Withdrawal rights, including five-and-five powers and demand rights
Powers of appointment: general or limited, lifetime or testamentary, and the permissible class of appointees
Spendthrift language and any exceptions

Investment and administration

Investment authority: prudent investor default, expanded powers, or direction by a third party
Retention and concentration clauses naming specific holdings
Fee provisions and the basis on which compensation is calculated
Accounting, notice, and reporting duties owed to beneficiaries
Termination provisions, perpetuities savings language, and any decanting authority

Tax attributes

Marital deduction structure where present
Generation-skipping inclusion ratio and exemption allocation as reflected in the instrument
Charitable payout provisions and their computation basis

Every one of these is a proposal. The system extracts the language and points at where it found it. It does not conclude what the language means. A person does that, on the record, and the record says who.

The human-in-the-loop control model

Extraction is fast and always provisional. Every governing term that reaches a system of record passes through fixed gates. Governance is the product, not a wrapper added afterward.

Intake

Document is received, hashed, and versioned. The original is never modified. Every downstream assertion points back to this immutable copy.
Extraction

The system produces a proposed abstract. Every field carries a citation: document version, page, and the span of text it came from. Fields it cannot support with a citation come back empty, not guessed.
Officer review

A trust officer works the proposed abstract field by field against the source, which is displayed alongside. Accept, correct, or reject. Corrections are recorded as corrections, not as silent overwrites.
Counsel review

Interpretive terms route to fiduciary counsel. No interpretive field advances on one signature.
Committee action

Terms that will drive a discretionary decision or a tax position go to the fiduciary or discretionary distribution committee with a written rationale attached.
Release to system of record

Only an approved abstract writes. Nothing reaches the trust accounting system without a named approver, a timestamp, and a citation behind every field.

There is no configuration that turns the gates off. A firm can decide who reviews what. A firm cannot decide that nobody reviews.

Review tiers

Not every field carries the same fiduciary weight. Routing follows tier, with escalation when policy requires it.

Tier	Example terms	Who approves
Clerical	Trust name, execution date, taxpayer identification, situs	One reviewer, sampled for quality
Structural	Trustee chain, beneficiary classes, revocability, fee basis	Trust officer, single approval, full audit record
Interpretive	Distribution standard, discretionary language, powers of appointment, investment direction, retention clauses	Trust officer plus fiduciary counsel — two people, never one
Judgment	Any term that will drive a distribution decision, a tax election, or a concentration position	Committee action with written rationale on the record

Clerical Trust name, execution date, taxpayer identification, situs One reviewer, sampled for quality
Structural Trustee chain, beneficiary classes, revocability, fee basis Trust officer, single approval, full audit record
Interpretive Distribution standard, discretionary language, powers of appointment, investment direction, retention clauses Trust officer plus fiduciary counsel — two people, never one
Judgment Any term that will drive a distribution decision, a tax election, or a concentration position Committee action with written rationale on the record

Rules and governance

The routing above is not hard-wired vendor behavior. It is the firm's own policy, written as rules, versioned, and testable.

Confidence floor

Any field below the firm's threshold escalates regardless of tier.

Unmatched amendment

If an amendment is detected without a corresponding restatement in the chain, the whole abstract holds. Nothing partial releases.

Conflict with the record

If a proposed term contradicts a previously approved term, the field freezes and notifies the account's officer of record. Silent correction is never permitted.

Concentration trigger

A retention or concentration clause naming a specific holding opens the firm's concentration review workflow.

Tax-sensitive terms

Generation-skipping and marital deduction terms route to tax review automatically, whatever the confidence score says.

Separation of duties

The person who corrects a field cannot be the person who approves it.

Rules are versioned like code. When an examiner asks what the review policy was in March of last year, the answer is a specific version, not a recollection.

Evidence and audit

Every approved field carries a permanent record of the document version and page it came from, who reviewed it, what they changed, when, and under which rule version the review was routed. Amendments supersede by effective date without destroying prior state, so the abstract can be reconstructed as it stood on any past date.

Records are retained under the firm's own retention policy on write-once storage. The deliverable is not a summary. It is a defensible file.

What this does not do

This section matters. Fiduciaries read it first.

It does not give legal advice or render legal opinions.

It does not determine what a discretionary standard permits in a given case.

It does not authorize, calculate, or execute a distribution.

It does not write to a system of record without an approval.

It does not overwrite a term a human approved.

It does not replace counsel, a trust officer, or a committee. It gives them a faster first draft and a cleaner record.

Where this fits

Document abstraction is a block. The same replacement-block pattern as statement freezing, fee calculation, and the rest of the foundation blocks catalog: prove it in parallel against current practice before it touches the system of record.

Run the proposed abstract beside the hand-keyed record on live accounts. Measure the disagreements. Only then move the system of record. See the Parallel-Run Method for how validation gates work block by block.