Why verification is a family conversation too
Student STEM projects often end with a claim: this design reduces energy use, this filter makes water clearer, this app saves time. Teachers and judges will ask how the student knows. Many students find that question hard, not because the work is poor, but because they have never had to explain their evidence out loud to someone outside the project.
Families are well placed to provide that first audience. A parent does not need to understand the technical details to ask good questions. In fact, an outsider's questions are often the most useful, because they expose assumptions a student has stopped noticing. The goal is not to judge the idea or fix the project, but to help the student see whether the evidence supports the claim.
Question one: what exactly are you claiming?
Ask the student to state the claim in one sentence, using plain words. A vague claim, such as it works better, is hard to verify. A specific claim, such as the insulated box kept water warmer for longer than the plain box in our test, can be checked. Helping the student narrow the claim is often the most valuable part of the conversation.
Listen for words such as always, proves or best. These usually signal a claim larger than the evidence. Encourage the student to describe what they actually observed and under which conditions, and to keep the claim to that.
Question two: how did you measure it?
Ask what was measured, with what instrument and how often. Did they use a thermometer, a timer, a ruler, a survey? Were the readings written down at the time or remembered later? This question helps the student see whether the measurement matches the claim.
If the student measured something indirect, such as appearance instead of a quantity, ask whether there is a simple way to measure more directly. The point is not to demand laboratory equipment, but to make the measurement method visible and honest.
Question three: what did you compare it with?
A result means little without a comparison. Ask what the project was compared against: an unchanged version, a previous design, a standard method. If there was no comparison, the student may be able to add one with a simple control test.
Ask also whether the comparison was fair. Were both versions tested in the same conditions, for the same time, with the same instrument? Students often discover a difference in conditions they had not thought about, which is exactly the kind of insight verification is meant to produce.
Question four: how many times did you try it?
One test can be a lucky result. Ask how many times the test was repeated and whether the results were similar each time. If the numbers varied a lot, ask what might explain the spread. Repeated trials are one of the simplest ways to strengthen a student project.
Encourage the student to report all trials, including the ones that did not fit the expected pattern. Leaving out inconvenient results makes a project less trustworthy, and judges often notice. A short note explaining an unusual trial is better than hiding it.
Question five: what could make you wrong?
This is the most important question and the hardest. Ask the student to name one thing that could explain the result other than their idea. It might be a change in room temperature, a measurement error or a difference in materials. Naming alternative explanations shows mature thinking.
Then ask whether there is a way to rule that explanation out, or at least to mention it as a limitation. A project that states its limits clearly is more credible than one that claims too much.
Asking without taking over
How the questions are asked matters. Use a curious tone, ask one question at a time and give the student time to think. Avoid supplying the answer or redesigning the experiment. If the student does not know, that is fine; it is a note for the next step, not a failure.
Keep the conversation short, perhaps fifteen minutes, and end with the student choosing one thing to improve. The project and the decisions remain the student's. A parent who listens well is helping more than a parent who fixes the method.
Before you ask: three ground rules
Agree three ground rules with the student before the first conversation. First, the project belongs to the student, so the parent asks and the student decides. Second, I do not know is an acceptable answer and becomes a note for the next step. Third, the conversation is about the evidence, not about whether the idea is good or the student is clever.
These rules matter because verification questions can feel like an interrogation, especially close to a deadline. Saying the rules out loud helps the student hear the questions as support. It also helps a parent stay in the role of curious outsider rather than drifting into the role of judge or co-author.
A worked example in plain words
Imagine a student claims that a home-made solar oven heats food faster than an uncovered dish. Asked to state the claim, the student narrows it to: water in the oven reached a higher temperature after thirty minutes than water in an open dish, on two sunny afternoons. Asked how it was measured, the student realises the same kitchen thermometer was used for both, which is good, but that readings were taken a few minutes apart.
Asked what could make them wrong, the student notices that clouds came and went on one afternoon. None of this needs a parent to know physics. The student now has a clearer claim, a note on timing and a limitation to report, all in their own words.
Recording the answers
Suggest the student writes the five questions at the top of a page and notes their answers. This becomes a verification summary they can bring to a teacher, mentor or judging panel. It also helps the student prepare for the questions those audiences will ask.
Revisit the page after any new test. Over time, the answers should become clearer and more specific. That progress is itself evidence of learning, and it is something the student can describe honestly in a reflection or presentation.