The CoA Annual Report: Assembling Outcomes Data Without a Scramble

The self-study gets all the attention — it's the big document, the one with the page count and the deadline. But the annual report is the accreditation obligation that never retires: it comes back every year, for as long as your program holds its accreditation, and CAAHEP's own process puts it in step nine, ongoing quality review, where CoAs "evaluate information submitted by programs to demonstrate continued compliance with the Standards, including but not limited to annual report and progress reports" [1]. CAAHEP's accreditation process page makes the point quietly: the self-study has a finish line. The annual report does not.

And here's what makes it different from the self-study: the self-study is a narrative about your program, while the annual report is a data assembly job. Every number in it — enrollment, faculty counts, credentialing results, placement, survey responses — has to come out of some system somewhere, be reconciled against last year's submission, and land in your CoA's portal before a hard deadline. This post is about that assembly: what goes into the report, why it scatters across four systems by year-end, and a workflow that turns submission week from archaeology into a form.

The Annual Report Is the Part of the Cycle That Never Ends

CAAHEP's accreditation process runs in nine steps, from the Request for Accreditation Services through the site visit and the board decision. Step nine is where the annual report lives: the CoA evaluates the information programs submit to demonstrate continued compliance with the Standards — "including but not limited to annual report and progress reports" [1]. That evaluation feeds the CAAHEP Board of Directors, which acts on recommendations at six meetings per year [1].

CAAHEP sets the obligation; your Committee on Accreditation (CoA) defines the report. Each CoA names it, scopes it, and sets its own deadline. The outcomes data in it — retention, credentialing, placement — is covered in our post on CAAHEP outcomes thresholds, including what happens when a number lands below your CoA's bar. This post assumes you already track those numbers; it's about the rest of the assembly.

What Actually Goes Into the Report

Every CoA's annual report asks for a different mix, but the same three families of data show up everywhere:

• Status data — enrollment, faculty counts, program administration changes, facilities. This is the "is the program still the program we accredited" check.
• Outcomes data — credentialing examination results, retention, placement, and whatever your CoA adds.
• Survey data — graduate and employer surveys, in many CoAs' reports.

Two accreditors make the shape of the job concrete. CAPTE — the Commission on Accreditation in Physical Therapy Education, which is not a CAAHEP CoA but publishes a clear example of the pattern — requires all accredited and developing programs to submit an Annual Accreditation Report (AAR), "which collects program data used for reviews, aggregate and salary reports, and research" [2]. Note the scope: that's not just your outcomes; it's program-level data CAPTE uses across the profession. And CAPTE publishes separate AAR instruction sets by program type — DPT, PTA, and candidate programs — with an explicit instruction to use the PDF instructions to gather data before entering it in the portal, because it "includes guidance not available online" [2]. The portal doesn't hold the whole spec; the instructions do.

CoARC — the Commission on Accreditation for Respiratory Care, which accredits through CAAHEP — runs its annual report as an Annual Report of Current Status (RCS) submitted through its own software. Its published page [3] links step-by-step directions for generating the school summary, instructions for calculating credentialing success from the NBRC Annual School Summary, FAQs, and a document literally titled "How to Ensure Your Report is Error Free." And the survey requirement is specific: graduate and employer surveys administered six to twelve months after graduation, with both surveys used when completing the annual report (the page notes the employer survey for Diagnostic Anesthesia programs is no longer required as of 2026). That six-to-twelve-month window is the detail that decides whether your placement data is complete at deadline: if you only send surveys in the month before the report is due, you're reporting on graduates who haven't had time to answer.

