A small museum should treat accreditation as an evidence-tracking job, not a writing job. Copy the scheme body's requirements into one spreadsheet, record which document proves each one, and use AI to find gaps, draft policies from what you already do and log dated trustee approvals. AI prepares the paperwork; trustees approve it, and practice must match it.
The usual failure is a polished policy that describes a museum you are not yet: a documentation procedure nobody follows, or a disposal rule that does not match what happened last year. One published standard asks you to show that you follow your documentation procedures, not only that you have written them, so every AI draft below starts from your own practice notes and every approval carries a date you can point to.
Start from your scheme body's own wording
Schemes differ in what they list, so the first column of your sheet is copied text, not anything an AI remembers. Open the scheme body's current standard or application guidance and paste each requirement into its own row, word for word, with the scheme's numbering. Those numbers become your row labels, and they let any question from an assessor map straight back to your evidence.
Two published schemes show how different the lists can look. One names five core documents (a mission statement, a code of ethics, a strategic plan, an emergency plan and a collections management policy) and asks first-time applicants to pass a documents check before the full application; its core-documents page is worth a read even if it is not your scheme. Another sets out nine numbered requirements in three sections (organisational health, managing collections, and users and their experiences) and says it judges each museum by its size and type, from small volunteer-run sites to national ones. Neither list is yours, and your scheme body's current wording wins over both.
Before you paste anything, check three points: which edition is current, whether first applications and renewals use different guidance, and whether the scheme body publishes sample policies you can hold yours up against. The first point is live for the nine-requirement scheme: one of its partner bodies said in August 2026 that the scheme is being redesigned, that a new standard is expected at the end of 2026, and that museums should keep following the 2018 edition until then. Keep each requirement's wording in its own column, separate from your evidence links, so that when the new wording arrives you re-map rows instead of rebuilding the tracker.
What published standards ask a small museum to show
The table groups what the two published schemes above ask for into twelve items. The right-hand column is my suggestion of what to keep, not the scheme body's list, so confirm each row against yours.
| Item | What the published wording asks for | Evidence to keep |
|---|---|---|
| Statement of purpose | Why the museum exists and who it serves; one scheme wants the date the governing body approved it on the document | Dated trustee minute; the statement printed on the front of each policy |
| Governing document and structure | A constitution suited to a long-term public-benefit body; an organisation chart covering volunteers and staff; agreements setting out roles; access to museum professional advice | Constitution; chart with a version date; signed volunteer agreements; the named adviser |
| Code of ethics | One museum-specific document covering trustees, staff and volunteers, plus collections ethics; one scheme wants the paragraph on spending disposal proceeds to match the collections policy word for word | Approved code with its date; a side-by-side check of the matching paragraph |
| Forward or strategic plan | Aims, how you will reach them, people, equipment and money needed, budgets for the current and next planning year, who is responsible, and the next review date | Approved plan; budget sheet; minute; list of action owners |
| Financial position | Accounts for the last two available financial planning years showing income and spending | Two years of accounts and the finance report trustees saw |
| Premises and security | Secure occupancy of buildings holding collections (normally at least 12 months in one standard); security advice at least every five years, with changes made or planned | Lease or ownership papers; the advice report; an action list with dates |
| Emergency plan | Covers every site holding collections, with staff, volunteers, visitors and collections; a risk assessment; how it is tested and shared; a priority salvage list; a review date | The plan; the salvage list; a test or exercise note; a record of who holds copies |
| Collections development policy | Approved by the governing body; collecting and disposal priorities; legal and ethical framework; next review date | Policy with approval date; minute; disposal register |
| Documentation policy and procedures | An approved policy; procedures such as object entry, accessioning, location and movement control, inventory, cataloguing, object exit, loans in and out; a written documentation plan with priorities and timescales | Policy; procedures manual; a recent entry form, location log and inventory extract; the plan with dates |
| Care and conservation | An approved policy, and a plan to maintain and, where possible, improve how collections are cared for and conserved | Policy; plan; condition reports; monitoring readings |
| Access policy and plan | Physical, sensory and intellectual access to collections and buildings, plus information about collections, with a review date | Policy; plan; notes from an access walk-round; website access information |
| Audiences and learning | Who uses the museum and who does not; feedback used to change things; a plan to widen use; learning activities based on the collection; a range of ways to communicate | Visitor counts; feedback summary; plan; programme list; examples of leaflets and web pages |
Several requirements can be met inside another document. The standard with nine requirements says a documentation policy may be part of a wider collections management or documentation plan, and that care, access and audience plans may sit within the forward plan. If your scheme allows the same, say so in the tracker, so a volunteer does not write four documents when one properly headed document would do. For the audiences row, turning visitor feedback into themes gives you proof that feedback changed something.
The evidence tracker: one sheet, ten columns
Build the tracker in a sheet your whole team can open, whether that is Google Sheets, Excel or a shared table in whatever you already use. Ten columns are enough:
- Ref and Requirement: the scheme's number and its wording, pasted.
- Evidence document and Link: the one document or folder that proves it, with a link that opens.
- Owner: one named person, not a committee.
- Status: Missing, Draft, Approved or Needs evidence, set from a drop-down so nobody invents new labels.
- Approved on and Next review: dates taken from the trustee minute, not from the file's properties.
- Flag: a formula that reads the review date.
- Notes for the assessor: the one-sentence answer you would give if asked.
With those columns in A to J, the flag in column I reads the review date in column H:
=IF(H2="","No review date",IF(H2<TODAY(),"OVERDUE",IF(H2-TODAY()<=60,"Due within 60 days","OK")))Here is how four rows might look for a volunteer-run local history museum with two part-time staff, eighteen volunteers, an eight-person board and about 6,500 objects. Every figure is illustrative, and the flags are what the formula would show on 1 November 2026.
| Ref | Requirement | Evidence | Status | Approved on | Next review | Flag |
|---|---|---|---|---|---|---|
| R4 | Forward plan | Forward plan 2025 to 2027 | Approved | 11 Jun 2025 | 11 Jun 2027 | OK |
| R7 | Emergency plan | Emergency plan v2, no approval date found | Draft | blank | blank | No review date |
| R8 | Collections development policy | Collections policy 2019 | Approved | 4 Jul 2019 | 4 Jul 2024 | OVERDUE |
| R9 | Documentation policy | None found; practice notes only | Missing | blank | blank | No review date |
Statuses are blunt on purpose. Approved means a trustee minute exists with a date on it. A policy that everyone believes was approved in 2022 stays Draft until someone finds the minute.
A gap list built from the documents you already hold
Put every policy, plan, minute extract and relevant spreadsheet in one folder, then load it into an assistant that can hold documents: a Claude Project, a ChatGPT Project or a Gemini Notebook (formerly NotebookLM). As of October 2026 the limits are modest but workable. ChatGPT Projects hold 5 files on the free plan and 25 on Go and Plus, Claude's free plan allows up to five projects, and Google's free Gemini Notebook takes up to 50 sources per notebook. A dozen core documents fit in a Gemini notebook or a Claude project, and in a ChatGPT project on Go or Plus; on ChatGPT's free plan, merge them into five files first. If the whole evidence folder will not fit, start with the policies, or paste only the first page of each, which is where approval and review dates usually sit.
You are helping a small museum prepare for accreditation.
I will give you the scheme body's requirements, then the documents we hold.
Build a gap list. For each requirement return:
1. the requirement reference
2. the document that appears to evidence it (name only)
3. status: Missing, Draft, Approved but out of date, Approved and current, or Cannot tell
4. the exact words in the document that show approval or a review date, or "none found"
5. one question I should answer before an assessor asks it
Rules: use only the documents I have provided. If a document shows no date of trustee approval, mark it Draft, not Approved. If you cannot find evidence, write "none found". Do not guess what our practice is.
REQUIREMENTS: [paste the scheme's numbered requirements]
DOCUMENTS: [attach files, or paste the front page of each]Pasting the requirement list and the front pages of the museum's documents returns something like this (illustrative output, trimmed to three rows):
| Ref | Evidence found | Status | Words found | Question to answer |
|---|---|---|---|---|
| R7 | Emergency plan v2.pdf | Cannot tell | "Reviewed by the Board, March 2022" (no approval statement, no review date) | Is there a minute approving it, and when is the next review? |
| R8 | Collections policy 2019.docx | Approved but out of date | "Approved by trustees 4 July 2019. Review due 2024." | Was the 2024 review done, and where is the minute? |
| R12 | None found | Missing | none found | Do the audience aims in the forward plan count, or is a separate plan needed? |
Three things to fix before this goes into the tracker. On R7 the assistant correctly said it could not tell; a tool that had answered Approved would have been guessing, so the row stays Draft until the minute turns up. Open at least three of the source files and read the quoted words yourself, because a scanned PDF with no text layer can produce confident nonsense. And paste the status into the tracker only after a person has opened the file.
Drafting from practice notes, not from a blank page
A policy that fits your museum starts with a conversation. Sit with the person who does the job, here the volunteer registrar, for twenty minutes and ask eight questions. How does an object enter the building? Who can accession it? Where are location changes written down? How often is anything checked against the register? What happens to loans? What is not documented yet? Who covers when the registrar is away? What would you change with more volunteer hours? Type the answers up as plain sentences. Those are the practice notes.
Draft a documentation policy for [museum name], a volunteer-run museum with about 6,500 objects.
Use ONLY the practice notes below for any statement about what we do.
Use these headings, copied from the scheme's requirement: [paste headings].
Plain English, British spelling, no more than two pages.
After the draft, list every sentence that makes a claim about our practice, with the line of the notes that supports it. Mark any sentence with no support as UNSUPPORTED and do not soften it. Do not cite laws or standards unless I named them.
PRACTICE NOTES: [paste the typed-up answers]The mistake that catches teams is a draft that sounds better than the museum. Before the "notes only" rule went into the example museum's prompt, the assistant wrote: "A full inventory of the collection is carried out annually and reconciled to the register." The registrar's notes said: "We check one gallery or store against the register each quarter. The whole collection has been checked once in four years." Nothing in them mentioned reconciliation. An assessor who asked to see last year's inventory would have found nothing, and a policy that overstates practice does more harm than a modest one.
With the rule added, the draft read: "Location checks cover one gallery or store each quarter, so the full collection is checked over a four-year cycle. The museum aims to move to a two-year cycle by 2029, subject to volunteer capacity." The second sentence came from the registrar's answer to "what would you change?". It also turns a weakness into a dated plan, and the standard I read accepts exactly that for documentation: show that you follow the procedures or have a plan to do so.
Read every drafted policy for three further problems. Legal or ethical references the assistant added on its own initiative (delete them, then ask your adviser or the scheme body what belongs there). Words such as "always" and "all" that your practice cannot support. And headings that do not match the scheme's, which make an assessor hunt for the answer.
A trustee pack and an approval you can prove
Both published schemes expect the governing body to approve most core policies. One wants the approval date printed on each document and lets the emergency plan carry only a date of last revision; the other asks for a next-review date on the forward plan and several policies. So build the pack backwards from the proof you need: a cover note, the marked-up draft, wording for the minute and a footer.
The cover note is where AI saves the most time. Give it the old and new versions and ask for one page, then check it against both:
Write a one-page cover note for trustees. Say what the document is, what changed since the last approved version, what the trustees are being asked to decide, and the two biggest risks if they approve it. Plain English, no jargon, no new facts. Old version: [paste]. New version: [paste].A minute that would satisfy the Collections development policy row reads like this, with the brackets filled in by whoever takes the minutes at the meeting:
Item 6. Collections development policy.
The trustees considered version 3 of the policy, dated [date], with the amendment to section 4 (disposal priorities) agreed at the meeting.
RESOLVED that the policy is approved. Next review: [date]. Owner: [role].
Proposed: [name]. Seconded: [name]. Carried.The assistant did not attend the meeting and cannot know what the trustees decided, so the clerk writes the minute from the meeting itself. If you record meetings with an AI note-taker, read the tutorial on board minutes and Fireflies before relying on its summary as the record. Then put a footer on the policy's front page: "Approved by the trustees on [date]. Next review: [date]. Owner: [role]." Copy the same two dates into the tracker the same day.
Evidence of practice: the log an assessor can open
Policies prove intent. The standard I read also asks to see how you implement the documentation procedures and what you have done as a result of security advice, so you need a second list: dated proof of things actually done. Keep it in a separate tab of the tracker with five columns: date, requirement reference, what it shows, file name and link.
The log for the documentation requirement might hold these entries (illustrative):
| Date | Ref | What it shows | File |
|---|---|---|---|
| 2026-03-14 | R9 | Q1 location check of the Maritime gallery: 212 objects checked, 3 moved without being recorded | 2026-03_R9_location-check_maritime.xlsx |
| 2026-05-02 | R9 | Loan-out form for two paintings, signed by both parties, with condition report | 2026-05_R9_loan-out_two-paintings.pdf |
| 2026-06-20 | R7 | Table-top exercise on a burst pipe in the main store: six people, four actions agreed | 2026-06_R7_exercise-note.pdf |
AI earns its place here on the dull parts. Give it a folder listing and the naming pattern (year-month, reference, short description) and it will propose consistent file names and one-line descriptions, and spot two files that look like duplicates. It must never write an entry for something that did not happen. The exercise note in the third row came from a volunteer's scribbled page that a person typed up; the assistant turned it into a tidy one-pager, and the volunteer checked every line before it was filed.
The reminders that keep review dates from slipping are the same ones every compliance list needs, so the compliance calendar tutorial covers the calendar side, and the sibling piece on a nonprofit filings and deadlines tracker applies if your museum is a registered charity.
A mock assessor session before the real one
Once the tracker has a status for every row, ask the assistant to play the assessor. Give it one requirement at a time so the questions stay specific:
Act as an accreditation assessor for a small museum. Requirement R9 reads: [paste]. Ask me one question at a time about how we meet it. After each answer say whether it would satisfy the requirement as worded, what evidence you would ask to see, and what a weak answer would look like. Stop after five questions and list the evidence I should collect.A short exchange from the example museum (illustrative):
Assessor: Show me the records for the last three object moves. Registrar: We write moves in the notebook by the store door. Assessor feedback: A notebook can be evidence if it is dated, legible and linked to the register. Photograph the last three entries, transcribe them into the location log, and note who made each move.
That answer produced a new row in the evidence log and a task for the registrar, which is the point. The session is useful when it finds work, not when it makes the team feel ready. Treat the assistant's view of what satisfies the requirement as a rehearsal, because only the scheme body decides.
What stays out of the AI tool
Four kinds of content should not go into a consumer chat tool. Security details: alarm arrangements, key-holder phone numbers, floor plans that show where the most valuable objects sit. Lenders' private information in loan agreements. Donor details. Staff and volunteer personal data. You can still check an emergency plan's structure with those parts removed; swap each one for a placeholder such as [ALARM DETAILS REMOVED] and the assistant will review headings, responsibilities and gaps as well as before.
Check the tool's privacy settings before you upload anything. Consumer ChatGPT and Claude plans have a switch for using your chats to improve the models, and business plans generally do not train on business content by default. If your museum qualifies as a nonprofit, the vendors' own programmes start at about $8 per user a month for ChatGPT Business (on annual billing) and for Claude Team (which has a two-seat minimum), and Google Workspace for Nonprofits includes the Gemini app and Gemini Notebook at no extra cost. Eligibility rules vary, so read the programme pages before you count on any of it. The trustee risk register for AI use is a good companion for the board.
Nine months, twelve requirements, about 53 volunteer hours
Back to the example museum. Its first pass over twelve requirements found three approved and current, three approved but past their review date, four that existed as drafts or as practice nobody had written down, and two missing. That means nine documents to refresh, draft or write. Everything below is a planning assumption for illustration; time your first policy and multiply.
| Months | Job | Hours | Output |
|---|---|---|---|
| 1 | Build the tracker; paste requirements; load documents | 3 | Tracker with owners |
| 1 | Gap list with AI, then check by hand | 4 | Status for all 12 rows |
| 2 to 3 | Four practice interviews at 1.5 hours | 6 | Typed practice notes |
| 3 to 6 | Nine documents at 3 hours (AI draft, check, edit) | 27 | Nine drafts ready for trustees |
| 4, 6, 8 | Three trustee packs at 1 hour | 3 | Dated approvals and minutes |
| 2 to 9 | Evidence log upkeep at 1 hour a month | 8 | About 25 dated entries |
| 8 | Mock assessor session and fixes | 2 | Final list of gaps |
That totals 53 hours, about 80 minutes a week across the volunteer team. Tool cost can be nothing on free plans, or about $16 a month for two nonprofit seats if you want larger file limits and your museum is eligible; ChatGPT's $8 nonprofit rate assumes annual billing, so budget about $192 for the year rather than for nine months. The comparison that matters is hours, because a volunteer's time is the scarce resource, and most of the saving sits in drafting and in the gap list, where AI turns a blank page into something to correct.
Three signs the tracker is doing its job: no row has an empty Owner, no row says Approved without a minute date, and the OVERDUE count falls at every trustee meeting. If a status has drifted since the last check, trust the minute over the tracker and correct the tracker. When something is genuinely unclear, ask the scheme body; it is the only party that can say what it will accept.
Questions museum teams ask before they start
What if our scheme body publishes policy templates?
Use its template as the skeleton rather than asking AI for a structure. Paste the template's headings into the drafting prompt, tell the assistant to keep any wording the scheme requires word for word, and fill the rest only from your practice notes. Then list every place your draft departs from the template, so the trustees can see and approve each change.
Can volunteers use their own AI accounts for this work?
It is better to work from one account or project the museum controls, so the documents, prompts and drafts stay with the museum when a volunteer moves on. If personal accounts are used, agree the rules first: redacted documents only, the model-training setting switched off where the plan has one, and finished drafts saved to the museum's shared folder rather than left in someone's chat history.
What if we cannot meet a requirement before we apply?
Say so in the tracker rather than papering over it, and write a dated plan to meet it: what will change, who owns it and by when, approved by the trustees. The 2018 standard accepts a plan for following documentation procedures; for other requirements, ask the scheme body, or any mentor or adviser it assigns, whether a plan will be accepted.
Does AI-drafted wording count as evidence?
The scheme body wants to see that your museum approved the policy and follows it. Who typed the first draft is not the test. Evidence is the approved version with its date, the trustee minute and the records that show practice, such as location logs and loan forms.
How often should the tracker be updated?
Update it after every trustee meeting and run a fifteen-minute review once a month. The review-date formula does the nagging, so the monthly check is mostly opening the sheet, filtering for OVERDUE and Due within 60 days, and giving each owner a date.
Further reads
- Charity Complaints Policy Template: Draft One With AI and Check It — A complaints policy is another document schemes often expect.
- Volunteer Onboarding Checklist for Charities: Build One With AI — Volunteer agreements and induction are part of showing who does what.
- How to Use AI to Write Grant Applications, Step by Step — Reuse approved policies and plans as evidence in grant bids.
- Claude AI for Charities: Five Admin Jobs Set Up With Projects — Set up the Project that holds your policies and minutes.
- Can an AI Guide for Museums Stick to Your Own Collection Notes? — Keep any AI guide to your own collection notes.
- AI Policy for Museums: Checklist for Labels, Audio Scripts and Visitors — Set rules for AI in labels, audio scripts and visitor-facing text.
- What to Check in an AI Tool's Privacy Policy and Terms — Read a tool's privacy terms before uploading security or lender details.
- AI Tool Discounts for Charities and Non-Profits: What to Claim — See which AI tool discounts a museum charity can claim.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: the published core-documents page of one accreditation scheme and the published text of another scheme's Accreditation Standard (November 2018 edition), both read in October 2026; a partner body's accreditation page on that scheme's redesign (updated August 2026); Anthropic, OpenAI and Google help pages for Projects and Gemini Notebook limits; vendor nonprofit-programme pages.