Lesson 16 of 18

A Governance Cadence & Checklist

Conventions only hold if someone actually does them. The trick is to attach each habit to a moment that already happens, so governance becomes routine instead of a project you keep postponing.

Tie the habit to the moment

EVERY PUBLISH   Name + annotate the version. Preview first. Smallest change that works.
WEEKLY          Skim what published. Confirm no surprise tags. Resolve stale workspaces.
MONTHLY         Prune paused/triggerless tags. Check unreferenced variables & triggers.
QUARTERLY       Full audit: duplicates, Custom HTML to retire, permissions review.
ON OFFBOARDING  Remove the leaver's access the same day. Reassign owned tags.

The publish-time checklist

Does every new object follow the "Type - Vendor - Detail" naming pattern?
Is everything filed in a folder, nothing left unfiled?
Did you Preview the exact change, and does the version note say what and why?
Any new Custom HTML, does a template exist that should replace it?

Scaling the model

As the team grows

Lock publish rights to a small approver group.
Stage on a non-prod environment before production.
Write the conventions down where new hires will find them.

As the setup grows

A server-side container needs the same naming and folders.
More environments mean version notes matter more, not less.
Document the dataLayer spec alongside the container.

1Attach habit to a moment→2Run the checklist→3Review on a cadence→4Scale the gate

Key takeaway

Governance sticks when it's a cadence, not a cleanup: a publish-time checklist, a weekly skim, a monthly prune and a quarterly audit, with publish rights and environments tightening as the team and the setup grow.