Skip to content

Glossary Decisions & governance

What is change control?

Change control is the process for proposing, assessing, approving and recording changes to engineering items against an agreed baseline.

Also called configuration control.

Change control

Change control is the part of configuration management that governs how controlled items, such as requirements, designs, interfaces and verification plans, are changed. A change is proposed, its impact is assessed, it is approved or rejected, often by a change control board, and then it is carried out and recorded against the baseline. The record says what changed, why and who approved it.

Why it matters

Without it, nobody can tell whether the current design reflects deliberate decisions or drift. With it, every change has a reason and an assessed impact, and the design can be traced back to any earlier agreed state.

How it goes wrong

  • Letting edits, by people or by AI, reach the design without review
  • Recording a decision but not what it actually changed
  • Putting early exploration through a heavyweight change board, so people stop recording changes

In Cairn

Every change to a Cairn model is a ChangeSet, and every ChangeSet passes the same guard, which refuses it whole if it would leave a missing reference, an empty required field or a loop in the tree. AI proposals open in Change Review, where you see each record they would create, change or delete, with the AI's reasoning, and apply only what you tick. Hand edits apply at once. History keeps every change with its summary and a diff, and you can undo one or restore the model to any earlier point. This is change control for one person's model: Cairn has no baselines, change requests or approval by other people.

Questions

Is change control only for late-stage programs?
Formal change boards usually come later, but knowing what changed and why is useful from the first design decision.
Is Cairn a configuration management system?
No. Cairn reviews and records changes to one model, with undo and restore. It has no baselines, change requests or approval workflow between people.

See it on your own system.

Describe what you are building and Cairn interviews you, then builds the first model with you.