# Tracking plan change list: <plan name> v<version>

- Baseline: window <YYYY-MM-DD> to <YYYY-MM-DD>, as of <YYYY-MM-DD>, tools <tool: project or stream placeholders>
- Audit report: <path or link>
- Prepared by: <agent run or role>. Applied by: <role per system>. Destination verification by: <role>
- Status: draft, not applied. Nothing in this list has been changed in any tool, tag manager, CDP or plan copy.

## Summary

- Privacy: <CR numbers>
- Double counting and wrong values: <CR numbers>
- Missing data: <CR numbers>
- Plan amendments: <CR numbers>
- Hygiene (separate release): <CR numbers>
- Numbers expected to move after release: <metric or report, direction, rough size, who has been told and when>

## CR-<n> <short title> (<finding IDs and rules>)

- Findings closed: <F-numbers with rule IDs; one hypothesis can close several findings>
- System to change: <application code | tag manager | CDP mapping or destination filter | tool configuration | enforcement copy (Protocols, Amplitude Data, Avo, RudderStack) | warehouse model | plan only>
- Entity: <tool>, <event>, <property>
- Current state (from the inventory): <numbers with denominator, share and window, for example "duration_ms sent as text in 612 of 18,450 rows (3.32%), 2026-10-03 to 2026-10-30">
- Change: <exact edit, at the emitter, tag or mapping>
- Plan edit: <field, current, proposed, change class (correction, documentation, compatible, breaking, rename), version bump yes or no>, or none
- Why: <the defect and its consequence in one or two sentences>
- Could break: <consumers that read the current behaviour: reports, cohorts, key events, ad conversions, workflows, warehouse models>
- Depends on: <other CR numbers, or none>
- Test cases and evidence per layer:
  - <case>: emission <payload or log line>; collection <CDP debugger or live view>; destination <tool view or export row>; warehouse <row>; use <metric or workflow state>
- Test approval and data: <who runs it, staging or a flagged test account, test references, approval for anything that submits a form, order or consent choice on a live site>
- Destination records the test creates: <list, and who excludes them>
- Rollback: <revert the commit, republish the previous container version, restore the mapping>
- Rollback pairing: <when the application and a tag manager container both changed, the compatible pair to restore together, or "single system">
- Rollback does not undo: <data already collected stays split or wrong; blocked data cannot be recovered; plan copies changed separately>
- Reporting annotation: <who annotates which reports for which dates>
- Post-release check: <re-run the inventory for this event over 7 days or 1,000 events, whichever is later; expected result>
- Owner sign-off: <role, date>

## Not changed, needs a decision

- <finding>: <question for the owner, for example "adopt export_clicked as a planned intent event or retire it?">, owner <role>, due <YYYY-MM-DD>

## Checked outside the inventory

- Emitter search: <roots searched and what was found, per event marked not observed>
- Live payloads: <test-account payloads captured, with the approval for each live test>
- Enforcement copies: <Protocols, Amplitude Data, Avo or RudderStack copy compared with the canonical plan, differences found>
- Tool-side rules: <GA4 created and modified events, Amplitude transformations, Mixpanel merges, CDP destination filters>