Skip to content

Stockertim Dictionary · Audit and assurance · Technology

Program change control

Also called change management, change control, program change management, software change control

In short

The controlled process by which changes to software and configuration are requested, approved, tested, documented and moved into the live system.

  • Advanced
  • Process
  • Checked

In detail

Every change to a live system carries risk. A badly tested update can corrupt data or switch off a key control, and an unauthorised change can be used to commit fraud. Program change control, one of the main IT general controls, makes sure changes happen in an orderly way. A typical process requires a documented request, assessment of the impact, approval by the business owner, development in a separate environment, testing including user acceptance, approval to deploy and a record of what was changed, when and by whom.

Segregation is central. The developer who writes a change should not be the person who moves it into production, and nobody should be able to change live programs or configuration directly without passing through the process. Emergency changes need a fast route, but with retrospective approval and review.

Auditors test change control by comparing a list of changes actually made in the system, often from system logs, with the approved change records, and sampling changes to check that each step was followed. Changes that appear in the logs but not in the records are a serious finding.

In practice

Most organisations use ticketing systems to run change control, with change advisory boards for significant changes.

Watch out

  • Developers with access to production can bypass the whole process.

Learn it properly

Official sources

Facts last checked on 3 November 2026.

Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.

English