Your copy. Your pace.

Tax document collection

Track outstanding tax documents from a secure intake portal, update a client checklist, and prepare reminders for staff approval. This blueprint separates document storage from reminder metadata, checks completion again before every nudge, and stops follow-ups when a client opts out or a staff member closes the request.

Planning workbook. This file helps you document a process. It does not connect to accounts, read records, send messages, or complete external actions. It works offline and sends no entries anywhere. Entries are not saved automatically; export or print a copy before closing. Avoid entering sensitive information.

1. Define the starting point

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.

Process owner and backup rolesWhat will count as complete?

Current handling time and exceptions

2. Walk through 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.

We have defined the owner, required information, and completion check for this step.Step 1 working notes

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.

We have defined the owner, required information, and completion check for this step.Step 2 working notes

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.

We have defined the owner, required information, and completion check for this step.Step 3 working notes

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.

We have defined the owner, required information, and completion check for this step.Step 4 working notes

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.

We have defined the owner, required information, and completion check for this step.Step 5 working notes

3. Check the information

Use invented references in this worksheet. Keep real documents and personal records in an appropriate private system.

Reference field	Working record	Check
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

Source of truth and access boundaries

4. Verify the process

Use synthetic examples. Mark a check only after recording what actually happened.

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.A named person can resolve an unclear or incorrect result.Work stops when the task is complete, withdrawn, or outside the agreed scope.A duplicate or interrupted handoff can be recovered without repeating a consequential action.Expected result, observed result, and recovery notes

5. Decide the next step

Your smallest reversible pilotReview date and decision

Retain qualified professional review for legal, accounting, tax, medical, financial, or other consequential decisions. This workbook does not certify compliance or guarantee results.