You've sent the third reminder email this month. The syllabus you need for one required course is still outstanding. The course instructor responded with a version from 2023. You need the current one, with updated learning outcomes aligned to the outcome indicators your program mapped last spring.
You don't mind doing the work. You mind that the faculty member didn't know what you needed, why you needed it, or when it was due. And the next time accreditation comes around — two years from now — the same thing will happen again.
This is the gap that lives at the centre of every accreditation coordinator's life. Not the criteria, not the self-study report, not the visiting team. The gap between what the coordinator knows must happen and what the faculty understands they need to do about it.
The Evidence Gap Nobody Talks About
Accreditation coordinators carry institutional knowledge that no one else in the program has. You know which courses need which outcome indicator evidence. You know what the visiting team looks for. You know that a syllabus from two years ago doesn't count when the curriculum changed last fall.
Faculty members teaching 45-student sections, reviewing grants, advising students, and preparing lectures — they don't carry that knowledge. When you ask for "evidence for a specific outcome from your course," the translation in their head is vague. What counts as evidence? An exam question? A rubric? A student project description? All of the above? They don't know, so they send what seems closest, which is rarely what's needed.
The result: you spend hours reconciling 30 different interpretations of the same request. Some are usable. Some need follow-up. Some are from the wrong term. By the time you've sorted it all, the deadline has moved, and two more courses are still outstanding.
This isn't a problem with your faculty. It's a problem with how evidence collection is structured.
Why Faculty Resistance Isn't Laziness
Here's something accreditation coordinators understand intuitively but rarely say out loud: faculty don't resist accreditation because they don't care about the program. They resist because the ask is unclear, the timing is arbitrary, and the submission process is friction.
Consider the typical evidence request from a coordinator's perspective:
- The ask is broad. "Please provide evidence for the outcome indicators your course maps to." That's 3-5 different attributes, each requiring different types of evidence. For a faculty member who hasn't thought about accreditation in 18 months, this is a research project, not a form to fill out.
- The deadline feels arbitrary. "I need this by March 15." But March 15 is mid-term grading week. The request competes with everything else on their plate, and accreditation isn't their job — it's yours.
- The submission process is manual. Email a PDF. Or drop a file in a shared folder. Or update a spreadsheet cell. Every method requires the faculty member to stop what they're doing, find the document, format it somehow, and send it through a channel that may not even confirm receipt.
- The impact is invisible. Faculty members don't see how their syllabus becomes a line in the self-study report. They don't see the visiting team's question that their evidence answers. To them, evidence collection feels like a box-checking exercise that lives in someone else's world.
When you understand these four factors, the solution stops being "send more reminders" and starts being "make the ask clear, the process simple, and the impact visible."
What Changes When Evidence Collection Is Built Into the Course Workflow
The best evidence collection systems share one property: they don't feel like accreditation work to the faculty member contributing evidence. They feel like normal course administration.
Here's what that looks like in practice:
Instead of: "Please upload your syllabus showing outcome indicator mapping" — a vague request sent in March.
Built-in approach: When a faculty member updates their course record each semester, the system prompts them to confirm or update the outcome indicator contributions. It shows them exactly which indicators apply to their course, what types of evidence are expected, and what's already been submitted. The prompt appears when they're already thinking about the course.
Instead of: Coordinators maintaining a master spreadsheet that only they can see, with colour-coded cells showing who owes what.
Built-in approach: A shared evidence dashboard where faculty can see their own contribution status, the program's overall readiness, and gentle automated reminders — not from the coordinator, but from the system.
Instead of: Evidence sitting in individual email inboxes and shared drive folders, where it's found by the coordinator who knows where everything is.
Built-in approach: Evidence stored in a connected system where it's searchable, auditable, and accessible to the next coordinator who takes over the role.
The shift isn't technological. It's structural. Evidence collection becomes part of the course management rhythm instead of a separate, accreditation-time-only event that interrupts everything else.
How to Frame Evidence Mapping to Faculty in Terms They Care About
If you've ever pitched evidence collection to faculty using accreditation language, you know how it lands. "We need to map your learning outcomes to outcome indicator 4 so the accreditation report has coverage." The eyes glaze over. Compliance language triggers compliance fatigue.
The reframing that works is simpler than you might expect: evidence mapping is teaching quality documentation.
Here's how to frame it in faculty conversations:
- "This isn't about accreditation. It's about showing how your course builds the skills we say it builds." Every faculty member wants students to learn. Evidence mapping is simply the documentation that connects what they teach to what students gain. That's professional pride, not regulatory burden.
- "The evidence you collect this semester saves you work next semester." When evidence is collected continuously, the next accreditation cycle starts with a head start, not a blank spreadsheet. Faculty who contribute now are the ones who get the lightest workload later.
- "This data is your evidence of teaching effectiveness." Promotion and tenure committees, external reviews, and teaching awards all look for evidence of learning outcomes. The same evidence that satisfies accreditation satisfies career development. Frame it as a dual-purpose activity, not a compliance tax.
- "When you map your course, you can see gaps you didn't know existed." Evidence mapping isn't just about collecting what's there — it's about discovering what's missing. A faculty member who sees that a specific outcome has no evidence in their course can adjust next semester's assessments to fill the gap. That's curriculum improvement driven by data, not by the accreditation cycle.
The coordinators who get the best faculty participation aren't the ones who nag the hardest. They're the ones who explain the why in language that connects to what faculty already care about.
A Coordinator's Practical Next Step
You don't need a new system to start reframing evidence collection. You can improve the faculty conversation this semester:
- Send specific asks, not general ones. Instead of "submit evidence for your course," say "I need the rubric for Assignment 3, which maps to the problem-solving outcome. Here's an example of what worked last time."
- Stagger deadlines by course group, not by calendar date. Give one group of courses one deadline, another group a different deadline. It reduces the coordination bottleneck and makes each deadline feel less overwhelming.
- Show faculty the output. When you finish the evidence section for a course, send the faculty member a brief summary: "Here's how your course evidence appears in the report. It looks strong on that outcome, but we could strengthen another one with one more assessment example."
- Start the conversation in September, not March. The faculty who are asked in the first month of the term are the ones who remember. The ones asked in the eleventh month are the ones who scramble.
These changes cost nothing and require no new tools. They're about shifting from coordinator-driven chasing to faculty-enabled participation.
The Bigger Picture
The faculty-coordinator evidence gap is the single largest source of accreditation coordinator stress. It's the reason coordinators work 10-20 hours a week during accreditation season. It's the reason turnover in coordinator roles is so damaging — the replacement has to rebuild the entire relationship from scratch.
Closing the gap starts with understanding that faculty aren't the problem. The system is. And systems can be redesigned — starting with the conversations you have this semester, not waiting for the next accreditation cycle.
The coordinators who make this shift don't just save themselves time. They build a culture where evidence collection is a shared responsibility, not a solo burden. That culture is the real accreditation asset — the one the visiting team can't see on paper but can feel in every conversation.
This post reflects the experiences of accreditation coordinators across accredited programs. The strategies described are practical and can be applied regardless of whether your program uses spreadsheets, shared drives, or purpose-built accreditation software.