Outreach States the Requisition Behind It

Every outbound message names the requisition it is sent against and its state — approved and open, or a pool record against a forecast — and the pool records opened against a forecast are answered on the day planning decides it.

Intervention I-009 Actor: recruiter process Scope: organizational Cost: low Evidence: supported

On the canonical path

Published with its terms on the page — The posting states the compensation band, the location rules, the stages the process has and roughly how long each takes. It comes down when the search ends.

This entry is one of the things that holds that commitment up.

What it looks like when this intervention is in place

Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.

The first message, and what it was attached to reconstruction

Subject: Two outreach templates, one week apart

day 0 Recruiter Req 5512, approved, open since 4 May, level L4. This is sent against that requisition — if you reply, that is the process you enter.
day 7 Recruiter No requisition yet. This is a pool record against a Q3 forecast; planning decides on 12 September and you get the outcome either way.
day 7 Candidate Understood — the second one I will answer in September.
12 Sep Recruiter Planning outcome: the forecast moved to Q1. The pool record is closed and I am not holding it open.

What to notice: Two templates instead of one. Whoever reads either of them knows which of the two conversations they are in before spending anything on it.

What this targets

Expected effects

B-014's pass condition is stated in the first message: whether a reply attaches to an authorised requisition or to a pool is part of what is sent
M-016 becomes datable — a conversation held against an unapproved forecast carries the planning date it depends on
The silence after a speculative conversation acquires a bound: the planning decision goes to the records opened against that forecast

What to measure

unattached_outreach_rate
pool_record_age_days
planning_decision_notice_rate

From each side

The same entry from inside each position that meets it: what reaches them, what it means from there, and what happens next given what they control.

Recruiter

What reaches them: Two outreach templates in the sequencer, and the field on the contact record that decides which one goes out.
What it means from there: The reply rate on the pool template is not the reply rate on the requisition template, and both are counted against the same outreach target.
What happens next: Sends the template the record's state selects, and books the planning date as the day the pool records opened against that forecast are answered.

Candidate

What reaches them: A first message that says which of the two it is, with a requisition number on it or a planning date.
What it means from there: A conversation against a forecast and a live process are separable before answering, and the silence that follows a deferred forecast has a date on it.
What happens next: Answers both, and schedules rounds against the one with a requisition behind it.

Employer policy

What reaches them: Outreach going out under a template that names the approval state of headcount the approval cycle has not decided.
What it means from there: A forecast named outside the company is a planning signal leaving the approval cycle before that cycle has settled anything.
What happens next: Decides which forecasts may be named in outreach and which may only be described as a pool, and that decision is the boundary the templates are written inside.

Share card png This page as markdown json