Check conflicts before submitting a candidate profile

Pause before sending a candidate profile to a client. The pause gives a candidate room to identify a prior relationship, a personal concern, or a role limitation before materials leave your control. The purpose is not an investigation into private history. The purpose is a clear submission choice and a clean route for concerns outside a recruiter’s role. Fast movement feels useful during a competitive search, yet an unapproved submission creates confusion for everyone involved.

Start by explaining the opportunity in plain terms. Name the employer, work location when shared, title, core duties, and known hiring contact only when each detail is ready for discussion. Then ask directly, “Are you comfortable with me sharing your profile for this role?” A candidate needs enough context for a meaningful answer. “I have an opening fitting your experience” leaves too much unknown. A precise role description gives the person a real choice about where their information goes.

Keep conflict questions narrow. Ask whether the candidate sees any concern connected to prior work, a relationship, or an agreement related to the opportunity. Do not request agreement documents, personal explanations, or details unrelated to a submission decision. A candidate might know who they want to consult. Your job is to provide time and a clear next step, not to interpret terms, weigh risk, or press for an immediate answer.

Here is a fictional practice conversation. Dev is considering a maintenance supervisor role with Northwood Manufacturing. He tells Morgan, his recruiter, “I worked with Northwood two years ago. Would a restriction stop me from applying?” Morgan replies, “I do not interpret agreements or tell people what action follows from one. I will hold your profile while you decide whether to seek advice from someone you trust.” Dev adds, “I know one manager on the team.” Morgan asks, “Would you like me to avoid mentioning your relationship when I speak with Northwood?” Her question centers Dev’s permission rather than the reason behind a relationship.

Dev asks for one day to review his situation. Morgan records only what supports follow through: “Candidate requested time before submission. Follow up requested Thursday.” She does not describe a possible agreement, name the relationship, or record her personal view of an outcome. Sensitive explanation in a general recruiting system travels farther than necessary and might influence a later decision. A short process note is more accurate and easier for a colleague to understand.

When a client asks for a profile quickly, return to the candidate’s decision. Morgan says, “I have discussed a possible candidate whose profile is under review. I will share materials after I receive permission.” Her update gives the client a status without exposing a private concern. Do not say a candidate is hesitating because of a restriction. Do not identify prior work or a mutual connection. A client needs timing information, not background detail, while a candidate decides.

Ask a client about process without assuming a result. Morgan might ask, “If a candidate raises a possible prior relationship after consent, who handles any disclosure question?” Northwood might name an internal contact or say no special route exists. Record the answer as client process information. Do not tell Dev a client contact resolves his personal question. Advice about an agreement belongs with a person Dev chooses for such advice or with an appropriate internal contact.

Consent has a defined scope. Permission to discuss a role does not automatically include permission to share a résumé, contact a reference, mention a mutual connection, or submit materials for another opening. Confirm a new action when scope changes. Morgan writes, “Northwood asked whether your scheduling software experience is current. Are you comfortable with me sharing your answer and updated résumé?” Dev has a clear choice. Morgan’s notes then show exactly which materials and information he approved.

Timing needs equal care. “Check back next week” is not approval for a submission today. Enter the exact date in a reminder. If a candidate gives no reply on the agreed date, send one neutral message. “You asked me to reconnect today about Northwood. Would you like more time, or do you want me to close this opportunity?” Silence is not agreement. If Dev requests more time, Morgan updates the reminder and sends the client a status note only when such an update is needed.

Mutual contacts often create avoidable urgency. A hiring manager might text, “Send Jordan over. We worked together before.” The message does not remove Jordan’s right to decide. Morgan replies, “I will speak with Jordan first and return after I know whether Jordan wants consideration.” She avoids confirming availability, interest, or a connection. A familiar name should not shorten a candidate’s decision window or invite disclosure before consent.

Once permission arrives, prepare a focused handoff. Confirm employer, role, approved materials, and anything the candidate asked you to omit. Review the profile for old contact information, stale work history, and notes meant only for internal use. Send the client a submission tied to the role. Private context is not useful color. Morgan’s internal record reads, “Dev approved submission for maintenance supervisor role. Current résumé approved Thursday.” The client receives the approved profile and role relevant information.

Keep a decision trail in call notes. Include discussion date, employer named, role discussed, materials approved, requested return date, and client process contact when one exists. Leave out theories, diagnoses, agreement interpretation, and details unrelated to an action. When a candidate shares more than a recruiter needs, acknowledge the concern and redirect. Morgan says, “Thank you for telling me. You do not need to give details. Would you like time before submission, or do you want to proceed?” The response keeps attention on a decision within the conversation.

Use a consistent check before every submission. Compare the client name on the message with the employer named to the candidate. Compare attached materials with materials approved by the candidate. Look for a consent note with a date and scope. If an item is missing, stop and ask a direct question rather than relying on a previous conversation about another role. A ten minute pause at this point is often easier than repairing a mistaken submission after a client forwards a profile.

In the fictional example, Dev replies Thursday morning. He says he wants Morgan to submit his current résumé and mention his scheduling software work, while leaving out his former manager connection. Morgan repeats the scope back to him in one sentence. Dev confirms. Morgan sends a focused profile to Northwood at 2:00 p.m., records the approved materials and omission in her note, and replies to the manager without mentioning Dev’s prior relationship.