How to Use the BlueLux Playbook
How to navigate the Playbook, use its field and learning layers, understand scope, and resolve instructions that differ.
This Playbook is an open operating standard for pool service and aquatics. It combines sourced technical guidance, field-ready procedures, jurisdiction-aware requirements, and clearly identified operating practices.
It is written for technicians and operators who need a reliable answer in the field. Pool owners, property managers, trainers, inspectors, and other professionals can use the same material to understand the task, its limits, and the evidence required for a sound decision.
It is not a stream of articles. Each entry answers a specific operational question and belongs to one of several content types.
Find the kind of answer you need
| If you need to know… | Look for… |
|---|---|
| Why a system behaves a certain way | A Fundamental |
| How to complete a repeatable task | A Standard Operating Procedure |
| What acceptable work looks like | A Quality Standard |
| What to check when something is wrong | A Diagnostic Guide |
| How a component works and what may be done to it | An Equipment Guide |
| A formula, limit, conversion, or fast answer | A Quick Reference |
| What must be checked or recorded | A Checklist |
| When to stop, protect people or property, and escalate | Safety Guidance |
Use the fast answer, then the detail
Operational entries begin with a field layer designed for a technician who already understands the subject and needs a fast reminder. In an SOP, that layer is the Field checklist. Other operational document types use a short diagnostic path, acceptance check, immediate reference, or quick reference. Learning and orientation guides may start directly with the explanation when a separate summary would only repeat the page. The detailed body preserves the reasoning, preparation, sequence, verification, common mistakes, and escalation rules.
The field layer and detailed body are two views of the same instruction. An article should not repeat that field layer as another TL;DR or completion checklist. If the two layers appear to conflict, stop using the entry and report the conflict through page feedback or your supervisor.
Understand facility scope
Most guidance is universal and carries no facility label. A document is labeled Residential, Commercial/Public Aquatics, or Jurisdiction-specific only when the entire document is limited to that setting.
An otherwise universal article may contain a short facility callout beside a step or value that changes in that context. The callout modifies only that part of the article. It does not turn the rest of the guidance into a residential or commercial procedure.
Know which instruction controls
When two instructions differ, use the most specific controlling authority for the exact situation. In general:
- An emergency direction, applicable law, adopted code, permit, or regulatory requirement
- The exact product label and Safety Data Sheet for a chemical
- The official instructions for the exact installed equipment, surface, or system
- A current facility-specific operating plan or authorized work instruction
- The current Playbook entry
- Your company's documented implementation when it adds a more protective control
- General training material or an older reference
Do not combine incompatible instructions or improvise around a warning. Escalate the conflict and document what you found.
Understand scope labels
- Inspect means observe, measure, photograph, or identify a condition without changing the system.
- Operate means use normal controls as designed.
- Maintain means perform a defined recurring service procedure using approved tools and materials.
- Repair means diagnose, disassemble, alter, or replace components within an expressly authorized scope.
- Refer means stop and send the condition to your supervisor, a qualified professional, licensed trade, manufacturer, emergency service, or other appropriate authority.
Authorization depends on the technician, equipment, hazard, and work order. A Playbook entry does not expand a person's training, license, or assigned scope.
Treat verification as part of the task
A task is not complete merely because the physical action occurred. Verify the expected result before calling the task complete.
Documentation is required only when the task creates a field record. Those pages include a Document before leaving section that may call for readings, pressure, flow, equipment state, photographs, chemicals added, observations, communication, or follow-up work. Learning and reference pages do not display a documentation block merely for consistency.
How Ask Blue fits
Ask Blue is available throughout the Playbook for questions and page feedback. It uses the current page and approved Playbook corpus as its primary context, identifies the material it relies on, and should acknowledge uncertainty rather than inventing a procedure.
Blue does not override emergency guidance, applicable requirements, product labels, manufacturer instructions, authorization, or human judgment. Use feedback mode to report a conflict, unclear instruction, missing scenario, or field result that should improve the Playbook.
Related Playbook entries
Was this guide useful?
Every rating and note helps improve this exact version.