Appendix C. Regulations

C1. Sourcing Mini-Regulation for a Single Role

Block Contents

Objective Find and verify relevant candidate pools against the approved search brief

Scope From intake meeting to handoff of a qualified candidate to the recruiter or client

Roles Sourcer, recruiter, client, hiring manager

Inputs Role description, business problem, mandatory requirements, constraints, feedback SLA

Steps Brief, portrait, market map, hypotheses, search, evaluation, contact, handoff, metrics

Timelines First brief before search; first calibration after 10–15 profiles; weekly update once per week

Exceptions Niche market, new introduction, missing feedback, changing must-have criteria

Metrics Viewed, saved, contacted, responses, interested responses, qualified, rejection reasons

Human Check All candidate decisions and all AI drafts are verified by a person

C2. Client Calibration Regulation

1. Before the search, agree on 3–5 mandatory criteria and the signs visible in a profile.

2. After the first 10–15 profiles, show not only strong profiles but also borderline examples.

3. Turn every rejection into a criterion: "which fact shows the risk?"

4. If a new criterion emerges, record it as a brief change.

5. If feedback takes longer than the agreed SLA, stop expanding the search and escalate the risk.

C3. Candidate Handoff Regulation

The handoff must include the source, hypothesis, facts on mandatory requirements, contact history, motivation, expectations, open questions and the recommended next step. Handing off "a profile link without context" is not allowed: such a handoff undermines the evidence-based nature of the process.

C4. ATS / CRM Cleanliness Regulation

1. Each candidate has an owner.

2. The candidate is linked to the correct role.

3. Source and hypothesis are recorded.

4. Stage is up to date.

5. Next action has a deadline.

6. Rejection reason is specific.

7. Duplicates are checked.

8. Communication history is visible to the next process participant.

9. Opt-out from communication is respected.

10. AI notes are not saved as fact without manual verification.