Quick Checks: Is Your Answer Reasonable?

Getting an answer is not the end; checking it matters just as much. This post focuses on estimation and "does this make sense?" questions.

You've done the calculation. You've got a number. But here's the question that separates good problem-solvers from everyone else: Does that answer actually make sense?

A student calculates that a car travels at 5,000 kilometres per hour and writes it down without blinking. A professional produces a spreadsheet showing negative revenue and sends it to their boss. A recipe app tells you to add 47 cups of flour and someone actually does it.

These aren't maths failures—they're reasonableness failures. The calculations might even be correct given the inputs. But somewhere, something went wrong, and no one stopped to notice that the answer was absurd.

This post is about building your "nonsense detector." It's a skill that catches errors, builds intuition, and saves you from embarrassing—or costly—mistakes.

Kid-Friendly Sense Checks

Children can start checking reasonableness long before they master arithmetic. The key is teaching them to pause and think before accepting an answer.

Does the answer fit the story? If the question asks how many sweets Sam has left after eating some, and your answer is more than he started with, something's wrong. If you're calculating someone's age and you get 347, that's not a human age.

Is it bigger or smaller than what we started with? Addition makes things bigger. Subtraction makes things smaller. Multiplying by numbers greater than 1 makes things bigger; multiplying by fractions makes things smaller. These basic directional checks catch sign errors and operation mix-ups.

Round and estimate first. Before calculating 48 + 33, a child can think: "That's about 50 + 30, so around 80." If their precise answer is 811 (a common error when carrying goes wrong), the estimate flags it immediately.

Use real-world anchors. How tall is a door? About 2 metres. How heavy is a bag of sugar? About 1 kilogram. How long is a lesson? About an hour. When answers involve physical quantities, children can learn to compare against things they know.

The goal isn't to make children paranoid about their answers. It's to build a habit of reflection—a natural pause between "I got a number" and "I'm done."

Upper and Lower Bounds for Teens

As maths gets more complex, sense-checking gets more sophisticated. Enter bounds.

A bound is a limit you're confident about. You might not know exactly how many people attended the concert, but you know it's more than 1,000 (they wouldn't call it "sold out" otherwise) and fewer than 100,000 (the venue isn't that big). Your answer should fall between these bounds.

Establish bounds before calculating. Facing 127 × 48? Before multiplying, note: it's definitely more than 100 × 40 = 4,000, and definitely less than 130 × 50 = 6,500. If your answer is 923 or 61,296, you've made an error.

Use bounds to check equations. Solving 3x + 7 = 28? Before doing algebra, estimate: 3x is about 21, so x is about 7. If your algebraic solution gives x = 70, go back and look for mistakes.

Understand significant figures. If your inputs are only accurate to two significant figures, your answer can't magically be accurate to ten. Reporting "the average is 47.38291" when your data is rounded to the nearest whole number is false precision. Bounds remind you how much uncertainty you're carrying.

Apply physical constraints. Probabilities must be between 0 and 1. Percentages can't be negative (usually). Distances can't be negative. Speeds can't exceed the speed of light. Many problems have built-in bounds that catch impossible answers.

Thinking in bounds transforms checking from "is this exactly right?" (hard to verify) to "is this plausible?" (much easier to judge).

Sanity-Checking Data for Professionals

In professional settings, the data is messier, the stakes are higher, and the errors are sneakier.

Look for impossible values. Ages of -5. Revenue of £∞. Dates in the year 2087. Automated systems produce impossible values more often than you'd think, usually from corrupted inputs or processing errors. A quick scan for outliers catches many problems.

Check totals and subtotals. If your regional sales should sum to total sales, do they? If percentages should add to 100%, do they? These "adding up" checks are simple but powerful. When numbers that should agree don't, something's wrong upstream.

Compare to benchmarks. Is this quarter's growth rate plausible given historical trends? Does this project cost align with similar past projects? Anomalies aren't always errors—sometimes they're discoveries—but they should trigger investigation, not blind acceptance.

Trace suspicious numbers backward. When something looks wrong, don't just flag it—find out where it came from. Was it a typo in data entry? A formula error? A misunderstood unit? Understanding why something is wrong prevents it from happening again.

Ask: "Who would be harmed if this is wrong?" A decimal point in the wrong place can mean underpaying or overpaying by a factor of ten. A flipped sign can turn profit into loss. Before publishing, signing off, or acting on numbers, ask what happens if they're wrong—and check accordingly.

Professional sanity-checking isn't about distrust. It's about appropriate caution. The more consequential the number, the more scrutiny it deserves.

Try These

Here are three exercises designed to sharpen your reasonableness radar. The goal isn't just to find the answer—it's to evaluate whether answers make sense.

Puzzle 1: The Suspicious Sum (Too Big/Too Small)

A student calculates the following and gets the answers shown. Without doing the full calculation yourself, identify which answers are definitely wrong and explain how you know.

(a) 245 + 389 = 534

(b) 72 × 8 = 576

(c) 1,000 − 467 = 633

(d) 84 ÷ 7 = 14

Hint: For each one, estimate rough bounds. Is 200 + 400 more or less than the given answer? Is 70 × 8 close to the given answer?

Puzzle 2: The Fenced Garden (Bounds and Inequalities)

A rectangular garden has a perimeter of exactly 36 metres. You know the length is at least 10 metres but no more than 14 metres.

(a) What are the possible values for the width?

(b) What are the minimum and maximum possible areas for the garden?

(c) A student claims the garden could be a 9m × 9m square. Without calculating the perimeter, explain why this must be wrong.

Hint: Perimeter = 2(length + width). If length is at least 10, what does that mean for length + width, and therefore for width?

Puzzle 3: The Suspicious Report (Realistic vs Unrealistic Data)

A company report includes the following claims. Identify which ones are plausible and which should raise red flags—and explain your reasoning.

(a) "Our customer satisfaction score improved from 78% to 94% this quarter—a 16 percentage point increase."

(b) "Website traffic grew 340% year-over-year, from 50,000 visitors to 220,000 visitors."

(c) "Employee productivity increased 25%, while working hours decreased 30%, resulting in overall output growth of 40%."

(d) "Manufacturing defect rate dropped from 2.3% to 0.8%, saving approximately £150,000 annually on a production run worth £12 million."

Hint: Check the arithmetic. Do the percentages match the numbers given? Do cause and effect align logically? Are the magnitudes plausible?

Final Thought

Calculators don't make mistakes. They do exactly what you tell them—which is precisely the problem. If you enter garbage, you get garbage back, delivered with perfect precision and zero judgement.

You are the judgement. Your sense of "that can't be right" is the last line of defence against errors that survive every formula and function. It's built from experience, from knowing roughly how big things should be, and from the habit of pausing to ask "does this make sense?"

So don't rush past the answer. Let it sit for a moment. Compare it to what you expected. Check it against the bounds of possibility.

Because catching a wrong answer before it escapes into the world? That's not extra work. That's the whole point.

Ever caught a ridiculous error at the last minute? Or missed one that made it into the wild? Share your war stories in the comments—we've all been there!