Canonical: https://www.playbookrg.com/get-started/

Description: Choose a starting point for your operator program, framework evaluation, or product integration. Begin with the part your team needs.

> 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.

Get started

# Choose how to start.

Use a resource, plan a rollout, or build with the open library.

Brand resources: free under CC0. No account.

Choose your path

## Three ways in.

1

### Launch or improve a gambling program

Start with player education, then add training, workflow, and independent review as needed.

[Explore player-page designs →](<https://www.playbookrg.com/adoption/>) [Request a walkthrough →](<https://www.playbookrg.com/adoption/#walkthrough>)

1. 01 Free · public domain

   Playbook Brand · provides player resources

   #### Launch player education

   Read, copy, and adapt the Brand book, messages, templates, and game guides for free. Before publishing, verify local requirements, game scope, contacts, and working product links.

   [Playbook Brand →](<https://www.playbookrg.com/brand/>) [Browse the player content ↗](<https://www.playbookrg.com/brand/content/>)
2. 02 Two free programs

   Playbook Academy · prepares staff

   #### Train each role

   Start with the free All Employees orientation and Brand Foundations. Explore role-specific organization previews, then arrange access before assigning them to staff.

   [Playbook Academy →](<https://www.playbookrg.com/academy/>) [Start the free employee orientation ↗](<https://academy.gamblingpolicy.com/all-employees/intro>)
3. 03 Six connected tools

   Playbook Tools · supports daily RG work

   #### Choose the tool for the task

   Create content, review advertising, assess game risk, monitor websites, or manage onsite work. Account access is required; features depend on your plan.

   [Playbook Tools →](<https://www.playbookrg.com/tools/>) [Open Builder ↗](<https://rgtools.gamblingpolicy.com/app/builder/>)
4. 04 Account-based workspace

   Playbook Review · assesses program evidence with AI

   #### See your accreditation standing

   Map evidence to your framework, run AI assessments, and track the gaps behind your standing. Publish a credential profile when ready; external verification is arranged separately.

   [Playbook Review →](<https://www.playbookrg.com/review/>) [See how Review works ↗](<https://www.playbookrg.com/review/#journey>)

2

### Evaluate or use the framework

Inspect the evidence, examine the method, or adapt it to your market.

- [Read the evidence →](<https://www.playbookrg.com/evidence/>)

  Review the informed-choice model, the Positive Play Scale, and the cited research behind the framework.
- [Examine the Review framework overview →](<https://www.playbookrg.com/review/#framework>)

  See the five domains, how to interpret quality and verification, and a complete fictional report.
- [Cite the framework ↓](<https://www.playbookrg.com/get-started/#cite>)

  Use the prepared citation below in research, policy, or regulatory work.
- [Write to collaborate →](<mailto:info@gamblingpolicy.com>)

  Get in touch about a trial, independent evaluation, jurisdiction module, or research collaboration.

3

### Build from the open core

Clone the repository, configure the Brand system, and use only what you need.

Clone the repository:

`git clone https://github.com/kphilander/Playbook.git`  Copy

1. 1

   Clone or fork the repository

   Start with the complete Brand system, content library, templates, and website source.
2. 2

   Configure your brand

   Set the program name, colors, fonts, support details, and market in \_brand.yml. Rebuild or export the affected files and review their actual output; a setting does not update already-published copies.
3. 3

   Review and publish

   Adapt the webpage, feeds, or widgets to your product. Verify module coverage, game rules, language, support and account links, accessibility, owners, and local approval before publishing.

[Developers & API →](<https://www.playbookrg.com/brand/developers/>) [Playbook Brand →](<https://www.playbookrg.com/brand/>)

Before publication

## Before you publish.

Your team owns local decisions, working services, and publication approval.

1. ### 1. Check the module’s actual scope

   The guide currently contains 11 jurisdiction modules. Coverage is limited to what each dated source documents; Macau and Singapore cover licensed land-based casinos. An unlisted market has no module. Check your operator, activity, game, channel and publication date against current local requirements.

   [Check jurisdiction coverage and dates](<https://www.playbookrg.com/brand/compliance/>)
2. ### 2. Review the finished content

   Confirm game rules and assumptions, age notices, support contacts and opening hours. Replace example names, links and QR destinations. Review each language and the actual image, HTML or printed output in its placement.

   [Inspect resources and their usage notes](<https://www.playbookrg.com/brand/content/collateral/>)
3. ### 3. Connect the real services

   Templates and widgets do not enforce account limits, pauses or exclusions. Connect and test the actual account, support, consent and notification flows. Check accessibility and the complete journey, including unsuccessful requests.

   [Prepare the website template](<https://www.playbookrg.com/brand/template/#get>)
4. ### 4. Record approval and maintenance

   Assign owners, record the approved scope and file versions, and choose a review date. Define the pilot’s questions, measures and data handling before collecting results. A downloaded file or a completed checklist does not grant regulatory approval.

   [Build a plan with owners and pilot questions](<https://www.playbookrg.com/operators/#plan>)

License

## Use and adapt the Brand files for free.

Copy, change, and publish the Brand book, messages, source templates, and game guides without a permission request or attribution requirement. These Brand resources use the [CC0 1.0 public-domain dedication](<https://creativecommons.org/publicdomain/zero/1.0/>). Here is what that covers:

What you can do

- Use it commercially

  Use the Brand files in a paid operator program without a copyright licence fee.
- Edit the Brand material

  Rewrite the copy, redraw the visuals, restructure the system.
- Rebrand it as yours

  Swap in your own name, colors, and voice. The Playbook RG name is not required.
- Keep your changes private

  CC0 does not require you to publish work built on top of the Brand system.
- No permission needed

  You do not have to ask, register, or notify anyone first.
- No attribution required

  You may credit Playbook RG, but you are not required to do so.

What CC0 does not cover

- Other rights still apply

  The dedication does not grant trademark, patent, privacy or publicity rights. Check rights in third-party material and your uploaded logo. Do not imply that the author endorses your use.
- No warranty

  The system is provided as is and is not guaranteed to suit a particular purpose.
- Regulatory review is still required

  CC0 addresses copyright, not gambling regulation. Confirm compliance with the rules and legal guidance that apply in your jurisdiction.

Two Academy programs are also free

The All Employees orientation and Brand Foundations are free to take. Their [CC BY-ND 4.0 terms](<https://creativecommons.org/licenses/by-nd/4.0/>) require credit and a license link when sharing, and do not permit sharing adapted versions under that license. Ask about separate terms for adaptations, white-label use, or proprietary LMS embedding. The other courses are organization previews.

[Read Academy access and reuse terms](<https://www.playbookrg.com/academy/#organization-access>)

Implementation support

## Need help putting it into practice?

You can use the open core without hiring us. If you want implementation support, these topics can help define a support inquiry. Confirm scope, timing, price, responsibilities, training access and any review arrangements before treating them as an engagement.

01 Scope to confirm

Configuration sprint

Discuss brand matching, template setup, and the outputs your team will review before publication.

02 Scope to confirm

Guided rollout

Discuss integration, game-guide adaptation, local-review responsibilities and staff preparation. Confirm course access and licensing separately.

03 Scope to confirm

Full program

Discuss custom messaging, player journeys, a proposed evaluation and maintenance responsibilities. Confirm deliverables and any assessment arrangements.

[Discuss implementation](<mailto:info@gamblingpolicy.com?subject=Playbook%20deployment>)

Cite and collaborate

## Cite the framework

If Playbook RG informs your research or policy work, please cite it:

```
Simeon-Rose, K. (2026). Playbook RG: An open framework for gambling entertainment literacy [Computer software]. https://github.com/kphilander/PlaybookRG
```

This citation identifies the Playbook RG website repository. Earlier research uses the name Philander; the [authorship note explains the public records](<https://www.playbookrg.com/about/#person>).  Download the citation file (CFF)

## Collaborate

Playbook RG is developed in the open. Corrections, questions, and proposals are welcome.

- [Open the developer guide →Report a problem, propose a change, or ask how something works.](<https://www.playbookrg.com/brand/developers/>)
- [Email the team →Ask about trials, evaluations, jurisdiction modules, or research collaboration.](<mailto:info@gamblingpolicy.com>)

Start now

## Start with the open core.

Explore the Brand system if you need player content now, or use the developer guide to integrate the content, widgets, and templates into your own product.

[Explore Playbook Brand](<https://www.playbookrg.com/brand/>) [Developers & API](<https://www.playbookrg.com/brand/developers/>)
