International schools have organized trip oversight around a single moment: the approval meeting. A stack of proposals. A committee. A signature.
The signature satisfies the formal requirement. It does not, on its own, produce the evidence the decision is supposed to rest on — whether activities have been risk-assessed against the right dimensions, whether providers have been vetted against the standards the school holds them to, whether destination intelligence is current, whether emergency protocols match the specific trip rather than the generic policy. Those are settled by the work that surrounds the signature, not by the signature itself.
The approval moment is the formal act of trip oversight. It is not the substance of trip governance.
What has shifted
Two changes in the landscape have moved beyond what the approval-as-governance model can carry.
ISO 31031 defines the bar.
The standard codifies adequate risk management for school-organized activities as an ongoing structured process — planning, provider selection, communication, monitoring, and review. Insurers, accreditation bodies, and governing boards now read a school's trip governance against it.
Incident reviews expose the gap.
Post-incident reviews return repeatedly to the same finding: the documentation produced under the approval-as-governance model is not the documentation a school needs when something goes wrong. The gap becomes the question the school is asked to answer.
A published standard that defines adequate practice, and an incident record that shows where current practice falls short — together they close off the ground the approval moment used to occupy.
What governance actually requires
If the approval moment is not the substance, the substance has to be located somewhere. Worked through against what each phase of a trip involves, it takes the shape of a continuous cycle.
Before approval is on the table. Activities, locations and providers put into comparable evidence form.
Trip Options BriefActivity-level risk assessment, compliance alignment, scenario testing, calibrated emergency documentation.
Operations PlaybookTransfer of operational understanding to the people who will execute the trip. Briefings and rehearsal.
Briefing PackThe duty-manager position established. Visibility into where students are. Incident procedures at hand.
Live Operational LogAfter-action analysis against the playbook. Feedback synthesis. Lessons captured for the next iteration.
Post-Trip ReviewEach macro-stage breaks down further into the operational stages shown on the home page cycle grid. The approval moment still happens — it now sits inside a cycle that has already produced the evidence it is supposed to certify.
Operational consequences
Running trip governance as a cycle requires work the approval moment alone does not — intelligence gathering, structured risk assessment, scenario testing, documentation production, post-trip analysis. Adequate execution typically calls for dedicated staff time, external support, or some combination calibrated to the school's trip portfolio.
The cycle also compounds. Intelligence developed for one trip to a destination is reusable for the next. Provider assessments accumulate. Post-trip reviews update the institutional record that the next Trip Options brief draws from. The first iteration is heavier than the approval-only model; later iterations cost less per trip as the institutional record matures.
How ETI360 fits
ETI360 was built to support the cycle. The firm structures the evidence each stage requires, surfaces the gaps the school may not have noticed, and produces the documentation the cycle is meant to generate. The firm's role is to structure, not to certify — schools and providers run their own governance; ETI360 supplies the infrastructure that makes adequate governance feasible at contemporary volume and complexity.