Find your next learning step
Choose the question closest to what you need today, or read the guide from the beginning.
Understand the idea · Compare the examples · See a full solution · Practise and check · Choose the next step
An estimate can show that an answer is impossible or implausible without identifying the exact correct answer. If a product should be around 600, an answer near 600 may pass a rough size check, but several nearby wrong values can pass it too. Passing a check means that this check found no contradiction; it does not automatically prove the whole solution correct.
For G1, G2 and G3 Mathematics, use estimation to test size, sign, units and sensible limits, then verify the requested answer with the appropriate exact calculation or justified approximation. When you need certainty that a value lies outside a range, use a defensible bound rather than treating an informal rounded estimate as an exact rule.
Contents
Sections 1–5
Sections 6–10
Sections 11–15
Sections 16–20
Sections 21–23
Consider 19.8 × 30.2. Rounding to 20 × 30 gives an estimate of 600. The exact product is 597.96. An answer of 59.796 should trigger a decimal-place check because it is about ten times too small. But an answer of 598.96 is also close to 600 and would pass the same rough estimate despite being wrong.
The estimate has done useful work: it can expose a large scale error. It has not inspected every digit. To check the finer result, use a calculation route or relationship capable of detecting that smaller discrepancy.
For a definite bound in this example, note that 19 < 19.8 < 20 and 30 < 30.2 < 31. Because all quantities are positive, the product lies between 570 and 620. Any proposed exact product outside that interval is impossible. Values inside still need further checking.
This guide focuses on the strength of a check. It complements the valid-solution guide and the exact-values and graph-estimates guide, which address other parts of verification.
Approximation, estimation and interpretation appear within the official Mathematics learning context. For scope, consult the SEAB G1 Mathematics syllabus for 2027, G2 Mathematics syllabus or G3 Mathematics syllabus. The examples below span different prerequisites rather than defining a separate official examination section.
An estimate is useful because it is often quicker than a full recalculation. It can provide an expected scale before calculator entry and a reason to inspect an unexpected output afterwards.
The danger is asking the estimate to do more than it can. A coarse calculation may detect a missing zero but not a small addition error. A sign check may reject a negative length but say nothing about whether the positive length is correct.
Think of each check as testing a particular property. State what failure it could detect and what information it leaves untested. This makes checking more purposeful than repeating the word reasonable after any familiar-looking answer.
The aim is confidence based on evidence. You do not need to distrust every calculation, but you should know why a check supports a conclusion and where its support stops.
Contents · Previous section · Next section
A rough estimate replaces values with convenient nearby numbers to predict a general size. For 19.8 × 30.2, 20 × 30 = 600 is a useful scale estimate. It does not, by itself, define a precise acceptance interval.
A bound establishes a one-sided or two-sided limit using justified inequalities. Since both factors are positive and lie between known endpoints, multiplying the lower endpoints and upper endpoints can give a valid interval for the product.
For example, 19 × 30 < 19.8 × 30.2 < 20 × 31, so 570 < product < 620. A claimed product of 700 contradicts the bound. A claimed product of 600 does not contradict it, but is not thereby proved equal to the true product.
The words approximate and between carry different commitments. “About 600” communicates a rough size. “Between 570 and 620” communicates a specific interval when its derivation is valid. Do not invent an exact interval from an informal impression.
This distinction is especially helpful when a question asks whether a threshold is definitely exceeded. A rough estimate near the threshold may be inconclusive. A valid bound entirely above or below it can settle the decision without requiring the exact value.
Contents · Previous section · Next section
Suppose a quantity should be positive. A result of −12 fails the sign check, while a result of 12 passes. Yet the correct result might be 15. Positivity eliminates some wrong answers without selecting a unique right one.
The same logic applies to units. An answer in square centimetres is appropriate for an area, but many wrong numerical areas can carry that correct unit. A unit check protects the dimension of the result, not every arithmetic step.
An estimate of around 600 filters out answers of the wrong scale. It does not guarantee that 597.96 rather than 598.96 was obtained. Every check has a resolution: it can distinguish some alternatives and leave others unresolved.
A useful final review combines checks with different strengths. The original relationship checks meaning, the unit check checks dimension, the estimate checks scale, and substitution or a suitable second route checks the numerical or algebraic result more directly.
Do not perform all possible checks on every trivial question. Choose checks that address the likely failure. A proportion question may need a reference-whole check more urgently than a second multiplication. A geometry perimeter question may need a boundary inventory before any number is recalculated.
Contents · Previous section · Next section
For 19.8 × 30.2, the exact calculation can be written as 19.8 × (30 + 0.2) = 594 + 3.96 = 597.96. The estimate 600 agrees with the overall scale.
If a calculator or written method gives 59.796, compare it with the expected size. Both factors are around tens, so their product should be around hundreds. The proposed result is too small by about a factor of ten.
Then inspect the entry or decimal placement. Perhaps 3.02 was entered instead of 30.2, or a decimal point was moved incorrectly after multiplying whole-number versions of the factors. The estimate identifies a likely scale problem; it does not tell you exactly which keystroke caused it.
If the answer is 598.96, the same estimate offers little discrimination. Use the distributive calculation above, an inverse division check, or another appropriate method to inspect the finer difference.
This is a useful teaching contrast. Give one wrong answer with a large scale error and another with a small local error. Ask which the rough estimate can detect reliably. The learner then sees estimation as a purposeful tool with a scope, rather than a ritual performed after every calculation.
Contents · Previous section · Next section
Consider 598/29.9. Since 29.9 × 20 = 598, the exact quotient is 20. A rough estimate 600/30 also gives 20, so the expected scale is clear.
If a proposed quotient is 200, multiplying it by the divisor gives about 6000, far larger than the dividend. If it is 2, the product is about 60, far smaller. These candidates fail a size or inverse check.
However, a proposed quotient of 20.1 is close enough to pass a coarse estimate. Multiplying 29.9 by 20.1 gives 600.99, which does not reproduce 598. The inverse relationship tests the result more precisely.
Before using a simple rule such as quotient smaller than dividend, inspect the divisor. Dividing a positive number by a value below one makes the quotient larger, not smaller. For example, 12/0.5 = 24.
The estimate must respect the operation and the sign of the quantities. A familiar intuition about division by whole numbers can fail when decimals or fractions are involved. Write what one group represents or use a nearby easy division to form the expectation correctly.
Contents · Previous section · Next section
Suppose you need 18% of 250. Ten percent is 25 and twenty percent is 50, so the answer should lie between 25 and 50. The exact value is 45.
An answer of 450 fails this range check. An answer of 44 does not fail it, but is still wrong. The check establishes a broad position relative to known percentage parts without verifying every digit.
For a percentage greater than 100%, the result can exceed the reference whole. For 120% of 250, the answer is 300. Rejecting it solely because it is larger than 250 would misuse a rule that applies only to percentages between zero and one hundred on a positive base.
Likewise, a reverse-percentage question asks for a whole from a part. If 80% is 200, the whole is 250 and should exceed the supplied part. A magnitude check needs the correct relationship before it can be helpful.
The reverse-percentage guide develops that relationship. Estimation supports it by checking whether the output is on the expected side of the known amount, but it cannot repair a wrong base chosen at the start.
Contents · Previous section · Next section
A probability must lie between zero and one inclusive. A calculated probability of 1.2 or −0.1 is invalid in the ordinary probability model. This is a definite range check, not merely a rough estimate.
But a value of 0.4 lies within the allowed range and can still be the wrong probability for the event. The range check does not inspect the sample space, the event definition or whether combined outcomes were counted correctly.
Suppose a bag has three red and two blue counters and one counter is selected uniformly. The probability of red is 3/5 = 0.6. A proposed answer 0.4 passes the zero-to-one check but describes the blue event instead.
The next check should therefore return to the event. Ask which outcomes are favourable and which outcomes form the denominator. A correct numerical range is necessary but not sufficient.
The without-replacement guide develops another example: a second-draw probability can be numerically plausible while using the wrong remaining total. A range check is useful, but the changing sample space requires its own inspection.
Contents · Previous section · Next section
If a right triangle has legs 6 cm and 8 cm, its hypotenuse must exceed either leg and be less than their sum. The exact hypotenuse is 10 cm. An answer of 5 cm fails the lower comparison, while 16 cm fails the upper comparison.
A proposed answer of 11 cm passes those broad bounds but does not satisfy the Pythagorean relationship. Squaring gives 121 rather than 36 + 64 = 100. The exact relationship provides a stronger check.
Do not use the hypotenuse comparison without knowing that the requested side is actually the hypotenuse of a right triangle. A right-angle mark or a valid deduction must establish the configuration.
The geometry-marking guide explains why the drawing’s appearance cannot supply an unstated right angle. An estimate based on the wrong shape model can reinforce an incorrect solution rather than expose it.
This example shows the order of a strong check: establish the geometry, derive a sensible range, then test the exact relationship when needed. The range is valuable because it catches large mistakes quickly; the theorem identifies the precise length.
Contents · Previous section · Next section
Suppose a shaded region lies entirely inside a rectangle of area 60 cm². Its area cannot exceed 60 cm². A proposed shaded area of 75 cm² contradicts that containment, assuming the model is a simple region counted once.
An answer of 45 cm² remains possible under that bound, but the bound does not prove it correct. The actual shading could have area 30, 40 or another value below 60.
If the shaded region is formed by subtracting a known cut-out, calculate that cut-out correctly and inspect whether the pieces overlap. A plausible final size can conceal double subtraction or an omitted region.
Perimeter needs separate reasoning. A region contained inside another can have a longer boundary, especially when it has indentations or holes. Do not transfer the area-containment bound directly to perimeter.
The composite-area and perimeter guide develops the foundational distinction. A check must apply to the kind of quantity being measured. A correct fact about area is not automatically a correct fact about boundary length.
Contents · Previous section · Next section
Consider 100.2 − 99.8. Rounding both values to 100 gives an estimated difference of zero, while the exact difference is 0.4. The rounded estimate loses the small separation between two close quantities.
This does not make estimation useless. It shows that the chosen rounding is too coarse for the target. You can retain one decimal place here or reason directly from the distance between 99.8 and 100.2.
A relative error can become large when the exact difference is small. Losing a few tenths from each input may seem minor compared with inputs near 100, but those tenths are central to a result smaller than one.
Before estimating a difference, ask whether the inputs are close. If they are, choose a representation that preserves their gap rather than rounding them to the same number. The precision needed depends on the operation and the target, not just the size of the inputs.
The early-rounding guide explains how an intermediate approximation can alter a later result. Here the approximation can erase the very feature the question asks you to measure.
Contents · Previous section · Next section
Earlier, the positive factors 19.8 and 30.2 were bounded by nearby positive endpoints. Multiplying the lower endpoints gave a lower product bound, and multiplying the upper endpoints gave an upper bound. Positivity made that ordering straightforward.
Do not apply the same shortcut blindly when negative values occur. For example, if −3 < x < −2 and 4 < y < 5, the possible products are negative. Comparing the endpoint combinations shows the product lies between −15 and −8, rather than between the products of arbitrarily paired lower and upper labels.
Multiplication by a negative value reverses inequality direction. A valid bound must respect that fact. If sign handling has not yet been taught, use simpler positive examples until the relationship is secure.
This section is an extension about the strength of a claimed range. A bound is useful only if its derivation is valid. Calling an interval a bound does not make it one.
When unsure, identify the signs and consider the relevant endpoint products carefully. The purpose is not to make every estimate complicated. It is to avoid presenting an informal approximation as a rigorous exclusion argument when its inequality steps have not been justified.
Contents · Previous section · Next section
If you calculate a quotient, multiply the proposed quotient by the divisor and compare with the dividend. If you recover an original amount from a percentage change, apply the forward change and see whether it returns the supplied final amount.
These checks use a relationship in a different direction. They can detect mistakes that a second identical calculator entry might repeat, such as copying the wrong number or using a rounded intermediate value.
However, even an inverse check has a scope. If you misread the original quantity and check against the same miscopied value, the arithmetic can agree with the wrong problem. Return to the source statement before accepting the check.
For an equation, substitute candidates into the original equation rather than only the final transformed line. That can reveal forbidden denominators or lost conditions. For a geometry result, inspect the diagram’s givens and target boundary as well as the number.
The valid-solution guide provides the wider route. Estimation is one layer of verification. A stronger review chooses an additional check that tests what the estimate leaves unresolved.
Contents · Previous section · Next section
Suppose one estimate rounds 19.8 × 30.2 to 20 × 30 = 600, while another uses 19.8 × 30 ≈ 594 and calls the result about 600. Their agreement supports the scale, but neither distinguishes 597.96 from 598.96.
Repeating a coarse approximation in a slightly different form does not automatically create an exact proof. The methods may share the same simplification and therefore share the same blind spot.
For a more informative second route, use a calculation with finer resolution, such as the distributive expansion or an exact inverse relation. Choose a method that could actually fail if the particular suspected error were present.
The same principle applies to graph readings. Two readings from the same low-resolution graph can agree while both remain approximate. If the question requires an exact algebraic result, that agreement does not supply the missing exactness.
This is a constructive way to think about checking: do not merely ask for another method; ask what new information the method contributes. A good check adds a different constraint or inspects a different decision in the solution.
Contents · Previous section · Next section
Suppose a question asks whether 19.8 × 30.2 exceeds 550. The positive lower bound 19 × 30 = 570 is already above 550. Therefore the product definitely exceeds 550 without needing its exact decimal value.
This does not contradict the article’s central point. A check can be sufficient for one target and insufficient for another. The bound proves the threshold claim, but it does not prove that a particular exact product is 597.96.
If the threshold is 600, the broad interval from 570 to 620 straddles it and is inconclusive. You need a tighter bound or an exact calculation. An inconclusive check is not a failed method; it accurately reports that the available precision does not settle this target.
Read the requested conclusion carefully. “Find the exact product,” “estimate the product,” and “decide whether it exceeds 550” are different tasks. Each can require a different amount of numerical detail.
The two-valid-examples guide develops the wider idea that information can be sufficient for one quantity or claim while leaving another unresolved. Estimation becomes more useful when its strength is matched to the actual question.
Contents · Previous section · Next section
Question A: Estimate 39.7 × 20.3 using convenient nearby whole numbers. Which proposed answers, 80.591 and 805.91, would the rough scale check distinguish? Then calculate the exact product.
Question B: For 18% of 250, use 10% and 20% to give a broad interval. Explain why an answer of 44 passes that interval check but is not thereby proved correct.
Question C: A probability calculation gives 0.7. What does the range zero to one establish, and what does it leave untested? Contrast this with a proposed probability of 1.4.
Question D: A right triangle has legs 5 cm and 12 cm. Use simple length comparisons to reject proposed hypotenuses of 4 cm and 18 cm. Does that alone prove a proposed value of 14 cm? Find the exact length.
Question E: Explain why rounding 200.4 and 199.9 to the nearest hundred is unsuitable for estimating their small difference. Calculate the actual difference.
Question F: A positive quantity is known to lie between 570 and 620. Can you prove that it exceeds 550? Can you prove that it exceeds 600? Answer the two threshold questions separately.
Contents · Previous section · Next section
For A, 40 × 20 gives an estimate of 800. The answer 80.591 is of the wrong scale; 805.91 is plausible under that check. The exact product is 39.7 × (20 + 0.3) = 794 + 11.91 = 805.91.
For B, the value lies between 25 and 50, since 18% lies between 10% and 20% on the positive base. The proposed 44 is inside the interval, but the exact value is 45. The broad bound does not inspect the final units.
For C, 0.7 satisfies a necessary probability range condition. It does not verify the event, sample space or counting. A value of 1.4 violates the allowed range and must be rejected.
For D, the hypotenuse exceeds 12 and is less than 17, so 4 and 18 are impossible. Fourteen passes those broad comparisons but fails the exact relation. The correct hypotenuse is square root of (25 + 144), which is 13 cm.
For E, rounding both inputs to 200 erases their separation. The actual difference is 0.5. For F, the lower bound proves the quantity exceeds 550, but the interval straddles 600, so that second comparison is unresolved without more information.
Contents · Previous section · Next section
A learner says an answer is correct because it is positive. Ask what other positive values would also pass. This reveals that the sign check leaves many candidates unresolved.
Another learner rejects a correct perimeter because removing a region should make the boundary shorter. The repair is geometric: inspect the new edges rather than applying an area intuition to length.
A third says two calculator entries agree, but both use the same miscopied input. The repair is to compare the entry with the original question. A fourth uses an estimate so coarse that close subtraction becomes zero. The repair is to preserve the relevant difference.
The marked-paper guide helps turn these observations into specific practice. Checking is itself a set of decisions: choose a property, choose a method that tests it, and interpret the result at the method’s actual strength.
Encourage the learner to complete the sentence, “This check rules out ___, but it does not yet establish ___.” That wording can be shortened with experience, but it makes the logic visible while the habit is being built.
Contents · Previous section · Next section
Consider 9.8 × 5.1 and the question, “Does the product exceed 50?” The rough estimate 10 × 5 = 50 lies exactly at the threshold. It cannot decide which side the exact product occupies.
Expand the expression while retaining the small changes: (10 − 0.2)(5 + 0.1) = 50 + 1 − 1 − 0.02 = 49.98. The two first-order changes cancel, leaving the negative product term. The exact product is below 50.
This example explains why replacing two factors by nearby convenient numbers does not automatically preserve the direction of a comparison. One replacement increases a factor while the other decreases a factor. Without further analysis, the resulting product is neither a guaranteed upper bound nor a guaranteed lower bound.
For a broad scale check, 50 is excellent. It tells you that 499.8 is unsuitable. For the close threshold question, it is insufficient. The same estimate is useful and inconclusive at the same time because it addresses two targets of different precision.
Do not invent a rule that a rounded result is always above or below the original. The direction depends on the changes and the operation. If the question needs a guaranteed inequality, establish it rather than relying on the visual closeness of the numbers.
This makes a good paired exercise with the earlier threshold of 550 for 19.8 × 30.2. There, a broad lower bound already settled the decision. Here, a convenient estimate lands at the threshold and a finer argument is required. The method should be chosen for the claim, not the claim weakened or strengthened to suit a favourite method.
Contents · Previous section · Next section
SECTION 20 OF 23
19. A narrow bound and an integer condition can determine one answer
Suppose a question establishes that an unknown whole number n lies strictly between 12.2 and 13.4. The only integer in that interval is 13. Together, the bound and the integer condition determine n exactly.
This is stronger than knowing that an unrestricted real number lies in the same interval. There are many real possibilities between those endpoints. The domain turns a range into a single permitted candidate.
The conclusion also depends on the endpoints. If the bound were 12.2 < n < 14.4, both 13 and 14 would remain. If the interval contained no integer, the conditions would be incompatible with an integer answer. A bound does not always produce one value merely because the target is a whole number.
For practical counting questions, check whether the task permits a fractional count or requires a whole number. Then inspect whether the derived interval or inequality is strong enough. Do not round to the nearest whole number automatically when the condition is at least or at most.
For example, enough 4-litre containers to hold 17 litres requires an integer count n with 4n ≥ 17. The quotient 4.25 is not itself an available count, and n = 4 fails the capacity condition. The least permitted count is 5. That conclusion comes from the inequality and the whole-number domain, not from ordinary nearest-integer rounding.
The capacity-and-contents guide develops the underlying volume interpretation. Here the example illustrates how a check can become decisive when it is combined with enough structural information. “An estimate cannot prove every exact answer” should not be misread as “bounds can never determine an answer.”
Contents · Previous section · Next section
Suppose a learner’s area result has the correct square unit, is positive and is smaller than the enclosing rectangle. Those checks rule out several common mistakes, but they may not detect an omitted cut-out or a double-counted overlap.
A useful next check is a region inventory: identify the pieces added and subtracted and compare them with the diagram. Repeating the same arithmetic will not expose a modelling omission if the same incomplete expression is entered again.
For an equation candidate, substitution in the original equation tests a different property. For a mean, multiplying by the count can check the total. For a ratio allocation, adding the parts can check the whole, while comparing the parts’ ratio checks the allocation relationship.
These paired checks are useful because a wrong answer can satisfy one condition and fail another. Parts can add to the correct total while being divided in the wrong ratio. A proposed mean can lie between the minimum and maximum while failing to match the sum of the observations.
Consider dividing 60 units in the ratio 2:3. A proposed split of 20 and 40 adds to 60, so it passes the total check. But 20:40 simplifies to 1:2, not 2:3. The correct split is 24 and 36. The second condition distinguishes a plausible allocation from the required one.
Likewise, a proposed mean of 6 for the list 2, 4, 9 lies between the minimum and maximum, but the total is 15 and the count is 3, so the mean is 5. A range check alone leaves that error unresolved.
When teaching, ask the learner what wrong answer could still pass the first check. Then choose a second test that would reject that answer. This turns verification into an exercise in understanding the relationships rather than following a fixed list of rituals.
The worked-example revision guide offers a route for fading prompts. At first, identify the check’s purpose together. Later, let the learner choose it and explain what it establishes. Independence includes knowing when a passed check is reassuring and when the requested conclusion still needs another piece of evidence.
Contents · Previous section · Next section
A checking statement is only as useful as the condition it relies on. “The answer must be smaller than the starting amount” is valid for a positive amount reduced by a percentage between zero and one hundred. It is not a universal rule for every operation involving a percentage.
Similarly, “the result must lie between the smallest and largest observations” applies to the ordinary mean of a nonempty list of real observations. It does not apply unchanged to their sum. A learner can remember a correct fact and attach it to the wrong target.
Before applying a check, finish the reason: “This must be true because…” If the explanation refers to a condition the question did not give, inspect the assumption. An unsupported right angle, an unstated constant rate or a mistaken percentage base can make an otherwise sensible check misleading.
This does not require a long proof of every elementary fact during an examination. It is a learning habit that makes the short checks reliable. Once the condition is understood, a brief annotation such as positive reduction or mean within data range may be enough.
For practice, give two near questions where the same check is valid in one and invalid in the other. Compare 20% of 50 with 120% of 50, or a triangle’s area with the perimeter of an indented region. Ask which condition changed and why the original checking sentence no longer follows.
The goal is a flexible understanding of verification. A check should return the learner to the mathematical relationship, not become another phrase copied from a worked example. Knowing when a familiar check does not apply is part of using it well.
Contents · Previous section · Next section
Is estimation pointless if it cannot prove every digit?
No. It can catch large errors quickly, guide calculator entry and sometimes settle a threshold question. A useful tool does not need to answer every possible question. Its value comes from matching it to the failure it can detect.
Can a bound prove a final answer correct?
Sometimes additional conditions make an interval contain only one permitted candidate, or the task asks only for a threshold decision. In general, a broad interval alone does not identify one exact real value. Read the target and domain before deciding what the bound establishes.
Should I always do a second full solution?
No. Choose an appropriate check. A unit check, substitution, inverse calculation or boundary inventory may be more efficient than repeating the entire method. The check should inspect a decision that matters to the particular problem.
What if my estimate and exact calculation disagree?
Inspect both. The exact calculation may contain an error, but the estimate may also use unsuitable rounding or a wrong model. A disagreement is a reason to investigate, not an automatic rule that one named method must be right.
Where should I go next?
Use the Mathematics explanation directory for another focused guide. The worked-example revision guide helps turn checks into independent habits. The Clementi Secondary 1 Mathematics small-group guide gives the local teaching context. The immediate habit is to use estimation confidently for what it tests, then seek stronger evidence when the requested conclusion needs more precision.