How to Replace Your ERG Charter With Something That Actually Works
The traditional ERG charter is a 6-page document nobody reads. Here's the lightweight, living replacement that actually drives the program.
[[youtube:YIC5inxuq5E]]
If your ERG has a charter, ask the last person who joined to find it. They can't. That's the problem. Charters were built for an era when ERGs were small, slow, and approval-driven. In 2026 they're a liability. This post is the direct answer to what to use instead, pulled from the video above.
Why traditional ERG charters fail
- They're written once, then ignored. A 6-page Google Doc nobody opens after Q1.
- They mix governance with operations. Mission statements next to meeting cadences.
- They use vague language. "Foster belonging" doesn't tell anyone what to do Monday morning.
- They're approval theater. They exist to satisfy legal, not to run the ERG.
This is the same root cause behind why structure is the real work of an ERG program — without a living operating doc, every quarter is improvised.
What to use instead: the 3Ps blueprint
Replace the charter with a one-page document organized around the 3Ps: Purpose, People, Programming.
Purpose (top of the page)
Two sentences. What this ERG exists to do for its members, and what it commits to deliver to the business. Not aspirational — operational.
People (middle)
The current leadership roster, the open roles, and the named succession plan. This is where you turn leadership roles into repeatable processes instead of relying on whoever remembers the password.
Programming (bottom)
The quarter's calendar at a glance — the Minimum Viable Quarter from the AI prep guide. What this ERG commits to doing in the next 90 days. Not a wishlist. A floor.
The rules that make it work
- One page. Always one page. If it grows, cut it.
- Revisited every quarter. Built into the rhythm, not the calendar app.
- Owned by the ERG, not HR. HR can host the template; the ERG owns the content.
- Linked, not attached. Live link, version history visible, never a PDF.
Pair it with the one-pager blueprint template and you have a governance doc that actually drives behavior.
What about legal sign-off?
Keep a separate, short governance addendum for legal — antitrust language, code of conduct alignment, brand usage. Two paragraphs. That's it. Stop bundling it into the doc the ERG actually uses to run.