Even CoAs whose public pages are lighter on detail run the same pattern — the Committee on Accreditation for the Exercise Sciences, for example, lists its annual report alongside its annual fee and maintains employer and graduate survey instruments for programs [4]. The takeaway is not "here's the universal checklist" (there isn't one); it's that your CoA's instructions are a complete specification, and reading them end to end is step one of the workflow.

Where the Scramble Comes From

Now put yourself in submission week. The report's fields live in at least four systems that were never designed to talk to each other:

• The registrar or LMS — enrollment, cohort sizes, retention at the checkpoint your CoA defines.
• Human resources — faculty counts, credentials, FTE. Often a separate office from the department.
• Your credentialing exam vendor — pass rates that arrive on the vendor's schedule, after students test, and students test on their own schedule.
• The career center, the alumni office, and your graduates themselves — placement and survey responses, the slowest data in the building.

Three things about that setup produce the scramble. First, the deadline is hard and the data is soft. Your CoA's date does not move because the exam vendor hasn't released the last cohort's results. Second, nobody owns the assembly. Each data owner knows their own number; nobody owns the report as a whole until the deadline makes them all own it at once. Third, the reconciliation is invisible until you do it. A number that looks fine on its own can be a twenty-point drop from last year's submission — and a drop like that needs an explanation in the report, not an apology to the CoA after the fact.

A Workflow That Turns the Report Into Assembly

The fix is not heroics; it's a sequence you run every year, starting well before the deadline.

1. Read your CoA's instructions end to end — before the data, not after. CAPTE's AAR guidance explicitly says the PDF holds guidance the portal doesn't; CoARC publishes step-by-step "error free" instructions and FAQs for exactly the fields that trip programs up. Your CoA's instructions are the spec. Treat them like one: every field, every definition, every deadline, written down in one place.
2. Build a field-by-field source map. One row per report field: what it measures, which system of record holds it, who owns that system, and when the number is final. The last column is the one everyone skips — "when is it final?" A pass rate isn't final until the vendor's last retake window closes; a placement figure isn't final until the survey window ends. If you don't know the answer for a field, that field is your project.
3. Set internal deadlines ahead of the CoA's. Collect by date A; reconcile against last year by date B; draft explanations for any movement by date C; final review and submission by date D — all before the CoA's deadline. The gap between D and the real deadline is your buffer for the thing that always goes wrong: one owner who is on leave, one vendor report that's late.
4. Keep the outcomes flowing year-round. The three CAAHEP outcomes — retention, credentialing, placement — are calendar-year obligations with their own tracking rhythm; our thresholds post covers what to track and what a below-threshold year triggers. If those numbers only exist in submission week, the annual report inherits the scramble. If they're current all year, the report is a copy, not a computation.
5. Reconcile against last year — and write the explanation before the question. For every field that moved meaningfully, draft the one-paragraph explanation now: what changed, why, what you're doing about it. A documented explanation filed with the report reads as competence; the same explanation sent to a CoA reviewer as a response to a query reads as damage control.
6. Archive every submission with its source map. Each year's filed report, plus the source map and the raw pulls behind each number, kept in one place. Next year's reconciliation takes minutes instead of weeks, and when the coordinator changes, the method survives the departure — which is also what CAAHEP's public-data expectations assume: CAAHEP lists each program's data and a link to where its outcomes are posted, and program directors are expected to review that listing for accuracy and notify CAAHEP of changes [5]. What you file, what you post, and what you keep on file should be the same numbers.

What MapOutcomes Changes

This is where the workflow meets the tool. MapOutcomes' CAAHEP vertical organizes your accreditation evidence as a connected map: outcomes data, survey results, and status documents are linked to the standards and criteria they support, so the annual report's fields aren't scattered across four systems — they're one export away. The source map becomes the evidence map itself; the reconciliation is a comparison against last year's filed numbers, visible before the CoA's deadline rather than after it. And when the coordinator leaves, the map stays: the next person inherits the assembled system, not the folklore of where the numbers live.

The CoA sets the report; you set the workflow that makes it painless.

Where to Go Next

If you're not sure which Committee on Accreditation covers your program, our guide to CAAHEP's committees will point you at the right one — because the annual report you're assembling is defined by that committee, not by CAAHEP centrally. Our outcomes thresholds post then covers the three numbers the report is built on.

Two things to do this week, before anything else:

1. Find your CoA's annual report instructions and read them end to end. Every field, every definition, every deadline. If the instructions are a PDF with guidance the portal doesn't show — as CAPTE's are — read the PDF, not just the portal.
2. Build the source map for the fields that always arrive late. Credentialing results, retention at the checkpoint, placement, survey responses, faculty counts. For each: which system, which owner, when it's final. The fields whose answer is "somewhere in a folder" are your first workflow to fix.

Until then: read the spec, map the sources, set the internal dates, and keep the annual report what it should be — a form, not a fire drill.

References

1. CAAHEP, "Accreditation Process," CAAHEP. [Online]. Available: https://www.caahep.org/program-directors/accreditation-process
2. CAPTE, "Annual Accreditation Report Instructions," CAPTE. [Online]. Available: https://www.capteonline.org/faculty-and-program-resources/annual-accreditation-report
3. CoARC, "Annual Reporting Tool," CoARC. [Online]. Available: https://coarc.com/accreditation-resources/annual-reporting-tool/
4. CAAHEP, "Committee on Accreditation for the Exercise Sciences (CoAES)," CAAHEP. [Online]. Available: https://www.caahep.org/committees-on-accreditation/exercise-science
5. CAAHEP, "Maintaining Program Data and Outcomes," CAAHEP. [Online]. Available: https://www.caahep.org/program-directors/maintaining-program-data