Glossary · Term
A dated, authored record of every configuration change made to a platform or integration, with reason and rollback path.
Definition
A change log is not a comments field in a platform. It is a discrete artifact — a wiki page, a shared document, a repo file — that records what changed, who changed it, why, and how to reverse it. Every revenue-impacting configuration change needs an entry, and the log needs to be legible without the operator present.
Why it matters
Change logs are the difference between a five-minute incident and a two-day forensic exercise. When revenue drops on a Monday, the log answers what changed on Friday. Without one, the network reconstructs from platform audit logs, buyer support tickets, and memory.
How it fails in practice
The log exists but is written by one person who abbreviates. Six months later, `updated cap rule` is unrecoverable context. Or the log is skipped for `small` changes that turn out to be causative. The discipline is uniformity: every change, every time, with the same fields.
Related terms
A 30-minute working session to map how this term shows up in your platforms, workflows, and reporting — and where it is currently exposed.