Skip to content
Playbook RG

Playbook Brand · Brand book · 07

Application guidelines

How the brand applies across digital, print, environmental, video, and audio, plus co-branding rules.

16 min read · CC0 public domain

This chapter defines how the Playbook RG brand system applies across channels and media – digital, print, environmental, and video/audio. The core principle: Playbook content should be woven into the player experience, not siloed into a separate “responsible gambling” section that nobody visits.


The integration principle

The biggest mistake operators make with player education content is treating it as a bolt-on – a separate “RG page” buried in the footer, a compliance checkbox disconnected from the actual player experience.

Playbook takes the opposite approach: integration over isolation.

Isolated (don’t do this)Integrated (do this)
A dedicated “Responsible Gambling” page linked from the footerPlaybook content woven into onboarding, account settings, game selection, and deposit flows
A helpline number in 8pt type at the bottom of the pageA helpline strip visible on every screen, properly designed and readable
A pop-up warning that players dismiss without readingA session reminder that provides useful context (time played, spend so far)
A static brochure PDF available for downloadInteractive quizzes, odds calculators, and shareable content in the content hub

The test: If a player can use your platform for a full session without encountering any Playbook content unless they actively go looking for it, the integration has failed.


General principles

1. Equal design investment

Playbook content gets the same design quality as commercial content. Same typography, same color system, same spacing, same layout principles. If the promotional banner looks like it was designed by a world-class agency and the player education section looks like a compliance afterthought, players will treat it accordingly.

2. One interaction to help

On every screen, page, or surface – a player should be able to reach a helpline number or support resource within one tap, click, or glance. Present, accessible, never intrusive.

3. Visible, not buried

Playbook content appears in primary navigation or settings – not in a submenu behind three clicks. Present in footers, account settings, and at key decision points (deposits, wager placement, session milestones).

4. Consistent across channels

A player should recognize Playbook content whether they see it on mobile, on a poster, or in a TV ad. Visual identity and voice stay consistent – only the format adapts.


Digital applications

Website

Landing page: Every operator site needs a Playbook content hub – a dedicated section for educational content, tools, quizzes, odds explainers, and support resources.

ElementRequirement
URLAccessible from primary navigation
Content hubEducational articles, quizzes, odds tools, feature guides
Tools overviewDeposit limits, session reminders, activity dashboard – all linked
HelplineProminently displayed above the fold
Footer presenceLink in global footer on every page

Footer strip: A persistent element on every page containing:

  • Playbook RG logomark (or text identifier)
  • Helpline number or link
  • Age restriction notice
  • Link to the content hub

Mobile app

Mobile is where most players gamble (60%+ of traffic). The mobile experience must be a first-class feature.

Key touchpoints:

MomentWhat to show
Registration / onboardingIntroduction to tools, optional limit-setting, first quiz
First depositDeposit limit prompt (optional but prominent)
During playSession awareness (configurable frequency)
Account settingsFull dashboard – limits, reminders, activity, quizzes
Limit reachedClear notification with support resources
Content hubQuizzes, articles, odds tools, myth-busters

Mobile design principles:

  • Touch targets: 44x44px minimum
  • Primary CTAs within thumb zone
  • One action per screen – don’t overload
  • Playbook tools accessible from hamburger menu or tab bar

Email

Playbook messaging should be woven into the transactional email lifecycle:

Email typePlaybook integration
Welcome seriesIntroduce Playbook, highlight tools, link to first quiz
Deposit confirmationInclude current limits and link to adjust
Monthly statementActivity summary with Playbook messaging
ReactivationSensitive re-engagement with prominent Playbook tools

Email rules:

  • Helpline number in every email footer
  • Playbook content uses the same font size and visual weight as commercial content
  • Never unsubscribe players from Playbook communications

Social media

Social media is where Playbook content earns organic reach through genuine engagement.

PlatformContent approach
Instagram / TikTokMyth-busting reels, quick tips, infographic carousels
X (Twitter)Quick facts, quiz hooks, odds breakdowns
FacebookLonger educational posts, community content
YouTubeEducational videos, how-it-works explainers
LinkedInIndustry-facing: program achievements, thought leadership

Social media rules:

  • Every profile bio includes helpline or support link
  • Content is designed to earn engagement, not just check a box
  • Quiz results and myth-busters are the highest-performing formats – lead with them

Tier 2 digital touchpoints

