Redacted Client Documents: What the Draft Uses and What Waits for the Client

Jane Doe sends a brokerage statement with the account number blacked out. On another page, a black bar covers a line in the activity list, and a letter carries a name she has struck through by hand. Nothing here is blurred or cut off. The client chose to hide these parts.

In this method, the Preparer handles redacted client documents with a list. The Preparer lists each hidden field on it before the drafting pass runs on that document. The Firm instructs: draft from visible fields only. Where the file needs what a hidden field holds, the Preparer asks the client, and the entry stays open, marked by hand, for the client's answer and the Reviewer's decision.

The plugin drafts; the Firm's preparer prepares; the Reviewer signs off. Every step here is one the Firm writes and keeps, in whatever systems the Firm already uses, and the Firm can adapt the document-handling steps; the Reviewer's sign-off on the whole file stays as it is.

This piece gives a redaction row layout, a client message, a marking table, a pre-review check, a Doe example and a line for the Firm's AI instructions.

Hidden on purpose, hard to read, or won't open

Three cases can look alike at first. A poor scan or a cut-off edge is an accident, covered in when a source page can't be read.

A file that won't open at all is a different case, covered in client documents that need a password.

This piece is about a readable page where the client has hidden some fields. In this method, the Preparer doesn't try to read under a redaction or guess what it holds.

What counts as a hidden field, in this method

In this method, the Preparer treats a field as hidden when any of these is true:

• A bar, box or marker stroke covers text or figures that were printed there.
• Characters are replaced with symbols, such as a run of X's or asterisks, or only the last few characters show.
• Part of the page is covered or cut away by hand while the rest reads clearly.

If the Preparer can't tell whether a part was hidden or lost in the scan, the Preparer lists it here and asks the client which it is.

Listing hidden fields before the pass

In this method, the Preparer adds a redaction row to the file index for each hidden field, before the drafting pass runs on that document. The Firm can add this layout to the index it already keeps.

The row records where the field is and how it's labelled, not a guess at what it holds. "Needed for the file?" is the Preparer's note; the Reviewer sees it with the rest of the row.

In this method, the Preparer keeps the client's redacted copy as it came in. Where it's kept, and who sees it, is for the Firm's own policy to decide.

A line for the Firm's AI instructions

In this method, the Firm adds a line, in its own words, to its instructions for the drafting pass on a redacted document. A version to adapt:

"Redacted: [document, copy ID]. Draft only from fields that show on the page and cite nothing to a hidden field; the Preparer checks and marks entries by hand."

The line is the Firm's wording, not a promise about what any drafting software does. The Preparer still checks each entry drafted from the document against the page and its redaction rows.

Asking the client

In this method, where a row says yes or "can't tell", the Preparer asks the client, as in the client question log. The Firm can adapt this message:

Hi Jane, thanks for the documents you sent. Some parts of [document] are covered. For your file, we'd like to know what [field] on [page] shows. You can tell us in a reply, send a copy that shows that part through our usual upload, or let us know if you'd rather not, and we'll talk it through. Thanks, [Preparer name] at [Firm]

The message names fields marked yes or "can't tell". If the Firm's own policy calls for other wording, the Firm's wording wins.

Marking entries drafted from a redacted document

In this method, the Preparer marks by hand, in the entry's note, every entry drafted from a redacted document. The Firm can rename the marks.

Every mark stays on its entry for the Reviewer's decision.

When the client answers

In this method, the Preparer puts the message reference under "Client asked". If the client sends a copy that shows the field, the Preparer gives it its own row on the file index and checks it like any other document. The redacted copy keeps its rows.

If the client answers in a message, the Preparer notes the message reference on the entry and marks it "Client answered" for the Reviewer. If the client would rather not say, the entry stays "Hidden field, open" with the client's answer noted for the Reviewer, and what the Firm does next is for the Firm's own policy to decide.

The pre-review check

In this method, the Preparer reads the file against this check before it goes to the Reviewer. The Firm can add its own lines.

• Each hidden field on a redacted document has a redaction row.
• Each redaction row says whether the field is needed for the file and who listed it.
• Each row marked yes or "can't tell" has a client message.
• The Firm's instructions hold a redaction line for each redacted document in the drafting folder.
• No entry cites a hidden field as its source.
• Entries drafted from redacted documents carry marks set by hand.
• Any entry marked "Client answered" has a note for the Reviewer with the client's answer and where it came from.

Who lists and who decides

The Firm names people for the document-handling steps; the Reviewer decides on entries and signs off. People at the Firm do every step.

A mark or a redaction row tells the Reviewer where to look. It isn't a sign-off and doesn't stand in for one. The Reviewer sees every marked entry and redaction row and decides what happens with each entry, and the Reviewer signs off on the whole file, redaction rows included. No file is done without the Reviewer's sign-off.

A Doe example

The names and file below are made up for illustration.

Jane Doe is a synthetic client of the Firm. Alex Doe is the Preparer and Pat Doe is the Reviewer. Among Jane's documents is a brokerage statement.

Alex reads the statement before the drafting pass. The account number shows only its last few characters, and a black bar covers a line in the activity list, with the line's heading left showing. Alex adds a redaction row for the account number, noted as not needed for the file, and another for the covered line, noted as "can't tell".

Alex adds the redaction line to the Firm's instructions, and the drafting pass runs on the folder. Alex checks the entries drafted from the statement against the page and marks them visible fields only, by hand. The activity list isn't whole without the covered line, so Alex notes an open entry for it and marks it hidden field, open, by hand.

Alex sends Jane the message about the covered line. Jane sends a copy with that line showing. Alex gives the copy its own row on the file index, adds redaction rows for anything still hidden on it, adds a redaction line for it to the Firm's instructions, and notes Jane's reply reference under "Client asked". The drafting pass runs on the new copy. Alex checks the redrafted entry against it and marks it fuller copy in, by hand, with a note of what changed.

Alex runs the pre-review check and sends the file to Pat. Pat reviews the marked entries and the redaction rows, including the account-number row, decides what happens with each entry, and signs off on the whole file.

Where TracePrep fits

We've built a TracePrep plugin that drafts these steps in your Firm's workflow, while your preparer decides and your Reviewer signs off. Join the waitlist and we'll tell you when plugin access opens.

Get on the list for plugin access

This is general information, not tax or legal advice. In TracePrep's workflow, the plugin drafts, the Firm's preparer prepares, and the Firm's Reviewer signs off. Access to the plugin is by waitlist. Keep client data inside the systems your Firm has approved.