In education, the value lies not only in the company that was acquired, but in a series of recognitions, accreditations, and curricula tied to a specific legal entity or institution. Where in other sectors an integration is mainly a matter of merging systems and processes, here an additional layer comes into play that is non-negotiable: a program that no longer meets the requirements of an accreditation body is no longer a program. That relationship — between what can be merged organizationally and what must legally and substantively stay in place — largely determines where an integration in this sector gets stuck.
On top of that, educational institutions often have participation structures that are not comparable to a works council in a commercial company. Teachers, students, and sometimes parents have a formal voice in decisions that affect the organization. A merger or acquisition that skips that process does not get stuck on resistance alone, but on the validity of decisions.
A common assumption is that a recognition transfers along with the organization offering the program. In practice, an accreditation is often tied to a specific institution, sometimes even to a specific location or examination board. When merging two education providers, the question is not only whether the quality remains the same, but whether the recognition process needs to reconfirm that. That process has its own timeline, which rarely runs parallel to the timeline of the deal. A synergy baseline that does not flag this as a separate dependency presents a more optimistic picture than reality allows.
Student information systems, scheduling software, and testing platforms in education are often configured per institution, with their own curricula, cohorts, and assessment rules built in. Where in retail a point-of-sale system is reasonably interchangeable, in education the content of the primary process sits within the system itself. Merging then means not just migrating data, but assessing whether a curriculum, an assessment matrix, or an examination regulation remains literally the same or effectively changes. That question belongs in the synergy baseline, not only at the point of execution.
Teachers often hold appointments tied to a collective labor agreement for education, with its own rules on appointment, qualification, and reassignment. A teaching qualification is, moreover, subject-specific: a teacher cannot simply be deployed in a different subject area, even if the organizational structure suggests otherwise on paper. A Day 1 plan that treats staff as interchangeable capacity misses this layer. The question of who is allowed to teach which class is separate from the question of who is on the payroll.
Where in most sectors a customer can absorb a switch to a new system or a new brand without much consequence, a student is in the middle of a multi-year program with interim assessments, internships, and a diploma at the end. An integration that cuts across the school year affects not just administration but the examination itself. That makes the phasing of a Day 100 plan in this sector less a matter of speed and more a matter of which point in the school year allows changes without affecting an ongoing cohort.
The standard question in every integration — should this component actually be merged — applies fully in education, and sometimes with more weight than elsewhere. An examination board that must be able to judge independently loses that independence if it is placed organizationally too close to the rest of the merger. A program with its own accreditation may sometimes be better off remaining separate, even if full integration seems obvious from a cost perspective. The decision list from the integration office is meant to make this kind of trade-off explicit, not to automate it.
These bottlenecks — accreditation, per-institution systems, staff bound by collective labor agreements, cohorts that cannot be interrupted — are not unique to education in the sense that similar tensions also arise in financial services, where licenses play the same role as accreditations, in the ict sector, where system architecture is often more deeply intertwined than expected, and in the agricultural sector, where permits and certifications can likewise be tied to a specific legal entity. The form differs, the pattern does not: something that looks organizational on paper turns out, on closer inspection, to be legally or substantively locked in place.
The generators and the integration office structure where the dependencies lie and which question needs to be asked for each component. What they do not do is calculate how much of the underlying work — processing schedules, checking test results, merging files — still needs to be done manually after the integration and which part of that can be taken over by AI. That question follows on from every synergy baseline and is answered by the work scan from FTE TO AI, task by task.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.