The operating problem
A missing W-2 should not require an accountant to search three inboxes. Use a client-period checklist as the source of truth. A file upload is evidence of receipt, not proof that a document is complete or correct.
Use your own working copy
The free workbook for this process opens in a browser and works offline after download. It includes editable checks and notes, a text export, and a print view. It is a planning resource: it does not send messages, read account data, or run actions in business systems. No vendor account is needed to use the workbook.
Map the process
1. Receive a portal event
Capture submission ID, client ID, tax period, and an approved storage reference. Keep attachments in the designated portal; do not pass full PDFs through an email connector.
2. Reconcile the checklist
Map each received document to an explicit requirement. Route an unknown document type to staff instead of letting an AI classifier silently mark it complete.
3. Set a due-at timestamp
Store the next permitted contact time in a persistent queue. A scheduled job finds due records; avoid a long-running sleep inside a process run.
4. Re-read before reminding
Fetch the latest checklist, communication consent, and matter status. Stop if complete, paused, opted out, or already reminded within the configured interval.
5. Approve and record
Create a draft reminder listing document categories only. Staff approves the recipient and language. Store a correlation ID, sent timestamp, and delivery outcome.
Information to check
These reference fields describe the process. Use invented values while planning. Keep real records in an appropriate private system; the public website does not need them.
| Reference field | Working record | Check before progressing |
|---|---|---|
| submission_id | event_key | Unique source event; reject a duplicate |
| client_reference | client_id | Use a stable ID, not a name match |
| document_category | checklist_item | Staff resolves unknown classifications |
| secure_file_reference | portal_link | No public storage URL |
| next_contact_at | queue_due_at | Store UTC; apply recipient quiet hours |
Acceptance checks
- A repeated submission does not create a second reminder.
- Uploading the final document cancels an already queued reminder.
- An opted-out client never reaches the send step.
- A corrupt or unclassified upload enters the staff exception queue.
Walk through a successful example, a duplicate, a missing item, an incorrect match, and an interrupted handoff with synthetic records. Record the expected result, observed result, owner, and recovery action. Checklists record your work; checking a box does not establish that an external action happened.
Ownership and review
Name the person responsible for the process and the person who can resolve an exception. Define which decisions require qualified professional review. Use stable references, limit access to private records, and document when work must stop. Educational material does not establish legal, accounting, tax, security, or regulatory compliance.
Run a measured pilot
Choose a small, reversible sample. Measure handling time, waiting time, review, rework, and errors before changing the process. Include the effort of maintaining the new method. Expand only when the observed result meets your acceptance criteria; a longer checklist is not proof of improved performance.
Use the free workflow planner to define your next step, or compare the assumptions in the opportunity calculator.