TL;DR / Summary: A data cleaning relay race teaches spreadsheet hygiene faster than a lecture. Each team inherits a deliberately messy file, fixes one defect per hand-off, and passes it on — with the clock running and a rules sheet enforcing the fixes.
The format in one paragraph
Four teams, four messy workbooks, ten minutes per leg. Each leg fixes one category of problem: duplicates, whitespace, date formats, or inconsistent categories. Then the workbook moves to the next team, which must accept what it inherits.
The hand-off is the point. Cleaning data is rarely a solo activity, and working on a file someone else has already touched is a specific skill that most courses skip.
Because the clock runs, teams stop polishing and start deciding what matters — which is exactly the judgement the exercise is meant to build.
Preparing the messy file
One workbook, five hundred rows, and a list of deliberate defects. Keep a master answer key so scoring is objective.
Inject: duplicate customer records with a slightly different spelling, leading spaces in names, mixed date formats, inconsistent country codes, and a column of numbers stored as text.
Defect menu
- Duplicates — three pairs with transposed names
- Whitespace — trailing spaces in the name and email columns
- Dates — mixed formats, plus one impossible date
- Categories — “UK”, “U.K.”, and “United Kingdom” in the same column
- Numbers — a total column with three values stored as text
Five defect types is enough. More than that turns the race into a scavenger hunt and hides the learning.
Rules that make it fair
Write the rules on one page and read them aloud before the first leg. Each leg may fix one defect type only; everything else must be left, even if it is obvious.
No deleting rows except confirmed duplicates. No retyping a whole column by hand — formulas or tools only, because the point is technique.
The constraint is the teacher. Without it, the fastest typist wins and nobody learns a function.
Require a one-line change log per leg. It forces teams to name what they did and makes the debrief much sharper.
Running the relay
Teams of three work best: one drives, one reads the rule sheet, one checks the change log. Rotate the driver each leg so everyone touches the keyboard.
Ten minutes per leg, with a two-minute hand-over briefing where the receiving team asks one question. That question is often the most valuable minute of the exercise.
Score each leg on three criteria: the defect type was fixed, nothing else was damaged, and the change log is accurate. Accuracy of the log matters because it reflects whether the team understood what it did.
The debrief
Project the original file and the final file side by side. Ask what got fixed, what got broken, and what nobody noticed.
Then show the master key. The gap between what teams believe they fixed and what actually changed is the lesson, and it is usually larger than anyone expects.
Finish by asking which defect would be most expensive in a real report. Duplicates and text-stored numbers both quietly corrupt totals, and students usually spot that without prompting.
Adapting the difficulty
Beginners need obvious defects, a smaller file, and more time. Advanced groups get ambiguous cases: two records that might be the same customer, a date that could be read two ways.
Add a final leg where one team member must explain the workbook to someone who has never seen it. If the explanation is confusing, the cleaning was incomplete.
For other spreadsheet activities that build the same habits, the Excel games collection includes team formats and templates. Take the structure, replace the data with your own, and the exercise stays fresh each time you run it.
Keep the fastest and cleanest workbook as an example for the next cohort. A real before-and-after is more persuasive than any explanation of why data hygiene matters.
Making the scoring visible
Project a simple scoreboard between legs: defects fixed, defects introduced, and log accuracy. Three columns, updated live.
Teams respond to a visible score in a way they never respond to a rubric. The scoreboard also makes the trade-off between speed and care impossible to ignore.
Weight the accuracy column heavily. A team that fixes five defects and breaks two has made the data worse, and the scoreboard should say so.
Score what you want repeated, not what is easy to count.
Announce the final scores with the before-and-after file. The combination of number and evidence is what the group remembers.
Keep the scoreboard template for next time. Rebuilding it wastes the first ten minutes of the session.
Adapting it for remote teams
Share one workbook per team through a collaborative editor and use separate tabs per leg. The hand-off happens by moving the active tab, which keeps the history visible.
Replace the physical hand-off with a short written message naming what was fixed. The message becomes the change log.
Remote drills need an explicit hand-off, because nobody can see the screen.
Keep the calls short and cameras off if bandwidth is limited. The exercise is about the file, not the meeting.


