Change Log
Track IT changes from request through verification with system, risk, approval, window, and rollback fields, plus views and digests for upcoming work.
Included with every MangoApps plan.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Saas And Software Companies · Financial Services It · Healthcare Technology Teams · Manufacturing Operations · Professional Services
Overview
Change Log is a working IT change register added to your MangoApps workspace. It records what is changing, which system is affected, who requested it, its Low, Medium, or High risk, the planned Window, the Approver, and supporting Notes. Status follows a defined pipeline: Requested, Approved, Implemented, Verified, or Rolled back.
The app is designed for planned operational changes that need an approval decision, a scheduled window, and a post-implementation check. Managers and admins add records, while the requester is notified when a change is approved. Awaiting approval isolates Requested records, This week's windows shows approved changes within the next seven days, and Implemented, unverified highlights work that still needs verification. The Pipeline screen provides a metric row and board, while Full log provides a grid and action bar for record-level review.
Use it for release coordination, infrastructure maintenance, configuration changes, and other planned updates. It is not a ticket queue, incident register, or substitute for a detailed technical deployment record. It also does not automatically prove that a change was successful: the owner still needs to update Status to Verified or Rolled back and document the outcome in Notes. The Monday window list automation sends the app owner an AI summary digest titled This week's change windows at 08:00, based on the approved upcoming-window view.
Standards & compliance context
- The register supports change-management record-keeping by retaining the request, approval, planned window, implementation status, and verification outcome in one operational record.
- For regulated or audited environments, define who may approve each risk level and retain sufficient detail in Notes to explain the decision and final result.
- The template does not by itself establish a regulatory control, segregation-of-duties policy, or technical evidence standard, so align its use with your organization's applicable governance requirements.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Add the Change Log app to your MangoApps workspace and confirm the managers and admins who are allowed to add records.
- Create one record for each planned change, entering the Change, selecting the affected System and Risk, choosing the Window, and adding the Requester and relevant Notes.
- Leave Status as Requested until the designated Approver reviews the record and then set it to Approved when the change is authorized.
- Use the Awaiting approval and This week's windows views, along with the Pipeline screen, to review pending decisions and coordinate approved work.
- After the window, set Status to Implemented and use the Implemented, unverified view to ensure the result is checked before marking it Verified or Rolled back.
- Review the Monday This week's change windows digest and update Notes and Status so the register reflects the final outcome.
Best practices
- Create a separate record for each planned change so one approval and verification outcome is not mixed with unrelated work.
- Enter the affected System and Risk before requesting approval so reviewers can judge scope and operational exposure.
- Set Window to the intended implementation date rather than the date the request was submitted.
- Use Notes to record implementation results, validation evidence, rollback reasons, and follow-up ownership.
- Review Awaiting approval before each change-planning meeting and resolve stale Requested records instead of leaving them ambiguous.
- Treat Implemented, unverified as an action list and do not mark a change Verified until the intended system behavior has been checked.
- Use Rolled back when reversal occurs rather than changing the record to Verified or deleting the failed change.
- Check the Monday digest against actual plans and correct approved windows before the work week begins.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What changes is the Change Log template designed to track?
Use it for planned changes to systems such as the Data platform, ERP, Website, Network, and Application environments. Each record captures the change, requester, risk, window, approver, notes, and lifecycle status. It is a change register, not a ticket queue for incidents or general support requests.
Who should add and maintain change records?
The template is configured so only managers and admins add records. They can record the requester, assign an approver, set the risk and window, and update the status as work progresses. The requester is notified when the record moves to Approved.
How often should the register be reviewed?
Review Awaiting approval whenever new changes are submitted and check Implemented, unverified after each implementation window. The Monday window list automation sends the app owner a digest at 08:00 each Monday for approved changes scheduled within the next seven days.
Does this replace an incident or service ticket queue?
No. The Change Log is intended for planned changes and their approval and verification trail. Use an incident or request workflow for outages, break-fix work, user support, and unplanned service issues.
What happens when a change is rolled back?
Set Status to Rolled back and use Notes to capture the reason, result, and any follow-up. The record remains available for review so the team can distinguish a completed change from one that required reversal.
Can we customize the systems, risk levels, or statuses?
Yes. The select fields can be adapted to match your operating model, including additional system categories or risk terminology. Keep the lifecycle meaningful for your review process and preserve a clear path from Requested through verification.
Can this template connect to another ticketing or monitoring tool?
The supplied app includes its listed fields, saved views, screens, and automations; no external integration is specified. You can review the working app in a demo to determine how it fits alongside existing tools and where links or reference details belong in Notes.
How should we roll out the Change Log?
Add the app to your MangoApps workspace, confirm which managers and admins may add records, and agree on when a change becomes Approved or Verified. Start by recording upcoming windows, then use the Pipeline and Full log screens to establish the review habit.
Related templates
Ready to use this template?
Change Log runs on a platform app included with every MangoApps plan — pick a suite and it comes along.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
