Approval workflows

Open review centre

Course outline route

Active v1

Sample Registry → School route, then Registry publish (DEMO).

  1. SubmissionRegistry Admin / Academic Services / Course Lead
  4. Completed10-day DEMO SLA from submission

Edit stage 1

Eligible reviewer roles2 of 6 selected

Assignment: any member of the selected roles. Named-reviewer assignment is not supported.

Route settings

Required evidence / checklist

  • At least one reviewed CLO linked (M10)
  • Assessment overview written

Derived from the record by the module; not editable here.

Matches active route

Version history

  1. Activev1Baseline (migrated from earlier configuration)SLA 10d · School review: School Reviewer/Dean → Registry publish: Registry Admin
How this worksShow

All routes, eligible roles and SLAs are samples pending WOU confirmation. The stages and their order follow each module's existing workflow (e.g. offering lists: course lead → Dean → ASU circulation), so stages can be renamed and re-staffed but not added, removed or reordered.

Activating creates a new route version. Reviews already submitted keep the version they were submitted under (stage roles and SLA), so audit and decisions are never changed retrospectively. Drafts and returned items pick up the active version when they are next submitted.

Assignment is "any member of the eligible roles"; naming an individual reviewer is not supported. Route roles control the review centre and in-app notifications; each record screen keeps its own permission checks.