← All articles
A new employee at a laptop in an open-plan office, colleagues visible working nearby

18 September 2026 · 7 min read

Onboarding Week Quiz Ideas That Outlast Day One

by Quiz Bru Team

The Quiz Bru Team are the product team at ShellRick Tech Pty (Ltd); we build and run live quizzes on the platform every day. We write from direct experience hosting quizzes for friend groups, corporate events, schools, and fundraisers across South Africa.

The day-one quiz that gets forgotten by day two

Most onboarding programmes that include a quiz put it in exactly one place: an orientation session on the first morning, wedged between the laptop setup and the tour of the office. It gets used once, gets a laugh, and then the new hire never sees anything like it again for the rest of their first month, even though that first month is when they're absorbing more unfamiliar information than at any other point in their time at the company.

That single placement wastes most of the format's value. A quiz is good at making a specific block of information stick, not at being a memorable icebreaker once. The real opportunity in onboarding isn't the first morning; it's the four or five weeks after it, when a new hire is meeting names they'll forget, learning tools they'll misuse, and hearing policies they'll only half-remember without a second pass.

Spreading three or four short quizzes across the onboarding period, each covering what's actually relevant at that stage, does more for retention than one polished day-one session ever will, and it costs less prep time overall because each one is smaller and more targeted.

Where a quiz actually fits across four onboarding weeks

Week one is about names and faces, run near the end of the week rather than the first morning, once the new hire has actually met the people it covers. A quiz on day one about names they heard forty minutes ago tests short-term memory, not learning; run at the end of week one, it tests whether the introductions actually landed.

Week two shifts to the tools and systems they've started using: which channel handles IT requests, where the shared drive for their team lives, what the internal shorthand for a recurring meeting actually stands for. This is the content most likely to have been mentioned once, in passing, during setup, and then never repeated.

Week three covers policy and process (expense claims, leave requests, who signs off on what) since this is usually the material a new hire is too embarrassed to ask about a second time once week one has passed. Week four, once the basics are settled, is the right point for company history and culture questions: the founding story, a past product pivot, a running team joke, content that matters for belonging rather than for doing the job correctly.

Keep each one to ten minutes, not a test

The moment an onboarding quiz feels like an assessment, a new hire starts treating it the way people treat any test: cramming beforehand, second-guessing answers, and quietly resenting being evaluated in their first month before they've had a fair chance to actually learn the job. None of that helps retention, and all of it undermines the point.

Keep each session to six or eight questions and ten minutes, run it live rather than as a take-home form, and never attach a score to a performance record. If a new hire gets a question wrong, the correct answer showing up immediately is the entire value of the exercise; there's no reason to track who got what wrong past that moment.

Run it with whoever the new hire has actually been working alongside that week, not the whole department. A five-person session with their immediate team feels like a light check-in; the same quiz run in front of forty people at an all-hands feels like being tested in public, and a new hire who's only been there ten days won't tell you which one it felt like unless you ask.

Writing questions from what actually got said, not a manual

The strongest onboarding questions come from something that was actually said or shown during the week, not from the employee handbook. If the IT walkthrough mentioned that support tickets go through a specific Slack channel, a week-two question asking exactly that reinforces the one thing they were told once and are now expected to remember indefinitely.

Pull two or three questions each week straight from that week's actual sessions: the tool demo, the team intro meeting, the process walkthrough. It takes five minutes to jot down right after each session, while the content is still fresh, and it means the quiz is testing what this specific new hire was actually exposed to, not a generic checklist that assumes every week ran the same way for everyone.

Multiple-choice with three or four options works better than open text for this content, because the goal is confident recall, not creative recall. 'Which channel handles IT requests: #it-support, #general, or #random' resolves in two seconds; an open text box invites overthinking on something that should be automatic by week three.

Running it for a cohort instead of one new hire

If several new hires start in the same week or month, run the quiz as a shared session for the cohort rather than one-on-one with each person, which turns a check-in into a light bonding exercise between people who are all equally new and equally unsure of the same things. A cohort of five new hires comparing notes on which acronym they'd already forgotten does more for their sense of camaraderie than a shared lunch does.

Keep the comparison friendly and light, never a ranking that gets shared with managers. The moment a cohort quiz becomes something a manager reviews to judge how quickly each new hire is picking things up, it stops being a safe space to admit 'I genuinely don't remember what that acronym means' and starts being something people quietly dread, which defeats the entire point of running it in the first place.

A four-week setup checklist for whoever runs onboarding

Before week one ends: note down the six people the new hire actually met and the context each one works in, so the names-and-faces quiz reflects real interactions rather than a generic org chart pull. Before week two ends: list every tool, channel, and shorthand term mentioned during setup, since this is the list most likely to have grown without anyone noticing.

Before week three ends: pull three policy questions from whatever actually came up in a real conversation that week, an expense question someone asked, a leave request someone filed, rather than reciting the handbook cover to cover. Before week four: pick one company history detail and one team-specific running joke, since these are the two things that make a new hire feel like they're actually part of the place rather than still processing it.

None of this needs new software beyond whatever live quiz tool the team already uses for anything else. The only real discipline is keeping a running note through each week of what got said once and matters, so by the time each week's ten-minute session comes around, the questions write themselves instead of becoming one more thing to invent from scratch.

Ready to run your own quiz?

Create a free account and host a live multiplayer quiz in minutes.