The operating problem
Start with an updated delivery pipeline. A successful handoff produces a proposed allocation plan with overload and dependency flags. Define the accountable owner before connecting systems. Task estimates are planning assumptions, not a measure of professional worth or billable output. 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. Read approved demand
Collect scoped engagements, due dates, skill needs, and current task estimates.
2. Read available capacity
Use the firm-approved working calendar, leave, and assignment constraints without exposing private HR detail.
3. Identify bottlenecks
Compare demand and capacity by skill and period, keeping estimates visibly uncertain.
4. Propose assignments
Suggest options with an accountable manager reviewing priorities and independence constraints.
5. Publish the agreed plan
Record changes and notify owners; track actual effort to improve future estimates.
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 |
|---|---|---|
| task_id | task_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| skill_requirement | skill_requirement | Resolve the stable source reference in the correct client, entity, and engagement. |
| capacity_period | capacity_period | Validate the date, timezone, and approved reporting or review period. |
| allocation_decision | allocation_decision | Use the authorized owner or reviewed decision; unknown values stop the handoff. |
Acceptance checks
- Unavailable staff are not assigned.
- An estimate revision updates the bottleneck picture.
- 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.