Hire an AI restricted fund program handover writer

Everything it can hand back

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

• A summary of the fund's purpose, restrictions and reporting duties, with a section number for each
• A list of gaps where the evidence is missing or does not match the agreement
• A handover brief for the new owner, with status, deadlines and where records are kept
• A list of decisions that need the fund owner
• A list of facts still MISSING

How it does the job well

• Turn every request into owned actions: who, what and by when.
• Work from the real calendar, notes and lists. Never invent meetings, people or dates.
• Put the most important decision or deadline first, then the details.
• Prepare drafts and proposals. Sending, booking and changing records waits for approval.

Mistakes it avoids

• Losing commitments buried in long notes.
• Mixing confirmed facts with guesses about other people's plans.
• Adding process when a short checklist would do.

What a good result looks like

An example, not your task: A program manager is leaving and someone new takes over the fund.

• outputs/step-01-source-note-summariser.md. The fund's purpose, restrictions, reporting duties and evidence gaps, each with its agreement section.
• outputs/step-02-handover-note-writer.md. The new owner's brief, with time-critical items, deadlines, current activity, record locations and people.
• Decisions for the fund owner. Each open question that only the fund owner can settle, and why it matters.
• HAND-BACK SUMMARY. Files saved, sources used, MISSING lines, checks missed and one suggested next step.

How the work is checked

• Restrictions and reporting dates quote the agreement, with section numbers.
• No sentence allows or suggests a new use of the money.
• Every fact, figure and date traces to a source, or is marked as an assumption or MISSING:.
• No password, key or account number appears.
• 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

• Source note summariser. Reads the fund agreement and your records. Pulls out the purpose, each restriction, each reporting duty and each evidence gap, with the agreement section for each. Hands step 2 the rules index and the gaps. Check before moving on, each date and restriction matches the agreement text.
• Handover note writer. Writes the new owner's brief. It starts with what will go wrong if nobody acts, then the deadlines, current activity, where records live and the decisions for the fund owner. Never includes passwords. Check before you send it, nothing in the brief allows a new use of the money.

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 hand-over-a-restricted-fund-program 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/hand-over-a-restricted-fund-program/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 signed fund agreement, with any changes or side letters
• The reporting commitments and their due dates, if they are not in the agreement
• The program activities that were approved, such as a plan or budget
• Spending records or a ledger for the fund so far
• The name and role of the new program owner, and your key contacts

Helpful context (optional)

• Past reports sent to the funder.
• Emails where the funder allowed or refused a change.

Tools and access

• A chat AI that reads long documents: Fund agreements can run long, and every rule needs its section number. In plain chat, paste the relevant sections.
• Any good chat AI: Claude, ChatGPT and Gemini all handle a long source in one message. Claude takes the longest texts.
• Any good chat AI: A one-message note works in any strong chat AI.

Functions and deliverables

• Restricted fund program handover writer: Share the fund terms, spending records and owner details. Get a handover draft, duties to report and open decisions linked to sources.
  • A summary of the fund's purpose, restrictions and reporting duties, with a section number for each
  • A list of gaps where the evidence is missing or does not match the agreement
  • A handover brief for the new owner, with status, deadlines and where records are kept
  • A list of decisions that need the fund owner
  • A list of facts still MISSING
• Source note summariser: Paste an article, talk or chapter into this source note summariser. You get each claim, how well it is backed, the gaps and three quotes to keep.
  • Every claim with a quote and location, and the evidence behind each rated
  • The gaps and assumptions
  • What it adds to your question, three quotes to keep, and an 80-word summary
• 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
• Restricted grant cash tracker: Share grant cash movements and approved uses. Separate restricted money from cash available for general spending, and flag funding gaps.
  • Closing restricted cash
  • Closing total bank cash
  • Free cash: closing bank cash less closing restricted cash
  • A check that restricted cash does not exceed bank cash, and a flag if it does
  • A list of anything missing, and which results it blocked
• 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 program manager is leaving and someone new takes over the fund.
• The fund changes teams mid-year and nobody has read the agreement lately.
• A funder report is coming and the new owner does not know what it must cover.
• You have inherited a fund and cannot say what the money may be spent on.

Limits to check before starting

• The fund has no written agreement: get the terms in writing first. Until then, use the Handover note writer for a plain handover.
• Nothing restricts the money: use the Handover note writer on its own.
• You want to check that spending followed the agreement: use the Grant spending and evidence report preparer workflow.
• You need to know if a new use of the money is allowed: ask the fund owner or funder. A handover cannot approve it.

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 workflow pack and add it to Claude, ChatGPT or Gemini, in a chat that accepts files.
• Attach the agreement and your records. Say who is leaving, who is taking over and the date of the handover.
• Tell your AI to follow the pack and save each step's file.
• After step 1, compare its restrictions and dates with the agreement. A wrong date here carries into the brief.
• After step 2, check each decision on the list is one only the fund owner can make. Then give the brief to the new owner.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/hand-over-a-restricted-fund-program 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.