Dated Funding Certification Before the Final Round

Carry a funding-certified-through date on every requisition, refuse to schedule a final round unless that date covers the expected start, and release the countersignature on a live certification rather than on a second approval.

Intervention I-015 Actor: employer policy Scope: organizational Cost: medium Evidence: hypothesis

On the canonical path

Approval already exists — Headcount was signed before the role was published, so this step is a countersignature rather than a second decision. If the budget goes, the search closes and everyone inside it is told.

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 requisition, with the funding date in it reconstruction

Title: req #5120 · Senior Backend Engineer

funding_certified_through: 30 November · certified by finance 12 August
d0 Final round requested — the scheduler reads the field: the certified date covers the expected start date. Round booked.
d0 Scheduling message to the candidate: this requisition is funded through 30 November, and that is the date the approval behind it expires.
d21 Contract issued · countersignature released on a live certification, with no second approval step.
Where a division freeze revokes the certification: req #5120 flips to a dated paused state and every candidate in flight is written to on that date.

What to notice: The date is one field. What it does is move the approval from after the panel to before the scheduler, and give the recruiter a date to quote where the pending row had none.

What this targets

Expected effects

B-010 is passed before the final round is scheduled: the certification date is in the requisition before the panel sits, rather than after it recommends
M-007 meets a requisition whose funded-through date is either live or lapsed; where a freeze lands mid-loop the requisition changes to a dated state and every candidate in flight is written to on that date
B-012 stops carrying a funding decision: the countersignature is blocked while the certification has lapsed and released while it is live

What to measure

panel_to_offer_latency_days
requisition_funding_lapse_rate
countersignature_latency_days

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.

Employer policy

What reaches them: A certification with an expiry on every requisition, and a quarterly review in which each line already carries the date it runs out.
What it means from there: Optionality narrows: a requisition can no longer sit in pending while the quarter is decided, because pending now blocks the scheduler rather than the offer.
What happens next: Sets the certification horizon and who may re-certify, and decides whether a lapsed date pauses the requisition or closes it.

Recruiter

What reaches them: The funded-through date as a field in the requisition, and a scheduler that refuses a final round when the date does not cover the expected start.
What it means from there: A date exists to quote where the pending row had none; the cost is that some final rounds cannot be booked at all.
What happens next: Quotes the date when scheduling, and where the certification lapses mid-loop, sends the dated notice instead of waiting for the row to move.

Candidate

What reaches them: A scheduling message naming the date the funding behind the requisition expires, and, where it lapses, a dated notice saying paused or closed.
What it means from there: The interval after a panel that went well has a stated cause and a boundary: the wait turns on a certification date rather than on the rounds already completed.
What happens next: Weighs that date against the other processes in flight, and stops holding capacity for this one once the notice says closed.

Share card png This page as markdown json