A lightweight change-management register — every production change is proposed with a blast-radius and rollback plan, approved by a change owner, then closed out with the actual outcome, so the record of what shipped and why is never lost.
Engineering and platform teams who want change control without a heavyweight CAB.
Quick answer
The Change approval register template is a ready-made workspace for Engineering and platform teams who want change control without a heavyweight CAB.
Change approval register template in short
Included when you apply it
Applying this template creates the 1 board below — with every list — and pre-loads 3 sample issues, all yours to edit. The automation rules further down are suggestions you can wire up next; they aren't created for you yet.
A preview of how this template lays out — the boards, their custom workflow states, and where the sample issues land. WIP caps show a badge.
Change register
Approve the production database migration window
Document the blast radius, the rollback plan, and the approver before the window opens.
Change request: rotate the production signing keys
Coordinate the cutover so in-flight tokens stay valid; record who approved the change.
Post-change review of last week's config rollout
These rules aren't created when you apply the template — they're recipes you can wire up in Settings → Automations once your board exists.
When
A change moves to 'Risk assessed'
Then
Require a documented rollback plan before it can be approved
When
A change is approved
Then
Stamp the approver and time, then notify the implementing owner
When
A high-risk change closes
Then
Open a post-change review card so the outcome is captured
Ready to spin this up?
Sign-up takes seconds. We build this template's boards, lists, and sample issues in your new workspace, all yours to edit.
FAQ
Sprint planning
A cycle-driven sprint board with WIP limits, estimates, and PR-linked issues — the default starter pack for product engineering teams.
View templateBug triage
An intake-to-resolution pipeline that separates triage from active fixing, with severity labels and reproduction notes on every card.
View templateRelease checklist
A repeatable release runbook as a sub-issue tree — cut, verify, ship, announce — so nothing ships half-checked.
View template