Solutions · By need · Accreditation readiness

From rescue mission to routine.

Readiness is not a folder you fill in the year before a visit. It is the ability, on any ordinary Tuesday, to show which criterion a piece of evidence satisfies and which requirements are still thin. Creatrix Campus captures evidence as the work happens, labels it to the standard it proves, and keeps coverage live, so the submission is assembled rather than reconstructed.

Request a demo See the four levels

Why it goes wrong

Nobody fails a review for lack of evidence. They fail for lack of a system.

The artefacts exist. The marking scheme was written, the committee did approve the change, the coordinator did record the action. What is missing is the one thing a reviewer needs: the link between a document and the requirement it satisfies, made at the time, by somebody who knew.

Without that link, readiness has to be manufactured. A campaign goes out, departments send what they can find, and the quality office spends months turning a folder of files into an argument, under deadline, using the people the institution can least spare.

The problem: readiness manufactured under deadline.
Six reasons the scramble repeats Each one is a habit, and each one is fixable at the point of work.
  • Evidence is filed by person, not by criterion Personal drives and shared inboxes
    Invisible to the quality office until it is asked for
  • The mapping lives in one spreadsheet Maintained by one person, between other jobs
    Readiness depends on somebody not leaving
  • Gaps are found once a cycle A gap analysis run when the date is set
    The thin standard surfaces too late to strengthen
  • Numbers are retyped into reports Copied from an extract taken weeks earlier
    The claim and its proof quietly disagree
  • Nobody can prove what was true then Documents edited after they were submitted
    A dated claim cannot be defended later
  • Reviewers get a folder link Access granted broadly, tracked nowhere
    No record of who saw what, or when

Six habits, one consequence: the institution proves itself retrospectively, every single cycle.

What readiness actually means

Four levels, and most institutions are at two.

Everyone says they are audit-ready. It is worth being precise about which kind, because the difference is not how much evidence you hold, it is when the link to the criterion gets made.

Level 1

Ad hoc

Evidence exists. Nobody can find it.

Where it livesPersonal drives, inboxes, one shared folder.
When it is linkedNever, until somebody asks.
A review feels likeA search party with a deadline.
CostMonths of senior time, every cycle.
Level 2

Documented

Collected centrally, once the date is set.

Where it livesA central repository, filled by campaign.
When it is linkedAfter collection, by the quality office.
A review feels likeA project, staffed and scheduled.
CostPredictable, and repeated in full each time.
Level 3

Mapped

Linked to criteria, still gathered in bursts.

Where it livesA repository with a mapping alongside it.
When it is linkedIn batches, by whoever maintains the map.
A review feels likeManageable, if the map is current.
CostConcentrated on one or two people.
Level 4

Continuous

Labelled at the point of work, coverage live.

Where it livesOne governed library, filled as work happens.
When it is linkedAt creation, confirmed by a person.
A review feels likeA query against work you already did.
CostMinutes per artefact, spread across the year.
The jump that matters is three to four: not more evidence, but the link made at the time.

How it is done

Six moves, none of which require a spare year.

Mapping and ownership come first, because everything downstream depends on a requirement having a home and a name against it. After that, readiness accrues on its own.

Nothing yet Crisis work Owned and steady Both running
  1. 01

    Map the standards once

    Load the framework you report against and map its criteria to your own programmes, courses and committees, so every requirement has a home in your structure rather than in a document.

    Standards · Criteria
  2. 02

    Give every requirement an owner

    A person and a scope against each criterion, so a thin area has somebody accountable for it rather than a shared inbox and a hope.

    Owner · Scope
  3. 03

    Capture where the work happens

    Artefacts are filed inside the course or committee that produced them, labels are suggested automatically, and a person confirms them. Nothing is filed on its own.

    Capture · Confirm
  4. 04

    Read coverage, do not run it

    Each requirement shows whether evidence exists for it, so gap analysis stops being an exercise and becomes something you glance at in a monthly meeting.

    Coverage · Gaps
  5. 05

    Author on calculated figures

    Start from a template with live institutional numbers already in place and write judgement rather than data. On publish the document freezes: numbers locked, PDF produced, filed.

    Template · Frozen
  6. 06

    Share under control

    Reviewers get scoped access to the evidence behind each criterion, and every view, download and share is recorded, so access is answerable rather than assumed.

    Access · Audit

On the day

Six questions a reviewer asks, and where the answer comes from.

None of these are unreasonable. They are only difficult when the answer has to be assembled in the room rather than retrieved.

Show me the evidence for this criterion.
FromCoverage, where every requirement lists what is backing it, with the artefacts one click away.
Where did this figure come from?
FromCalculated KPI values that documents reference rather than restate, so the number in the report and its source are the same thing.
Is the programme being delivered as approved?
FromVersioned curriculum against actual delivery, so the approved version and what ran can be compared rather than asserted.
How do you know students met the outcomes?
FromAttainment calculated from live performance, traceable to the cohort, the assessment and the marking scheme behind it.
What did you do about the last finding?
FromActions recorded against the requirement they address, with the decision, the owner and the date still attached.
Was this document changed after submission?
FromPublished documents that freeze on publish, with locked numbers and a date, so what you submitted is what remains.

