A programme is review-ready when, on request, the institution can hand a reviewer a defined set of documents and the reviewer recognises what they are looking at.
That is the definition. It sounds modest. In practice, it disqualifies most providers in the field, because most providers cannot hand over the documents, not because they are hiding them, but because they were never written.
The documents themselves
The minimum set is shorter than people assume. A serious programme should be able to produce:
- Programme rationale. One page. Why this programme exists. Who it serves. What it claims to deliver.
- Learning objectives. Stated in operational language. On completion, the learner should be able to…
- Module outline. The sequence of modules, with topic and duration per module.
- Faculty profiles. Qualifications, experience, declared interests, and the section each faculty member is responsible for.
- Assessment plan. What is assessed, how, and what counts as completion.
- Certificate wording. The exact text that will appear on the certificate, with the issuing body and scope.
- Reference list with version dates. When references were last reviewed.
- Evidence-level mapping. Major claims tagged to the institution’s evidence hierarchy.
- Review and update cycle. When the programme will be re-reviewed.
- CPD/CE alignment statement. Where the programme stands with respect to external recognition, current and intended.
That is the whole list. Ten items. None of them are heroic.
Why most providers cannot produce them
The list looks easy until it has to be repeated across a catalogue. A single programme can be documented to this standard in a focused week. Two hundred programmes cannot, unless the governance model that produces them is itself built to produce documentation as a byproduct.
This is the test of a serious institution. Not whether one programme is review-ready, but whether the institutional process produces review-ready programmes by default.
What review-readiness signals
When an institution can hand over these documents fluently, it signals two things to a reviewer.
First, that the institution is internally disciplined. A team that maintains this documentation is a team that has thought about each component, made decisions, and recorded them.
Second, that the institution is durable. Review-ready documentation survives staff turnover, programme updates, and external scrutiny. It is the substance under the brand.
What it does not signal
Review-readiness does not mean accreditation. It does not mean recognition. It does not guarantee a positive review. A reviewer can read all ten documents and conclude that the programme is not appropriate for their context.
But the conversation will happen on substance, not on what is missing. That is what makes the institution review-ready: it has earned the right to a substantive conversation.
Most providers never reach this conversation. Their programmes can only be reviewed for what they show on a page. A reviewer with five minutes can dismiss them. An institution that has done this work cannot be dismissed in five minutes, and the difference is most of what credibility consists of.