Template & checklist · pre-build control sheet

UTM Naming Template

Use the governed sheet that sits between naming rules and URL building. Keep approved values, ownership, row state, exceptions, and handoff readiness in one place before links reach build or QA.

Download template suite Download workbook
Primary jobPre-build control
Main risk it solvesRow drift
Best outcomeClean handoff

Sheet architecture

The template controls the row before the URL exists. It keeps the request, approved values, owner, state, and exception history visible so the build step starts from one governed line instead of scattered notes.

Approved inputsSource, medium, campaign, content, and term values should arrive from governed naming and taxonomy rather than free text.
Visible ownershipEvery row needs a named owner, approver, and last editor before it moves to build or release.
Clear stateRequest, approved, built, QA-ready, live, and archived should be visible without guessing which stage the row is in.
Clean handoffThe sheet should send one controlled row into the builder and final QA rather than absorbing post-launch proof or reporting notes.

Core columns and row lifecycle

The template works when the row moves through a simple, visible sequence instead of being rebuilt from scratch at every handoff.

01Request

The row opens with campaign context, destination, owner, and requested launch details.

02Approve

Values are checked against the naming rules and approved dictionary before anything is built.

03Build

The approved row moves into the builder to assemble the candidate URL.

04Release

The finished link goes through final QA and signoff before it is published.

Exceptions and version control

Exceptions should be logged, approved, and reviewable. Reruns, cloned campaigns, and reused rows need version notes so teams can tell whether the line is still valid or only looks familiar.

Log exceptionsEvery one-off value needs a reason, approver, and review date.
Do not overwrite historyReuse should create a new controlled row or version note, not silently rewrite the original.
Keep sheet purpose cleanDo not turn the template into the post-launch evidence log or monthly reporting sheet.

Go deeper in naming control

Lock the naming rules Keep the writing pattern stable before values hit the template. Lock approved values Keep the dictionary, aliases, and field meaning under control. Normalize raw labels Clean incoming values before they reach the template or the builder. Assemble the final URL Move approved rows into the builder only after the template is ready. Run final signoff Use the human release gate after build and before launch.