Tier 2 content (crisis/support) appears at specific moments in the player journey. These touchpoints use a different visual treatment – calmer, more white space, no playful elements. See visual-identity/tier-2/tier-2-visual-guide.md for the full visual specification.

TouchpointWhat to showVisual treatmentTone
Support/help pageHelpline (phone/text/chat), self-exclusion link, FAQWhite surface, navy text, teal CTA only, no orangeWarm / Direct
Self-exclusion flowDuration selection, confirmation, what happens nextSingle column, 640px max, one action per screenWarm / Direct
Activity dashboardTime played, amount spent, session count, trendsMuted data viz, no gamification, neutral paletteConfident / Informative
Limit-reached notificationCurrent limit, when it resets, support resourcesClear banner, not dismissible for 5 seconds, helpline visibleWarm / Direct
Cooldown/pause screenAccount paused confirmation, when it expires, supportMaximum white space, simple message, helpline prominentWarm / Direct
Post-session summarySession duration, spend, limit usage, support linkCard format, muted colors, no celebratory elementsConfident / Informative

The Tier 2 test: Can a player in distress find help within one tap? Is the helpline number above the fold? Is there anything playful, witty, or gamified on the page? If yes to the first two and no to the third, the Tier 2 implementation is correct.

Tier 2 implementation checklist

Before launching any Tier 2 touchpoint, verify the following:

CheckRequirementPass criteria
Helpline visibility1-800-522-4700 appears above the foldVisible without scrolling on all breakpoints
Color complianceNo orange, no vibrant accent colorsOnly navy, teal, and neutral grays used
Typography scaleBody text at 16px minimumMeets WCAG AAA for readability
White space ratioAt least 40% of the viewport is white spaceVisual breathing room is evident
AnimationNo spring, bounce, or celebratory motionOnly simple opacity fades permitted
GamificationNo points, badges, streaks, or progress barsContent is purely informational
IconographyFunctional icons onlyNo decorative or playful illustrations
LanguageWarm and direct – no wit, no wordplayReviewed against Tier 2 voice guidelines

Tier 2 content hierarchy

Every Tier 2 screen follows a strict information hierarchy:

  1. Primary: The support action – what the player can do right now (call, text, chat, self-exclude)
  2. Secondary: Context – what is happening and why (limit reached, session length, account status)
  3. Tertiary: Additional resources – links to FAQ, further reading, alternative support channels

Never invert this hierarchy. The support action always comes first. Context explains, but never blocks the path to help.

Transition between Tier 1 and Tier 2

When a player moves from standard content (Tier 1) to a support context (Tier 2), the visual transition should be deliberate:

  • Background shifts from brand colors to white
  • Accent color shifts from orange to teal
  • Typography weight increases for body text (improved readability under stress)
  • Layout simplifies – single column, fewer elements per screen
  • Playful brand elements (illustrations, mascots, decorative patterns) are removed entirely

This transition signals a shift in context. The player should feel that the platform is taking their situation seriously.


Print serves land-based venues (casinos, betting shops, lottery retailers) and community outreach.

FormatSizePurposeBest placement
PosterA2 / 18x24”High-visibility awarenessEntrances, restrooms, near ATMs
BrochureLetter / A4 tri-foldDetailed informationInfo centers, reception desks
Rack card4x9”Quick reference, portableCard racks near exits, host desks
Table tent4x6”Point-of-play reminderGaming tables, restaurants, bars
Business cardStandardHelpline contact cardGiven by staff, info centers

Print design rules:

  • Minimum logo height: 0.25 inches
  • Minimum body text: 10pt
  • Helpline numbers: minimum 14pt, bold
  • QR codes linking to digital content hub – test before printing
  • Design quality matches or exceeds commercial print materials

Environmental applications

Venue signage placement

LocationFormatContent priority
Entrance / exitWall-mounted or digital displayBrand awareness + helpline
Near ATMs / cashiersSmall sign or posterBudget reminder + helpline
Gaming floorOverhead or column-mountedQuiz QR codes, “Know your game”
RestroomsMirror cling or stall cardDiscreet helpline access
Break rooms (staff)PosterTraining reminders, player referral info

Design principles:

  • Readable from 3 meters for public signage
  • Match content length to dwell time (restroom cards > corridor signs)
  • Privacy-sensitive placement for helpline information
  • Multilingual in diverse communities

Video and audio applications

TV spots

FormatDurationStructure
Standard30 secondsHook (5s) → Message (15s) → CTA + helpline (10s)
Short15 secondsHook (3s) → Message (7s) → CTA + helpline (5s)

