Hire an AI volunteer training clearance reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• An induction checklist for each role, tied to your own rules
• A status for each volunteer and requirement, such as evidenced, attendance only, missing or overdue
• A practice plan with supervised practice for each role
• A list of supervision gaps
• A short handover note when a supervisor changes
• A review log for your next review

How it does the job well

• Attendance at a session is not clearance and is not a demonstrated skill. Record it as "Attendance only" unless the rule says attendance is enough.
• Do not invent records, dates, sign-offs or requirements.
• Keep personal data to what the review needs. Do not copy sensitive details into any file.
• Access and responsibilities stay within the approved role.
• Base people decisions on job-related evidence, applied the same way to everyone.
• Write in plain, respectful language the person affected could read.
• Keep personal data to what the task needs, and handle it privately.

Mistakes it avoids

• Treating attendance as clearance.
• Adding safeguarding rules the organisation did not approve.
• Copying sensitive personal details into outputs or logs.
• Describing a status file as a clearance record.
• Biased wording in job ads, reviews or interview questions.
• Plans with no owner, timing or way to check progress.

What a good result looks like

An example, not your task: A new volunteer role is approved, or an existing role changes.

• induction-checklist.md. Numbered requirements for each role, each tied to the rule it comes from.
• induction-status.md. Each volunteer's status for each requirement, with the record behind it and the next step.
• practice-plan.md. What each volunteer should demonstrate in supervised practice, who watches and when.
• supervision-gaps.md. Volunteers, shifts or roles with no supervisor, with options for you to decide.
• handover-note.md. Only when a supervisor changes. What the volunteer has shown and what is still open.
• review-log.md. Missing facts, checks not done and the state for the next review.

How the work is checked

• Criteria are written down before people are assessed.
• Every plan has milestones and owners.
• Sensitive steps are marked for human and legal review.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Read the last state. It keeps the role version, requirement IDs, evidence seen and sign-off status, without sensitive detail. The first run sets a baseline.
• Check what changed. A review runs when an approved role or required evidence changes, or when you ask for one.
• Build the checklist per role. It turns your approved rules into numbered requirements for joining, briefing, access, supervision and escalation. It adds no rule you did not supply.
• Set a status for each requirement. Each one is evidenced, attendance only, missing, overdue or ready for sign-off. Nobody is marked cleared.
• Plan practice and spot gaps. It plans supervised practice for each role and lists volunteers or shifts with no supervisor.
• Write a handover if needed. When a supervisor changes, it lists what the volunteer has shown and what is still open.
• Save the review. It records what changed and what is missing for next time.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id volunteer-induction-evidence-review-assistant only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/volunteer-induction-evidence-review-assistant/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your volunteer roles and what each one does
• Your approved conduct, safeguarding and induction rules for each role
• Records of what each volunteer has done, with dates and who signed it off
• Who supervises whom, and when
• The name or role of the person who signs off clearance
• Your last review file (optional)

Helpful context (optional)

• Your volunteer handbook or code of conduct.
• Your shift or rota list, so supervision gaps show up by shift.
• The sign-off dates your group already holds.

Tools and access

• Claude, ChatGPT or Gemini with file upload: It reads your rules, your records and your last review together.
• Claude, ChatGPT or Gemini with file support: They read the pasted text or files and keep each step's result as a file. None of them can run a lesson, a class or a check for you.
• Any good chat AI: A one-message note works in any strong chat AI.

Functions and deliverables

• Volunteer training clearance reviewer: Review volunteer training and practice records. Get supervision gaps and handover notes that keep missing clearance visible.
  • An induction checklist for each role, tied to your own rules
  • A status for each volunteer and requirement, such as evidenced, attendance only, missing or overdue
  • A practice plan with supervised practice for each role
  • A list of supervision gaps
  • A short handover note when a supervisor changes
  • A review log for your next review
• Volunteer onboarding checklist writer: Plan how volunteers join and train. Get a checklist, supervised practice and a clear record of missing checks.
  • An induction procedure for joining, role briefing, access, supervision, escalation and exit, with who does each step
  • A checklist with one row per stage, who signs off and what evidence is kept
  • A plan for role-specific demonstrations and supervised practice
  • A list of supervision gaps: roles with no named supervisor or no cover
  • A clear note of what is not yet checked, such as safeguarding clearance
• Handover note writer: Turn a brain dump into a handover note. The person covering your work sees what breaks first and what is due, and can act on day one.
  • Time bombs first, each with a date and an action
  • What is due, live work with next steps, and where things live
  • The people and how to deal with them, what to leave alone, how to reach you
• AI session handover note writer: Finish or pause a chat. Get a short handover note with progress, open work, file references and suggested skills for the next session.
  • A one-page note with the goal, what is done and what is open
  • The first step for the next chat
  • Pointers to files and links, not copied text
  • A list of skills the next chat should use
  • A line confirming keys, passwords and personal details were left out
  Source: Matt Pocock.
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• A new volunteer role is approved, or an existing role changes.
• You need to know who has finished induction and who has not, before a shift or an event.
• A supervisor is leaving and the volunteers need a clean handover.
• A trustee, funder or partner asks how you induct volunteers.

Limits to check before starting

• You have no induction checklist yet. Use the Volunteer onboarding checklist writer workflow.
• You need a decision on whether someone is safe to volunteer. Your named safeguarding lead makes that call, not an AI.
• You only need a handover note for one supervisor change. Use the Handover note writer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI. If you cannot add it, paste SKILL.md into a new chat.
• Attach your role descriptions and your approved induction and safeguarding rules. Say who signs off clearance.
• Add your records using initials or an ID for each volunteer. Do not paste background check results or health details.
• Say "Review induction evidence by role. Do not mark anyone cleared." Your AI asks once for anything missing.
• Read induction-status.md first. Check each "attendance only" and "overdue" line against your own records.
• Give the status file to your named sign-off person. Only they record clearance. Keep review-log.md for next time.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/volunteer-induction-evidence-review-assistant for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.