Change management your auditors can test in minutes.
Request, assess, approve, implement and review IT changes, with approval boards and separation of duties enforced rather than hoped for.
Change management is a lifecycle with evidence gates, and SOX IT general controls test it every year. That makes it a natural first application for IT, alongside the tools you already run.
The starting spec
This is what the App Configurator generates when you start from this example. Every row is editable before you publish, and every mechanism stays available inside the running app, so the app can keep changing after launch.
| Kind | Name | Definition | Notes | |
|---|---|---|---|---|
| 1 | Hub | change_request | title · type (standard/normal/emergency) · risk · systems_affected · requester | Primary record |
| 2 | Child | approval | change_request 1 → n · approver · decision · rationale | Change board votes |
| 3 | Child | task | change_request 1 → n · implementer · steps · backout_plan | Implementation work |
| 4 | Index | window_unique | (system, window_start) unique | Blocks conflicting windows |
| 5 | States | change.lifecycle | Draft → Assessed → Approved → Scheduled → Implemented → Reviewed → Closed | Emergency path recorded separately |
| 6 | SoD | implement_rule | implemented_by ≠ approved_by | Separation of duties |
| 7 | Report | unapproved | Changes implemented without approval (target: zero) | Control test |
| 8 | Report | change_failure | Failed and backed-out changes by system and team | Dashboard |
Early accessOpen this spec in the App Configurator, change what doesn't fit, and download the application file.
The lifecycle
The control auditors test is simple: every production change was approved by someone other than the person who made it. Here that is a rule the record enforces, not a sample someone checks.
| Transition | Who may make it | What must be true | Result |
|---|---|---|---|
| Draft → Assessed | Change manager | Risk rated; affected systems listed | Allowed · attested |
| Assessed → Approved | Change board quorum | Quorum reached; backout plan attached | Allowed · attested |
| Scheduled → Implemented | Implementer, never an approver | Window open; tasks complete | Allowed · separation of duties checked |
| Implemented → Reviewed | Change manager | Outcome and verification recorded | Allowed · attested |
| Draft → Implemented | No one | Transition not defined | Refused · refusal recorded |
What you get that the usual tools don't give you
Control tests become a query
The "changes without approval" report runs against attested records. Auditors test the control, not a sample.
Fast, but never invisible
Emergency changes follow their own lifecycle, with retrospective approval required and recorded.
Agents that open changes, not doors
An agent can draft a change and its backout plan. It cannot approve its own work.
Start from this spec.
Open it in the App Configurator, rename it in your terms, change what doesn't fit, and review the result before anything runs. Your license includes full access to its source. Or bring it to the development advisory and we'll shape it with you.