Cambios Normales, Estándar y de Emergencia
Three paths through the same governed process — and the review that closes the loop after installation.
Normal changes
Most changes. They go to the committee at each gate — Pre-production and Production — and the decision is recorded with its Acta, its authorizer and its notes.
Standard changes
Low-risk, repeatable changes — a monthly patch, a certificate renewal — that a Committee Approver authorizes once, in advance, as an entry of the Standard change catalog with its procedure and an optional expiry date.
- The change names its catalog entry in its Committee tab before it is submitted.
- At each committee gate it is authorized by that pre-approval, recorded as a committee decision with the same audit trail.
- An expired or inactive entry no longer applies: the change waits for the committee like a Normal one.
- The catalog lives in Administration › Change governance, where the automatic authorization can also be switched off.
Emergency changes
- Justified before submission: what is failing, the impact and why it can't wait.
- Decided by a single Committee Approver without an Acta, at the top of the agenda.
- Allowed to install during a freeze window.
- Closed only with a completed post-implementation review (by default).
Revisión post-implementación
Once a change is installed in production, its Post-implementation review tab records the outcome (successful, with issues, failed, rolled back), whether its objectives were met, the incidents it caused, the downtime, what went well, what to improve and the follow-up actions. Completed, it is read-only and travels in the change's consolidated report and evidence package.