Getting Started with Playbook

You can start by using a free resource, planning a rollout or building your own product on the open library.

Brand resources are free under CC0 and need no account.

Three Paths

1

Program Launch and Improvement

Most programs start with player education and add training, workflow tools and independent review as they need them.

  1. 1Free · public domain

    Playbook Brand · provides player resources

    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.

  2. 2Two free programs

    Playbook Academy · prepares staff

    Role-Based Training

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

  3. 3Free to try

    Playbook Tools · checks ads and drafts messages

    Ad Check and Builder

    Ad Check reads ad copy against market rules, and Builder drafts player messages in Playbook voice. Both are free to try without an account.

  4. 4Account-based workspace

    Playbook Review · assesses program evidence with AI

    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.

2

Framework Evaluation and Use

Regulators and researchers can inspect the evidence and method behind the framework or adapt it to their own market.

3

Products Built on the Open Core

Developers can clone the repository, configure the Brand system and use only the parts they need.

Clone the repository:

git clone https://github.com/kphilander/Playbook.git
  1. 1

    Repository

    Clone or fork the repository, which holds the complete Brand system, content library, templates and website source.

  2. 2

    Brand Configuration

    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 Publication

    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.

Pre-Publication Checks

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

  1. 1. Module 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
  2. 2. 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
  3. 3. Working 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
  4. 4. Approval and Maintenance Records

    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

License

Free Use of the Brand Files

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. Here is what that covers:

What you can do

  • Use it commercially

    Use the Brand files in a paid operator program without a copyright license 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 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

Implementation Support

You can use the open core without hiring us. If you want implementation support, the three options below can help define an inquiry, and the scope, timing, price, responsibilities, training access and any review arrangements need to be confirmed before any of them becomes an engagement.

1Scope to confirm

Configuration Sprint

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

2Scope to confirm

Guided Rollout

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

3Scope to confirm

Full Program

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

Discuss implementation

Citation

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

Simeon-Rose, K. (2026). Playbook RG: One open standard for responsible gambling [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.

Collaboration

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

Next step

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.