Your spreadsheet has 200 cells filled with evidence. The visiting team asks to see three of them. Two are three years old. The third is a folder path that leads to a file nobody can find.
This is the evidence quality problem. And it is the most common reason programs receive “areas of concern” — not because the program is bad, but because the evidence does not prove it is good.
Here is what strong evidence looks like, how to build it before the visit, and the mistakes coordinators make that visiting teams notice immediately.
The Difference Between Having Evidence and Having Good Evidence
Every coordinator knows the pressure to fill cells. You have 45 courses, 8 outcome categories, and dozens of indicators. The spreadsheet demands data, so you put something in every cell.
But a filled cell is not evidence. A PDF link that opens a syllabus from 2021 is not evidence. A rubric that exists but was never actually used to assess student work is not evidence.
The visiting team can tell the difference. They have reviewed hundreds of programs. They know what authentic evidence looks like — and they know what coordination desperation looks like.
What Visiting Teams Actually Look For
An accreditation committee evaluates evidence against three criteria. Understanding these criteria is the single most useful thing you can do to improve your evidence quality.
Criterion 1: Relevance
Does the evidence directly demonstrate the indicator it is supposed to support?
Strong evidence: A final exam question that requires students to apply discipline knowledge to solve an open-ended problem, with a rubric that explicitly scores that knowledge component. The exam is current, the rubric is aligned, and the scoring data shows how students performed.
Weak evidence: A course syllabus that lists learning outcomes. The outcomes mention “critical thinking” but there is no assessment instrument, no scoring data, and no way to tell whether students actually demonstrated the skill.
The gap between these two examples is enormous. One shows what students can do. The other shows what the course claims to teach.
Criterion 2: Recency
Is the evidence from a recent academic term, or is it stale?
Strong evidence: Assessment data from the current academic year. Rubrics from the last two terms. A CI narrative that references specific changes made in the previous year and shows the impact of those changes.
Weak evidence: Assessment data from three years ago. A rubric that was used once in 2022 and never updated. A CI narrative that says “we improved the course” without specifying when, how, or what the measurable result was.
Stale evidence is the silent killer of accreditation quality. A cell that says “evidence collected” looks fine until the visiting team asks “when?” and the answer is “2021.”
Criterion 3: Verifiability
Can the visiting team independently verify the claim the evidence supports?
Strong evidence: An assessment report showing 120 student responses, with aggregate scores, a distribution chart, and a narrative explaining how the results compare to the program’s target. The raw data is available if the team wants to see it.
Weak evidence: A statement that “students performed well on the design project.” No data. No sample. No way for the visiting team to verify the claim beyond the faculty member’s word.
Five Mistakes That Create Weak Evidence
Mistake 1: Syllabi as Assessment Evidence
A syllabus describes what the course intends to teach. It does not show what students actually learned. Syllabi are valid evidence for curriculum structure — which courses exist, which outcomes are stated. They are not evidence of student achievement.
If your evidence cell for a specific indicator contains only a syllabus, the visiting team will flag it. Replace it with assessment data that shows students meeting that outcome.
Mistake 2: Single-Point Evidence
One exam. One project. One rubric. If you have only one assessment addressing an indicator, you have a single point of failure — and the visiting team will notice.
Strong programs have multiple assessments per indicator, spread across different courses and different terms. This creates a pattern of evidence that is harder to challenge and easier to verify.
Mistake 3: No Closed-Loop CI Narrative
Continuous Improvement is where most programs lose credibility. You identified a problem last year. What did you do about it? Did it work?
Strong CI evidence has three parts:
- Identification — data showed students were struggling with X
- Action — the course was redesigned to address X
- Verification — new data shows students are now performing better on X
If you cannot complete all three parts of the loop, your CI evidence is incomplete. And incomplete CI is the number one reason programs receive “areas for improvement” from the visiting team.
Mistake 4: Undated Files
Every piece of evidence should have a clear date. Not “fall term” — “Fall 2025.” Not “recent” — “March 2025.”
Date-stamping solves two problems: it proves recency, and it lets you track trends over time. A visiting team that sees evidence from multiple years, clearly dated, will have much more confidence in your program than one that sees undated files.
Mistake 5: Evidence Without Context
A spreadsheet cell that says “see folder 3B” is not evidence. It is a treasure hunt. The visiting team does not have time for treasure hunts.
Every evidence reference should include a one-sentence narrative: what the evidence is, what it demonstrates, and when it was collected. This turns a file path into a verifiable claim.
The Evidence Quality Checklist
Before you finalize your self-study, run this 10-point check on every indicator:
- Is the evidence directly relevant to this specific indicator?
- Is the evidence from the current or previous academic year?
- Can the visiting team independently verify the claim?
- Do you have multiple assessments per indicator (not just one)?
- Does every evidence file have a clear date?
- Is there a narrative explaining what the evidence shows?
- For CI indicators: is the full loop documented (identify → act → verify)?
- Are rubrics aligned to the indicator they claim to assess?
- Is sample student work included at different performance levels?
- Can you pull this evidence report in under five minutes?
If you cannot answer “yes” to all ten, you have work to do before the visiting team arrives.
How Connected Evidence Mapping Fixes Quality Problems
The evidence quality problems described above are not solved by working harder. They are solved by working with better tools.
A connected evidence management system addresses each quality criterion automatically:
- Relevance — Every evidence item is explicitly mapped to the indicator it supports. No more guessing whether a syllabus proves student achievement.
- Recency — Every upload carries a date. Stale evidence is flagged automatically. You can filter by term to see only current-year data.
- Verifiability — Every evidence item includes metadata: who uploaded it, when, what course, what assessment. The full trail is one click away.
- Multiple sources — The system shows you how many evidence items support each indicator. Gaps are visible before the visit, not during it.
- CI tracking — Continuous improvement actions are tracked from detection through resolution. The loop is visible, documented, and exportable.
You do not need to replace your faculty or your curriculum. You need tools that turn the evidence they already produce into something the visiting team can actually use.
Start Before the Visit
Evidence quality is not something you fix six weeks before the visiting team arrives. It is something you build throughout the cycle.
The programs that walk into their visits with confidence are not the ones that worked the hardest in the final months. They are the ones that treated evidence quality as a year-round practice, not a pre-visit scramble.
Run the checklist above this month. Fix what you can. Build the habit for what you cannot fix quickly. The next cycle will be easier because of it.