What this template is for
This worksheet exists to keep naming decisions explicit before they become buried inside platform setup and reporting cleanup.
Sheet 1: Pattern definition
| Position | Token | Required? | Format | Example | Owner |
|---|---|---|---|---|---|
| 1 | Channel | Yes | approved abbreviation | ps | Paid media |
| 2 | Market | Yes | ISO-like internal code | us | Marketing ops |
| 3 | Audience | Yes | controlled short name | revops | Campaign owner |
| 4 | Offer | Yes | lowercase slug | audit | Campaign owner |
| 5 | Objective | Optional | approved value | pipeline | Analytics |
Sheet 2: Approved values
Create one row per allowed token value with the full label, approved abbreviation, owner, effective date, and retired date. Do not silently repurpose a retired value.
Sheet 3: Examples and exceptions
Include at least five valid examples, three invalid examples, and the named exceptions your team expects. Add a reason, approver, and expiration date to every exception.
Adoption check
Ask a second operator to generate names from the worksheet without verbal guidance. Any point that requires explanation belongs in the worksheet before rollout.