From Draft to Deed: The Document Chain Every Trust Needs

There is a moment between a draft trust deed and a signed one that most families never think about — but that moment is exactly where disputes begin. The question is not whether the deed was signed. The question is whether the signed deed matches what was agreed. A document chain answers that question definitively, and without one, you are leaving the door open to challenge.

Why 'document chain' matters in trust law

A trust deed is a legal instrument that confers rights, imposes duties, and transfers assets. Its authority depends on one thing: that the document signed is the document agreed. If a beneficiary later claims that a clause was altered after approval but before signing, or that the version on file is not the version executed, the burden of proof falls on the trustees.

Without a document chain — a timestamped record linking the agreed draft to the executed copy — that burden is almost impossible to discharge. With one, it takes seconds.

What a SHA-256 hash does

A SHA-256 hash is a cryptographic fingerprint. Feed any document — any file, any text — into the SHA-256 algorithm and it produces a unique 64-character string. Change a single character anywhere in the document and the hash changes completely. Two documents that produce the same hash are, to a mathematical certainty, identical.

For a trust document, this means: the moment a draft is saved, a hash is computed from its exact content. That hash is stored permanently. Later, when the signed PDF is uploaded, a second hash is computed from the binary content of the scanned file. Both hashes are stored, and both are linked together.

The draft-to-executed chain in practice

In Equity Steward, the chain works as follows. The AI Document Wizard generates a complete draft instrument — trust deed, schedule, letter of wishes, or any other document — from the architecture you defined in Stage 2. The draft is saved to your workspace with a SHA-256 hash computed at the moment of saving.

You review the draft. You send it to your solicitor if appropriate. When the signed version is returned — as a scanned PDF — you upload it back into the platform with one click. The platform computes the hash of the signed PDF, links it to the source draft, records both hashes, automatically advances the draft status to Executed, and closes the relevant checklist item.

What the chain protects you against

The most common attack on a trust deed is the allegation of alteration: that the version on file was changed after the parties agreed it, or after execution. With a hash chain, this allegation fails immediately. The draft hash proves what was agreed. The signed-document hash proves what was executed. If they match, there was no alteration. If they differ, the difference is explained and visible.

A secondary protection is temporal: the draft's creation timestamp, the status history, and the upload timestamp of the signed copy all form part of the audit trail. This shows the sequence — draft created, reviewed, executed, uploaded — in the order it actually happened.

Frequently Asked Questions

Do I need a solicitor to use the Document Wizard?

No. The Document Wizard generates complete draft instruments for self-directed review. For complex or high-value trusts, having a solicitor review the draft before execution is advisable. The platform is designed to complement professional advice — you bring the structure and record-keeping; your solicitor brings legal expertise when needed.

What happens if I lose the original draft?

The draft is stored permanently in your workspace. The SHA-256 hash is computed from the saved content. As long as the platform holds the draft, the hash can be recomputed and verified against any purported copy at any time.

Can the hash chain be independently verified by a third party?

Yes. SHA-256 is a public standard implemented in every major programming environment. Any competent technical advisor can take the original document text or PDF, compute its SHA-256 hash independently, and compare it against the value stored on the platform. No access to the platform is required for verification — only the document and the recorded hash value.

Does uploading the signed PDF replace the draft?

No. The draft and the signed copy are stored as separate, linked records. The draft remains in your workspace at its original status; the signed copy is stored in the Executed Documents section with its own hash. Both are accessible independently.