The reconstruction test for estate-planning records

When a question surfaces about a household’s estate-planning documents, it gets answered from records, not from memory. Advisors preparing to offer estate planning tend to focus on the conversation: what can and cannot be said. The question about a completed household arrives years after the engagement, from a compliance examiner, a state bar, or the lawyer for a beneficiary who expected more, and nobody replays a conversation. Advisory firms already run on this rule everywhere else: SEC Rule 204-2 enumerates the books and records a registered investment adviser must keep, examinations are conducted against those records, and broker-dealers carry a parallel obligation under FINRA Rule 4511. Estate-planning coordination is usually the newest service line in a practice, and usually the only one documented informally.

The reconstruction test

Pick a completed household and try to produce four records without relying on someone’s memory. Note what is available, what requires a support request and what the firm must keep elsewhere.

On the first question, most firms can show an engagement letter and a calendar full of meetings. Neither names the person who made the selection. Question two is where the file stops entirely, because a client clicking through a screen was unremarkable on the day it happened, so nothing captured it.

What the request looks like

Suppose a household completes a trust-based plan. Some years later the grantor dies. One adult child receives less than expected, hires a lawyer, and the lawyer sends the firm a preservation letter followed by a document request: all correspondence, drafts, the executed documents, and any record of how the documents were selected, with a date range and an instruction that nothing be deleted.

The executed documents are easy. The correspondence is an email export, including every scheduling message and whatever a colleague wrote in a hurry three years ago. The selection record shows whether the household chose its own plan, and it is the part of the request most firms cannot fill.

System-generated records can help a firm answer a later request. Their usefulness depends on the events captured, access to exports and retention. Test those capabilities with a sample file; do not assume a log covers every action or replaces the firm’s other required records.

Where the answers usually live

The record accumulates wherever the work happened:

• Email threads. What the household decided arrives as a message and stays there, interleaved with scheduling, searchable only by whoever still works there. Reply-all forks the thread, and the fork is the copy nobody kept.
• A shared drive. Final versions overwrite drafts. A file named trust-FINAL-v3.pdf establishes nothing about what v2 said or when v3 replaced it.
• Somebody who was there. The associate who sat in on the meetings, the junior advisor who has since left. A common answer to how a firm would reconstruct what happened, and the least durable one.
• A system nobody chose for this. A CRM note field, a task tool, a shared calendar. Records that exist as a by-product of something else and were never meant to be read back.

What a record has to establish

Actor attribution comes first. A log line reading "document created, actor: the firm" records that a document exists. A line reading "selection submitted, actor: the client" records the fact everything else depends on: the document-preparation framework rests on the client making the selections. The distinction is not new. In Janson v. LegalZoom, 802 F. Supp. 2d 1053 (W.D. Mo. 2011), a federal district court treated the sale of blank forms as lawful self-help but held that LegalZoom’s document preparation service went beyond self-help because of what its employees did after the customer finished the questionnaire, and denied LegalZoom summary judgment. Separately, the 2015 LegalZoom consent judgment with the North Carolina State Bar made review of each template by a North Carolina-licensed attorney a term of LegalZoom’s own operation in the state.

Then sequence, with timestamps that come from the system rather than from a filename. Then immutability: a log that anyone can edit after the fact carries the weight of an undated memo, and a log whose alterations would be detectable carries considerably more. Then retention past the life of the engagement, because the request tends to arrive after the household has moved on, and often after somebody has died.

The same properties convert into questions a firm can put to any platform in writing, where the answers become records themselves:

• When a client makes a selection, is the client logged as the actor, or does the event record the firm?
• Can an administrator at the vendor edit or delete an audit record, and would anyone be able to tell if they had?
• What exactly is captured at the moment a client accepts terms: the version, the timestamp, the IP address?
• Can the firm export a household’s full audit history itself, without asking the vendor to produce it?

How Bancroft builds the record

Bancroft records account, document and administrative events in audit records designed to make alteration detectable. Event coverage and export scope matter as much as the presence of a log. Ask for a sample of the records your firm will need and confirm retention and access after termination.

The consent-record design includes the user, timestamp, terms version, IP address and user agent. A record design is not a guarantee that every event was successfully captured. See review scope and security controls.

What the record does not do

A complete audit trail does not make conduct lawful, and it confers no protection or indemnity. Where a selection was not the household’s, a thorough log records that plainly, and the plain record serves the firm worse than a vague one would have.

There is also no public data on how often advisor estate-planning coordination draws a bar inquiry or a beneficiary dispute; bar proceedings are largely confidential, and nobody publishes denominators. The case for the record is cost rather than probability: a record either accumulates as the work happens or it does not exist, and no amount of diligence afterwards produces one.

Run the test on one completed household. If the answers have to come from an email search, that gap cannot be closed for households already completed. The record for the next household can start at intake.