Safeguarding evidence for an accreditation visit: a checklist

I coordinated accreditation at an international school in Astana, which meant I spent several months assembling the safeguarding evidence for an accreditation visit and then watched a team work through it. The lesson from that week was about shape rather than volume. A team does not read everything. It samples, and it follows threads. It picks one policy, finds the training that taught that policy, finds a member of staff who took that training, and asks whether the date, the version and the person line up. Where the thread breaks, it pulls harder.

That changes what a school should build. A drive containing forty documents is not evidence; it is raw material. Evidence is the set of connections between those documents, and the connections have to be visible without the coordinator standing next to the team explaining them. The practical test I used before every visit was simple. Hand the folder to a colleague who does not work in safeguarding, name one member of staff, and ask them to prove that person knows the school's reporting route. If they cannot do it in five minutes, the team will not either.

The checklists below cover the material CIS, COBIS, NEASC and BSO teams ask for in some form. The naming differs between schemes and the underlying questions do not. The Council of International Schools built its accreditation protocol around recommendations from the International Task Force on Child Protection, which covers allegation management, staff selection, detection and reporting, education for leaders, teachers and students, policy implementation, and work with the local community. COBIS puts Safeguarding and Safer Recruitment at Standard 1 and examines it in the first of its two visits.

Start with the documents, because every other piece of evidence is dated against them. A team wants to see a policy set where each document carries a version, an approval date, the body that approved it and the next review date, and where the versions agree with each other. The contradiction that surfaces most often is between the child protection policy and the staff code of conduct, usually because one was revised and the other was not. NSPCC Learning makes the same point plainly in its guidance on writing safeguarding policies: include review dates and make sure the review happens on time.

• Child protection and safeguarding policy, with the version approved by governors and the date of approval.
• Staff code of conduct or behaviour policy, covering low-level concerns about adults, allegations against staff, and whistleblowing.
• Reporting and referral procedure naming the local authorities and the route to them in the host country.
• Safer recruitment policy, including the checks the school runs on staff who have lived or worked in other jurisdictions.
• Online safety policy, and the filtering and monitoring arrangements behind it.
• Anti-bullying strategy and the child-on-child abuse procedure.
• Trips, residentials and visitors procedures, including contractors and volunteers on site.
• Photography, images and communications policy covering staff use of messaging apps with students.
• Data protection and record-retention statement covering safeguarding records specifically.
• A single index page listing every policy above with its current version, approval date and review date.

The training log is where most schools lose ground, because a completion date on its own answers none of the questions a team asks. The useful record ties a named person to a role, to the version of the policy they were taught, to the date, to a result, and to whoever reviewed the material before it was published. That last field matters in an international school, where modules are often bought or translated and nobody has confirmed that the translated wording still matches the policy. I have set out the field-level detail in what a defensible safeguarding training record contains.

Split the log by role rather than presenting one flat list. A team reads a flat list as an administrative export. A list grouped by teaching staff, boarding staff, non-teaching staff, senior leaders, governors and the designated safeguarding lead shows that the school has thought about who needs what. The groups most often missing are the ones with the most unsupervised contact with children, which is why training for drivers, security, catering and nursing staff is worth building separately rather than sending everyone the same module.

• Induction safeguarding training for every member of staff appointed since the last visit, with the date it happened relative to their start date.
• Annual or cyclical refresher records for all staff, showing which policy version each cycle taught.
• Higher-level training for the designated safeguarding lead and deputies, with certificates and renewal dates.
• Governor safeguarding training, including the designated governor for safeguarding.
• Role-specific training for boarding staff, trip leaders, nurses, drivers, security and catering teams.
• Safer recruitment training for everyone who sits on an appointment panel.
• A record of the language each member of staff took the training in, where the school works in more than one language.
• Evidence that the designated safeguarding lead reviewed and approved each module before staff took it.

