Stop duplicate client document requests

Decide whether two requests concern the same requirement

Someone has to find it, explain the mistake and rebuild confidence in your process. Check the actual gap before the next reminder goes out.

A complete client folder still leaves someone turning supplier invoices into spreadsheet rows. That is the step ParseMill handles: upload invoice PDFs, review extracted details and line items beside the source, then download Excel. Keep document requests and engagement tracking in your existing process.

Compare the client/entity, covered period, account or transaction reference, and purpose of the request. Similar wording or the same dollar amount is not enough. Two September statements for different accounts are distinct requirements. A revised invoice and its earlier version may need comparison rather than a second request.

Choose one authoritative record for each requirement. Other queues should link to it and show who owns the next client contact. This is a recommended coordination method, not a claim that every product automatically deduplicates requests.

Use a decision table before combining requests

Synthetic example: North Pier Studio is an invented client. Copy these administrative cases into your review log and adapt them.

Keep both references when combining conversations. Closing a duplicate request record should not delete its message history or change any accounting transaction. Assign uncertain matches for review.

Inspect existing request threads before writing another

Start in the system where the gap was identified. Intuit documents transaction-linked information requests, visible request/reply states, and completion and reopening of a request. For a QuickBooks transaction question, inspect that existing conversation before creating a separate receipt chase elsewhere. Confirm the feature and permissions in your account.

Then check communication channels used by the team. Canopy's client-request guide explains that a direct notification-email reply goes to the sender, while an in-request comment notifies the assigned member. Check both routes when sender and assignee differ.

Record the original request reference, last client response, current owner and next follow-up date in the shared view. Avoid copying sensitive document contents into every system merely to prove that a request exists.

Apply a short check immediately before sending

1. Confirm the requirement is still open and still within the agreed scope. Check whether a reviewer accepted evidence or withdrew the requirement.
2. Check recent uploads, request comments and the agreed email route. Mark received-but-unreviewed material for staff review instead of calling it missing.
3. Read the latest promise or explanation. Respect a recorded follow-up date unless the owner has a reason to change it.
4. Confirm who sends the next message. In a manual process, record “Sam preparing follow-up” with a timestamp before another staff member begins the same action.
5. Refresh the item once more before sending, then record the actual outcome and message reference. Preparing a draft is not evidence that it was sent.

A manual reservation is a coordination cue, not a technical lock. Agree how another person takes over an abandoned draft, and retain the handoff. If several tools can send, identify the active reminder path and pause or close redundant paths through their supported controls. Do not assume an update in one tool has changed another.

Recover clearly when the client has already received two asks

First inspect both requests and confirm whether they genuinely concern the same item. Choose the surviving conversation, attach the other reference and stop its separate follow-up. If an automatic message may already be queued, check what your system lets you cancel and inspect the outcome.

Copyable wording for a confirmed duplicate: “We sent two requests for the same September card statement. Please use request R41; no second upload is needed. We have closed the separate follow-up. If you already uploaded it elsewhere, tell us the upload reference and we'll check it before asking again.” Only state that the follow-up is closed after confirming that action.

Record the cause: competing owners, stale review status, an outside-channel reply or two active reminder processes. Correct that cause rather than simply asking staff to be more careful.

Test the control with four small cases

Use synthetic records to test simultaneous staff drafts, an upload just before a reminder, a client promise for a later date and two same-amount transactions. The expected outcomes differ: one sender, staff review, a dated wait and separate identity checks. Record which tool and person must take each action.

During an ordinary cycle, count confirmed duplicate asks against all document asks, plus staff minutes spent checking and correcting them. Keep suspected duplicates separate until reviewed. A lower request count alone is not success if needed evidence stops being collected.

Use the workflow audit checklist to record those cases. If cross-system status checks remain a repeated burden, bring the measured step to a document-chasing workflow review. The review can assess fit; implementation scope and any fee are agreed separately.

Questions about this workflow