Operations · 4 min read · Updated 2026-10-07
- Request ID and date: [a short ID, and the date the request was made].
- Client, account and item: [the exact store, ad account, campaign or tag, with its ID].
- Requested by and approved by: [names and roles, with the approval channel and time].
- What changes: [the current value and the new value, written exactly as they appear in the account].
- Why: [one sentence on the reason, tied to a number or a client decision].
- Expected effect: [what should move and by how much, or 'not measured'].
- Rollback step: [how to return to the current value, and who can do it].
- Read-back: [the check after the change, and the time it is due].
Rules
- No change goes live before the approval field is filled in.
- One request per change. Bundled changes make the read-back impossible to read.
- Keep the form next to the change log row it creates.
Made-up scenario: a request to raise the daily budget of one made-up campaign from 200 to 260 currency units. The client approves by email. The rollback step reads 'set back to 200'. The read-back is due the next morning.