Change Log¶
The Change Log provides lightweight change management for districts where a small team may plan, approve, implement, and troubleshoot the same change.
Quick Log¶
Use Quick Log for a routine change. Provide a descriptive title, category, impact level, implementer, and a useful summary. High-impact changes prompt for affected users and a back-out plan.
Full Change¶
Use Full Change for larger or riskier work. Capture the maintenance window, planned start and end, affected systems, user impact, detailed implementation plan, back-out plan, related ticket, and documentation links.
Use the log during troubleshooting¶
Search recent changes or use the calendar view when a problem begins after an earlier implementation. A detailed entry also becomes a repeatable procedure when a certificate renewal or configuration change returns months later.
Good change titles: Name the system and action—such as “Update SSL certificate on wireless controller”—so another technician can recognize the likely impact without opening every entry.
Video 4: Change Log — Watch on YouTube