Spreadsheets as Academic Work: Teaching Students to Communicate with Data

A teacher asks his class to analyze school lunch waste and make a recommendation. He collects the submissions. Most students have produced well-organized spreadsheets: the data is entered correctly, the formulas work, the charts display the right numbers. When he asks each student to explain their recommendation, many cannot. The spreadsheet shows what happened. The student has not decided what it means.

This is the technical-communicative gap in spreadsheet instruction. A student who can build a functional spreadsheet has developed a technical skill. A student who can use that spreadsheet to make a specific, defensible claim about what the data shows, support it with selected data points, and explain why it matters has developed an academic skill. Most spreadsheet instruction stops at the technical. The academic skill, the ability to reason from data to claim, is left unaddressed.

The Technical-Communicative Gap

The gap between building a spreadsheet and communicating from one is not a gap in data familiarity. Students who built the spreadsheet know more about the data than anyone in the room. The gap is a process gap: they have not been given a method for moving from observation to argument.

Observation says: waste is highest on Mondays. Argument says: waste is highest on Mondays because Monday menus feature items students have not selected and do not prefer, which suggests that expanding student menu choice would reduce Monday waste more effectively than reducing portion size. The first statement describes a pattern. The second makes a claim about what the pattern means and what should be done about it. The cognitive distance between those two statements is substantial, and most students have never been taught how to cross it.

What Data Communication Actually Requires

Making an academic argument from data requires four moves that go beyond technical spreadsheet competency.

Identifying a pattern worth arguing from: not all data patterns support claims equally. The student must look at the full dataset and identify which pattern is strong enough, specific enough, and relevant enough to support a claim the audience should care about. This judgment is not produced automatically by the spreadsheet.

Constructing a specific claim from the pattern: the claim must be arguable. It must say something that a skeptical reader could push back on, that the data can genuinely support, and that is specific enough to require the evidence the student has. “Lunch waste should be reduced” is not a claim. “Expanding student choice on Monday menus would address the menu-preference mismatch that drives the highest waste day” is one.

Selecting which data points support the claim: not every cell in the spreadsheet is evidence for the specific claim. The student who has identified a claim must identify which specific rows, columns, or chart elements actually support it, rather than presenting the entire dataset as undifferentiated evidence.

Explaining the connection between the data and the claim: the data does not speak for itself. A student who presents a bar chart and says “as you can see” has displayed evidence. A student who presents the same bar chart and explains what the pattern establishes about the claim has made an argument.

Why Students Stop at Display

Students stop at data display for the same reason they stop at surface editing in writing: the assignment structure rewards completion of the technical task without requiring the communicative one. A rubric that assesses spreadsheet accuracy, formula use, and chart type does not assess whether a claim was made. Students produce what the rubric measures.

Time pressure pushes in the same direction. Building the spreadsheet is concrete and finishable. Constructing a defensible claim from the data is open-ended and requires judgment. Under pressure, the concrete task wins. The result is a technically complete spreadsheet with no academic argument, submitted against a rubric that never asked for one.

What the Research Says

Harvard’s data literacy research has consistently found that data literacy is primarily a communicative skill rather than a technical one. Students who can interpret and argue from data significantly outperform students who can only organize and display it on assessments of academic reasoning. The technical skill, building the spreadsheet, is a prerequisite. The communicative skill, arguing from it, is the goal. Teaching the former without the latter produces students who can handle data but cannot use it as evidence.

Graham and Perin’s Writing Next (2007) identified explicit argument strategy instruction as the highest-effect intervention in writing development. The parallel holds for data communication: explicit instruction in how to construct a claim from data, and how to connect data to claim, produces the skill. Exposure to data without that instruction does not.

What This Looks Like in Guided Scholar

Guided Scholar’s Teach Me mode applies to spreadsheet analysis assignments, delivering criteria-specific feedback on both the technical work and the communicative claim. When a student submits an analysis that describes the data without making a claim, the feedback asks: what specific argument does this data support, and why should the audience act on it? When the student makes a claim without connecting specific data points to it, the feedback asks: which rows or chart elements support this claim, and what do they establish?

The teacher sees what the student submitted, what feedback was delivered, and how the analysis changed. A student who revised his explanation from describing a data pattern to arguing from it has developed a skill that the spreadsheet assignment was designed to produce but that technical instruction alone does not develop.

Practical Starting Points for Teachers

• Require a written claim with every spreadsheet submission. One sentence: what does this data establish, and why should the audience care? A student who cannot write that sentence has produced a spreadsheet but not an analysis.

• Teach “shows” versus “establishes.” “This chart shows that waste increases on Mondays” is display. “This pattern establishes that menu preference drives waste more than portion size” is a claim. Teaching students to move from one to the other is the cognitive move the assignment requires.

• Ask students to identify the three data points that most support their claim before building the final submission. This selection exercise forces evaluation of relevance rather than inclusion of everything. The selection is the academic work.

• Build a claim-plus-evidence requirement into the rubric. If the rubric does not assess whether a claim was made and connected to specific data, students will not make claims. The criterion creates the expectation.

• Model the full process from data to claim. Take a simple dataset, show the class the raw data, and model identifying a pattern, constructing a claim from it, and explaining the connection. Then ask students to apply the same process to their own data.

The Through Line

The spreadsheet is a tool for organizing data. The academic work is making an argument from it. A teacher who assigns spreadsheet work and assesses only technical execution has assigned research and evaluated typing. The instruction that develops the academic skill requires making the process visible: identify the pattern worth arguing from, construct a claim, select the supporting data, and explain the connection. That process is teachable and transferable to every context in which students will encounter data.