A change request form template for ad and tracking changes

A change that is not written down cannot be checked or undone. A short request form turns every change into a record that can be reviewed before it reaches the account.

Operations · 4 min read · Updated 2026-10-07

The form

  • 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.

Tick it off

Your ticks stay in this browser only.

Built for shop owners, creators and agencies. Stock photos, not customers.

Run the next client review from one screen.

We open one agency at a time, with your own accounts connected read-only first.

Request access

How we plan to price it