Before the first handoff

Check the handoff before you give someone the task.

Use one small task lane. Check the scope, source of truth, examples, decision owner, review time, access limits, pause rule, and backup plan before day one.

Check this handoffCheck the SOP instead
Checks8

The basics a new person needs before starting.

Results4

Pause, prepare, test, or start with review.

Data savedNone

Answers stay in this browser tab.

Handoff check

Score what is written down.

This is a planning check, not a safety guarantee. Keep manager-only decisions and sensitive actions out of the first task until the right controls are in place.

Narrow task scope

Can you name one small task lane instead of a whole role?

Start with a repeatable task that has a clear start and finish.
Source of truth

Is there one current SOP, folder, or approved source for the work?

The person should not have to reconcile old chat messages or scattered files.
Finished examples

Can you show a few acceptable finished examples?

Examples make the standard visible before the first task starts.
Decision owner

Is one person named to answer questions and approve exceptions?

A task can stall when nobody owns decisions.
Review time

Has a reviewer protected time for the first work samples?

Review time needs a place on the calendar before work begins.
Access limits

Are the needed accounts, permission limits, and access owner written down?

Do not grant broad access just to get the first task moving.
Stop rule

Does the person know when to pause and ask before acting?

Money, customer promises, access, legal, payroll, and unusual cases need clear pause rules.
Change and backup plan

Is there a way to update the handoff and cover the task if the owner is away?

A handoff changes after real work begins. Name where updates live and who can cover.

Your answers stay in this browser tab. This tool does not save or submit them.

How to use the result

Start narrow, then learn from the first samples.

A clear handoff does not remove the need for review. Use the first few outputs to tighten the SOP, fix access gaps, and make pause rules clearer.

  1. Choose one narrow task lane.
  2. Answer the eight written-handoff checks.
  3. Fix the missing controls before the first task starts.
  4. Test a small batch and update the handoff from real questions and misses.