POS Data Dashboard: Tool Mismatch and Team Equity

The failure is a delimiter and locale mismatch, not corrupt student work. The file uses semicolons instead of commas and decimal commas instead of decimal points, so a default comma import puts whole rows into one column. The five 'corrupted' files are likely recoverable by re-exporting or by importing with the correct delimiter.

One-period plan:

• First 5 minutes: Show the raw file on the projector and ask students to notice the semicolons and decimal commas. Do not fix it for them silently.
• Next 10 minutes: Demonstrate the import wizard or the split-text-to-columns feature on one platform, then have students repeat it on their device. Pair a confident student with a less confident student, but both must import their own file.
• Next 20 minutes: Students clean one column and enter three required formulas: total revenue, units sold, and average price. Provide a formula card and a partially completed template for students who need it.
• Last 15 minutes: A checkpoint. Each pair shows the teacher or a peer checker that the row count matches the source and that one total is correct.

Because 12 Chromebooks plus 16 desktops equals 28 seats, every student can work on a device. I would keep the cloud spreadsheet as the common tool where possible so instructions match, and use the desktops for students who need the larger screen. The five affected students would re-export rather than rebuild.

I would assign four rotating roles: data importer, formula checker, visualization designer, and storyteller. Each role has a visible checklist. The early finishers would not simply decorate charts; they would add a pivot table, test a second chart type, or write a validation rule that flags negative quantities or missing product names. That extends the same learning targets rather than adding busywork.

Assessment would be individual even though the dashboard is a team product. Each student would submit a short 'evidence card' showing their own formula, one cleaning step they performed, and one sentence interpreting a chart. The team rubric would cover accuracy, appropriate chart choice, and a clear takeaway. The individual rubric would cover the evidence card and a brief oral checkpoint: 'Explain what your formula does and how you know the import is correct.'

For students with low formula confidence, I would use a worked example, color-coded cell references, and a requirement that they type the formula rather than only watch. For early finishers, the extension would be assessed at a higher rubric level, not used as a reason to stop working. The teacher's checkpoint notes would identify which students still need a re-teach before the final period.

The data include student cashier initials, which can identify individuals when combined with schedules or small class sizes. Even if the store is not an official education record in every context, the school should treat cashier initials as sensitive. Sharing dashboards publicly could expose individual work patterns or performance, and it could create unnecessary pressure on student workers.

Before sharing beyond the classroom, I would:

• Remove or aggregate cashier initials. Replace them with 'shift A/B' or delete the column unless the learning objective specifically requires it.
• Aggregate daily sales into weekly totals if daily patterns could identify a single worker.
• Review whether the store data are covered by district records policy and ask the administrator responsible for student privacy.
• Use a fictional or anonymized dataset for public examples, and keep the real dashboard inside the learning management system.
• Require students to caption charts with business takeaways, not personal commentary about workers.

The instructional point is data minimization: collect and display only what the question requires. Students should be able to explain why removing initials does not weaken the sales analysis. If the class wants to publish a showcase, it should use percentages and totals, not raw records.