Playbook Brand · Brand book · 08
Governance
Brand stewardship, review cadence, and how changes to the standard are managed.
10 min read · CC0 public domain
A brand system is only as good as its stewardship. Without clear ownership, regular review, and a process for updates, guidelines drift and consistency erodes. This chapter defines how to manage, maintain, and evolve the Playbook RG brand – and how to measure whether it’s working.
Brand stewardship
Who owns the brand
Every operator deploying Playbook RG should designate a brand owner – a person or team responsible for:
- Maintaining the guidelines and keeping them current
- Reviewing new content for brand consistency before publication
- Approving adaptations and exceptions
- Coordinating with legal/compliance on jurisdiction-specific messaging
- Training new team members on the brand system
- Managing the relationship with the upstream Playbook open-source project
Recommended ownership model
| Organization size | Recommended owner |
|---|---|
| Small operator (< 50 employees) | Marketing lead or product manager |
| Mid-size operator (50–500 employees) | Dedicated program manager |
| Large operator (500+ employees) | Team with brand manager, content strategist, and compliance liaison |
| Regulator / non-profit | Communications director |
Cross-functional involvement
While one person or team owns the brand, these functions should be consulted:
| Function | Consulted on |
|---|---|
| Legal / compliance | Jurisdiction-specific messaging, required disclaimers, advertising rules |
| Product / UX | Digital touchpoint design, feature placement, user flows |
| Customer service | Scripts, training content, front-line messaging |
| Marketing | Campaign messaging, co-branding, advertising |
| Data / analytics | Engagement metrics, content performance, player behavior |
Review cadence
Annual brand review
Conduct a comprehensive review once per year:
| Review area | What to check |
|---|---|
| Brand foundation | Do the mission, vision, and pillars still reflect the program’s direction? |
| Visual identity | Are assets current? Do colors and fonts still meet accessibility standards? |
| Voice and tone | Is the language guide current? Are there new terms to add or retire? |
| Messaging | Are taglines and CTAs still effective? Is the content still engaging? |
| Accessibility | Have WCAG standards been updated? New requirements? |
| Jurisdictions | Have regulatory requirements changed? All modules current? |
Quarterly regulatory check
Gambling regulations change frequently. Every quarter, verify:
- Jurisdiction-specific required messaging is still accurate
- Helpline numbers and URLs are still active
- Advertising rules haven’t changed
- Self-exclusion requirements haven’t been updated
- No new jurisdictions need to be added
Continuous updates
| Trigger | Action | Timeline |
|---|---|---|
| Regulatory change | Update affected jurisdiction module | Within 30 days of effective date |
| Helpline number change | Update _brand.yml and all content | Immediately |
| New jurisdiction launch | Create module from template | Before market launch |
| Content underperforming | Review and revise | Within 2 weeks |
| Accessibility issue | Fix | Within 1 week |
Content review rubric
Use this rubric when reviewing any new or updated Playbook RG content before publication. Score each dimension 1–3. Content must score 2+ on every dimension to ship.
| Dimension | 1 – Needs work | 2 – Acceptable | 3 – Excellent |
|---|---|---|---|
| Voice alignment | Sounds like compliance or clinical copy | Follows Playbook voice but could be sharper | Unmistakably Playbook – a friend explaining something interesting |
| Specificity | Uses generic phrases (“responsible gambling,” “play smart”) | Names some specific behaviors | Every sentence names a concrete action or fact |
| Stigma-free language | Uses clinical/judgmental terms in Tier 1 | Mostly clean, one or two terms to swap | Fully aligned with stigma-free language guide |
| Accessibility | Fails contrast, missing alt text, or broken keyboard nav | Passes WCAG AA, basic screen reader support | AAA where possible, tested on real devices |
| Actionability | No clear CTA or next step | CTA present but could be stronger | CTA is obvious, specific, and compelling |
| Visual quality | Looks like a compliance afterthought | Acceptable but not remarkable | Matches or exceeds commercial content quality |
Any dimension scoring 1 is a blocker. Fix before publishing. The content review rubric is a complement to – not a replacement for – the content approval workflow.
Post-deployment testing: The rubric evaluates content before publication. For testing how content performs with players after publication, see the Content Scorecard.
Version control
Semantic versioning
Playbook RG brand guidelines use semantic versioning (MAJOR.MINOR.PATCH):
| Version component | When to increment | Example |
|---|---|---|
| MAJOR (X.0.0) | Breaking changes to brand identity or architecture | Rebranding, new pillar system, structural reorganization |
| MINOR (0.X.0) | New content that doesn’t break existing usage | Adding jurisdiction, new collateral templates, new messaging |
| PATCH (0.0.X) | Corrections, clarifications, regulatory updates | Updated helpline number, corrected contrast ratio, typo fix |
CHANGELOG maintenance
Every change must be documented in CHANGELOG.md:
## [0.2.0] - YYYY-MM-DD
### Added
- Jurisdiction module: Australia (ACMA requirements)
- Interactive content: Game IQ quiz framework
### Changed
- Updated UK helpline number
- Revised session reminder messaging per A/B test results
### Fixed
- Corrected contrast ratio for accent-on-white combinationGit workflow
- Main branch contains current approved guidelines
- Feature branches for proposed changes
- Pull requests for review before merging
- Tags for each version release (e.g.,
v0.2.0)
Approval workflows
Content approval levels
| Change type | Approval required |
|---|---|
| Typo / formatting fix | Brand owner |
| Messaging update | Brand owner + compliance |
| Visual identity change | Brand owner + design lead |
| Jurisdiction module | Brand owner + legal/compliance |
| Voice / tone change | Brand owner + program lead |
| Structural change | Brand owner + executive sponsor |
Compliance sign-off
For content with jurisdiction-specific claims:
- Draft content following brand guidelines
- Cross-reference against the relevant jurisdiction module
- Have legal/compliance verify regulatory accuracy
- Document the review (date, reviewer, jurisdiction)
- Set a review date in the jurisdiction module
Training
Onboarding new team members
When someone new joins a team that creates Playbook content:
- Read the brand book – at minimum, the Introduction (Chapter 0) and Voice and Tone (Chapter 4)
- Review the glossary – understand preferred and avoided terminology
- Walk through
_brand.yml– understand how the configuration system works - Review existing content – read 3 examples that embody the Playbook voice
- Write a test piece – draft a short piece and have the brand owner review it
Estimated time: 2–3 hours for thorough onboarding.
Ongoing education
- Share examples of good and bad player education messaging (anonymized)
- When guidelines are updated, summarize changes for all content creators
- Consider an annual brand refresh workshop
- Monitor industry developments and share relevant findings
Brand audit checklist
Conduct a comprehensive brand audit annually, or when onboarding a new operator. This checklist covers every component of the Playbook RG system.
Identity
- Logo is used in an approved layout and minimum size
- Color palette matches
_brand.ymlconfiguration - Typography uses specified font families and weights
- Iconography follows the 2px stroke, rounded-cap style
Voice and tone
- All Tier 1 content passes the stigma-free language audit (8-point checklist)
- All Tier 2 content uses warm/direct tone – no humor, no playful elements
- Helpline framing is “for any question about gambling” (not crisis-only)
- No instances of “responsible gambling,” “gamble responsibly,” or retired phrases
Digital
- Content hub is accessible from primary navigation
- Helpline is visible above the fold on every page
- Footer strip present on all pages (logomark + helpline + age restriction + content hub link)
- All interactive elements are keyboard-accessible
- All content passes WCAG 2.1 AA contrast requirements
- Touch targets are 44x44px minimum on mobile
Print and environmental
- Print materials match digital design quality
- Helpline numbers are minimum 14pt bold
- QR codes link to correct URLs and have been tested
- Venue signage is readable from 3 meters
Governance
- Brand owner is designated and active
- Jurisdiction modules are current
- CHANGELOG is up to date
- Last quarterly regulatory check was within 90 days
Stewardship handoff process
When brand ownership transfers – whether to a new team member, a new department, or a new organization – follow this handoff process to maintain consistency.
| Step | Action | Timeline |
|---|---|---|
| 1. Knowledge transfer | Outgoing owner walks incoming owner through the entire brand book, _brand.yml, and key decisions made since launch | 1–2 sessions |
| 2. Access transfer | Transfer access to: Git repository, design files, content management tools, analytics dashboards | Day 1 |
| 3. Relationship mapping | Introduce the new owner to: compliance contacts, content creators, design team, jurisdiction specialists | Week 1 |
| 4. First audit | New owner conducts a brand audit using the checklist above | Within 30 days |
| 5. First review cycle | New owner leads a quarterly regulatory check and content review | Within 90 days |
| 6. Signoff | New owner confirms readiness and formally accepts ownership | After step 5 |
Document the handoff. The CHANGELOG should include: date, outgoing owner, incoming owner, and any decisions or exceptions that were in-flight during the transition.
Upstream contributions
If you’ve adopted Playbook from the open-source repository and made improvements, consider contributing them back.
What to contribute
| Contribution type | Impact |
|---|---|
| New jurisdiction module | High – helps operators in new markets |
| Translation | High – expands accessibility |
| Messaging improvements backed by data | High – evidence-based improvements benefit everyone |
| Accessibility improvements | High – helps all players |
| Bug fixes (broken links, typos, inaccuracies) | Medium – maintains quality |
| New collateral templates | Medium – expands the toolkit |
| Interactive content concepts | Medium – new quiz/calculator ideas |
How to contribute
See CONTRIBUTING.md for the contribution workflow and content standards.
Measuring success
North star: Operator adoption
The primary success metric for Playbook as an open-source project is operator adoption – the number of operators who fork, customize, and deploy the system.
| Metric | How to measure |
|---|---|
| Forks | GitHub fork count |
| Deployments | Self-reported (operators who share their implementation) |
| Contributions | PRs and issues from adopters |
| Star count | GitHub stars as a proxy for interest |
Downstream proof: Player engagement
For individual operators, the proof that Playbook works is player engagement with the content:
| Metric | How to measure |
|---|---|
| Quiz completions | Number of players who start and finish quizzes |
| Content engagement | Time on page, scroll depth, click-through on Playbook content |
| Tool adoption | Percentage of players with at least one active limit |
| Feature usage | Session reminder activations, bankroll planner usage |
| Share rate | How often players share quiz results or myth-busters |
| Return visits | How often players come back to the content hub |
Qualitative complement: These metrics tell you what players do. For why – whether content resonated, what they remember, and whether cultural adaptations improved the experience – see the Content Scorecard.
Content performance
| Metric | What it tells you |
|---|---|
| Quiz completion rate | Is the content engaging enough to finish? |
| Share rate | Is the content interesting enough to share voluntarily? |
| Helpline click-through | Are support resources findable when needed? |
| Deposit limit adoption | Are tools framed effectively as features? |
| Content hub return visits | Is the content worth coming back to? |
| Social engagement rate | Does the content earn attention on social media? |
What NOT to measure
Playbook is not a clinical intervention. Don’t measure:
- “Problem gambling reduction” (Playbook doesn’t treat conditions)
- “Harm prevention” (Playbook prevents nothing – it informs)
- “At-risk player identification” (Playbook doesn’t diagnose)
Measure engagement. Measure adoption. Measure whether players find the content useful and interesting. That’s the standard.
Previous: Chapter 7 – Application Guidelines | Next: Glossary