The operating problem
Start with a prior-year return uploaded to the approved portal. A successful handoff produces a staff-reviewed list of source documents needed for the new period. Define the accountable owner before connecting systems. Prior-year information is a starting point, not a determination of current filing requirements. A source event is a request to evaluate the current state; it is not permission to make an irreversible change.
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. Identify client and period
Match stable client ID and tax year without relying on filename alone.
2. Preserve the source
Store the restricted source reference and checksum; flag unreadable or incomplete pages.
3. Draft a carry-forward checklist
Extract candidate schedules and related entities with source-page references, leaving requirements unconfirmed.
4. Review current-year relevance
A preparer adjusts for changed facts, services, and applicable requirements.
5. Release the request list
Send only the approved document categories through the client portal and track receipt.
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 |
|---|---|---|
| client_id | client_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| tax_year | tax_year | Resolve the stable source reference in the correct client, entity, and engagement. |
| source_page | source_page | Resolve the stable source reference in the correct client, entity, and engagement. |
| approved_requirement_id | approved_requirement_id | Resolve the stable source reference in the correct client, entity, and engagement. |
Acceptance checks
- A missing page blocks a complete intake status.
- A prior-year schedule cannot become a current requirement without review.
- A repeated source event creates only one current review task.
- A changed source version invalidates an earlier approval.
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.