Create a source-preserving entry check for role brief

The operational risk around role brief

Most role brief 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. The cost shows up later as a reopened case, an unexplained slate completion change, or a correction that takes longer than the original task. 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. A familiar vendor, member, candidate, or client name is not evidence that the underlying role brief value is still valid.

Evidence map for role brief

In executive hiring, role brief often begins as a small favor from executive recruiter, which makes it easy to skip the evidence that would let someone else reconstruct the decision. The team may also overstate loop completion, because a closed status is counted before the candidate slate and the destination update are verified. Treat the role brief as a closed loop rather than a message: every action needs a source, a boundary, a destination, and a time. The operator should be able to point to the exact field in the candidate portal that will change, not only to the message that requested the change.

Decision rights for role brief

If candidate supplies the instruction, keep the instruction and the underlying candidate slate together rather than replacing one with a summary of the other. A candidate slate that arrives after the action can still be useful, but it must be marked late and linked to the correction it supports. After the conflict is resolved, add a short correction entry to the role brief log and link it to both source versions. A late candidate slate is still evidence, but it should not be presented as if it existed at the time of the first decision.

Daily workflow for role brief

Start the evidence map by naming the field in the interview loop tracker that the role brief action is supposed to change. Keep the original interview loop plan and the corrected version side by side, with the reason for the change and the person who approved it. If the interview loop tracker and the interview loop plan disagree, stop the dependent action and record both values with the time each was observed. A source that cannot be opened by the reviewer is not a usable source, even if the operator can see it on their screen.

Exception handling for role brief

For role brief, the governing source is the assessment platform; a note in the queue is only a pointer to that source. If the work sample contains sensitive data, store it in the approved location and record only the minimum reference needed for the role brief review. If the assessment platform and the work sample disagree, stop the dependent action and record both values with the time each was observed. The evidence map should show which fields are required, which are conditional, and which may be marked unavailable.

Close and verify role brief

Write the role brief boundary in plain language: which systems the operator may touch, which fields may change, and which questions must go back to board sponsor. If the operator discovers that the request falls outside the approved scope, pause the work and route the scope question before touching the interview loop tracker. A verbal approval can be recorded as a lead, but the operator should confirm it in the approved channel before changing the interview loop tracker. A standing approval should have a limit, a review date, and a clear description of the role brief work it covers.

Review cadence for role brief

The approver should see the evidence packet, not a paraphrase that removes the conflict or the missing work sample. 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. The approval record should point to the work sample that was reviewed, not only to the request that started the work. For high-risk role brief work, require a second reviewer who is not the person who prepared the packet.

Start with the cases that affect unapproved offer, then

Start with the cases that affect unapproved offer, then move to routine requests; age alone is not the only priority signal. When the next step belongs to candidate, write the request and the due time instead of leaving the case in a waiting state. Do not carry an item forward without a dated next action; an unexplained carryover is an exception, not a plan. Use a queue view that shows owner, age, next action, and missing evidence in one screen.

Start the role brief review by opening the reference

Start the role brief review by opening the reference log, sorting the oldest unresolved item, and checking the reference packet before reading the latest summary. A status update should describe a verifiable event, not a feeling about progress; link the event to the reference log or the reference packet. Record any correction made during the day and link it to the original role brief record. When a case moves between owners, require an acknowledgment before the old owner stops watching it.

Before adding a new role brief item, check whether

Before adding a new role brief item, check whether the request already exists under another name or channel. A status update should describe a verifiable event, not a feeling about progress; link the event to the offer approval system or the onboarding plan. Record any correction made during the day and link it to the original role brief record. Use the same role brief status values across owners so the daily count means the same thing to everyone.

An exception is not a generic failure; name

An exception is not a generic failure; name the evidence problem so the team can fix the source instead of blaming the operator. An escalation that ends in silence should remain open; silence is not approval. If the exception affects weak 90-day plan, pause the dependent action until board sponsor decides and the decision is recorded. A workaround used during an outage in the reference log should have an expiry time and a reconciliation owner.

When stale role brief is involved, use the highest

When stale role brief is involved, use the highest escalation path even if the role brief request looks routine. Keep the escalation in the role brief case so the response is visible to the next reviewer. If the same stop trigger appears repeatedly, change the intake rule or the onboarding plan requirement instead of coaching around it. Do not close an exception because the customer stopped replying; record the last contact and the next attempt.

Classify exceptions by whether the work can continue, must

Classify exceptions by whether the work can continue, must pause, or needs an immediate owner decision. When the decision is urgent, call out the consequence of waiting and the last safe time to act. A stop-work rule should name the trigger, the person who can release the work, and the evidence needed to restart. Keep a separate escalation log for items that required candidate, so response time can be reviewed.

A sent message, a closed ticket, or a verbal

A sent message, a closed ticket, or a verbal yes is not proof that the role brief outcome reached the record. The reviewer should be able to trace the role brief from the original request to the final field without opening a personal inbox. Track reopen rate with a denominator; a raw count without the number of closures overstates or hides the problem. If the destination is a downstream team, keep the role brief open until that team acknowledges receipt.

Use the same close definition for routine and exception

Use the same close definition for routine and exception cases so the candidate withdrawal rate does not improve by redefining completion. When the role brief is sensitive, record the approved reference and the access location rather than copying the content into the queue. A reopened case should show what changed, who noticed it, and which earlier decision is now in question. Closed cases should remain searchable by object, owner, date, and source so a later correction can find them.

Include a case where the owner said no

Include a case where the owner said no or asked for more evidence; those decisions show whether the boundary is working. Report open cases by age and dependency, not only the total, because a stable total can hide an aging tail. When the same gap appears twice, change the intake field, the approval rule, or the executive search CRM permission instead of repeating the coaching. Choose the sample from the queue export before the meeting so the discussion cannot drift to memorable cases.

Keep the sample small enough to finish and large

Keep the sample small enough to finish and large enough to expose a repeated gap. Track loop completion with a clear denominator and a review owner; a count without context is not a control. Review the action after two cycles and report what moved, what did not, and what remains unknown. Track the number of sampled cases, the number with missing evidence, and the number reopened after review.

Frequently asked questions