The operating problem
Start with a firm-approved new-year service cycle. A successful handoff produces a reviewed new-period checklist without inherited stale decisions. Define the accountable owner before connecting systems. Do not copy prior-year assumptions, authority, or access without review. 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. Select the source engagement
Record the previous period and the authorized next-period service scope.
2. Copy stable structure only
Carry forward checklist categories and task templates while excluding completed statuses and old approvals.
3. Flag changing facts
Ask staff to review contacts, entities, services, deadlines, software access, and data handling.
4. Approve the new-period setup
A responsible professional confirms the scope and ownership for the new year.
5. Open the new workflow
Create new request and task IDs with explicit links back to historical records.
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 |
|---|---|---|
| prior_engagement_id | prior_engagement_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| new_period | new_period | Validate the date, timezone, and approved reporting or review period. |
| scope_review_ref | scope_review_ref | Use the authorized owner or reviewed decision; unknown values stop the handoff. |
| rollover_manifest | rollover_manifest | Resolve the stable source reference in the correct client, entity, and engagement. |
Acceptance checks
- Old signoffs cannot satisfy new-period review.
- A changed client contact requires a permission check.
- 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.