How to tell a Fair Go summary from the rule that governs your case

On a phone, a Fair Go rule page can look finished long before it is. A summary, a collapsed panel or a shortened example may be all that fits at first glance, and the complete text can sit further down or behind a control you have not opened. The useful question is not which text is longer, but which text actually governs the situation you are in.

Summary text versus the complete Fair Go rule

A summary and a complete rule do different jobs, and on a narrow display the difference is easy to miss. A summary is written to be read quickly and may leave out conditions, time limits or definitions that only matter in specific cases. The complete rule is the longer document that sets out how a term applies across those cases. Seeing a short block of text at the top of a Fair Go page does not tell you that it is the whole rule, and seeing a longer block further down does not tell you that it is the governing one either. What you need is evidence of which document applies to your situation, not an impression formed from screen length. Treat any mobile page as a layout you have to navigate rather than a single continuous statement, because panels, tabs and expandable sections can hide the parts that change the outcome.

The distinction also affects how you read examples. A worked illustration inside a summary may be hypothetical, written to show how a calculation or condition works, and it should not be taken as a description of an actual Fair Go account condition or a current offer. If a page presents an example without saying whether it reflects a real term, the example is evidence of the rule’s logic, not of your entitlement. Before you rely on any passage, check whether it is labelled as an illustration, whether it sits under a heading that marks it as a summary, and whether the page points to a fuller document. Where the mobile layout does not show the full rule, the honest position is that you have not yet read it, and that is a useful thing to know rather than a gap to fill by guessing. As you compare the choices associated with https://poolworldwide.com/, read the complete relevant condition instead of relying on a clipped line.

A hypothetical example checked against the rule text

Suppose a Fair Go page shows a short example on a phone: a hypothetical player meets a condition and receives a described outcome. On a narrow screen this example may fill the visible area, and it reads like a statement of what happens. The proportionate next step is to look for the rule text that the example is meant to illustrate and check the scope it sets. Ask which action the rule covers, which version of the terms applies, and whether the example is marked as illustrative. If the example covers one situation but the rule covers several, the example is not a complete account of the condition, and matching your own case to the example alone can lead you to apply a rule that was never written for it. Note what the page actually says rather than what the example implies, and record the heading and section you found it under so you can return to it.

Now imagine the fuller rule appears but appears to conflict with the summary you read first. A shorter confirmation does not automatically override a summary, and a summary does not automatically override a complete rule. Length and position on the screen are not tie-breakers. Check the action the passage governs, the version or date attached to it, and the scope it claims, because a rule about one kind of transaction may legitimately differ from a rule about another. If a material contradiction remains after that check, the correct move is to pause rather than choose the text that looks more convenient or sits higher on the page. You can raise the discrepancy with Fair Go support and ask which document governs your situation, which is more reliable than resolving it yourself from a mobile view.

Deciding when the mobile rule text is complete enough

A practical decision method starts with what you can see and what you cannot. Confirm that you have opened every collapsed section and reached the end of the rule rather than the end of the first screen. Where Fair Go provides a search, contents list or expansion control, use it if it exists; do not assume the current mobile layout includes one, because layouts change and the absence of a tool is not evidence that no fuller text exists. Then compare the passages you have found on the three points that matter: the action covered, the version or date, and the scope. If those align, you can treat the text as consistent enough to act on. If they do not align, you have identified a genuine question rather than a reading preference.

The final step is proportionate. For a minor point, re-reading the relevant section carefully may settle it. For anything that affects money, eligibility or a decision you are about to make, ask Fair Go support to point you to the governing rule and confirm how it applies to your case. Keep the question specific: name the section, quote the passage, and say what appears to conflict. That gives a clear answer rather than a general reassurance. If no complete rule can be located on the mobile page and support cannot resolve the conflict, treat the condition as unconfirmed and do not proceed on the assumption that the example was accurate. The goal is not to find the longest text but to know which text applies, and stopping short of that is a sound outcome.

The goal is not to find the longest text but to know which text applies to your case, and stopping short of that is a sound outcome rather than a failure. If the mobile page leaves the condition unconfirmed, treat it as unconfirmed until Fair Go support points you to the governing rule.