1. Accreditation Management
  2. Who it's for
  3. Multi-institution quality offices
Who it's for

Multi-institution quality offices

A quality office working across institutions needs to compare progress without confusing each institution's evidence or policy. Accreditation cycles and standards belong to organizations, and people carry their organizational context. Use those references to establish who prepares the work and which institution's standard the reviewer is considering.

How Accreditation Management is set up for you

Institution ownership

A similarly named cycle at another institution is still separate work. Confirm the organization before selecting a standard, assigning an owner or attaching an observation.

Local policy context

Keep the effective period and policy reference with the standard. A shared framework name does not mean every institution uses the same version at the same time.

Scoped review

Agree authorized organizational access for each operator and reviewer. A shared quality office needs an explicit basis for examining another institution's cycle, including its supporting documents.

Comparable progress

Read cycle status alongside evidence outcomes and pending decisions. A Decided cycle may still require delivery work; use its actual decision and trace to explain progress.

A quality office working across institutions needs to compare progress without confusing each institution's evidence or policy. Accreditation cycles and standards belong to organizations, and people carry their organizational context. Use those references to establish who prepares the work and which institution's standard the reviewer is considering.

Pilot a bounded set of institutional cycles with named preparation owners and independent reviewers. Use deliberately similar cycle names to test whether the team can still identify the right organization and standard. Have Read Only Analyst compare progress while retaining the source institution in the explanation.

Include an access rehearsal using an account assigned outside the pilot institution. Check that ordinary working access follows the agreed scope. Next, review an uncertain delivery and a corrected successor so the central quality office can distinguish local preparation issues from execution exceptions. Resolve any difference in date conventions before comparing reporting periods. Expand only when each institution's owner can trace its submitted evidence, independent decision and recorded delivery without borrowing context from another institution.

[Rehearse permissions](/accreditation-management/roles) and [review reporting definitions](/accreditation-management/reports) before extending the rollout.

Features to start with

Roles on the team

Administrator
Maintains approved accreditation configuration: record entry on Accreditation Standards, read-only on all operational, review and provenance tables, and access to all four accreditation pages. No schema editing, deletion, bulk operations or export grants.
Accreditation Management Operator
Prepares assigned work: record entry on Accreditation Cycles, Criterion Evidence, Follow Up Actions and Evidence Documents, read-only on configuration, review and provenance tables. Scope to authorized organizations is enforced by workflow guards.
Accreditation Management Reviewer
Reviews independent assigned work: record entry on Review Decisions only, read-only on every other table. Reviewers cannot approve their own preparation; the workflow guards enforce reviewer independence.
Read Only Analyst
Reads authorized summaries and aggregates across every table plus the four accreditation pages. No record creation or editing, no schema or administrative capability.
Admin
Configures staff access, organizational reference records and reviewed source mappings during implementation without replacing independent accreditation decisions.

Set up Accreditation Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started