The Trivia Question That Started a Lawsuit
When Trivial Pursuit first launched in the early 1980s, it became one of the fastest-selling board games in history. It also became a cautionary tale about what happens when you skip the fact-checking step.
The game's 6,000+ questions were compiled quickly, and some of the material reportedly came from a trivia reference book by Fred Worth called Trivia Encyclopedia. Worth had anticipated exactly that kind of copying. He intentionally planted a fake answer in his book, claiming that the TV detective Columbo's first name was "Philip." No source confirmed that. He made it up, on purpose, as a trap.
When Trivial Pursuit cards repeated that same fake fact, Worth sued. The case was eventually dismissed, but the story has stuck around in trivia circles ever since. You can find the full history in the Wikipedia article on Trivial Pursuit.
The lesson isn't just about plagiarism. It's about the fragility of unverified questions. One bad answer in your bank gets read aloud to 40 people, argued over, and sometimes fact-checked on a phone mid-round. That's a bad night for your credibility as a host.
A Question Worth Adding to Your Bank
Here's one that's verified, surprising, and plays well across most crowd types:
What was the first product ever scanned by a barcode reader at a store checkout?
Answer: A pack of Wrigley's Juicy Fruit gum, at a Marsh supermarket in Troy, Ohio, on June 26, 1974. The original pack is now in the Smithsonian.
It hits that ideal spot: specific enough to feel like a real fact, obscure enough that nobody at the table is certain, and satisfying once the answer lands. Good questions feel like that.
How to Build a Bank That Keeps Paying Off
Most hosts who say they "have questions" really have a pile: a Google Doc here, a few screenshots there, some leftovers from a game they bought once. A bank is something different. A bank is organized, tagged, and easy to pull from on short notice.
Tag every question by category and difficulty
When you tag questions as you add them (sports, science, history, pop culture; easy/medium/hard), building a round becomes a retrieval task instead of a writing session. Most rounds play better with a few accessible questions early so teams get into it before the harder ones arrive.
Record what you've used and when
A simple spreadsheet column that says "Used: Sept 14" is enough. Regulars have good memories. A question they recognize from three weeks ago goes quiet instead of generating the table chatter you want. Some hosts add a reaction column too: did the room light up, argue it out, or stare blankly? That's information worth keeping.
Cross-check before anything goes in
The Trivial Pursuit story is funny in retrospect. In the moment, it was expensive. Cross-check facts against a second source before you add them to your bank. A wrong answer read aloud with confidence is worse than saying you'll look it up after the round.
Know how many questions you actually need
A standard trivia night runs six or seven rounds of eight questions each, plus a tiebreaker: call it 55 to 60 questions per event. If you're running weekly and want a 12-week buffer before repeating anything, you're looking at 700 or more questions minimum. Building that from scratch takes most hosts six months to a year of steady effort, and that's before you factor in specialty rounds or picture rounds.
What Heat Trivia Does Instead
The whole point of Heat Trivia's game library is to hand you a finished, verified, ready-to-run game without the bank-building overhead. Each game comes structured across rounds, difficulty-balanced across the evening, and fact-checked before it reaches you.
The presentation and scoreboard run right in a browser window. You connect a laptop to the TV, teams sign up from their phones, and the night runs without special software or a PowerPoint deck you spent two hours building the night before. The whole system is designed so a host can focus on the room instead of the logistics.
Experienced hosts sometimes keep a small supplementary bank for local questions or callbacks to something that happened in the room earlier in the night. That works fine alongside a pre-built game. But if you're starting out or adding a regular trivia night to your venue, not having to solve the question bank problem from day one is a real head start.
Take the live demo for a look at how the whole thing runs.