Creative direction: Feature real, diverse people enjoying themselves. Confident, energetic tone – not somber PSA energy. End with helpline displayed for at least 5 seconds.

Radio and audio

  • Speak helpline numbers clearly and repeat
  • Use a natural, conversational voice – not announcer energy
  • Match the warmth and confidence of the Playbook voice

Digital pre-roll

15-second pre-roll for YouTube and streaming platforms:

  • First 5 seconds work without sound (text overlay)
  • Helpline number as persistent text
  • CTA links to content hub or quiz

Motion and animation

Motion reinforces meaning and helps players understand system responses. All animation in Playbook RG content follows four principles: purposeful (every animation has a reason), fast (never make users wait), accessible (respect prefers-reduced-motion), and consistent (same patterns everywhere).

PatternDurationEasingUse case
Micro-interaction150-200msease-outButton press, toggle, selection
Panel transition300-500msease-outPage navigation, drawer open
Data visualization600-800msease-out, staggeredChart entrance, quiz results
Modal/dialog200ms backdrop + 250ms contentease-out, scale from 95%Limit reached, session reminder
Toast notification300ms slide-in, 5s displayease-outConfirmation messages

Tier 2 motion: Support contexts use slower, subtler animation – no spring/bounce easing, no celebratory motion, no staggered reveals. Simple fades only. See visual-identity/motion/motion.md for the complete specification including CSS custom properties.

Reduced motion: All animation must respect the prefers-reduced-motion media query. When reduced motion is active, show all content instantly – keep opacity fades at 100ms but disable all transform-based animations.

Animation do’s and don’ts

DoDon’t
Use animation to confirm a player action (button press, limit saved)Animate purely for decoration or visual flair
Keep durations under 500ms for interactive elementsUse animations longer than 1 second for any UI response
Stagger chart data entrance so players can follow the narrativeAnimate all data points simultaneously (overwhelming)
Fade content in when it enters the viewportUse slide-up reveals that shift page layout
Provide instant fallback when prefers-reduced-motion is activeAssume all users can tolerate motion

Loading and skeleton states

When content loads asynchronously, use skeleton screens rather than spinners:

  • Skeleton blocks match the shape and position of incoming content
  • Use a subtle pulse animation (opacity 0.6 to 1.0, 1.5s duration, infinite loop)
  • Replace skeleton with real content using a 150ms crossfade
  • Never show a spinner for loads under 300ms – show nothing instead
  • For Tier 2 contexts, use static gray placeholder blocks (no pulse animation)

Haptic feedback (mobile)

On supported devices, pair micro-interactions with light haptic feedback:

ActionHaptic pattern
Limit saved successfullySingle light tap
Self-exclusion confirmedSingle medium tap
Quiz answer selectedSingle light tap
Error / validation failureDouble light tap
Toggle switchSingle light tap on both on and off

Haptic feedback is always optional and respects system-level accessibility settings. Never use haptic patterns that could be interpreted as celebratory or rewarding in Tier 2 contexts.


Co-branding rules

When Playbook RG content appears alongside the operator’s brand:

Visual hierarchy

RuleRationale
Playbook logo no smaller than 60% of operator logo heightPrevents visual subordination
Same or larger font size as surrounding commercial copyPrevents the “fine print” effect
Helpline numbers in bold or distinct weightEnsures readability
Adequate white space around Playbook contentPrevents visual crowding

The adaptive identity in practice

  • Operators replace: Colors, fonts, logo, program name, helpline numbers
  • Operators keep: Layout patterns, information hierarchy, icon system, voice and tone, message structure, accessibility standards

A player who sets deposit limits on Platform A will recognize the same flow pattern on Platform B – even though the two platforms look completely different. The consistency is in the structure, not the skin.

Non-RG marketing pairing

Where jurisdictions require or operators desire Playbook messaging alongside commercial advertising:

  • Playbook elements complement the promotion, not contradict it
  • Helpline information is integrated, not tacked on as fine print
  • The transition between commercial and Playbook messaging feels natural
  • Playbook messaging uses the same production quality as the commercial content

The goal: A player seeing a promotional ad with Playbook messaging should think “this brand takes me seriously” – not “here’s the legal disclaimer.”


Responsive design

Breakpoints

BreakpointWidthPrimary context
Mobile< 768pxPhone, in-app
Tablet768px – 1024pxTablet, small laptop
Desktop> 1024pxDesktop browser

