Talent Acquisition Specialists use this to send consistent stage-based rejections without rewriting from scratch for every requisition. Recruiting Managers rely on it to standardize team language so candidate experience doesn’t vary by recruiter. HR Business Partners use the SBI structure to keep messaging job-related and easier to defend when questions come back. Agency Recruiters apply it to deliver respectful feedback that protects the client relationship and avoids over-disclosure.

SaaS and tech teams benefit because multi-round hiring (screens, technical loops, panels) creates lots of rejection touchpoints that need consistent wording. Healthcare and regulated employers get value from the tighter compliance constraints, especially when candidate communications must stay strictly job-related. Financial services teams use SBI templates to reduce vague language and keep feedback aligned with documented criteria and audit expectations. High-volume retail and hospitality hiring teams use it to speed up messaging while still offering a respectful candidate experience at scale.

A typical prompt like “Write me a rejection email for a candidate” fails because it: lacks the SBI structure that forces job-relevant clarity, provides no constraints to avoid protected-class or personal references, ignores stage context (phone screen versus final round), produces generic filler like “we went another direction” instead of observable feedback, and misses the required balance of including a strength plus one improvement area. You end up with language that feels polite but invites follow-up questions because it doesn’t explain anything safely.

Yes, but you will customize it through the details you provide, since the prompt itself is a structured system. Add your hiring milestones, your role criteria, and your preferred voice by defining a clear BRAND_VOICE (for example: “warm, concise, straightforward, no corporate buzzwords”). You can also specify how much feedback to give at each stage, like “minimal closure at phone screen, SBI feedback only after onsite.” Follow-up prompt: “Using the same compliance constraints, rewrite these templates for BRAND_VOICE = [your voice] and milestones = [your stages], and keep each under 110 words.”

The biggest mistake is leaving BRAND_VOICE vague — instead of “professional,” try “calm, kind, direct; 6th–8th grade readability; no euphemisms.” Another common error is giving non-observable feedback like “you lacked leadership”; a better input is “In the stakeholder scenario, you did not outline decision criteria or a communication plan.” Teams also slip into risky comparisons (“another candidate was stronger”), so replace that with role-linked Impact (“this would slow onboarding for a role that requires independent execution in week one”). Finally, people over-share in early stages; set a rule like “no detailed SBI beyond one sentence until after interviews.”

This prompt isn’t ideal for teams that want to give fully personalized, line-by-line feedback to every candidate, because it intentionally avoids being overly specific in ways that can increase risk. It’s also not a fit if you have no documented role criteria yet, since SBI Impact needs something job-related to anchor to. And if you’re dealing with a sensitive dispute or a threatened claim, you should pause and route communications through counsel review instead of relying on templated language.