Trivia
A daily question that teaches the rules your operation runs on, and pays for the right answer.
The operational problem
The rules that keep a site running are written down somewhere nobody reads twice. The handbook is signed on day one. The safety bulletin goes up on a board. The policy change arrives by email in the middle of a shift. Then a load moves without a spotter, and the answer is always the same: it was in the handbook.
Reading is not remembering. A rule someone read once in onboarding is not a rule they can act on eight months later, and nothing in a shift tells you which is which.
How Array HQ solves it
Trivia turns those rules into one question a day, in the app your team already opens for their points. A correct answer pays right away. Nobody is scheduled into a training room and no shift stops.
For you it is a goal like any other in //Ops. It carries a point value, it runs on a window, and attainment shows up by site. What makes it different is the content — the questions themselves, and which one goes out on which day.
How it works
Trivia has four layers. They are separate on purpose, and knowing which one you are looking at is most of what there is to learn.
| Layer | What it holds | What it is for |
|---|---|---|
| Goal | The point value, the window, the scope | Makes trivia pay, like any other //Ops goal |
| Library | Every question you have saved | The collection you draw from |
| Playlist | The order you intend to repeat | The rotation |
| Queue | What goes out on which day | The calendar |
The goal
A trivia goal is set up once for a site. It carries the point value a correct answer earns and the window it runs on, and it sits in //Ops beside your other goals. Everything below is content that hangs off it.
The library
The library is every question saved for that site. It has no order and no schedule. A question in the library is not scheduled to go out — it is available to be.
Questions come from your own material. You paste in a handbook section, a safety bulletin, or a policy page, and the //Ops agent drafts multiple-choice questions from it with the correct answer marked. You review the set before anything is saved, and you drop the ones you don't want.
Two things about a saved question are worth knowing before you save it:
- The wording is fixed. A saved question can't be reworded. Correcting one means retiring it and saving a replacement.
- A wrong question keeps going out. Until it is retired, it stays in the library and stays in the rotation. That is why the review step is worth the minute it takes.
Retiring a question reaches further than the library. It also comes out of every playlist it is in and off its upcoming days. A question that has already gone out is archived rather than removed, so the answers people gave still mean something.
The playlist
The playlist is the order you intend to repeat. It is a subset of the library, arranged, and it is what the calendar is built from.
A library of forty questions with a playlist of ten means ten questions rotate and thirty sit available. Changing the playlist does not change days that are already scheduled — it changes what gets scheduled next.
The queue
The queue is the calendar: which question goes out on which day. It is built from the playlist and it repeats. When the playlist runs out, it starts again.
The date belongs to the slot, not to the question. Putting a question on the row dated the 16th is what makes it go out on the 16th. The question does not carry a date around with it.
Days that have already gone out are history. They hold the answers people gave, so they are never reordered or removed.
Two ways to edit
Both work, and they are good at different things.
Chat takes intent and volume — build the playlist from everything saved, drop anything about parking, put the holiday hours question out on Thursday. Twelve removals is one sentence.
The trivia panel takes precision — move a question onto a specific day, reorder the rotation, retire the one question you are looking at.
What your team sees
Team members answer in the My Array HQ app: one question a day, points for a correct answer, and a streak for consecutive correct days. See Trivia (Talent).
What you'll be able to do
- Turn a handbook section into a reviewed set of questions without writing them yourself.
- Keep a rotation running without picking a question every morning.
- Put a one-off question out on a chosen day — a policy change, a seasonal rule.
- Retire a question that is wrong or out of date, and know it left the calendar with the library.
- See which questions people get wrong, and treat that as what it is: a rule the floor does not know.
Key terms
| Term | Meaning |
|---|---|
| Trivia goal | The //Ops goal that makes a correct answer pay, with its point value and window. |
| Library | Every trivia question saved for a site. No order, no schedule. |
| Playlist | The subset of the library, in the order you intend to repeat. |
| Queue | The calendar — which question goes out on which day, built from the playlist. |
| Retired | Taken out of the library, every playlist, and its upcoming days. |
| Archived | Kept for reporting because it has already gone out or been answered. |