Confirm the requester's identity, organization, contact route, intended recipient, purpose, questions, format, deadline, and authorization to collect the response. Ask which executive reference request intake decision or handoff this stage supports, then let the executive reference request owner collect requester identity, subject identity, purpose, consent, relationship scope, questions, format, deadline, policy route, drafter, approver, and delivery channel. For verify the request, distinguish confirmed facts from preferences, assumptions, estimates, and unresolved questions.
Apply verify the request in proportion to the executive reference request intake consequence and keep sensitive inputs in their approved system. The assistant may organize verified facts and approved wording but does not promise participation, invent an endorsement, disclose private information, or answer on the executive's behalf. The executive reference request owner should reject informal shortcuts that erase this boundary.
Before moving executive reference request intake forward, ask the executive reference request owner to compare executive and recipient needs with operating-owner and backup responsibilities. Review original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy for missing executive reference request intake context, access limits, timing consequences, and escalation triggers. Close verify the request with a next action that the executive reference request owner and an authorized backup can verify.
Confirm subject consent
Establish whether the person knows about the request and follow the organization's consent, employment, education, and privacy rules. Give executive reference request intake a visible state with terms defined by the executive reference request owner. The confirm subject consent label is credible only when it links to original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy.
Test one live executive reference request intake item before the executive reference request owner turns confirm subject consent into a broad rule. Employment, education, legal, regulated, confidential, or disputed requests should pause until the responsible people, legal, or policy owner provides direction. Record original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy so reviewers can separate the exception from a new default.
Define the relationship scope
Record how the executive knows the subject, which period and work are relevant, and which topics fall outside firsthand knowledge. For executive reference request intake, the executive reference request owner connects requester identity, subject identity, purpose, consent, relationship scope, questions, format, deadline, policy route, drafter, approver, and delivery channel to this step. Define the relationship scope ends when the executive reference request owner can show original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy.
Use original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy as the executive reference request intake trail for define the relationship scope. The executive reference request owner should check accuracy, authority, recipient clarity, and closure without using activity volume as a quality claim.
Before moving executive reference request intake forward, ask the executive reference request owner to compare executive and recipient needs with operating-owner and backup responsibilities. Review original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy for missing executive reference request intake context, access limits, timing consequences, and escalation triggers. Close define the relationship scope with a next action that the executive reference request owner and an authorized backup can verify.
Route policy questions
Send employment verification, legal forms, background checks, regulated statements, and confidential questions to the accountable specialist owner. The maintained executive reference request intake record names the executive reference request owner, source, state, and review point. Route policy questions should reduce ambiguity about requester identity, subject identity, purpose, consent, relationship scope, questions, format, deadline, policy route, drafter, approver, and delivery channel while preserving accountable authority.
A executive reference request intake handoff needs more than a sent message during route policy questions. Confirm that the executive reference request owner has requester identity, subject identity, purpose, consent, relationship scope, questions, format, deadline, policy route, drafter, approver, and delivery channel, along with the access, authority, and next action needed to proceed. Route disagreement under employment, education, legal, regulated, confidential, or disputed requests should pause until the responsible people, legal, or policy owner provides direction.
Prepare factual support
Collect only approved dates, roles, shared work, and examples that the executive can verify without adding promotional or predictive claims. Ask which executive reference request intake decision or handoff this stage supports, then let the executive reference request owner collect requester identity, subject identity, purpose, consent, relationship scope, questions, format, deadline, policy route, drafter, approver, and delivery channel. For prepare factual support, distinguish confirmed facts from preferences, assumptions, estimates, and unresolved questions.
Apply prepare factual support in proportion to the executive reference request intake consequence and keep sensitive inputs in their approved system. The assistant may organize verified facts and approved wording but does not promise participation, invent an endorsement, disclose private information, or answer on the executive's behalf. The executive reference request owner should reject informal shortcuts that erase this boundary.
Before moving executive reference request intake forward, ask the executive reference request owner to compare executive and recipient needs with operating-owner and backup responsibilities. Review original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy for missing executive reference request intake context, access limits, timing consequences, and escalation triggers. Close prepare factual support with a next action that the executive reference request owner and an authorized backup can verify.
Control drafting and approval
State who may draft, which words are the executive's, what must be reviewed, and how material changes return for renewed approval. Give executive reference request intake a visible state with terms defined by the executive reference request owner. The control drafting and approval label is credible only when it links to original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy.
Test one live executive reference request intake item before the executive reference request owner turns control drafting and approval into a broad rule. Employment, education, legal, regulated, confidential, or disputed requests should pause until the responsible people, legal, or policy owner provides direction. Record original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy so reviewers can separate the exception from a new default.
Deliver through the right channel
Use the verified recipient and approved format, protect attachments, and avoid copying the response to people without a valid purpose. For executive reference request intake, the executive reference request owner connects requester identity, subject identity, purpose, consent, relationship scope, questions, format, deadline, policy route, drafter, approver, and delivery channel to this step. Deliver through the right channel ends when the executive reference request owner can show original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy.
Use original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy as the executive reference request intake trail for deliver through the right channel. The executive reference request owner should check accuracy, authority, recipient clarity, and closure without using activity volume as a quality claim.
Before moving executive reference request intake forward, ask the executive reference request owner to compare executive and recipient needs with operating-owner and backup responsibilities. Review original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy for missing executive reference request intake context, access limits, timing consequences, and escalation triggers. Close deliver through the right channel with a next action that the executive reference request owner and an authorized backup can verify.
Close and retain
Record the final disposition, handle follow-up questions through the same owner, and retain or remove copies under the approved rule. The maintained executive reference request intake record names the executive reference request owner, source, state, and review point. Close and retain should reduce ambiguity about requester identity, subject identity, purpose, consent, relationship scope, questions, format, deadline, policy route, drafter, approver, and delivery channel while preserving accountable authority.
A executive reference request intake handoff needs more than a sent message during close and retain. Confirm that the executive reference request owner has requester identity, subject identity, purpose, consent, relationship scope, questions, format, deadline, policy route, drafter, approver, and delivery channel, along with the access, authority, and next action needed to proceed. Route disagreement under employment, education, legal, regulated, confidential, or disputed requests should pause until the responsible people, legal, or policy owner provides direction.
Put the workflow into practice
Test executive reference request intake with one current case and compare its controls with privacy framework. Connect the executive reference request owner to our guidance on contact protocol and tone guide, then confirm how those adjacent records hand work into this one.
Review executive reference request intake after employment, education, legal, regulated, confidential, or disputed requests should pause until the responsible people, legal, or policy owner provides direction. Keep the fields that help the executive reference request owner decide, act, verify, or recover, and remove entries that do not support original request, identity verification, consent record, policy disposition, approved scope, final wording, executive approval, delivery record, and retained copy. A dependable result protects executive attention while preserving the assistant may organize verified facts and approved wording but does not promise participation, invent an endorsement, disclose private information, or answer on the executive's behalf.