When the Coordinator Leaves: Surviving Accreditation Staff Turnover

Your accreditation coordinator is leaving. They have three years of notice — which in academia means two weeks. The spreadsheet that holds the entire accreditation evidence map for your program is on their desktop. The visiting team is 18 months away. What happens next determines whether your next cycle is smooth or a crisis.

Staff turnover in accreditation roles is the quiet risk that every accredited program carries. Coordinators move to new institutions, retire, take on heavier teaching loads, or simply burn out from the six-year crunch cycle. When they leave, they take the institutional memory with them — unless you have built a system that survives them.

This is not a people problem. It is a systems problem. And it has a fix.

The Single Point of Failure

Here is the most common accreditation architecture in accredited programs:

• One person — the coordinator — holds the full picture of where every course maps to every indicator.
• One spreadsheet — often 40+ tabs, version-controlled by “final_final_v3_reallyfinal” in the filename.
• One timeline — the six-year cycle — during which most of the actual work happens in the final 18 months.

When the coordinator leaves, all three converge into a single point of failure. The new person inherits a spreadsheet they did not build, containing abbreviations and logic only the previous person understood, with no documentation of why certain decisions were made.

The department chair might know that the program is accredited. The dean knows the last visit went well. But nobody besides the departing coordinator knows that the evidence for one key outcome is three years old, that two courses no longer run but still appear in the curriculum map, or that the self-study narrative was written around a strength that no longer exists.

What Gets Lost

It is not just data that disappears when a coordinator leaves. It is context. Here is what is typically lost:

1. Rationale for past decisions. Why did the program decide to map one specific course to Indicator 2.3 instead of 2.4? The answer exists only in the previous coordinator’s head.
2. Faculty relationships. Which faculty members are reliable evidence contributors? Who needs chasing? The coordinator knows. The institution does not.
3. The state of evidence freshness. Some evidence is current. Some is from 2019 and was carried forward because nobody got around to updating it. The distinction matters enormously to a visiting team — but only the coordinator knows which is which.
4. Lessons from the last visit. What did the visiting team push back on? What recommendations were made? Were they addressed? If the answer lives in an email thread or a PDF report that nobody has opened since 2021, the lessons are effectively lost.

The Handover That Never Happens

You might think a handover process solves this. In theory, the departing coordinator sits down with their replacement, walks through the spreadsheet, and explains the logic. In practice, the handover is a rushed meeting in September with a USB drive and a list of passwords.

This happens because the system was never designed for transferability. It was designed for one person to get through one cycle. The spreadsheet works for the person who built it — that is the entire point of spreadsheets. They are personal tools. They are not institutional systems.

There is a difference. A personal tool requires the original operator. An institutional system works regardless of who is running it.

Four Principles for Survivorship

Building accreditation infrastructure that survives staff turnover does not require expensive software or a dedicated IT team. It requires four design principles:

1. The evidence must live outside any one person’s device

If the evidence map is on a laptop, a USB stick, or a personal cloud account, it is not institutional knowledge. It is personal knowledge that happens to be in spreadsheet format. The system must reside on a shared platform with access controls, version history, and the ability for multiple people to view and contribute.

This does not mean the coordinator should lose ownership. It means the institution should own the data while the coordinator owns the process.

2. Context must be captured alongside data

A cell that says “Course X — satisfies Indicator 2.3” is useful to the person who entered it. To someone else, it is a puzzle. The system should capture why that mapping exists: a note, a link to the syllabus section, or a record of the faculty discussion that led to the decision.

This is the difference between a database and a spreadsheet. A spreadsheet stores values. A database stores values and relationships. When the next coordinator asks “why does this course map to this indicator?” the answer should be in the system, not in a conversation with someone who left two years ago.

3. Status must be visible without asking

The new coordinator should be able to log in and immediately see: which indicators have fresh evidence, which are overdue, which courses have not reported in the current term. This visibility should not require opening 40 tabs and cross-referencing dates. It should be a single dashboard.

If the dean needs to ask “are we in good shape for the next visit?” the answer should be available in under 30 seconds. Not “let me check with the coordinator.” Not “I will need to review the spreadsheet.” A live status view that anyone with access can see.

4. Onboarding must be a feature, not an event

The best handover is the one that does not require a handover. When a new coordinator joins, they should be able to start contributing within a single afternoon. The system should guide them through what exists, what needs attention, and who to talk to.

This is possible only if the system documents its own structure. Course names, indicator definitions, evidence types, and contribution history should all be self-explanatory to someone seeing them for the first time.

The Cost of Not Building This

What happens when the system does not survive the coordinator? Here is the typical trajectory:

• Month 1–3: The new coordinator tries to understand the existing spreadsheet. They spend weeks reverse-engineering logic they cannot see.
• Month 3–6: Frustrated by the opaque system, they start rebuilding from scratch. The previous coordinator’s work is discarded — along with the institutional memory it contained.
• Month 6–12: The rebuild is underway, but now there is a gap in evidence collection. Courses run without their assessments being captured for accreditation purposes.
• Month 12–18: The visiting team date approaches. The new coordinator realizes the evidence gap is significant. The faculty gets pulled into a crunch cycle that could have been avoided.

The total cost: six to twelve months of wasted effort, a stressed faculty, and an accreditation cycle that is riskier than it needed to be. All because the system was personal, not institutional.

What to Do Today

You do not need to wait for the next coordinator to leave to start building survivorship into your accreditation process. Three actions you can take this week:

1. Audit where your evidence lives. Is it on one person’s device? In a shared drive? In a system with version history and access controls? If it is not in a shared system with audit trails, start planning the migration.
2. Ask your coordinator to document three key decisions. Pick the three most complex mappings or judgments in your current evidence set and ask for the rationale in writing. Store it alongside the evidence.
3. Test the handover yourself. Ask someone who is not the coordinator to explain your accreditation status using only the documents and systems you have. If they cannot do it in under 15 minutes, you have a survivorship gap.

The Bottom Line

Your accreditation coordinator is doing an excellent job. They will not always be here. The question is not whether turnover will happen — it is a matter of when. The question is whether your evidence, your decisions, and your institutional knowledge survive them.

Systems that are built for one person will fail when that person leaves. Systems that are built for the institution will keep working. The difference is not technology. It is design intent.

Build for the institution. The next coordinator will thank you.

This post applies across accreditation frameworks, regardless of which accreditor your program reports to. The turnover challenge is universal across accredited program administration.