Define a duplicate in context
Start with examples from the practice process. A repeated upload for the same request may be a duplicate, while a similar document for another client entity or period may be valid new material. A fictional client might resend a file because they were unsure whether it arrived. The workflow should recognise that possibility without assuming every matching filename is the same submission. Define the identifiers and context staff use to decide. Keep the rule narrow enough that legitimate amendments and separate requests still reach review.
Preserve the original submission history
Keep the received message or upload linked to the document and the relevant request through the approved system. If the same file arrives again, retain enough history to explain that it was received twice. Avoid silently deleting evidence or replacing the first copy before review. The administrative record should show when material arrived and which request it was associated with. Do not use the most recent received time as proof that a document is the current approved version. A client may resend an older copy.
Distinguish amendments from exact repeats
A replacement may have a small but important difference, even if the name is unchanged. Give the reviewer access to the relevant versions and identify that an amendment is possible. Do not let automation decide the professional effect of the change. Ask the responsible person whether the new material supersedes, supplements or is unrelated to the earlier submission. Record that decision in the intake history. If the previous document has already moved into professional work, make that state visible before the replacement is routed further.
Prevent duplicate administrative tasks
Where the approved process identifies a repeat, link it to the existing open request rather than creating another independent chase or review task. Preserve any new message from the client, because the attachment may be unchanged while the explanation adds useful context. Do not mark the original work complete simply because a second copy arrived. If the matching result is uncertain, send it to a maintained review queue. One clear task with the submission history is more useful than several disconnected items that different staff may resolve differently.
Keep downstream actions outside the intake decision
A duplicate flag is an administrative signal, not authority to post, pay, lodge or alter accounting records. The responsible professional determines the appropriate treatment through the practice process. The intake workflow should provide the relevant references and current review state. If another system has already acted on a document, escalate the possible repeat with that context instead of attempting an automatic reversal. Keep uncertain outcomes visible. A decision to suppress a second notification must not be confused with a professional decision about the document itself.
Test genuine repeats and legitimate new material
Use fictional cases for an identical resend, changed contents under the same filename, similar documents for different entities and an older version resent later. Include a repeated attachment with a new explanatory message. Verify that valid new material reaches review and that known repeats do not create unnecessary tasks. Inspect the intake history and owner assignment. Review mistakes with the practice team before tightening matching rules. A lower duplicate count is not proof of improvement if the workflow also starts hiding documents that staff needed to see.