Canonical: https://www.playbookrg.com/operators/lottery/playbook/ Description: Plan lottery player-information placements, staff preparation, and evaluation. Use the guide to organize your program’s rollout. > Static reading copy of the published page, including authored disclosures. Interactive controls, personalized state, and account data are not reproduced. Use the canonical page for interaction and citations, and the dedicated content feeds for complete resource inventories. Source terms still apply; this format does not extend the Brand CC0 license to other products or third-party material. # The lottery playbook. Use the guide to plan placements, staff preparation and evaluation. Confirm the current game and jurisdiction scope, adapt the actual files, implement their linked controls and record local approval before publication. [Build a brief with owners, costs and a pilot →]() 4 min read · Free to copy and adapt · CC0 How to deploy Playbook across a lottery: draw games, instant tickets, the retail counter, and the app. > **Operator note**: Lotteries reach many casual players through brief retail interactions and a distributed workforce. Keep the content short, welcoming, and easy to use: show odds in plain numbers, correct myths about luck without judgment, and give clerks material that needs little explanation. The goal is to make the math as visible as the jackpot. --- ## Quick-scan index Quick-scan index: Section, What it covers | Section | What it covers | | --- | --- | | [The 30-second version]() | The lottery deployment logic | | [The player journey]() | Touchpoint map from queue to draw night | | [What to deploy]() | Guides, campaigns, myths, and templates for lottery | | [Segments to know]() | Who plays the lottery | | [Retail readiness]() | Preparing a network you don’t employ | | [Jurisdiction overlay]() | Pairing with compliance modules | | [Measure it]() | Scoring the deployment | | [Start this week]() | First-deployment sequence | --- ## The 30-second version A lottery deployment prioritizes reach. Counter materials have only seconds to communicate, so each piece should carry one idea: the odds, the helpline, or one myth. Use the app and email for more detail. When a jackpot grows and participation rises, increase the visibility of odds information. Because retailers are partners rather than employees, their material should require minimal training. ## The player journey The player journey: Moment, Where, What runs there | Moment | Where | What runs there | | --- | --- | --- | | The queue | Counter mat, screen loop | One-idea pieces: draw odds in plain numbers ([digital display specs]()) | | Buying | Counter | [Rack cards]() within reach; clerk materials that need no script | | The ticket | Ticket-adjacent print | Helpline and odds statements per jurisdiction mandate ([helpline card]()) | | Scratch play | Play stations | Instant-game myths: near misses and lucky stores ([myth-busting]()) | | Draw night | App, social, email | Results framing plus one literacy beat ([social media toolkit]()) | | Jackpot surge | Everywhere at once | The odds piece, loudest when the prize is biggest ([Myth 16]()) | | The app | Ticket checker, account | Lifecycle placements from the [mobile app touchpoints]() set | The placement rule: at retail, one idea per piece. Depth lives in the app and the [content hub](), one QR code away. ## What to deploy Prepare this material for use Adapt and review this material for your actual game and audience. Check language and local requirements, connect working destinations, and assign a publication owner. [Review the preparation steps]() ### Game guides Game guides: Content, Use | Content | Use | | --- | --- | | [Lottery guide]() | Draw games, scratch tickets, and the underlying odds | | [Lottery quick ref]() | The counter and play-station takeaway | | [Bingo guide]() + [quick ref]() | For lotteries running bingo halls or bingo-style games | | [Odds at a glance]() | Where lottery odds sit next to every other game | ### Campaigns Campaigns: Campaign, Why it fits | Campaign | Why it fits | | --- | --- | | [Luck, Numbers & Lotteries]() | The lottery flagship: lucky numbers, due numbers, and ticket math in one week | | [Game IQ Challenge]() | Quiz content for social and app; strong during surge weeks | | [Know Your Game]() | The guide push, paced game by game across a season | ### Myths that matter most here The luck set from [myth-busting](): choosing your numbers improves odds (10), some numbers are due (15), and more tickets move the odds in a way that matters (16). Behind them, the lucky machine (3) transfers to lucky stores and lucky scratch packs. Myth 17, winning back losses, belongs in every scratch-heavy placement. ### Collateral - [Rack card](), [helpline card](), [brochure]() – the retail print set - [Venue signage guide]() and [digital display specs]() – counters, kiosks, and screen loops - [Social media toolkit]() and [email templates]() – draw-night and lifecycle beats - [Radio scripts]() and [TV spots]() – the broadcast reach lottery still owns - [Render templates]() – production-ready cards, displays, and myth pieces ## Segments to know Segments to know: Segment, In lottery | Segment | In lottery | | --- | --- | | Traditional players | The weekly-numbers regulars; firm rituals, warm response to respect | | General players | Surge players who show up when the jackpot makes the news | | Friends and family | Office pools and family tickets; group play is the social pillar’s home turf | | Young adults | App-first entrants; instant games and ticket-checker moments | ## Retail readiness You train a network, not a staff. Materials do the work: 1. Send the [staff FAQ]() as a one-page counter card; a clerk should find any answer in ten seconds. 2. Keep the stigma-free language list inside every retailer kit. 3. Give corporate-owned stores and claim centers the full [conversation scripts](), including the Tier 2 handoff; high-value claims are the moment a real conversation can happen. ## Jurisdiction overlay Lottery requirements can specify odds statements, helpline text, age notices, and beneficiary disclosures. Use the relevant [jurisdiction module]() with this playbook, and give required wording priority. Modules tagged `lottery` contain ticket-level detail. ## Measure it Evaluate deployments with the [content scorecard](). Compare the reach of odds content during a normal week with its reach during a jackpot surge. Player education should become more visible as participation increases. ## Start this week 1. Configure [\_brand.yml]() with your lottery’s name and helpline. 2. Render the counter set: rack card, helpline card, and the lottery quick ref. 3. Put draw odds in the screen loop in plain numbers. 4. Schedule [Luck, Numbers & Lotteries]() for the next surge window. 5. Send the one-page FAQ card to the retail network with the next terminal update.