International Education Services Group
Published
An evidence register is an index that helps people locate and maintain the information behind an institutional statement or review. It should tell the team what an item supports, where it is held, who owns it and when it needs attention.
The register is not a second archive and should not become a collection of sensitive records copied into a spreadsheet. Its value lies in reliable references and clear responsibility.
Decide what the register is for
Define the activity and intended users. The register might support a school self-review, a programme project, an institutional process or preparation for a particular external review.
This purpose determines the useful fields and access arrangements. A register for an operational team may need different detail from a package index used for formal transmission.
Do not label an internal review status as an official finding. The register should preserve the distinction between the institution's preparation and a determination made by another body.
Start with a small, useful field structure
| Field | Why it matters |
|---|---|
| Evidence identifier | Gives the team a stable reference when a title or file location changes |
| Scope or activity | Shows which provision or period the item concerns |
| Topic or requirement | Explains the question the item is intended to support |
| Title and source | Helps locate the original and understand its provenance |
| Owner | Identifies someone able to maintain or explain the item |
| Date and version | Distinguishes current, historic and working material |
| Access classification | Prevents an index from becoming an unrestricted disclosure route |
| Review status | Identifies what the team has and has not checked |
| Limitation or question | Keeps material uncertainty visible |
| Next action and trigger | Explains who needs to act and what prompts review |
Additional fields are useful only if someone maintains them. A complex register with unreliable entries can create more uncertainty than a simpler one that the team actually uses.
Assign ownership at the right level
The register owner manages the structure and maintenance process. Individual evidence owners remain responsible for the records within their control.
Agree who can add an item, confirm a version and change a status. If an entry depends on another department or partner, identify the person who can explain the source rather than assigning ownership to a general mailbox with no review responsibility.
A departure or role change should trigger reassignment. An institutional record should not become unusable because its only reference points to a former member of staff's private folder.
Link questions to evidence without duplicating files
One item may support several topics. Use stable references to the maintained source, with short notes explaining relevance where necessary.
Conversely, a single question may require several records. A procedure, decision record and follow-up action can each address a different part of the same operating question. The register should not imply that one document answers everything merely because it has the expected title.
When a formal process specifies a submission structure, map the working register to that structure without losing the institution's source and version record.
Keep access and version control workable
Use a source location suitable for the intended users and test the access needed for the task. Do not place personal data, passwords or unrestricted sensitive links in a widely shared index.
Distinguish a working draft, an approved current document, a historic record and material confirmed for a particular package. If a version changes, retain enough information to identify what was previously reviewed or transmitted.
Avoid informal labels such as “final final”. A version, date and accountable confirmation are more useful than a filename that suggests certainty without establishing it.
An illustrative register entry
Consider a hypothetical entry for a programme responsibility schedule. The index records the programme, document owner, controlled location, version and review date. It also notes that the schedule describes assigned roles but does not itself show how a recent change was approved.
The open question is then explicit: which operating record demonstrates use of the decision arrangement? A responsible person can locate that record or identify a genuine gap.
This example explains the method. It is not a client finding, an assessment result or a statement that every programme must use a document with that title.
Manage questions and changes
Review status should lead to an action when necessary. An entry marked “needs clarification” needs a question, an owner and an intended follow-up, not an indefinite colour code.
Useful review triggers include changes to provision, responsible personnel, operating systems, relevant source requirements or the intended use of the evidence. A periodic housekeeping check can supplement those triggers, but should not substitute for responding to a material change.
Keep completed actions distinguishable from verified implementation. If the institution reviews the effect of a change, retain the basis for its conclusion.
Keep the register proportionate
The measure of success is whether the team can locate and explain relevant evidence and identify unresolved work. It is not the number of rows or the apparent sophistication of the spreadsheet.
Remove redundant fields, broken references and duplicate copies through a controlled review. Retain what is needed for institutional accountability and the applicable process.
Tool and application
The editable CSV includes illustrative rows explaining the field structure. Delete those rows before entering operational information. The tool is an IESG working aid; official requirements remain at the responsible source.
Download the evidence register · Institutional quality improvement · Self-review support