Responsive rules

  • Helpline strip: Collapses from full text to icon + number on mobile
  • Navigation: Playbook section in hamburger menu on mobile; main nav on desktop
  • CTAs: Stack vertically on mobile; inline on desktop
  • Tables: Convert to card layouts on mobile

Component-level responsive behavior

Beyond the basic breakpoints, specific Playbook RG components have defined responsive behaviors.

ComponentMobile (< 768px)Tablet (768-1024px)Desktop (> 1024px)
Helpline stripIcon + number onlyFull text, single lineFull text + multiple contact options
Quiz cardFull width, swipe to advanceCentered, 600px maxCentered, 640px max, keyboard nav visible
Activity dashboardStacked cards, sparklines2-column grid3-column grid, full charts
Deposit limit controlFull-width sliderInline slider + inputInline slider + input + comparison
Support resource blockStacked, phone first2-column, all channels visible3-column with descriptions
Social sharing cardFull-width previewSide-by-side preview + shareSide-by-side with platform selection
Session reminderBottom sheetCentered modalCentered modal, 480px max

Always test at each breakpoint. Component-level responsive behavior should be smooth – no layout jumps, no content disappearing, no touch targets shrinking below 44px at any size.

Touch target specifications

All interactive elements must meet minimum touch target sizes across breakpoints:

Element typeMinimum sizeMinimum spacingNotes
Primary CTA button48x48px8px from adjacent targetsIncludes deposit limit save, self-exclude confirm
Secondary button44x44px8px from adjacent targetsIncludes cancel, back, learn more
Icon button44x44px (hit area)12px from adjacent targetsVisual icon may be smaller; hit area must meet minimum
Text link (inline)44px height (hit area)N/AUnderline on focus/hover; sufficient line height
Checkbox / radio44x44px (hit area)8px between optionsLabel is part of the hit area
Slider thumb44x44pxN/AIncludes deposit limit slider, session reminder duration

On mobile, if two interactive elements cannot maintain 8px spacing, stack them vertically rather than reducing their size.

Responsive image and media handling

Asset typeMobileTabletDesktop
Hero illustrationHidden or simplified version50% width, right-aligned40% width, right-aligned
InfographicStacked sections, scroll to revealTwo-column layoutFull layout, side-by-side
Data chartSparkline or simplified bar chartStandard chart, horizontal scroll if neededFull chart with legend and annotations
Video embedFull width, 16:9 aspect ratioCentered, 80% widthCentered, max 960px width
Quiz card imageAbove question, 100% widthInline left, 40% widthInline left, 30% width

Always serve appropriately sized image assets per breakpoint. Use srcset and sizes attributes to prevent mobile devices from downloading desktop-sized images.

Orientation handling

Account for both portrait and landscape orientations on mobile and tablet:

  • Portrait (default): Standard layouts as defined above
  • Landscape mobile: Reduce vertical padding, keep single-column layout, ensure helpline strip remains visible
  • Landscape tablet: Can switch to desktop-style two-column layouts where appropriate
  • Lock orientation only for the self-exclusion flow (portrait) to prevent accidental input errors during a critical process

Testing protocol

Before any Playbook RG implementation goes live, verify responsive behavior with the following device matrix:

Device categoryExample devicesTest priority
Small phoneiPhone SE, Galaxy A seriesHigh – smallest common viewport
Standard phoneiPhone 15, Pixel 8High – most common viewport
Large phoneiPhone 15 Pro Max, Galaxy S UltraMedium
Tablet portraitiPad 10th gen, Galaxy Tab SHigh – breakpoint boundary
Tablet landscapeiPad Pro 12.9”Medium
Small desktop1280x800 laptopHigh – minimum desktop target
Large desktop1920x1080 and aboveMedium

Run each test scenario with assistive technologies active (screen reader, increased text size at 200%, high contrast mode) to confirm that responsive behavior does not break accessibility.


Visual examples by channel

Representative renders showing how the brand applies across channels. Click the template name to view the full HTML source. See collateral/render/ for all 36 templates.

ChannelTemplatePreview
EmailWelcome seriesWelcome email
Social cardHouse edgeSocial card
StorySports bettingStory
PosterNo Fine PrintPoster
Print – brochureInside spreadBrochure
Print – rack cardRack cardRack card
Venue signEntrance signEntrance sign
Digital displayLandscapeDisplay
Tier 2 – supportSupport pageSupport page
Tier 2 – posterHelpline posterTier 2 poster

Previous: Chapter 6 – Accessibility | Next: Chapter 8 – Governance