When a client uploads a new document, does your team actually see it?
By Consaya Editorial — 2026-10-25
A reviewer closes an engagement, notes one unresolved question, hands the file to the preparer. Then the client uploads a replacement statement. It lands in the folder. The preparation team keeps working from yesterday's evidence.
The operational question isn't whether the upload succeeded. It's whether the change reached the person responsible for deciding what happens next.
Three things need to connect
The changed source, the work that may depend on it, and the practitioner who decides what it means. Most firms miss this middle step. They notify that a document arrived. They don't trace whether the notification landed on the right person or whether that person understands which task it affects.
You can test this before it costs you a filing deadline. Build a small fictional engagement with one supporting statement and one unresolved question. Use a dummy client name. Record which source version the reviewer considered and what the handoff actually accepted. Then introduce a replacement document with a clear version reference.
Ask a colleague who wasn't in the review to answer three questions without asking you: What changed? Which preparation step might need attention? Who decides whether the change matters? If they have to guess or reconstruct the engagement from scattered messages, your workflow has a gap.
Identify the source precisely
"New PDF received" tells you nothing. Record the document period, timestamp, which earlier version it replaces. Keep the distinction between the source file, any extracted value and a reviewer note separate. An old statement may need to stay in your records under retention policy, but that doesn't mean it should stay the source for the next step.
The IRS treats records as supporting return preparation and reported items. That's worth taking seriously. But retention policy and workflow process are different things. You need enough history that a team member can trace an important statement back to the source and version you intend to use, without relying on someone's recollection of why the old file is still there.
Connect the source to the work that depends on it
If the replacement statement differs from the original, the comparison the reviewer made may no longer hold. That's not a permission to let software change a tax conclusion automatically. It's a signal to keep that uncertainty visible until the authorized practitioner decides whether anything needs revisiting.
This is where AI summaries become a liability if no one checks their source reference. Fluent text doesn't prove the summary used the latest version.
Reopen the specific decision, not the whole engagement
Avoid a single fuzzy "complete" status. Say what was complete: document receipt, an evidence check, the draft preparation, or practitioner sign-off. A replacement might affect one stage without requiring every task to restart. Name the specific decision that needs review, its owner and the next action. For example: "Replacement statement received; the prior comparison needs reassessment by the assigned reviewer before this is accepted for preparation."
A reopened item is resolved by an accountable decision, not by making the warning disappear. The practitioner may determine the replacement has no effect on a particular conclusion. That's fine. Record it and the reason why.
Test the handoff itself
A notification proves a message was generated. It does not prove the right person accepted responsibility or that downstream work uses the intended evidence. During your fictional test, have the receiving team member explain the changed source, affected work, the unresolved question and who owns the next step. Check that person has the access they need. Record any point where the next person must guess.
Before filing season starts, ask a colleague to run this test. If that person can explain the replacement and the next decision without reconstructing the engagement from scattered chat messages or walking to someone's desk, the firm has a concrete basis for what works. If not, the exercise has identified where the next improvement belongs.
How Consaya fits
If a source document changes mid-engagement—a corrected bank statement, a revised invoice, a replaced tax authority notice—Consaya's job is to keep the books updated and ready to file. The decision about which evidence to use, when to reopen a review, and who owns that decision is yours to build into your process.