Go deeper

Readiness is the visible part of a lifecycle.

Evidence is produced by curriculum, delivery, assessment and people. These are the pages that explain where it comes from and who runs it.

By role The QA office view Library, tagging, review, coverage, documents and governance: the six surfaces the quality team works in. See the role page → Lifecycle Quality & Accreditation Standards, evidence, gap analysis, reporting and improvement, end to end. See the lifecycle → Lifecycle Assessment & Outcomes Where the proof behind any claim about academic quality is actually generated. See the lifecycle → Lifecycle Academic Governance Curriculum versions and approval chains: approved against delivered, without an investigation. See the lifecycle → In practice Institutions already doing this Universities and colleges across Europe, the Middle East, Southeast Asia and Oceania, and the frameworks they report against. Meet our customers → Product Continuous Evidence The capture and labelling layer that makes level four possible at all. See the product →

What it runs on

The products that make readiness continuous.

Adopt the evidence layer on its own, or with the lifecycles that produce the evidence. The record model underneath is the same either way.

Standards
Accreditation & Evidence →

Standards mapped to your structure, evidence tagged to the criterion it proves, coverage against every requirement.

StandardsEvidenceCoverage
 Capture
Continuous Evidence →

Artefacts captured and labelled at the point of work, with a person confirming before anything is filed.

TaggingReviewLibrary
 Proof
Outcomes & Attainment →

CO and PLO attainment calculated from live performance, so an outcomes claim has a cohort behind it.

OutcomesAttainmentOBE
 Currency
Curriculum & Catalog →

Versioned curriculum and approval history, so approved and delivered can be compared on demand.

VersionsApprovalsMapping
 Artefacts
Examination Management →

Question papers, marking schemes, moderation and results: the documents a reviewer asks for first.

PapersModerationResults
 People
Faculty Management →

Qualifications, workload and scholarly activity evidenced from the faculty record, not a CV request.

QualificationsWorkloadActivity
Start with the evidence layer. The lifecycles feed it as they run.

Institutions have used Creatrix to organise the documentation an accreditation actually requires.

Our vision was to be able to map our curricula against our regulatory body’s expectations and provide various reports enabling us to research all activities in relation to this mapping. The Creatrix Campus application has not only helped to evaluate our curricula; it has been key in organising the documentation necessary for accreditation.
Audrey Nolan · Dental Studies Manager Dublin Dental University Hospital
Bespoke change log and search functions permit quick tracking of these items, while the reporting feature allows us to work within the app online, or to export in other formats for sharing or analysis.
Dr Maria T van Harten · Curriculum Mapping Project Officer Dublin Dental University Hospital

Frequently asked

Plain answers about readiness.

What does accreditation readiness actually mean?

Readiness means that at any moment you can show which criterion a piece of evidence satisfies, and see which requirements are thin.

It is a state the institution is in, not a project it runs in the year before a visit. The practical test: if a reviewer asked today, would you retrieve the answer or assemble it?

We have a visit in nine months. Is it too late to change how we work?

No. Mapping the standards and giving each requirement an owner can be done early, and everything produced from that point onward is captured and labelled as it happens.

Historical artefacts are imported alongside it, so the submission is assembled from one place rather than from a campaign. You will not get a full cycle of continuous evidence, but you will get the last two thirds of one.

Which standards and accreditors does this support?

The model is standards-agnostic. You load the framework you report against and map its criteria to your own programmes, courses and committees.

Institutions commonly run a national regulator, one or more programme accreditors and an internal quality framework side by side, against the same evidence, because an artefact can satisfy more than one requirement.

How is this different from a document repository?

A repository stores files. Readiness requires that each file answers a question: which criterion does this satisfy.

Evidence in Creatrix carries the standard, KPI, course and term it belongs to, which is what allows coverage to be calculated rather than asserted, and a gap to be found before a reviewer finds it.

Can our numbers be challenged at a review?

KPI values are calculated from the source data rather than typed in, and authored documents only reference them, so the figure in a report always matches its proof.

Published documents freeze on publish, with their numbers locked and a date attached, so what was submitted is what remains.

How much of this lands on faculty?

Filing an artefact becomes a short task inside a lecturer’s own course, with labels proposed automatically and confirmed by a person.

Set against the alternative, repeated last-minute requests from the quality office for documents written months earlier, it costs faculty considerably less time, not more.

GET STARTED

Tell us which standards you report against, and when the next visit is.

We will map your framework against the evidence your institution already produces, and show you where the thin areas would be today.

Request a demo Talk to us