How to prepare for a university accreditation visit

How to prepare for an accreditation visit in higher education: list the evidence a panel asks for, then let your exams produce it, traceable to each decision.

The simplest answer to how to prepare for an accreditation visit is to start from the question the panel will ask — how do you assess? — and work back to the evidence: item analysis, cohort outcomes, marking consistency and an audit trail per decision. NUADU produces that documentation as a by-product of running your exams, not as a project three months before the visit. For programme directors and QA offices in higher education: what a panel asks for, where each answer comes from on the platform, and why the committee, not the platform, makes the case.

How do you prepare for an accreditation visit?

Start from the panel's list, not the platform's. Write down the four kinds of assessment evidence a panel asks for, and for each one name who produces it today and from what. The gaps you find are the real preparation work; the lasting fix is to run the exams on something that records each piece of evidence as it happens.

NUADU's Higher education page puts the starting point in one sentence: "The accreditation visit is in eight months and our assessment evidence is spreadsheets and paper." The syllabus is in order and the learning outcomes are written. What is missing is proof that assessment measured them, because the tools that ran the exams were never asked to keep it. Whether a quiz feature inside the LMS can carry that load is a decision of its own, set out in LMS or assessment platform.

A preparation sequence that works from the evidence backwards:

  1. List the four kinds of evidence the panel will ask for.
  2. For each, write down who produces it today and from which system.
  3. Mark every step where evidence is rebuilt by hand — exports that disagree, a spreadsheet only one person maintains.
  4. Move those steps into the assessment workflow, so the record is written when the work is done.
  5. Ask for NUADU's accreditation evidence checklist, in BAN-PT and PKA variants. It is available on request, not as a download.
Assessment quality is demonstrated by data, not by a syllabus.

What evidence does an accreditation panel ask for?

Four kinds recur: item analysis, cohort outcomes, marking consistency and an audit trail per decision. Each answers a different panel question — whether the items work, whether intended learning outcomes are being met, whether marking holds steady across markers, and how each decision was reached and by whom.

  • Item analysis — item quality statistics per item, in the language of academic quality; item analysis in assessment explains what the panel will read.
  • Cohort outcomes — cohort comparisons and intended-learning-outcome tracking in the programme view of exam results reporting, with accreditation-ready exports.
  • Marking consistency — the marker signs every grade, inter-rater agreement is visible to QA and every override is logged; with AI assistance on, AI is a documented second rater inside your moderation and marking policy.
  • An audit trail per decision — every AI output, override and approval logged, exportable and reviewable; the AI audit trail shows what that record holds.

Good accreditation evidence examples, in this sense, are not documents written for the visit. They are records written while the exams ran, by the people who did the work.

A panel may also ask about AI. NUADU's posture is stated as EU AI Act-ready: human oversight, logging and documentation built into the workflow, with GDPR and FERPA posture documented and a DPA ready to sign. In that workflow, AI prepares evidence and proposes; a named educator or approver decides and signs. "Ready" describes the workflow, not a certificate. The DPA and data residency page covers the DPA — a signable copy is requested through the contact form — alongside data residency options and the sub-processor list.

Where does each piece of evidence come from?

From two of Report's three views, written at the moment the work happened. Cohort comparisons and intended-learning-outcome tracking live in the programme view, beside resourcing signals and accreditation-ready exports. One level up, the institutional view aggregates by faculty and site, tracks the impact of a reform, and breaks results down for equity where the institution has configured it.

Two illustrative cases show the shape. A programme preparing an accreditation self-study might produce intended-learning-outcome reports across three cohorts, generated against its own accreditation framework — the one the panel will use. A faculty reviewing a curriculum might set four years of cohort evidence side by side and decide where content, assessment or the rubric needs revising. In both cases, the decisions stay with the committee.

Nothing in either case is reconstructed later. A named marker signs the marks, results are released, the analytics update, and when the session closes the audit trail closes with every output, override and approval logged. A panel member who asks what a figure rests on can be taken to the rubric criterion, the item, the marker and the response.

The educator view sits underneath the programme view and draws on the same signed results; tracking student progress covers that layer for teachers and tutors.

What should the platform not decide?

The verdict. The platform supplies evidence against your framework; what the panel accepts is the panel's decision, and the case is the committee's to make. NUADU does not claim that any export satisfies a named standard — only that the evidence is traceable and was produced in the course of ordinary work.

The same restraint runs through the views. The institutional view carries no automated individual prediction. Where the Programme reviewer is switched on, it identifies where intended learning outcomes are being met and where they aren't, and hands that to academic committees for human curriculum and programme decisions. In a competency-based programme, each item can be connected to a specific intended learning outcome, and the academic team reviews and decides on progression — the system does not.

Frequently asked questions

What is an accreditation self-study report?

An accreditation self-study report is the document a programme or institution prepares for its accreditor, assessing itself against the accreditor's standards and supporting each claim with evidence. Its assessment section rests on the four kinds of evidence above. NUADU's programme view produces accreditation-ready exports for that section; the narrative and the judgement remain the institution's.

What is quality assurance in higher education?

Quality assurance in higher education is the set of internal and external reviews that check whether programmes meet the standards they claim. For assessment, it asks whether items work, whether marking is consistent and whether decisions can be traced. A QA office reviewing NUADU can ask for the documentation pack, which covers methodology, retention, data flows and a DPIA template.

How do you assess student learning outcomes for accreditation?

Connect each item to the intended learning outcome it evidences, mark it against a rubric, and report attainment across cohorts. On NUADU, intended-learning-outcome tracking sits in the programme view, and a competency-based programme can connect each item to a specific outcome. The academic team, not the system, decides what the results mean for progression or for the curriculum.

→ See the Higher education path