# Hiring handoff wait review

Use this without a Metix account. The files measure elapsed calendar time at a handoff. They do not search people, evaluate candidates, change a hiring bar, send messages, integrate with an ATS or predict time saved. All sample records are invented.

## Record the handoff

1. Define one observable readiness event: the evidence and permission needed for the next step are complete. An interview ending is not necessarily readiness for a decision if a scorecard is missing.
2. Copy the blank CSV. Use an internal handoff ID rather than a candidate name. Keep personal evidence in the employer's existing record system. Record the stage, the readiness timestamp, and when the next step actually started.
3. Set status to completed, open or unknown. Leave a missing timestamp empty. Identify the owner of the next action and the evidence that must remain. Record the reason for a gap only when it is known. A candidate's chosen date is not automatically employer delay.
4. Use ISO8601 with Z or an explicit UTC offset. Pin an observation cutoff before comparing records. The calculator uses UTC elapsed hours, including weekends and holidays; it does not calculate working hours or hands-on labor.

## Calculate locally

With Python 3 installed, run from this folder:

    python3 calculate.py fictional-handoffs.csv --as-of 2026-10-19T12:00:00Z

To save the output, redirect it to a different filename. The program does not edit the input and uses no network. The supplied fictional-results.csv is the output of that command. CSV files also open in ordinary spreadsheet software.

Completed hours = next step started minus readiness. Open age = cutoff minus readiness, and is reported in a separate column. Missing readiness or completion is labelled instead of filled with zero. Zero hours is valid only when two known timestamps coincide. A duplicate ID, missing offset, event after cutoff, reversed interval or open record with a completion timestamp stops the calculation without partial CSV output.

## Read the fictional cases

- A: Readiness means the screening evidence and permission to coordinate are complete. The next event is interview coordination starting, not an interview held. Friday October 16 at 16:00 UTC to Monday October 19 at 09:00 UTC is 65 calendar hours. It is not 65 hours of labor, and this example does not establish how much can be removed.
- B: Monday 09:00 to 11:00 is 2 completed hours.
- C: The offer evidence is ready for an authorized approver to review; the approval review has not started. This is not a completed approval. Friday 12:00 to the Monday 12:00 cutoff is 72 hours still open. Do not treat it as a completed duration or combine it into a completed-only average.
- D: The readiness event was not recorded. The result is unknown, not zero.
- E: The candidate chose a later conversation time. The completed interval is 70 hours; retain that reason rather than blaming a recruiter or pushing an earlier date.

These are separate handoffs across fictional cases, not five consecutive stages of one hire. Do not sum them into a time-to-hire total. Repeated or overlapping stages need their own event definitions. This worksheet does not infer delays from a completed-hire-only sample or choose a benchmark for you.

## Review one change

Inspect the evidence for the gap, confirm the owner, and agree one next action. Check that required scorecards, job-related assessment, candidate availability and employer approvals remain. Use comparable role definitions and the same cutoff/follow-up rules when observing another cohort. Track missing records and open cases beside completed ones. A shorter interval is not proof of hiring quality or a product effect.

Method reviewed November 6, 2026. This is an independent worksheet accompanying /blog/reduce-time-to-hire, not a vendor benchmark or customer case.
