Give a candidate clear facts before requesting a résumé

Candidates who receive vague outreach have reason to ask for facts before sharing a résumé. A recruiter should separate verified information from open questions, identify a source for each answer, and seek permission before profile submission. Salary, employer identity, work location, schedule, reporting line, and submission process each deserve a direct answer or a direct statement marking an answer as pending. Guessing wastes time when a later correction changes a person’s decision.

Start before a qualification call. Open a note with two sections. Place details approved by a client contact or shown in a current role brief in one section. Place questions requiring client confirmation in another. Write a date beside every verified detail. A range approved last month might no longer appear in a current brief. “Hybrid schedule” lacks enough detail unless a brief states office days, work location, or flexibility. A dated note helps you speak precisely instead of relying on memory.

Use plain labels during conversation. Say “confirmed” for a fact supported by a current client brief or named client contact. Say “pending” for information you asked a client to confirm. Say “not shared at this stage” when a client chose not to release a detail. Those labels make uncertainty visible without forcing a candidate to interpret vague wording. They also stop a recruiter from mixing an approved fact with a personal estimate about what a client might accept.

Before responding, check whether a candidate asked one question or several. A question about salary might sit beside questions about location, employer identity, or schedule. Answer each point separately. Do not make a broad statement such as “the role has strong compensation” when no approved range exists. Do not use a city name as a substitute for a work arrangement. A candidate needs words matching the source, especially where an unanswered detail affects whether a conversation deserves more time.

In a fictional practice situation, Jordan is a data analyst responding to an initial message. Jordan asks, “What is the salary range, and who is the employer? Earlier recruiters changed both details after our first call.” Recruiter Keisha checks her note before answering. The role brief confirms two office days each week at a named city office. No approved range appears in her brief. The client requested an initial discussion before employer disclosure. Keisha says, “Two office days each week are confirmed. I do not have approved salary wording yet. The employer name is not shared during this first discussion. I will not submit your profile without written permission.”

Jordan replies, “Two office days work for me. I need the range before I decide whether to spend time on a discussion.” Keisha does not offer a market range or predict whether a client will meet Jordan’s expectation. She replies, “I will ask the client HR contact for approved salary wording today and return by 3 p.m. tomorrow. If no answer arrives, I will send an update either way.” Her promise has an owner, request, and time. Jordan knows a next step without receiving an invented answer.

Record each exchange so another recruiter has a clear record. Keisha notes confirmed office attendance, Jordan’s request for salary information, employer disclosure limit, request sent to HR, and promised response time. She records no submission permission. Silence is not consent. Do not attach Jordan’s résumé to a client email while waiting for an answer. A profile should move only after a candidate has enough information for a meaningful choice and has given permission required by your process.

At 2:30 p.m. next day, HR replies with a range and authorizes employer disclosure before submission. Keisha sends Jordan a concise update: “The client approved a range of 84,000 to 96,000 for this role. The employer is Northfield Services. Two office days each week are confirmed. Would you like to discuss the role, or would you prefer no further contact?” She does not describe bonus plans, promotion paths, benefits, or manager style because no approved detail supports those subjects. Her message gives Jordan room for a decision without pressure.

Jordan says, “The range works. Please send the full role outline, then I will decide about a submission.” Keisha sends the approved outline and waits for review. After Jordan responds, she asks one consent question: “Do you give written permission for me to submit your résumé to Northfield Services for this role?” Keep submission permission tied to a named employer and role. A prior conversation about general opportunities does not answer a later question about a particular submission. Record date and exact permission wording after receipt.

Sometimes a client has no answer by a promised time. In a second fictional practice situation, Keisha receives no HR reply. She contacts Jordan at 3 p.m. and writes, “I have not received approved salary wording. I asked HR again and will update you by Friday at noon. I understand if you prefer to pause.” This response respects Jordan’s schedule and keeps a missing fact visible. Do not fill a gap with “competitive pay.” Do not turn delay into a test of enthusiasm. A candidate has every reason to wait for an answer or end contact.

Employer disclosure needs an honest path as well. A client might want a recruiter to assess interest before naming an organization. Tell a candidate directly: “The employer name is not released before an initial discussion. I understand if you do not want to continue without employer disclosure.” Give a real choice. A candidate who declines made an informed decision. Do not suggest secrecy is standard or imply a person lacks commitment. If a client later authorizes disclosure, return with exact name and repeat a consent question before submission.

Salary questions often lead to related questions. A candidate might ask whether a range includes a variable payment, whether work occurs in one office or several, or whether a title matches a current career level. Handle each question separately. Share approved facts. Mark open items pending. Send a client contact one focused question where possible, so a reply has a clear record. Your purpose is not to make every role sound attractive. Your purpose is to support an accurate decision.

Avoid asking for a résumé as a price for basic facts. A résumé contains personal work history, and candidates deserve enough role information before sharing one. If a candidate prefers a verbal discussion first, ask which information would help. If salary is a deciding point, do not redirect toward credentials or availability. Return to a client with the exact unanswered question. Respecting order of decisions creates a cleaner process for both sides and reduces later reversal.

For a fictional practice exercise, create a note for a product analyst role. Mark office attendance as confirmed at one day each week. Leave salary wording and employer disclosure pending. Ask a partner to play a candidate who says, “I will share my résumé after I know those two details.” Answer without estimates. Send a fictional client request at 10 a.m., promise an update by 10 a.m. next business day, then write your 9:55 a.m. follow up message for a missing reply and place your draft beside your request record.