Skip to content
The 72 Hour Protocol

A new hire’s first task: how to pick it and how to check it

Published Friday 13 November 2026 by 3D CODED LIMITED

The first deliverable is the centre of a 72-hour plan. It turns a start date into evidence: by hour 72 there is a real piece of work and an agreed way to say whether it passed.

What makes a good first task

  • It is real. Someone in the team would otherwise do it, and its output gets used.
  • It fits the time. About a day of effort, so it can be assigned in the second phase and checked in the third.
  • It uses the day-one accesses. If it needs a system, that system is on the access list for hours 0–24.
  • It has a clear owner for checking. One named person decides pass or fail.
  • It can be checked. Someone else could look at the output and agree on the result.

Examples by role

Illustrations only; adapt them to your own work.

  • Operations: process the ten oldest open orders and note what slowed them down.
  • Customer support: answer a set of real tickets using the team’s templates, reviewed before sending.
  • Sales: research a short list of existing accounts and log a next step for each in the CRM.
  • Software: fix a small, already-triaged bug and get the change through code review.
  • Finance: reconcile one week of transactions in a test or review copy.
  • Marketing: draft one email or social post from an approved brief, ready for sign-off.

Writing the checks

Two to five checks is usually enough. Each one is a sentence that is either true or false about the output: a count, a standard met, a deadline, or a named review passed. Share them with the new starter before they begin, so they know exactly what “done” means.

If it fails

Record the fail and the reason, then look at the earlier phases. If an access was late or the brief changed, the plan failed before the person did. Fix the cause, agree a new checkpoint, and keep the record so the next start goes better.

Related guides

General information, not legal or HR advice.