TASC Mathematics Methods – Foundation Level 3 common mistakes
TASC Mathematics Methods – Foundation Level 3 · Understand the traps and how to avoid them.
When solving an equation such as 3(x − 2) = 5x + 4, the candidate expands the bracket but drops the minus sign, writing 3x − 2 instead of 3x − 6, then solves the resulting wrong equation to a tidy-looking answer.
The candidate treats the bracket as decoration and distributes the coefficient only to the first term, a habit carried over from mental arithmetic where only one operation is tracked at a time.
What to do instead
Before solving, write the expansion on its own line with an arrow from each term in the bracket to its product, then re-read the line and check the sign of every term against the original. Practise ten expansions with negative coefficients daily until the sign check becomes automatic.
The candidate substitutes a value into a function and reports a negative output as a negative rate or a negative gradient, without distinguishing the value of the function from the sign of its slope.
The candidate conflates two different quantities that share the word 'negative', because the notation f(−2) and f′(−2) look nearly identical on the page.
What to do instead
Adopt a labelling habit: annotate each computed number with 'value' or 'slope' before using it, and when a question asks about increase or decrease, restate the question as 'is f′ positive or negative here?' in writing before computing.
When asked for the probability of 'at least one' success in repeated independent trials, the candidate computes the probability of exactly one success and stops.
The phrase 'at least one' is read as 'one', because the candidate scans for the number rather than parsing the qualifier, and the complement method is not the first strategy that comes to mind under time pressure.
What to do instead
Build a reflex: whenever the words 'at least' or 'at most' appear, write '1 − P(none)' or the appropriate complement expression before doing any arithmetic, and only then substitute numbers.
The candidate sets up a modelling problem by grabbing the numbers in the order they appear in the text, producing an equation whose variables do not match the quantities defined in the question.
The candidate reads for numbers rather than for relationships, so the sentence structure that encodes the relationship is skipped and the arithmetic becomes a guess dressed as algebra.
What to do instead
Force a two-line preamble for every modelling item: line one lists each defined variable with its unit, line two states the relationship in words ('total cost equals fixed fee plus rate times hours') before any symbols are written.
The candidate differentiates a product or quotient by differentiating each part separately, writing the derivative of a product as the product of the derivatives.
The candidate has memorised the sum rule and generalises it by analogy, since the sum rule is the first and simplest rule learned and no counterexample was ever worked through.
What to do instead
Work one numerical counterexample once and keep it as a reference: take two simple linear functions, compute the true derivative of their product at a point, and compare with the product of derivatives, so the rule is anchored to a remembered discrepancy rather than a slogan.
The candidate computes a mean, median, or standard deviation from raw data but reports it without units or with the wrong unit, or compares two distributions using only their means.
Summary statistics are treated as pure numbers detached from the context, and the candidate has not internalised that spread matters when comparing consistency or risk.
What to do instead
Whenever a summary statistic is produced, immediately write it with its unit and add one sentence on spread using the standard deviation or range; when a question asks which group is more consistent, require that sentence before choosing.
The candidate solves an inequality by the same steps as an equation and keeps the inequality sign unchanged after multiplying or dividing by a negative number.
The manipulation steps look identical to equation solving, and the sign-reversal rule is a small exception that is easily lost when the procedure is executed quickly from memory.
What to do instead
Before dividing, circle the divisor and write 'flip?' beside it; if the divisor is negative, redraw the inequality with the reversed symbol on a fresh line rather than editing in place. Verify the final answer by testing one value from the solution set.
The candidate finds a stationary point and declares it a maximum or minimum without checking the second derivative or testing either side.
Stationary point and turning point are treated as synonyms, and the candidate assumes any zero derivative implies an extremum, forgetting cases such as inflection points with zero slope.
What to do instead
Adopt a mandatory two-step close: after solving f′(x) = 0, evaluate f″ at each root and state the conclusion in words ('negative, so local maximum'), or sign-test f′ either side if the second derivative is zero.
The candidate answers a 'show that' or 'explain why' modelling question with the final numerical answer only, omitting the reasoning that carries the marks.
The candidate equates answering with computing, because most practice items reward the final value, and the command word in the question is not read as an instruction about the form of the response.
What to do instead
Underline the command word in every question before starting, and for 'show that' or 'explain', pre-plan the response as a chain of numbered statements each ending in a stated reason, then check the chain answers the command word.
The candidate rounds intermediate values aggressively, then uses the rounded figure in later steps, so the final answer falls outside the accepted range.
The candidate treats each line as a finished answer and writes down a display-ready number, rather than carrying full precision through the working.
What to do instead
Keep exact or high-precision values in the working lines and round only on the final line, marking the rounded answer with a small 'final' note; where the question specifies a precision, write that precision beside the question before starting.