The Same Document Twice: Logging Duplicate Client Uploads for the AI Pass

Jane Doe uploads her bank statement to the Firm's portal. Later she attaches the same statement to an email, in case the upload didn't go through. The folder now holds the same document twice. In this method, the Preparer keeps logged duplicates outside the drafting folder.

That's the case this piece covers: duplicate client documents. In this method, a duplicate means a copy that is byte-for-byte or page-for-page the same as another copy, as checked by the Preparer. The Preparer lists each copy, compares the copies by hand, names a working copy in a copy log, and notes the others as duplicates of it. The comparison is a step a person at the Firm does; the drafting pass isn't relied on to find duplicates. Copies that differ in any way are not duplicates, and they go to the Firm's own steps for differing documents.

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 comparison checklist, a copy log layout, a client message, a marking table, a pre-review check, a Doe example and a line for the Firm's AI instructions.

Duplicates, replaced copies and differing documents

A corrected copy that takes the place of an earlier one is covered in marking the current copy of a statement. Here nothing replaces anything; the copies are the same.

Different documents that show different figures for one item are covered in when client documents disagree, and different documents behind one item in pairing entries from two source documents.

This case is narrower: one document, more than one copy, and no difference between the copies.

What counts as a duplicate, in this method

In this method, the Preparer checks for a duplicate when a document arrives more than once, as in these cases:

• The client uploads the same file more than once.
• The client sends the same document in two formats, such as a PDF and a photo of each page.
• The same document comes in by email and through the portal.

If the Preparer can't tell, the copy isn't logged as a duplicate, and the Preparer treats the copies as differing.

Comparing copies by hand

In this method, the Preparer reads the copies side by side against this checklist. The Firm can add its own lines.

• The issuer or sender name is the same, as printed.
• The account name or number is the same, as printed.
• The period shown on the pages is the same.
• The page count is the same.
• Each page matches its pair: headings, figures, dates and text, as printed.
• Neither copy carries a mark the other lacks: handwriting, a stamp, a highlight, a "corrected" or "revised" label, a cut-off edge.
• Every page is readable on each copy.

If any line doesn't hold, the copies are not duplicates. The Preparer logs them as differing and doesn't pick which copy is right.

The copy log

In this method, the Preparer keeps a copy log on the file index, in a layout the Firm can adapt.

Each copy gets its own line, the working copy included. The Preparer names the working copy; the duplicates stay in the file as they came in, outside the drafting folder.

This piece states no rule about how long copies are kept. Any further document steps follow the Firm's own policy.

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 folder with logged duplicates. A version to adapt:

"Working copy: [copy ID]. The copy log lists other copies of this document as duplicates; they are outside this folder. Cite each entry by working copy ID and page; the Preparer checks entries by hand."

The line is the Firm's wording, not a promise about what any drafting software does. The Preparer still checks each drafted entry against the page it cites.

Telling the client

A second copy can mean the client meant to send a different document. In this method, the Preparer can ask, as in the client question log. The Firm can adapt this message:

Hi Jane Doe, thanks for sending your documents. We received [document name, as printed] more than once: [how each copy arrived]. Our Preparer compared the copies page by page and they match, so we're working from one of them. If you meant to send a different document, could you send it through our usual upload? Thanks, [Preparer name] at [Firm]

If the Firm's own policy calls for other wording, the Firm's wording wins.

Marking entries

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

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

When copies turn out to differ

If the Preparer finds any difference, the Preparer changes the copy log status to "Differs from [copy ID]", notes what differs by page, and takes the copies to the Firm's own steps for differing documents. Entries that rest on those copies stay open for the Reviewer's decision.

If the client sends a different document, the Preparer indexes it like any other document, runs the drafting pass again on that document and checks the new entries against it.

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 copy of each document that arrived more than once has a copy log line.
• Each copy log line names how the copy arrived and who logged it.
• Each "Duplicate of" line names the copy it was compared with.
• The Firm's instructions hold a working-copy line for each document with logged duplicates.
• No logged duplicate sits in the drafting folder.
• No entry cites a logged duplicate without a mark set by hand.
• The copies on each "Differs from" line have gone to the Firm's steps for differing documents.

Who compares 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 document-handling step.

A mark or a copy log line 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 the copy log and decides what happens with each entry, and the Reviewer signs off on the whole file, copy log 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. Jane uploads a Doe Bank statement to the portal and later emails the same statement. She also sends a Doe Brokerage statement as a PDF and as phone photos of its pages.

Alex logs each copy with how it arrived. Alex reads the Doe Bank copies side by side against the checklist. Every line holds, so Alex names the portal copy the working copy and logs the email copy as its duplicate, outside the drafting folder.

Alex reads the Doe Brokerage copies. A photo shows a handwritten note in a margin that the PDF lacks. Alex logs the copies as differing, notes the page, and takes them to the Firm's steps for differing documents.

Alex adds the working-copy line to the Firm's instructions and runs the drafting pass on the folder. Alex checks Doe Bank entries against their cited working-copy pages and marks them "Working copy" by hand. Alex marks the entries from the Doe Brokerage copies "Copies differ, open" by hand.

Alex sends Jane the message about the Doe Bank statement, logs it, and notes her answer on the copy log.

Alex runs the pre-review check and sends the file to Pat. Pat reviews the marked entries and the copy log, 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.