Write a backup-owner plan for reference packet

The operational risk around reference packet

Most reference packet problems in executive hiring start before the work is done: the request is accepted without a source, a deadline, or a clear boundary around what the operator may change. A single missing interview loop plan can turn a routine reference packet request into a search through messages, spreadsheets, and memory, which is exactly when the team is most likely to guess. The control should make the reference packet path readable from the request, the interview loop plan, the named owner, the decision, and the confirmation in the reference log. When the team reviews 90-day milestone, it should ask which cases are excluded from the count and why. For this October 28 pass, Hire Executive Team should record which reference packet exception was paused and who released it.

The reference packet queue rarely fails in a dramatic way; it usually drifts when a familiar request arrives and the operator copies the previous outcome instead of reopening the offer approval system. That gap creates rework, weakens candidate withdrawal rate, and makes it hard to tell whether the outcome was authorized or merely convenient. The record can be short, but it must be specific enough for a second reviewer to repeat the check without asking the original operator what happened. The risk is highest when the offer approval system looks current but the work sample behind it was never opened. The reference packet review at Hire Executive Team should state whether the work sample was current on October 28.

Evidence map for reference packet

The source of truth may be a system, a signed document, or an approved message, but the team should name it once and use the same definition every day. A work sample that arrives after the action can still be useful, but it must be marked late and linked to the correction it supports. Resolve the conflict by naming the authoritative source, the owner who decided, and the correction applied to the offer approval system. Keep the work sample in the approved repository and link it to the reference packet case instead of attaching it to a personal message. On October 28, Hire Executive Team should compare the reference packet queue count with the slate completion denominator.

Start the evidence map by naming the field in the executive search CRM that the reference packet action is supposed to change. When the reference packet is missing, write missing rather than leaving the field blank; missing, unavailable, and confirmed negative are different states. Resolve the conflict by naming the authoritative source, the owner who decided, and the correction applied to the executive search CRM. When the requester supplies a correction, keep the original request and the corrected value in the same reference packet history. The October 28 reference packet note should distinguish a missing reference packet from a confirmed negative.

The reference packet evidence set should include the request, the onboarding plan, the owner decision, the action taken, and the final value in the candidate portal. Keep the original onboarding plan and the corrected version side by side, with the reason for the change and the person who approved it. After the conflict is resolved, add a short correction entry to the reference packet log and link it to both source versions. The evidence map should show which fields are required, which are conditional, and which may be marked unavailable. At Hire Executive Team, record the October 28 reference packet correction and link it to the original source.

Decision rights for reference packet

The operator can make the reference packet usable, but should not invent the rationale for an approval that board sponsor never gave. A decision right is not the same as system access; the operator may be able to edit a field without being authorized to decide its value. An approval that cannot be linked to a specific reference packet case is too vague to support the destination change. The approval record should not be a forwarded thread with ten replies; summarize the decision and link the evidence. The board sponsor decision on reference packet should be dated October 28 and linked to the reference packet.

The operator can make the onboarding plan usable, but should not invent the rationale for an approval that executive recruiter never gave. A decision right is not the same as system access; the operator may be able to edit a field without being authorized to decide its value. An approval that cannot be linked to a specific reference packet case is too vague to support the destination change. A standing approval should have a limit, a review date, and a clear description of the reference packet work it covers. For the October 28 sample, Hire Executive Team should include one reference packet case that crossed owners.

Daily workflow for reference packet

Before adding a new reference packet item, check whether the request already exists under another name or channel. For each open reference packet, record the source, the onboarding plan, the decision, and the destination field before moving to the next item. Close the day by checking that each completed reference packet has a destination update in the candidate portal and a confirmation for the requester. A daily stand-up should review exceptions and aging items, not read every completed ticket aloud. The October 28 reference packet close should name the destination field, the approver, and the 90-day milestone check.

Open the reference packet queue in the interview loop tracker and mark every item with the current owner, the next action, and the time it is due. Use the candidate withdrawal rate field to flag a possible exception, but do not let the flag replace the evidence review. Do not carry an item forward without a dated next action; an unexplained carryover is an exception, not a plan. A case with no next action should be treated as an exception even if its status is marked in progress. At Hire Executive Team, the October 28 reference packet review should name the backup owner and the coverage window.

Use the same reference packet queue for new work, corrections, and reopened cases so the daily count reflects the real load. Keep the reference packet case note short enough to read during the day and specific enough to survive a weekly review. If a handoff is pending, name the receiving role and the time by which acknowledgment is expected. A daily stand-up should review exceptions and aging items, not read every completed ticket aloud. The October 28 reference packet exception log should show the reason code, owner, and release decision.

Exception handling for reference packet

Track repeated exceptions separately from one-off errors; a pattern may point to a form, a queue rule, or a permissions problem. After the decision, link the response to the destination change and close the exception with the reason it occurred. If the exception affects weak 90-day plan, pause the dependent action until board sponsor decides and the decision is recorded. The escalation packet should be short enough to read on a phone and complete enough to decide without a meeting. For the October 28 audit walkthrough, Hire Executive Team should be able to open the role brief from the case.

Track repeated exceptions separately from one-off errors; a pattern may point to a form, a queue rule, or a permissions problem. After the decision, link the response to the destination change and close the exception with the reason it occurred. When the request conflicts with policy or the approved scope, the operator should route it rather than negotiate a workaround in the queue. The escalation packet should be short enough to read on a phone and complete enough to decide without a meeting. The October 28 reference packet recovery test should record the restore point and the loop completion result.

Classify exceptions by whether the work can continue, must pause, or needs an immediate owner decision. Send the exception to the named owner with the interview loop plan attached and a specific question, not a general request to review. A stop-work rule should name the trigger, the person who can release the work, and the evidence needed to restart. Reason codes should be short enough to use at the queue and specific enough to route the case to the right owner. For the October 28 review at Hire Executive Team, log the reference packet check with the interview loop plan and the reference completion result.

Close and verify reference packet

Close reference packet only when the destination field in the assessment platform shows the approved change and the candidate slate supports it. When the candidate slate is sensitive, record the approved reference and the access location rather than copying the content into the queue. If the correction affects stale role brief, notify candidate before the next dependent action. A quality reviewer should be able to reproduce the close from the source and the approval without reading the operator’s inbox. The October 28 control note for Hire Executive Team should name the reference packet source, the owner, and the next review time.

Use the same close definition for routine and exception cases so the offer cycle does not improve by redefining completion. A quality check that only reads the close note cannot detect a destination that never changed. Track reopen rate with a denominator; a raw count without the number of closures overstates or hides the problem. Closed cases should remain searchable by object, owner, date, and source so a later correction can find them. At Hire Executive Team, keep the interview loop plan attached to the reference packet case and record the offer cycle observation date.

Review cadence for reference packet

Use the same checklist each week so 90-day milestone can be compared without renegotiating the definition. Compare 90-day milestone before and after a process change, using the same definitions and observation window. Review the action after two cycles and report what moved, what did not, and what remains unknown. When a measure improves, check whether the definition, the sample, or the queue mix changed. The October 28 evidence trail for reference packet should show the source version and the board sponsor decision.

Use the same checklist each week so candidate withdrawal rate can be compared without renegotiating the definition. Review the exception mix each month; a rising missing-evidence count may be an intake problem rather than an operator problem. When the same gap appears twice, change the intake field, the approval rule, or the offer approval system permission instead of repeating the coaching. Choose the sample from the queue export before the meeting so the discussion cannot drift to memorable cases. For this October 28 pass, Hire Executive Team should record which reference packet exception was paused and who released it.

Frequently asked questions