# Tracking fix list: <site or app>

- Source audit: <report link and date>
- Status: draft. Nothing in this list has been applied.
- Order: score-audit fix order (P1 to P4, then severity, impact and effort).
- Numbers expected to move after release, and who was told: <metric, direction, rough size, owner told on date>
- Container changes also follow gtm-container-audit's change list format (entity, current setting, change, test, rollback version).

## Rules

- One item per hypothesis. A test may depend only on its own change; anything else it needs becomes its own item.
- Every item names the system and the role who applies it, and the role who verifies at the destination.
- When a fix lowers a reported number (duplicates removed, VAT taken out of revenue), say so and tell the reporting owner before release, so a correction is not read as a drop in performance.

## FX-<n> <short title> (<priority>; <check IDs>)

- Finding: <one or two sentences with evidence IDs>
- Affects: <conversion or report, share of volume or revenue, used for bidding yes or no>
- System and owner: <system>; applies: <role>; verifies at the destination: <role>
- Draft change: <the exact change, field by field or line by line>
- Do not: <the tempting wrong fix and why it fails>
- Depends on: <other FX numbers, or none>
- Test: <steps, the requests expected, the destination evidence expected>
- Test approval and data: <who runs it, where, markers, test identities, test order references>
- Rollback: <what to restore>. Does not undo: <data already sent, records created, anything outside the change>
- Report annotation: <who annotates which reports for which dates>
- Effort: <S | M | L>. Hand-off skill: <skill, if any>
- Sign-off: <owner, date>

## Not changed, needs a decision

- <check ID>: <the question, and the owner who answers it>

## Release evidence to collect per item

- Configuration changed as written: <diff, version comparison or screenshot>
- Runtime behaviour matched: <HAR or Tag Assistant record of the test cases, and the har-audit output>
- The destination received the event once: <DebugView, Test Events, platform diagnostics or an order-ID match>
- A yes to the first does not stand in for the other two.