> For the complete documentation index, see [llms.txt](https://help.rafflelink.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rafflelink.com.au/managing-your-raffle/activation/the-activation-checklist/raffle-structure.md).

# Raffle Structure

The activation checklist automatically verifies two key aspects of your raffle structure:

1. Raffle Duration
2. Ticket Package Compliance

### Duration Compliance

The system checks if your raffle's duration aligns with state regulations and permit requirements

### Ticket Package Compliance

#### Western Australia (WA)

* **Strict Requirements**: NO discounted ticket packages permitted
* All tickets must be sold at the same unit price
* Example of compliant pricing:
  * 1 ticket for $5
  * 2 tickets for $10
  * 5 tickets for $25

#### All Other States

Discounted packages allowed but must follow these rules:

### Ticket Package Pricing Structure

* Unit price must be descending or equal as quantity increases
* Example of compliant pricing:`1 ticket  = $5.00 ($5.00 per ticket)`\
  `3 tickets = $10.00 ($3.33 per ticket)`\
  `8 tickets = $20.00 ($2.50 per ticket)`

### Non-Compliant Example

The following would NOT pass the check:

`1 ticket  = $5.00 ($5.00 per ticket)`\
`3 tickets = $10.00 ($3.33 per ticket)`\
`8 tickets = $30.00 ($3.75 per ticket) ❌`

*Issue: $3.75 per ticket is higher than previous package's $3.33*

### Making Corrections

If compliance issues are found:

1. Return to the Edit Tab
2. Adjust ticket packages or dates as needed
3. Rerun compliance check
4. Proceed with activation once passed

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rafflelink.com.au/managing-your-raffle/activation/the-activation-checklist/raffle-structure.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.