CIS accreditation safeguarding: what evaluators look for

I have worked in international education since 2008, as an IB and MYP teacher, an IB and CIS evaluator and workshop leader, and most recently as CIS accreditation coordinator at Miras International School in Astana. The CIS accreditation safeguarding requirements are the part of the protocol that heads and safeguarding leads ask me about most often, usually a few months before a team arrives. The question is nearly always what the evaluators will actually ask for.

The answer starts with the framework itself. CIS International Accreditation is built on eighteen standards organised in three dimensions: Guiding Principles, Learning, and Well-being. CIS states plainly that the accreditation protocol includes standards that evaluate the school's child protection policy and practices. The expectations underneath those standards were shaped by the International Task Force on Child Protection, which CIS helped to found in 2014 and which CIS describes as providing the framework for implementing child protection policies and procedures.

CIS describes the ground those expectations cover as allegation management, staff selection, detecting and reporting abuse, education and support for leaders, teachers and students about behaviour and boundaries, implementation of policies, and collaboration with the local community. Read that list again and notice how much of it is about practice rather than paperwork. A school can hold a well-written child protection policy and still fail on every item, because the standards ask whether adults in the building behave the way the policy describes.

The CIS cycle does not test safeguarding once. It returns to it at every stage, from different angles, and the school sees the same questions asked in progressively more concrete ways. Cornerstone Conversations open the dialogue between the school and CIS. A Preparatory Engagement Visit follows, run by CIS-trained evaluators and lasting around three days for most schools, and its job is to confirm readiness rather than to judge quality. Schools that are honest at this stage save themselves a great deal of work later, because a preparatory team that names a weak reporting route gives the school two years to fix it.

Then comes the self-study, during which the school advances two to four Development Initiatives drawn from the CIS standards and its own strategic priorities. Safeguarding turns up here more often than most heads expect, because a self-study that involves staff, students, parents and the board quickly surfaces the gap between what the policy says and what people believe. At Miras the self-study was the first time several departments read the child protection policy end to end.

The Team Evaluation Visit closes the cycle. Peer evaluators, colleagues from other CIS accredited schools rather than full-time inspectors, spend around four days in professional dialogue, learning walks and evidence review. Peer review matters for safeguarding specifically. The people asking your DSL about referral thresholds run a safeguarding system of their own, in another country, under another set of local laws, and they know which answers are practised and which are recited.

Every team reads the policy before arriving. That reading takes an hour and tells the team very little, because policies are the easiest artefact in a school to improve. What the visit adds is triangulation: the team takes a claim from the policy, then looks for the same claim in three other places.

The pattern I have seen most often runs like this. An evaluator reads that concerns are reported to the DSL by the end of the school day. In a learning walk the same evaluator stops a teaching assistant in a corridor and asks who the DSL is and what happens if a child says something worrying at 3.40pm. Later the evaluator asks the DSL to show the record of a recent concern, without names, and looks at the date it was written against the date it was received. Three sources, one claim. Where the three agree, the standard is met and the conversation moves on in under ten minutes.

Schools lose credibility at the second source, almost never at the first. The policy is usually fine. The bus driver, the catering supervisor and the newly arrived maths teacher are the people who cannot answer, and they are exactly the people an evaluator will find, because a learning walk goes through kitchens and corridors as well as classrooms. Training for non-teaching staff is the cheapest repair available to a school in the year before a visit.

Staff selection sits inside the CIS child protection expectations, and the ITFCP publishes a Safer Recruitment Checklist that describes the standard in operational detail. It asks the school to collect a full employment history on an application form rather than a CV, to explain every gap, to take three referees with one being the current or most recent employer, and to require that referees can say whether any low-level concerns existed about the applicant. It rules out open letters addressed to whom it may concern. It asks for criminal record checks covering, where possible, every country where the applicant has lived for six months or more in the previous ten years.

International schools rarely fail this on principle. They fail it on files. A school hires nineteen people across three continents in a hurry in May, and by September four files are missing the second reference, two have a passport copy but no note of the name check against the police certificate, and nobody recorded which of the two interviewers had completed safer recruitment training. An evaluator does not need to read all nineteen. Pulling six at random tells the team what the system does under pressure. More detail on the cross-border version of this problem sits in the piece on safer recruitment across borders.

The expectations ask for education and support for leaders, teachers and students about behaviour and boundaries. Most schools answer that with a September session and a spreadsheet of names. The spreadsheet proves attendance, and attendance is the weakest form of evidence a school can offer, because it says nothing about what the adult can now do.

Stronger evidence answers three questions. What did this member of staff learn, specifically, about this school. When did they learn it, and who approved the content. What can they show they can do as a result. A record that names the policy version the training was written from, the date the DSL approved it, and the scenario the member of staff worked through carries far more weight in a four-day visit than a signature sheet. The article on safeguarding training records works through what that record should contain.

This matters more in a school where staff work in several languages. If your operations team reads Russian or Kazakh and your safeguarding training runs in English, the training record proves attendance and nothing else. An evaluator who asks a Russian-speaking security officer to explain the reporting route will hear the honest answer.

Preparation is mostly retrieval. The school already holds nearly everything a team asks for, and the work is putting it where one person can find it in two minutes rather than across four drives and a filing cabinet. I keep a single folder, dated, with a one-page index at the front.

• The current child protection policy, with its version number, approval date and the name of the board member or owner who approved it.
• The staff code of conduct, with signed acknowledgements from every adult on site including contractors and regular volunteers.
• A recruitment register showing, for each appointment, which checks were completed and on what date.
• Training records naming what each member of staff completed, in which language, from which version of the policy, and who approved the content.
• An anonymised sample of concern records showing date received, action taken, decision, and the reason for the decision.
• The board minute or annual safeguarding report that shows governors discussed safeguarding, with a date.
• A short note on local law: which authority receives a referral in your host country, and what the school does when local thresholds and international expectations differ.

I built SafeguardIS because the training half of that list was the part my own school could not produce honestly. The platform builds staff training from the school's own safeguarding and child protection policies, so what staff learn is what that school actually does. 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 means a training record can name the policy version and the approver rather than only a date. Certificates are countersigned by the Head of School and the DSL and carry a code anyone can check on a public verification page.

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. A policy audit feature checks a school's documents against ITFCP-aligned expectations and produces an action plan, which is a reasonable place to start eighteen months before a Team Evaluation Visit. Staff can also ask an AI policy assistant questions that are answered from the school's own policies, while the DSL keeps every safeguarding decision. Miras International School in Astana is the pilot school. I also run live workshops in English and Russian and whole-school safeguarding audits.

If you are inside an accreditation cycle and want to see what the evidence looks like when it is generated as a by-product of training rather than assembled afterwards, book a 20-minute walkthrough.