# Review one admissions or programme journey.

Choose a real route and work through it with someone responsible for the facts and someone who does not know the institution.

Output: A short publishing brief with page decisions, content owners and the next review date.

- [ ] Name the audience and the task.
  For example: a prospective learner checking entry requirements, or a parent looking for the next open day. Keep current-student tasks separate.
  Keep: An audience, a task and its starting page.
  Owner: ____________________
  Notes: ____________________

- [ ] Check the programme facts together.
  Confirm level, location, dates, requirements and application status with the source owner. Record repeated instances that also need updating.
  Keep: Approved facts and a source owner.
  Owner: ____________________
  Notes: ____________________

- [ ] Follow the actual next step.
  Check the application, enquiry or booking destination and programme context. Agree any submission test with the receiving team; do not create a real application.
  Keep: The correct destination and a handoff owner.
  Owner: ____________________
  Notes: ____________________

- [ ] Review the documents and their sources.
  Is the prospectus or policy current and usable? Record the original editable file, its owner, version and the pages that link to it.
  Keep: A file decision, source and replacement owner.
  Owner: ____________________
  Notes: ____________________

- [ ] Give the next update a trigger.
  Ask an intended editor to try a date or document change in a safe preview. Set a term, policy or programme event that triggers review.
  Keep: An editor, reviewer, review trigger and retest note.
  Owner: ____________________
  Notes: ____________________

A blank review worksheet from Hilvy. Checkbox changes on the web page are not included in this download.
This is not an audit, certification, legal advice or a guarantee of search performance.
https://www.hilvy.io