Planning
Program gap review
Structure a high-level comparison between documented practices and a defined review baseline.
A program gap review builds a traceable picture of the current state before changes are proposed. It can connect requirements to procedures, personnel records, technique documentation, equipment controls, forms, and retained evidence across the selected method and facility boundary.
The output is a prioritised gap register with the source, observation, impact, owner, and recommended next action kept distinct. It is a planning tool, not a certification, accreditation, or substitute for an independent audit.
Inputs to prepare
Approved baseline
The specific requirements, customer expectations, or internal standard agreed for comparison.
Program records
Controlled documents, representative evidence, roles, interfaces, and change history.
Decision ownership
People authorised to interpret observations, accept risk, and approve next actions.
Turn comparison into a usable plan
Map
Connect each baseline topic to current documents, records, and owners.
Describe
Record the observed state and evidence without overstating conclusions.
Prioritise
Apply agreed risk, dependency, effort, and timing criteria.
Assign
Name the decision owner, next action, evidence of completion, and review date.
Who chooses the review baseline?
The organisation and appropriately authorised stakeholders approve it before comparison begins.
Is every difference a nonconformance?
No. Classification requires the agreed baseline, evidence, scope, and authorised judgement.