You have mapped every course. You have defined every indicator. You know exactly what evidence is needed. The only thing missing is the evidence itself — and it is sitting on a faculty member's desk who has not received an email from you since October.
This is the accreditation coordinator's fundamental dilemma. You are responsible for the program's accreditation readiness, but you have no direct authority over the people who hold the evidence. You cannot mandate that a full professor submits a rubric. You cannot CC the dean on a request for anonymized student work samples.
The problem is not that faculty do not care about accreditation. The problem is that evidence collection is an add-on to their teaching workflow, not a part of it. And add-ons always lose to priorities. This post is a practical playbook for making evidence collection stick — five strategies that work, why faculty actually participate, and how to build a submission culture that survives beyond your tenure as coordinator.
The Four Real Reasons Faculty Don't Submit
Before fixing the problem, you need to diagnose it correctly. The reason faculty do not submit evidence is rarely "they don't care." It is one of four things.
They do not know what is needed
"Submit evidence for your courses" is not a clear instruction. Which courses? Which indicators? What counts as evidence? By when? Coordinators often send a spreadsheet with 45 rows and expect faculty to fill in the cells. But faculty members are not accreditation specialists. Without specific guidance — "for MECH 340, I need the design project rubric and three anonymized student project reports from the Fall 2025 offering" — the request is too vague to act on.
It is not part of their workflow
Faculty manage syllabi, assessments, grades, research, and service commitments. Evidence collection is a task that arrives via email, disconnected from the tools they use daily. If submitting evidence requires logging into a separate system, finding a specific folder, or reformatting a document to match a template, it becomes another thing on the to-do list that gets deferred. And deferred evidence is evidence that arrives too late.
They do not see the value
Many faculty members have never seen a visiting team request their specific evidence. They have never read an accreditation report that mentioned their course. To them, evidence submission feels like paperwork for an abstract process. If they do not understand how their rubric connects to a Graduate Attribute, how that attribute connects to the program's accreditation status, and how that status affects their students' professional standing, they will treat it as a low-priority administrative task.
The process asks for too much
Some programs ask faculty to submit a full set of evidence every semester — every rubric, every exam, every work sample. That is a significant time investment. If the submission process takes longer than the actual teaching activity it is documenting, faculty will resist. We covered this in our post on what coordinators wish faculty understood. The solution is not to ask for less evidence. It is to ask for the right evidence, at the right time, in the right format.
Five Strategies That Actually Work
The playbook below is not theory. It is what works in programs where evidence collection is reliable, timely, and does not require constant coordinator follow-up. Use all five — they reinforce each other.
Strategy 1: Embed evidence requests in the teaching calendar
Do not ask for evidence in January for a course that ran in April. Send the evidence request during the course — ideally in the second or third week, when the faculty member is actively teaching, grading, and assessing. The evidence is fresh, the assessment instruments are open, and the cognitive load of remembering what was done is low.
Practical approach: build an annual evidence calendar that maps submission deadlines to course offering dates. If MECH 340 runs in Fall and Spring, the evidence request goes out in Week 4 of each term. The faculty member receives it while the course is active, not three months after the deadline.
Strategy 2: Make the request specific and scoped
Replace "submit all evidence for your courses" with a targeted request:
- Course: MECH 340 — Design and Analysis
- Indicators mapped: GA3-Indicator 2 (Problem Analysis, Mastery), GA4-Indicator 1 (Design, Introduction)
- Evidence needed: Design project rubric, three anonymized student project reports, mid-term exam section on problem formulation
- Due: Week 8 of the term (before mid-term grades are finalized)
A specific request takes five minutes to act on. A vague request takes twenty minutes to understand and then gets deferred. We explored this in our post on the faculty evidence submission playbook — the clearest requests get the fastest responses.
Strategy 3: Show faculty what their evidence is used for
Faculty are more likely to participate when they understand the downstream impact of their contribution. A ten-minute briefing at the start of the accreditation cycle can change the entire submission culture.
Show them:
- The curriculum map — where their course sits in the program's Graduate Attribute coverage.
- A real piece of evidence — an anonymized example of what the visiting team asked for in the last cycle, and why it mattered.
- The self-study narrative — the paragraph that references their course's evidence, so they can see exactly how their submission becomes part of the program's accreditation story.
This is not a one-time presentation. It is a recurring practice. Every time a new faculty member joins the program, or every time the curriculum map changes, re-run the briefing. We covered the narrative-writing process in our post on the CEAB self-study narrative — showing faculty the narrative draft before it is finalized is one of the best ways to make them feel ownership over the evidence.
Strategy 4: Reduce friction to zero
The submission process should take less time than the activity it documents. If a faculty member spent three hours creating a rubric, submitting that rubric should take three minutes.
Friction points to eliminate:
- Multiple systems — evidence should be submitted where the faculty member already works, not in a separate accreditation portal they rarely visit.
- File formatting — do not require faculty to reformat documents. Accept the rubric as-is, the exam as-is. The coordinator's job is to organize and link the evidence, not to standardize its format.
- Unclear deadlines — set a single due date per term, not rolling deadlines that faculty lose track of.
- No feedback loop — acknowledge receipt within 48 hours. If the evidence is sufficient, say so. If it needs something more, specify what. A faculty member who receives no confirmation will assume nothing happened and may not follow up.
The best programs treat evidence submission like grade submission — a routine part of the teaching cycle, not a special project.
Strategy 5: Get the department chair to champion it
Coordinators ask. Chairs direct. When the department chair frames evidence submission as a program expectation — not a coordinator's request — participation rates improve measurably.
What the chair can do:
- Mention it in faculty meetings — a two-minute update on evidence deadlines is more effective than ten coordinator emails.
- Tie it to course review cycles — require evidence submission as part of the annual course review process, so it becomes a standing item, not an ad-hoc request.
- Recognize participation — a simple acknowledgment in a faculty meeting ("thanks to everyone who submitted evidence for the Fall term — it made a real difference in our self-study") builds positive reinforcement.
We explored the chair's role in our post on what department chairs need to know. When chairs are engaged, evidence collection stops being the coordinator's solo burden.
What a Good Submission Culture Looks Like
A program with a mature evidence submission culture has these characteristics:
- Faculty submit on time — not because they are policed, but because the request is clear, timely, and low-friction.
- Evidence is current — submitted during the course, not retrofitted months later from memory.
- Quality is consistent — because faculty understand what the visiting team needs and have seen examples of good evidence.
- New faculty are onboarded — every new hire receives the evidence briefing during their first term, so the process does not depend on informal knowledge transfer.
- The coordinator's role is review, not collection — the coordinator validates submitted evidence, identifies gaps, and writes the narrative. They do not spend hours chasing down rubrics.
This culture does not emerge from a single email or a policy document. It is built through consistent practice, clear communication, and tools that make the right thing the easy thing.
How a Connected Evidence Map Changes the Equation
The spreadsheet-based evidence model makes faculty engagement harder. Faculty members are asked to fill cells in a shared spreadsheet or upload files to a folder structure they cannot navigate. The coordinator is left connecting dots manually — matching uploaded files to indicators, verifying that the evidence is current, and rebuilding the map every cycle.
A connected evidence map reverses this dynamic. The coordinator pre-loads the structure — courses, indicators, mapped evidence requirements — so faculty members only need to submit what is needed, when it is needed, with clear instructions. The platform handles the linking, the organization, and the traceability.
Faculty members see exactly what is requested for their specific course, with the deadline and the indicator it supports. They submit directly into the system. The coordinator receives the evidence already connected to the right place in the map. No folder hunting, no cell filling, no manual cross-referencing.
We covered this in our post on the evidence review — a connected map makes it trivial to validate that every piece of evidence is current, relevant, and sufficient. When faculty submit into the right place at the right time, the coordinator's role shifts from evidence hunter to evidence reviewer.
Summary
Faculty evidence submission is not a compliance problem. It is a workflow problem. Faculty do not submit because the request is vague, disconnected from their teaching calendar, unclear in purpose, or too much friction for the value they see.
The playbook is straightforward: embed requests in the teaching calendar, scope them specifically, show faculty the downstream impact, reduce friction to zero, and get the department chair to champion the process. A program that practices all five strategies will see faculty participation rates improve within one term.
The tool you use matters, too. A connected evidence map — where every indicator is linked to its courses, every course to its assessments, and every assessment to the evidence that supports it — makes submission easy for faculty and review easy for coordinators. The visiting team does not need to see a sophisticated platform. They need to see evidence that is current, traceable, and sufficient. A system that makes that possible is worth the investment.
MapOutcomes builds that connected evidence map for your program. Faculty submit evidence directly into the structure, the coordinator reviews and validates, and every claim in your self-study is supportable by evidence that is findable in seconds. Book a demo to see how the evidence map works in practice.