# UTM Naming Template Suite — Operating Guide

## Purpose
This pack is designed to make the naming sheet adoptable as a controlled operating asset, not a loose spreadsheet.

## Core operating rules
- No row goes live without a named owner.
- No controlled field becomes free text without a logged exception.
- No builder should have to infer campaign meaning from notes or chat history.
- No rerun should reuse an old row without a visible version tag.
- No post-launch reporting evidence should flood the active template.

## Suggested 30-day rollout
### Week 1
Lock the tab structure, required columns, status ladder, and approved values.
### Week 2
Force all new launches through requested → drafted → approved states.
### Week 3
Require exception logging and visible approvers before build.
### Week 4
Audit blocked rows, reruns, and archive discipline.

## Monthly template audit
- Are any controlled fields using free text?
- Are rows stuck in draft or built with no movement?
- Are exceptions still temporary?
- Are version tags being used on reruns and migrations?
- Is downstream evidence leaking back into the template?

## Boundary discipline
The suite is deliberately not a builder, QA checker, redirect audit log, or campaign reporting archive. It should hand off to those layers instead of competing with them.