Every scheme opens the recruitment file, and every scheme samples. Expect the team to pick names rather than read the whole set, and expect at least one of those names to be somebody appointed in a hurry in August. COBIS describes its single central record as a dashboard covering employment checks, qualifications, criminal record checks, references, safeguarding training dates and probation, and offers member schools a health check on that record before the compliance visit. The BSO standards ask for a register that records whether identity, right to work in the host country and qualifications were checked, whether an International Child Protection Certificate and any further checks were obtained, and the date each was completed.

The gap that comes up in international schools is the unobtainable check. A police certificate from a country that no longer issues them to former residents, a referee who has left the school and cannot be traced, a qualification that cannot be verified because the awarding institution has closed. None of that fails a visit on its own. What fails is silence in the file. Record what was sought, what was received, what was accepted instead, who made that decision and on what date. A note of that kind takes two minutes to write and answers the only question the team was going to ask.

A team wants to see that the reporting system is used, so the concerns log matters more than its contents. Prepare an anonymised extract covering the last two or three years, showing the volume of concerns by month, the type, the action taken and the closure. A log with three entries in a school of eight hundred students tells a team that staff are not reporting, which is a culture finding rather than a paperwork one. The reasons behind that pattern, particularly in schools with strong hierarchies, are worth understanding before a visit rather than during it: I have written about why staff hesitate to report and what changes it.

Governance is the second thread. Bring the minutes where safeguarding was reported to the board, and mark the passages where a governor asked a question and the answer came back at a later meeting. A team distinguishes between a board that receives a safeguarding report and a board that interrogates one. Alongside the minutes, bring the role description for the designated safeguarding lead and deputies: the time allocated to the role, the reporting line, the deputising arrangement during absence, and who covers a disclosure at nine in the evening during a residential. The scope of that job in an international setting is covered in the designated safeguarding lead role in an international school.

Two further items complete the file. The first is evidence of what students and parents were taught: assembly and pastoral programme outlines, the age-appropriate curriculum content on personal safety and online safety, the induction material given to new families, and how students were told who to go to. The second is the action plan from the last self-study or inspection, annotated. For each recommendation, show what was done, when, by whom, and what evidence exists that it worked. An honest line saying a recommendation was not completed and explaining why reads better than a plan where every item is marked green.

Work backwards from the sample rather than forwards from the shelf. Begin with the policy index, because it dates everything else. Fix contradictions between the child protection policy and the code of conduct before adding a single training record, since the team will find them and every later document inherits the doubt. Then build the training log against the policy versions, so each cycle points at the document it taught.

Next, run the sample yourself. Choose ten names spanning a new teacher, a long-serving teacher, a boarding tutor, a bus driver, a member of the kitchen team, a nurse, a contractor with regular site access, a governor, a deputy designated safeguarding lead and somebody appointed within the last two months. Trace each one through the register, the personnel file and the training log, and write down where the trail stops. That list is the real preparation task, and it usually takes a fortnight rather than a term.

Finish with the narrative. A team reads a two-page summary that says what the school changed since the last cycle, what it found difficult, and what it is still working on. Writing that summary honestly does more for a visit than a fifth policy revision, because it tells the team where to look and shows that the school already knows. A school that hides its weakest area spends the whole visit defending it.

I built SafeguardIS while coordinating accreditation, because assembling this file by hand told me the connections were the hard part. The platform builds training from a school's own safeguarding and child protection policies, so the module a team samples points back at the policy version it taught. The designated safeguarding lead reviews and approves every module before staff see it, publishing requires a named reviewer's declaration, and the content is hashed and logged, which produces the version trail that a training log needs to be worth reading.

Certificates are countersigned by the Head of School and the designated safeguarding lead and carry a code anyone can check on a public verification page, so a visiting team can confirm one without the school vouching for it. Training ships in English, Russian and Kazakh today. If your staff work in a language the platform does not ship yet, I build that language in for your school as part of the pilot. There is also a policy audit that checks a school's documents against ITFCP-aligned expectations and produces an action plan, which is the fastest way to find the contradiction between the child protection policy and the code of conduct before an evaluator does. Miras International School in Astana is the pilot school.

If a visit is on your calendar in the next twelve months, you can book a 20-minute walkthrough and see how the policy set, the modules, the approvals and the training log connect.