Job Handover Checklist: Inventory to Working Solo

チーム運営・人事

Job Handover Checklist: Inventory to Working Solo

For the person leaving a role and the person taking it over, opened on day one of the handover and used until it closes. The whiteboard holds the goal and exit criteria, a frequency-versus-key-person matrix for deciding what to transfer first, a grid of the material each type of work needs, and the five steps from inventory to working solo. The task board moves work from inventory through documentation, review and shadowing, and starts with four parent tasks - map the work, write it down, work side by side, and hand over - each with its own subtasks.

0 いいね 0 コピー 作者: WeProcess
handover knowledge transfer documentation offboarding onboarding
無料登録してこのテンプレートを使う

無料登録すると、マーケットプレイスからこのテンプレートをコピーして使えます

ホワイトボード プレビュー

プレビュー表示中 Job Handover Checklist: Inventory to Working Solo

ホワイトボード プレビュー

1. What This Handover Has to Achieve 2. What to Transfer First (frequency ... Time bomb (rare, one person) Start here (frequent, one person) Leave for later (rare, shared) Already shared (frequent, shared) 3. Type of Work x Material Needed (bl... 4. Five Steps per Task (run them one ... 5. Every Doc Must Say 6. What Gets Left Behind 7. Where the Successor Got Stuck Job Handover Chec... How to use: 1. Li... Goal & done Steps & criteria Risks & gaps Notes & quest... GoalBy the end of May, the successor runs the daily and monthly work solo, using the docs alone. How to run itShow it, do it together, then watch them do it. Anything explained out loud gets written into the doc. What done looks like- One full cycle completed solo- Someone else can follow the doc- Contacts told about the change Usually missedOnce-a-year jobs / what to do in an outage / access tied to a personal account / unwritten judgment calls 縦軸: Key-person ri... The annual renewal nobody remembers, known only to you. Write the doc and put it in a shared calendar first. Runs every day and only one person knows how. Take this first and leave real time for shadowing and solo runs. Comes up occasionally and anyone can do it. Keep it on the list, point to where it lives, skip the detailed doc. Daily work several people can already do. Hand over the existing doc and mention only what has changed. Procedure doc Judgment & ex... Contacts & ac... Daily routine Opening checklistKeep screenshots alongside the steps Where to draw the line between answering and escalating Shared inbox account and forwarding rules Monthly close Month-end close steps (2nd business day) What to check, in order, when figures don't match Finance contact / accounting system access Outages & exc... First-response flow and who to notify in an outage The threshold for escalating rather than retrying Vendor support line / after-hours emergency contact 1. InventoryList everything you do, then rank it by frequency and key-person risk. 2. DocumentWrite up the top items first. Include the reasoning so less needs explaining out loud. 3. ShadowRun the real work while they watch, and fold their questions into the doc as they come. 4. Solo runThey complete a full cycle alone. You step back and only help where they get stuck. 5. Follow upStay reachable for two weeks after the switch and add each new question to the doc. When it runs and how often Which systems, and what access they need The rule to follow when it's a close call How to undo it if it goes wrong Files on a personal laptop or account Outside contacts only you deal with Work that runs once a year Judgment calls waved off as "you'll pick it up" Note the exact step where they stopped Anywhere they guessed and carried on Add shadowing questions the same day
100%

ドラッグで移動・ホイールで拡大縮小

タスクボードの内容

Inventory 16件

Map the work
Write it down
Work side by side
Hand over for real
List every task
Log frequency & time
Place on the matrix
Document the routine
Capture judgment
Cover the exceptions
Book the sessions
Show the real work
Fix gaps in the doc
Let them run it solo
Transfer the access
Notify stakeholders

Documenting 0件

In Review 0件

Shadowing 0件

Done 0件