Ask a chair what went wrong in their last review and you rarely hear a story about writing. You hear a story about a folder. Somebody needed three years of assessment data and found one. Somebody needed the syllabus that was actually used in a term and found four files with similar names. The report was late because the evidence was late, and the evidence was late because nobody was collecting it until the report needed it.
This is a timing problem more than an effort problem. Evidence that takes three years to produce cannot be produced in the six months before a visit. If you start collecting when you start writing, some gaps are already permanent.
What tends to be missing
Across the reviews we have looked at, the same categories come up again and again.
- Assessment results for terms where the person who ran the assessment has since left
- The closing half of the improvement loop, where an action was taken but never reassessed
- Syllabi for sections taught by adjuncts, which often never reach a central location
- Rubrics as used, rather than rubrics as designed
- Meeting minutes that document a decision the narrative later refers to
None of these are hard to collect at the time. All of them are hard to reconstruct later.
A gap analysis is cheaper than a finding
The useful move is to run a gap analysis at the start of the cycle rather than the end. Load what you already have, map it against the standards, and look at what has nothing behind it. The exercise usually takes a few days and it changes the shape of the next two years.
The output should be a list, not a feeling. For each standard, either you have the evidence, or you know who is going to produce it and by when. Standards with no owner are the ones that go missing.
Sort gaps by lead time, not by size
It is tempting to work the list from top to bottom. A better order is by how long each item takes to produce.
- Multi year trends. These need to start now or they will not exist.
- Anything requiring a committee decision, which moves at the speed of the meeting calendar.
- Documents held by other offices, where you are in someone else's queue.
- Faculty submissions, which are quick individually but slow in aggregate.
- Signatures and formatting, which take a day and always get done.
Working in this order means the slow items are already running while you handle the fast ones.
Collect where the work happens
The most reliable collection strategy is to capture evidence at the moment it is created rather than asking for it later. A rubric result recorded in the term it was scored is accurate. The same result recalled two years later is an estimate.
That usually means asking faculty for small things often rather than large things rarely. A request for one syllabus at the end of a term is a two minute task. A request for eight terms of syllabi at once is a project, and it gets postponed.
The test
Here is a quick way to know whether your evidence is in good shape. Pick a claim from your last report at random. See how long it takes to produce the document behind it. If the answer is more than a minute, your next reviewer is going to find that out too.