Keep live tax work readable while it is still moving.
Tax Dashboard
Tax Dashboard keeps the active return legible across requests, receipts, routing, review, signatures, and client response. It gives the firm a working surface for what is happening now, so the real point of delay, ownership, and next action do not disappear into inboxes, side notes, portal status, and private memory. It is the operational control layer for high-volume individual tax delivery.
This is work in motion, not status reporting after the fact.
Live tax work becomes hardest to trust while it is active
The return exists. Documents have started arriving. Someone requested something from the client. A reviewer is waiting on one condition. A signature is still outstanding. An item is back with the preparer. Another is sitting in the portal. The problem is not that nothing is known. The problem is that what is known is scattered across too many places to hold the work together cleanly.
Once that happens, teams start re-reading the return through email, the DMS, portal activity, side trackers, and conversation. The return is moving, but the firm’s reading of it is partial and unstable.
The problem is rarely one tax application by itself. The real difficulty is the workflow between them. During tax season, requests, signatures, client documents, and status updates get scattered across vendor portals, email, and internal handoffs, leaving teams to manage by follow-up.
One return, carried all the way through
Tax Dashboard keeps the live chain attached while the return is being prepared, reviewed, signed, and filed.
Requests and receipts stay visible
Open items, missing documents, received documents, and client responses remain attached to the return instead of splitting across inboxes and side follow-up.
Routing and review do not go soft
The firm can see where the return is, who owns the next move, and whether the work is actually in preparation, review, waiting, or blocked.
Signatures and authorizations stay in the chain
8879s, e-file authorizations, and related client actions do not disappear into separate tracking logic the team has to reconstruct later.
The real blocker stays attached
The point of delay is visible on the return itself, not hidden inside a side message someone else now has to rediscover.
What the product governs in practice
Tax Dashboard brings the most fragile parts of individual tax delivery into one governed workflow, from client requests through signatures, routing, and exception handling.
Client requests and source documents
Keep questionnaires and client-submitted documents moving through one consistent workflow, even when they arrive through different channels.
generate organizers from CCH
send through SafeSend
capture documents that arrive through email as well as portal workflows
track what is complete, what is missing, and who owns the next step
route completed items toward the DMS on schedule
Engagement and consent documentation
Manage engagement letters and offshore consent forms with clear status and controlled follow-up.
generate engagement letters
generate offshore consent forms
send through DocuSign
track sent, signed, voided, and outstanding status
support resend and void actions when intervention is needed
Delivery status, routing, and exceptions
Keep delivery dependable with scheduled routing, visible exceptions, and one operating view for what needs attention next.
one control surface for requests, signatures, documents, and delivery status
scheduled exports from SafeSend and DocuSign
programmatic routing into the DMS with standardized handling
exceptions surfaced clearly with owners and next actions
audit-friendly visibility across the workflow
Permissions and controlled intervention
Give the firm broad visibility into status while keeping workflow actions in the right hands.
see-versus-do permissions
controlled resend, void, override, and upload actions
visibility without opening every action to every user
intervention when the workflow needs help without losing control
Scheduled DMS routing built for real firm conditions
Routing with real-world constraints in view
Completed items are exported from SafeSend and DocuSign and routed into the DMS on a scheduled sweep, along with status history. The workflow accounts for real-world constraints such as naming, formats, and vendor limitations, and surfaces exceptions so one edge case does not create invisible delay across the rest of the process.
Common targets include
Common targets include:
GoFileRoom
DocuWare
Email-aware intake matters
Tax Dashboard is also built around email-aware intake because client documents do not arrive one way. Even in firms with strong portal usage, important items still arrive through email. The workflow accounts for that reality so teams are not forced into manual downloading, re-uploading, and side tracking just to keep the process aligned.
What improves in practice
Operational improvements
less manual follow-up just to understand current status
fewer handoffs across portals, email, and the DMS
clearer ownership of what is missing, blocked, or ready to move
more reliable routing into the DMS with exceptions surfaced early
controlled actions for resend, void, overrides, and uploads
see-versus-do permissions that protect the workflow without slowing visibility
orchestration across existing tools instead of another disconnected system
Who benefits
Teams and roles
tax operations leaders responsible for workflow control across the season
admin teams coordinating requests, signatures, document intake, and routing
tax staff and reviewers who need clean status without chasing multiple systems
firm leadership focused on cleaner delivery control and stronger operational discipline
Typical implementation
1. Discovery
Confirm the firm’s current workflow, roles, routing rules, source systems, and exception patterns across CCH, SafeSend, DocuSign, the DMS, and email.
2. Pilot with a contained workflow
Start with one office, team, or return group and validate the full flow with real users, from requests and signatures through routing and exception handling.
3. Expand once the workflow is trusted
Broaden adoption as teams gain confidence in the status view, controls, routing, and exception handling, while refining dimensions, permissions, and operating views.
4. Continue refining as the firm evolves
Adjust workflow behavior over time as vendors, document requirements, policies, and seasonal operating needs change.
Not generic workflow tracking
Tax Dashboard is not a retrospective report about what happened to returns last week. It is a working surface for live tax work while requests, documents, review, signatures, and routing are still changing the condition of the return.
The firm does not need to replace its tax software, portal, DMS, or signature tools to regain readability. The problem is that the live chain across them is too easy to lose.
FAQ
Do we need to replace our current tax tools?
No. Tax Dashboard is designed to work across the tools the firm already uses. The goal is not to replace every application in the stack. It is to give the firm one governed workflow across requests, signatures, document intake, routing, and exceptions.
Is this only for 1040 returns?
Today, Tax Dashboard is focused on high-volume individual workflows, where fragmented status and manual coordination are especially costly.
Why do you emphasize email so much?
Because client documents do not arrive one way. Even in firms with strong portal usage, important items still arrive through email. Tax Dashboard accounts for that reality so teams are not forced into manual downloading, re-uploading, and side tracking just to keep the workflow aligned.
What issues does this help surface earlier?
Missing signatures, unsigned engagement letters, offshore consent gaps, routing failures, and unresolved exceptions become visible earlier instead of being discovered late through follow-up and side checking.
Which DMS systems are supported?
GoFileRoom and DocuWare are common targets. Other DMS platforms can be evaluated based on available APIs, connectors, and approved routing methods.
Can workflow, permissions, and statuses be configured to fit our firm?
Yes. Views, role-based permissions, status groupings, exception handling, and routing behavior can be configured to reflect how the firm actually operates.
How do you handle exceptions and manual edge cases?
Exceptions are surfaced clearly with ownership and next actions instead of disappearing into side work. The workflow also supports controlled intervention, such as resend, void, manual override, or upload, when a case requires human judgment.