Candidate Talent Pool

Candidate Talent Pool defines a small prospect record for future recruiting needs. Its recommendation is a warm pool with consent and a re-engagement date, rather than an undirected resume archive. The proposed process adds a candidate, records consent, sets a permitted re-engagement date, and later revisits an open role. Reminder delivery is not implemented by this module.

The default is a recommendation. Advice is answered directly, reviews check a supplied process, and artifacts are built on request. Intake covers roles and vacancies, difficult-to-fill positions, sourcing practices, referrals and inbound candidates, retention duration, contact permission, consent to re-engage, existing CV storage, pool size, and the desired pool, tracker, or alert structure. Questions are asked one at a time only when missing facts change the output; unknowns remain unknown.

Use it for a talent-pool database, candidate tracker, recruiter pipeline spreadsheet, or a process for keeping candidates warm. It fits Growth stage in the Acquire layer. A request can be:

We keep losing good candidates we rejected 6 months ago.

It creates empty templates and does not source candidates, send outreach, provide automation, reminders, or synchronization, or compute payroll, tax, leave, or KPIs. Human legal and HR review remains necessary; consent is not inferred from a data field or an open role.

The seventeen fields cover Candidate Name and ID, Department, Email, Experience (Years), Last Contact, LinkedIn URL, Notes, Phone, Consent Status, Consent Date, Re-engage Date, Referred By, Skills, Source, Status, and Target Role. Experience is numeric, contact and consent dates retain date types, email and URL retain their types, and no relation fields are defined. Administrative statuses include Active, Contacted, Interested, Not Now, and Closed; they are not employability scores.

Consent Status has Not recorded, Granted, and Declined. Only recorded Granted consent unlocks a Re-engage Date. Otherwise leave the date empty, record Not recorded where applicable, and report how many records are blocked. A CV on file, one reply, a referral, public profile, or unrecorded verbal agreement is not blanket consent. Declined is final for re-contact and must not be silently reset to enlarge a list.

Additional guidance separates consent source, scope, date, expiry or review date, communication preference, and retention basis from skills and stage. Re-engagement outside the confirmed scope needs permission. Limit information to the recruiting purpose, restrict access by recruiting need, and keep rejection reasons factual and job-related. Do not encode protected characteristics or inferred health, family, or immigration details. A withdrawal stops outreach while retaining only policy-required minimum audit evidence.

Requested CSV, SQL DDL, JSON Schema, and Notion mapping share one list. CSV uses a UTF-8 byte order mark for Excel and needs date and number formatting; a workbook requires a specific request. Templates stay empty, with requested examples clearly synthetic.

Notion output goes to notion-manual-import. Manual output needs no connection; actual workspace writes require verified access, target, authorization, and successful tool evidence.

Sensitive review inputs are minimized and templates remain empty. Consequential privacy, legal and disciplinary cases require qualified human review.