A document routing workflow a tax or CPA firm can actually run

When a file lands, someone or some rule has to answer four questions without guessing:

• What is it? (W-2, K-1, 1099-B, organizer, signed 8879, random photo)
• Whose year is it, and which client?
• Which folder does it live in, and who looks next?
• If any of that is unclear, where does it sit until a person decides?

If you cannot answer those, you do not have routing. You have a portal that is another inbox. Publication 583 wants electronic records indexed, stored, preserved, retrieved and reproduced in a legible form, with a complete and accurate record the IRS can get to. (Publication 583) A pile named "client uploads" fails that test the first time you cannot find last year's W-2.

Write the map on one page before you buy anything. Use these rows or your own names. The owner is a role, not a person who might be on leave. Client advisory services (CAS) files need an entity and a month, not only a tax year.

Name files so a stranger on your team can find them: Client_2025_W2_AcmeLogistics.pdf. Pretty names are optional. Searchable names are not. The collection list that tells you what should exist is in the document request system.

Keep the original bytes. A renamed copy, an extracted number, or a tool summary is not the record. Publication 583 applies every paper rule to the electronic system, including the duty to reproduce a complete, accurate, legible file. (Publication 583)

Publication 4557 tells tax professionals to limit access to people who need the file, encrypt files and messages that carry personally identifiable information, turn on multi factor authentication, keep an audit log of who did what and when, and back up to a place that is not sitting on the live network all day. Protecting taxpayer data is the law, and the FTC Safeguards Rule is the one the IRS points to. (Publication 4557)

Translate that into routing rules:

• Do not route a tax document through a personal Gmail rule that dumps it in a shared drive with no access log.
• Do not let a classifier replace the original with a stripped text file.
• Do not send the file to a second tool for "smarter naming" unless that tool is already in your security plan.
• If email is how a client insists on sending, treat it as the least safe path. TaxDome itself says requesting documents by email is not the most secure way, and attachments can be auto saved only into a client folder the client can view and edit. (Request docs from clients)

Most routing failures are not misses. They are confident mistakes. Build a queue that is allowed to be ugly:

The queue needs an owner every weekday in season. A queue with no owner is a drawer. Measure how long items sit, not how many files the tool "processed."

Search for "what to look for in a document routing workflow solution" and you get generic approval software. For a tax firm, ask these in writing. Keep the answers with the vendor file. If you are also buying an AI product, pair this with how to choose an AI tool for a CPA firm.

Publication 4557 also asks you to recognize phishing that pretends to be a tax software vendor or a cloud storage vendor. A routing tool that emails staff surprise links fails that on day one. (Publication 4557)

You may not need a new product. You may need a folder template and a habit.

In TaxDome, every client account has three top level locations: Private (firm only), Firm docs shared with client, and Client uploaded documents (where document requests land). Folder templates define the subfolders inside those, commonly by year and service. You can set a default template for new accounts, apply a template to existing ones, and apply a template automatically when a job enters a pipeline stage. Applying a template adds missing folders. It does not delete existing ones. Editing a template later does not update accounts until you apply it again. Matching is exact, including capital letters. Firm owners and admins have the rights by default. Other staff need Manage templates to change templates and Manage documents to apply them. Clients never see Private. (Folder templates explained)

TaxDome also lets you point a file request at a folder you specify, and lets organizers and client requests save uploads into a subfolder of the client upload area. Document checklists, sent through an organizer, make the client match each file to a named item. (Request docs from clients) That is collection plus a destination. It is still not a classifier. Someone has to notice the W-2 that landed in "other." The chasing build is in the TaxDome document chasing workflow.

If you use Karbon or Canopy, the same map applies. Put the destination in the request, not in someone's head. Drake Portals checklists and Liscio File Upload questions are the same map inside those products. See the Drake Tax documents and electronic signature workflow and the Liscio document request workflow. For the generic classification and exception design outside a tax firm, stay with the AI document routing workflow.

Download the evaluation checklist. It is the questions in this guide, with columns for the vendor answer, pass or fail, evidence, and who at the firm signed off. Fill one sheet per vendor. Run it against a messy packet: a corrected 1099, a photo of a W-2, a K-1, and a scan that belongs to two people.