You have stakeholder buy-in. Your department chair is engaged. Faculty understand what evidence they need to submit. Now comes the part that consumes three months of your life: writing the self-study report. The document that will sit in front of the visiting team, inform their findings, and determine whether your program keeps its accreditation status. Where do you even start?
The self-study report is the single most important document in the accreditation cycle. It is not a marketing brochure for your program — it is an honest, evidence-backed account of what you do, how well you do it, and what you plan to improve. Visiting teams read it cover to cover before they arrive, and every question they ask during the site visit traces back to something in those pages.
This post breaks down the self-study report section by section: what each section requires, what evidence belongs there, common mistakes that weaken the report, and how to organize your writing so the visiting team can find exactly what they need.
Section 1: Program Overview
The program overview sets the stage. It should answer three questions in approximately two to three pages:
- Who are you? Program name, degree offered, year established, enrollment numbers (current and five-year trend), full-time and part-time faculty counts, key program contacts.
- What is the program’s mission? A concise mission statement that connects to the institution’s broader goals. This is not the place for aspirational language — state what the program actually does.
- How does the program fit within the institution? Faculty affiliation, shared resources, administrative structure. If your program shares labs, libraries, or assessment infrastructure with other departments, note it here.
Common mistake: Copying the program overview from the previous cycle’s report without updating enrollment, faculty, or structural changes. The visiting team will have current data from Engineers Canada — discrepancies between your report and their records create an immediate credibility gap.
Evidence to include: Enrollment charts (five-year trend), faculty list with qualifications, organizational chart showing the program’s position within the institution.
Section 2: Curriculum Map and Graduate Attribute Coverage
This is the core of the report. The curriculum map shows every course in the program, its learning outcomes, and how each outcome maps to the CEAB Graduate Attributes and their indicators. This section typically runs 8–15 pages depending on program size.
The map must demonstrate three things:
- Completeness: Every Graduate Attribute is addressed. No gaps. If an attribute is covered only implicitly (embedded in a project rather than assessed directly), explain how.
- Progression: Evidence of an Introduce → Reinforce → Master progression across years. First-year courses introduce concepts. Third and fourth-year courses demonstrate mastery. The map should make this visible.
- Balance: No single course carries an unreasonable burden of assessment. If three Graduate Attributes all depend on one capstone project for their mastery-level evidence, that is a risk worth acknowledging.
Common mistake: Presenting the curriculum map as a static table without commentary. The map tells the team what you teach, but the commentary tells them how you think about it. Add a narrative that explains design decisions: why certain attributes are introduced in specific courses, how progression was designed, what changes were made since the last cycle and why.
We covered this in our post on curriculum review for accreditation, which includes a five-step process for building and maintaining the map.
Evidence to include: Curriculum map table (course-by-attribute matrix with I-R-M codes), course descriptions, sample syllabi for one course per year of the program.
Section 3: Assessment Methods and Evidence Collection
This section explains how you measure whether students are meeting each learning outcome. It should cover:
- Assessment tools used: Rubrics, exams, project evaluations, peer reviews, self-assessments, capstone defence evaluations. Describe the tool, not just the method.
- Frequency of assessment: How often is each outcome assessed? Annually? Each semester? Once per program? The visiting team expects regular assessment — not a one-time measurement at graduation.
- Data aggregation: How do you collect results from individual courses and synthesize them into program-level conclusions? This is where many programs falter. Having course-level data is not the same as having program-level insight.
- Evidence storage and recency: Where is evidence kept? How is it organized? What is the recency of the evidence cited in this report?
Common mistake: Listing assessment methods without showing results. Saying “we use rubrics” is not enough. The report should include aggregate results: what percentage of students met each outcome, trends over time, and what the data reveals about program strengths and weaknesses.
Evidence to include: Rubric samples, aggregated assessment results (tables or charts showing pass rates by outcome over the last two to three years), description of data collection workflow.
Section 4: Continuous Improvement
This is often the most scrutinized section of the report. Continuous improvement is not a buzzword — it is a CEAB requirement. The section must demonstrate a closed loop:
- Identify: What did assessment data reveal? Where are the gaps?
- Decide: What action did the program take in response?
- Implement: What changed? A revised rubric? A new course module? A different assessment method?
- Verify: Did the change improve outcomes? Show the before-and-after data.
The visiting team will look for at least three to four documented examples of closed-loop improvement. If your report says “we continuously improve” but cannot show specific instances of data-driven change, that is a finding.
Common mistake: Describing planned improvements without evidence of implementation. “We intend to revise the rubric next semester” is not continuous improvement. It is a to-do item. The report should focus on improvements that have already been made and verified.
Evidence to include: Continuous improvement log (date, issue identified, action taken, result verified), meeting minutes from curriculum committee decisions, before-and-after assessment data for at least two improvement cycles.
We covered the closed-loop process in our post on closing the loop with assessment evidence and the CI trap in our post on continuous improvement traceability.
Section 5: Resources and Infrastructure
This section covers the physical and human resources that support the program. It typically includes:
- Faculty qualifications: Degrees, professional engineering status (P.Eng.), research areas, industry experience. CEAB expects a majority of faculty to hold professional engineering credentials.
- Libraries and learning resources: Physical and digital collections, access to technical databases, lab equipment, software licenses.
- Industry partnerships: Co-op placements, advisory boards, guest lecturers, joint research projects, donation-supported equipment.
- Student support: Academic advising, tutoring, career services, mental health resources.
Common mistake: Underplaying resources. Programs often list only what they consider “impressive” — a new lab, a major industry partnership. But the visiting team also needs to know about baseline resources: how many computers are in the lab, whether students have reliable internet access, how often equipment is maintained. The full picture matters.
Evidence to include: Faculty credential summary table, inventory of key lab equipment (with dates of last update or replacement), list of co-op/industry partners with active engagement, photos of facilities (if the report format allows).
Section 6: Student Outcomes and Graduate Feedback
This section connects program activities to real results. It covers:
- Graduation rates: Four-year and five-year completion rates. Trends over the last cycle.
- Employment outcomes: Placement rates within six months of graduation, industries of employment, starting salaries (if available).
- Graduate surveys: What do graduates say about the program? How well did it prepare them for their careers? Include methodology: response rate, survey instrument, how results were analyzed.
- Employer feedback: If your program collects feedback from employers about graduate performance, include it here. Even informal feedback (from co-op supervisors, advisory board members) is valuable.
- Alumni engagement: Alumni who serve on advisory committees, guest lecture, or participate in capstone evaluations.
Common mistake: Presenting outcomes without context. A 70% placement rate is either good or bad depending on the national average, the economic climate, and the program’s own historical baseline. Always provide context.
Evidence to include: Graduation rate table (five-year trend), employment outcome summary, graduate survey results with response rate, employer feedback summary (anonymized if needed).
Section 7: Self-Evaluation and Areas for Improvement
This is where you demonstrate intellectual honesty — a quality that visiting teams value more than a flawless report. Every program has areas for improvement. The section should include:
- Strengths: What is the program doing well? Be specific. “Strong student outcomes” is not specific. “Graduate Attribute 5 (design) shows consistent mastery-level performance across all fourth-year courses, with 92% of students meeting or exceeding the rubric standard over the past three years” is specific.
- Areas for improvement: What needs work? Prioritize them. List three to five areas, ordered by impact. Explain why each area matters and what the program plans to do about it.
- Timeline for improvement: When will each improvement be addressed? Short-term (within one year), medium-term (one to three years), long-term (three to five years)?
Common mistake: Listing trivial improvements (“we could update the department website”) while avoiding real gaps. The visiting team will identify the gaps themselves. It is more credible to identify them first, acknowledge them honestly, and show a plan to address them.
Evidence to include: Prioritized improvement list with timelines, responsible parties, and success metrics.
Section 8: Appendices
The appendices contain the supporting evidence referenced throughout the report. This is where organization matters most. A disorganized appendix section makes the entire report harder to evaluate.
Standard appendices include:
- Complete curriculum map (detailed version, not the summary table in Section 2)
- Course syllabi (at minimum, one per year of the program; ideally all current courses)
- Assessment rubrics
- Aggregated assessment results (full data sets, not just summary charts)
- Faculty list with credentials and contact information
- Graduate survey instrument and raw results
- Continuous improvement log
- Institutional strategic plan (if relevant to program goals)
Organization tip: Number each appendix item and cross-reference it in the body of the report. “See Appendix A for the complete curriculum map.” This allows the visiting team to verify claims without searching through 200 pages of unlabelled documents.
How to Organize the Writing Process
The self-study report is too large for one person to write. Even with stakeholder buy-in (covered in our post on getting buy-in), the coordinator must manage the writing process. Here is a practical approach:
Step 1: Assign sections to section leads
Each section has a natural owner: curriculum coordinator for the curriculum map, assessment chair for assessment methods, program director for resources. Assign ownership early — at least four months before submission — and set internal deadlines that are two weeks ahead of the actual deadline.
Step 2: Gather evidence before writing begins
Do not assign writing tasks without the underlying data. Run the evidence collection process first. We covered this in our post on getting faculty to submit evidence. Faculty should upload rubrics, exam results, and project evaluations before anyone starts writing.
Step 3: Draft in parallel, consolidate sequentially
Section leads draft their sections independently. The coordinator consolidates into a single document, checking for consistency: are Graduate Attribute numbers used the same way in every section? Does the curriculum map match the assessment section? Are improvement actions in Section 7 tied to gaps identified earlier?
Step 4: Internal review before submission
The department chair reads the full draft. Not their section — the whole thing. They are looking for two things: accuracy (is this what the program actually does?) and tone (does this read as honest and professional, or defensive and evasive?).
Optionally, ask a coordinator from another institution to review the draft. They will catch assumptions that your team takes for granted.
Step 5: Build the appendix cross-reference
After the body is finalized, build a cross-reference table: every claim in the body that cites evidence gets a line item pointing to the specific appendix document and page. This is the step that makes the report verifiable — and it is the step most programs skip.
Summary
The self-study report is not a document you write once and forget. It is a living record of what your program does, how well it does it, and how it plans to improve. A well-organized report makes the visiting team’s job easier, which means fewer surprises on the day of the visit.
The key principles are simple: be honest about gaps, be specific about evidence, be organized about cross-references, and be proactive about continuous improvement. The visiting team does not expect perfection. They expect a program that knows what it does, can prove it with evidence, and has a plan to get better.
If you are building this report and feeling overwhelmed by the evidence collection and organization work, let us talk. MapOutcomes replaces the spreadsheet-based evidence workflow with a connected map that makes every section of this report easier to write and easier to verify.