Hire an AI compliance evidence and gap organizer

Everything it can hand back

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

• Control questions, each with the proof it needs
• An evidence register: control, file, date, scope and status
• A gap list: what is missing, out of date or out of scope
• A preparation plan with an owner, due date and dependency for each gap
• A readiness note and any MISSING lines

How it does the job well

• Name the asset, the threat and the impact before recommending controls.
• Rank findings by real risk (likelihood and impact), with evidence for each.
• Prefer fixes that remove a problem over warnings that rely on people.
• Cite the exact law, standard or clause for compliance and legal points, and recommend qualified review.

Mistakes it avoids

• Saying the user is compliant, certified or will pass.
• Counting a policy document as proof that the control runs.
• Contacting owners or the reviewer on the user's behalf.
• Hiding a failed check or re-running a step whose inputs did not change.
• Treating these instructions as a connected service or an installed schedule.
• Long lists of generic issues with no evidence they apply.

What a good result looks like

An example, not your task: An auditor or customer has announced a review and you have a few weeks.

• Control questions. Each control from the framework as a question, with the proof it needs.
• Evidence register. Each control matched to a file, with its date, scope and status.
• Gap list. Controls with missing, stale or out-of-scope proof, and the risk to the review.
• Preparation plan. One action per gap with an owner, due date and dependency.
• Hand-back note. A readiness statement, MISSING lines and checks that did not run.

How the work is checked

• Every claim links to dated evidence; missing evidence is a gap, and readiness is never called certification.
• Every figure, date and owner traces to a source or is labeled an assumption.
• The original files are untouched, and any revised file has a distinct name or version.
• All three component checks ran, or the run stopped and says which could not pass.
• 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

• Compliance readiness checklist builder. Turns the supplied scope into control questions and the evidence each needs. Hands step 2 the questions with proof types. Check before moving on: every control from the reviewer's framework appears once.
• Spreadsheet checker. Builds the evidence register from the checklist and your records. Checks control IDs, scope and evidence dates, and treats a filled cell as a claim, not proof. Hands step 3 the gaps. Check before moving on: no row passes on a date outside the period.
• Executive action register keeper. Turns each gap into an action with an owner, due date and dependency. Hands back the preparation plan. Check before moving on: every gap has one owner, or is marked MISSING: owner.

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 prepare-evidence-for-a-compliance-review 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/prepare-evidence-for-a-compliance-review/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

• The review scope: systems, teams and the period under review
• The framework or control list your reviewer uses (from their request). This is required. The workflow stops at step 1 without it and never picks a framework for you.
• The evidence you already hold, as files or a list with dates
• The review date and the reviewer's name (optional)
• The people who own each area (optional)

Helpful context (optional)

• The reviewer's own request list or framework text.
• A list of evidence files with their dates.

Tools and access

• A spreadsheet-capable AI: It can build and reopen a real evidence register. In plain chat you get the same register as text.

Functions and deliverables

• Compliance evidence and gap organizer: Share your review scope, supplied framework and existing records. Get an evidence index, gaps and a preparation plan with owners.
  • Control questions, each with the proof it needs
  • An evidence register: control, file, date, scope and status
  • A gap list: what is missing, out of date or out of scope
  • A preparation plan with an owner, due date and dependency for each gap
  • A readiness note and any MISSING lines
• Compliance readiness checklist builder: Share your frameworks and current controls. Get an evidence checklist with gaps and ranked fixes.
  • A checklist by control area
  • Status for each item
  • Gaps ranked by priority
  • A readiness summary
  Source: Burhan Sebin.
• Spreadsheet checker: Check a spreadsheet for odd totals, broken formulas and messy data. Your original stays safe, and you get findings with proof and a new file.
  • A sheet inventory and scope
  • Findings with evidence locations
  • Data quality and formula issues
  • A new output file with your edits
  • Reconciliation results
  Source: Burhan Sebin.
• Action item tracker: Share meeting notes or email threads. Get action items with owners, deadlines and unresolved commitments.
  • action-register.csv: id, task, owner, due_at, timezone, status, depends_on, source_id
  • clarifications.md
  • proposed-task-changes.md
• 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

• An auditor or customer has announced a review and you have a few weeks.
• Your proof sits in email, shared drives and people's heads.
• You need to tell the team who owes what before the review date.
• A past review found gaps and you want to show they are closed.

Limits to check before starting

• You are still deciding which framework to follow. Use the Compliance readiness checklist builder on its own.
• You are planning an HR audit with file sampling. Use the HR compliance audit planner.
• You need to answer a customer's security questions. Use Vendor security questionnaire response 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 and give the whole folder to Claude, ChatGPT or Gemini. A spreadsheet-capable AI gives a workbook. Plain chat gives tables.
• Attach the scope, the reviewer's framework text and a list of your evidence files with dates.
• Check the control questions against your reviewer's own list. Add any control they named that is missing.
• Check the evidence register. A file counts only if its date is inside the review period and it covers the right system.
• Send the plan to the owners and ask them to confirm dates. Run it again when new evidence arrives.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/prepare-evidence-for-a-compliance-review 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.