The self-study narrative is the single document that the visiting team will spend the most time with. It is the story of your program, told through evidence, and it determines whether CEAB sees your program as well-run or perpetually on the run.
For most coordinators, writing it feels like starting from scratch. The last narrative was filed seven years ago. The person who wrote it has moved to another department. The spreadsheet that tracked the evidence has been revised, renamed, or lost in an email thread. So you open a blank Word document and stare at it for a while.
You do not have to start from scratch. If your evidence map is current and your continuous improvement records are organized, the narrative writes itself. Here is how to build a self-study narrative that is grounded in evidence, structured for the visiting team, and easy to update each cycle.
What the Self-Study Narrative Is (and Is Not)
The self-study narrative is not a marketing brochure. It is not a list of achievements. It is a structured account of how your program meets — and continuously improves against — each of the eight CEAB Graduate Attributes and their indicators.
The visiting team uses the narrative as a roadmap. They will read section 3.2 and expect to find the evidence you describe. If the evidence is not there, or if it contradicts what the narrative says, the team will flag the inconsistency. A confident narrative with missing evidence is worse than a cautious narrative with complete evidence.
As we noted in our post on what visiting teams look for, the team is checking for three things: accuracy (does the narrative match the evidence?), completeness (does it address every indicator?), and self-awareness (does the program understand its own strengths and gaps?).
The Evidence-First Writing Method
Most coordinators write the narrative first and then scramble to find evidence to support it. This produces narratives that are optimistic but unsubstantiated — the program "demonstrates strong coverage" of Graduate Attribute 4, but the only evidence is a single assignment from one course, three years old.
The evidence-first method reverses the process. You start with the evidence map and let it tell you what to write.
Open your evidence map. For each indicator, review the connected evidence: what courses address it, at what coverage level (Introduction, Reinforcement, Mastery), and what exemplars exist. Write one paragraph per indicator that describes exactly what the evidence shows. If an indicator has thin evidence, write honestly about the gap and the plan to address it.
This approach eliminates two common problems. First, it prevents overclaiming. You can only write what the evidence supports. Second, it makes cross-referencing trivial. When you write "MECH 340 provides Mastery-level coverage of GA3-Indicator 2," the visiting team can find MECH 340 in the evidence map and verify the claim in seconds.
Structure Your Narrative Around the Criteria
CEAB organizes its evaluation around the criteria in the Manual of Accreditation Procedures. Your narrative should mirror that structure so the visiting team does not have to translate between your document and theirs.
A practical structure looks like this:
- Section 1 — Program Overview: Brief description of the program, enrollment numbers, faculty count, and any structural changes since the last visit. Keep this to one page.
- Section 2 — Governance and Resources: How the program is governed, resource allocation, and faculty qualifications. This is where faculty licensure compliance goes — see our post on CEAB faculty licensure changes for the updated requirements.
- Sections 3–10 — Graduate Attributes: One section per Graduate Attribute, with subsections for each indicator. This is the core of the narrative and typically 60–80% of the document.
- Section 11 — Continuous Improvement: How the program closes the loop on assessment findings. Reference specific changes made since the last visit.
- Section 12 — Appendices: Course syllabi, exemplars, and supporting documents referenced in the narrative.
Do not invent sections that CEAB does not use. If the manual has 12 sections, your narrative should have 12 sections. Extra sections create noise. Missing sections create gaps.
Write the Continuous Improvement Section Last
The continuous improvement section is the hardest to write because it requires you to connect assessment findings to concrete changes. You cannot write it until the Graduate Attribute sections are done, because the improvements you describe are responses to gaps identified in those sections.
Start with a table. Three columns: the finding (what the assessment showed), the action taken (what you did about it), and the result (how you measured the impact). Fill in the table from your closing-the-loop records.
As we discussed in our post on closing the loop, the visiting team does not expect perfection. They expect a process. If your assessment found that students were struggling with GA2 (problem formulation), and you responded by adding a design thinking module to the first-year curriculum, that is a complete CI story. Finding → Action → Result.
If you find indicators with no closing-the-loop story, do not fabricate one. Write: "This indicator was identified as an area for improvement. The following plan is in place for the next assessment cycle." A honest gap is better than a fictional improvement.
Use the Previous Cycle's Narrative as a Scaffold
The seven-year gap between CEAB visits makes the previous cycle's narrative feel ancient. It is not. The Graduate Attributes have not changed significantly. The structure of the narrative has not changed. What has changed is the evidence underneath it.
Open the previous narrative. For each indicator, ask three questions:
- Has the evidence for this indicator changed? If yes, rewrite the paragraph with current evidence.
- Has the coverage level changed? If yes, update the I-R-M designation and explain why.
- Has the program made improvements in this area? If yes, add the CI story to Section 11.
This is not copy-paste. It is informed revision. The previous narrative gives you the structure and the language. Your job is to update the facts.
If the previous narrative is not available — because the last coordinator left, or because it was stored on a personal drive — this is a strong argument for a centralized evidence map. When the evidence lives in a shared system, the narrative can be rebuilt from the data, not from memory. We cover this in more detail in our post on surviving coordinator turnover.
Cross-Reference Everything
Every claim in the narrative should have a cross-reference to the supporting evidence. Not a vague "see appendix" — a specific reference the visiting team can act on.
Good: "GA3-Indicator 2 is addressed at the Mastery level in MECH 340 (Design Project). See exemplar MECH-340-EP3-2024 and course syllabus appendix A-7."
Bad: "The program provides good coverage of problem-solving skills. See appendices."
Cross-referencing takes extra time during writing, but it saves hours during the visit. When the team asks to see evidence for a specific claim, you can point them directly to the document. No searching, no scrambling, no "I think it was in that folder somewhere."
Who Should Write (and Review) the Narrative
The coordinator should draft the narrative because they understand the evidence map. But they should not be the only writer. Department chairs should review the sections that cover their departments. Faculty who teach the key courses should verify the course-level claims.
A practical review process:
- Draft (Coordinator): Write the full narrative using the evidence-first method. Two to three weeks.
- Department Review: Circulate to each department chair with their section highlighted. Give two weeks for comments. Ask them to flag any inaccurate claims or missing evidence.
- Faculty Spot-Check: Select five key courses. Ask the instructors to verify that the narrative's description of their course's contribution is accurate.
- Final Edit (Coordinator): Incorporate feedback, resolve inconsistencies, and finalize cross-references.
As we discussed in our post on faculty understanding of evidence, faculty engagement is not optional. It is the difference between a narrative the team trusts and one they question.
What Happens When You Do Not Write the Narrative Well
A weak self-study narrative does not automatically mean a failed accreditation. But it does mean more questions, more document requests, and more pressure on the program during the visit.
The visiting team will spend two to three days with your document. If the narrative is unclear, they will spend that time asking for clarification instead of evaluating the program. If evidence references do not match the appendices, they will raise conditions. If the continuous improvement section is thin, they will question whether the program has a real process or is just filling in boxes.
The self-study narrative is the first impression your program makes on the visiting team. Make it accurate, make it complete, and make it easy to follow.
Summary
The CEAB self-study narrative does not have to be a seven-year project that starts from a blank page. Build it from your evidence map, structure it around the criteria, write honestly about gaps, and cross-reference every claim. Use the previous cycle's narrative as a scaffold, not a template. Get faculty to review their sections. And write the continuous improvement story last, when you know exactly what the assessment data shows.
A current evidence map makes the narrative easier to write. MapOutcomes connects your courses, indicators, and evidence in one place so the narrative data is always available — not buried in spreadsheets or waiting on a faculty member's inbox. Book a demo to see how the connected evidence map works.