UnixTime

Research Note

Source Code Change Control Checklist

  • Updated Jun 17, 2026
  • Read 01 min read
  • Status reviewed

Use this checklist when reviewing whether code, scripts, macros, reports, and database logic changes are controlled before release.

On this page

When to use this

Use this checklist when reviewing whether code, scripts, macros, reports, and database logic changes are controlled before release.

Checklist

  • Change request or issue exists.
  • Business or technical owner approved the change.
  • Code review completed.
  • Security impact considered.
  • Tests completed.
  • Branch protection or merge approval applied.
  • Build artifact is traceable to source change.
  • Release approval recorded.
  • Rollback or recovery path exists.
  • Production deployment was performed by authorized personnel.

Change record

Change ID Repository/component Reviewer Test evidence Approval Release date Notes
TBD TBD TBD TBD TBD TBD TBD
  • Template
  • Iso27001
  • Technological controls
  • Source code
  • Change control

Note Metadata

Aliases: Code Change Checklist

Source: 90 Templates/Source Code Change Control Checklist.md