Additional Mathematics Synthesis Guide 43: Linked Multi-Stage Problems — Hence, Result Handoffs, Parameters and Preserving Conditions

Produce the result → label what it means → preserve its conditions → pass it into the next stage → verify the handoff.

1. A multi-part question can be one mathematical system

Parts (a), (b) and (c) may look separate on the page while sharing one dependency chain. Part (a) can construct a factorisation, parameter, coordinate or derivative that part (b) is designed to reuse.

The learner should therefore ask after every part: what job might this result perform next?

2. “Hence” is a dependency signal

When a question says “hence”, an earlier result is intended to simplify or enable the next conclusion. The correct response is not merely to mention the earlier result; it must be connected to the next mathematical operation.

A handoff is successful when the earlier output is in the form the later stage needs.

3. Preserve exact results when they will be reused

If part (a) gives

x=ln12/ln5,

and part (b) requires a function of x, substituting the exact expression or the calculator’s full stored value is usually more reliable than replacing it prematurely with a short decimal.

Early rounding converts an exact handoff into an approximate one and can contaminate later stages.

4. Carry domain restrictions with the result

Suppose a logarithmic part establishes x>1 before deriving candidate roots x=3 and x=−3. The usable handoff is not “x=±3”. It is “x=3 after applying the original domain x>1”.

A later part that uses x should receive the admissible result, not the unfiltered candidate set.

5. Carry units when the next stage changes interpretation

If a calculus part gives a velocity of −4 m/s, the sign and unit both matter. A later distance or direction question must know that the particle is moving at speed 4 m/s in the negative direction.

Dropping the unit or sign can destroy the meaning of the handoff even when the number 4 is retained.

6. Parameters need labels

If part (a) finds k=3, write what k controls. Is it the vertical shift? Growth constant? Line intercept? Circle radius parameter? The same symbol can play different roles in different questions.

Parameter meaning is part of state. A bare number copied into the next line is easier to misuse.

7. Worked quadratic handoff

Suppose part (a) asks you to show

x²−6x+5=(x−1)(x−5).

Part (b) then asks for the roots. The factorisation is already the prepared representation:

(x−1)(x−5)=0 ⇒ x=1 or5.

Expanding again would undo the useful work produced in part (a).

8. Worked discriminant-to-tangency handoff

Suppose part (a) derives an intersection equation

x²−2x−k=0.

Part (b) asks for k when the line is tangent to the parabola. The relevant handoff is not the roots themselves; it is the quadratic structure. Tangency means a repeated intersection, so

Δ=4+4k=0 ⇒ k=−1.

9. Worked trigonometric identity handoff

If part (a) proves

a sinx+b cosx=R sin(x+α),

then a later maximum-value question should use the compressed form because the amplitude R is now visible. The proof has prepared a better representation for the optimisation step.

10. Worked derivative handoff

Suppose part (a) finds

f′(x)=3(x−1)(x−3).

Part (b) asks where f is increasing. The factorised derivative is already organised for sign analysis. There is no need to expand it before constructing intervals around x=1 and x=3.

11. The form of an earlier answer can be intentional

If a question asks to “show that” a result has a particular form, that form may be selected because it is useful later. A completed square exposes a minimum; a factorisation exposes roots; an R-form exposes amplitude; a logarithmic transformation exposes linear structure.

Do not immediately transform away from a supplied or proved form without checking why the examiner or author may have prepared it.

12. Handoffs can change mathematical type

An earlier answer may be a number, while the next part needs a coordinate. Or part (a) may produce a gradient and part (b) needs a line equation. A successful handoff may therefore require adding the missing structure.

Example: m=4 is not yet the tangent line. Pair it with the point and write y−y₁=4(x−x₁).

13. Handoffs can require substitution into a new object

If part (a) finds the stationary time t=3 and part (b) asks for the displacement then, the correct handoff is:

t=3 → substitute into s(t), not back into v(t).

The meaning of the target tells you which function should receive the earlier result.

14. Dependency order matters

Some results cannot be computed sensibly before their prerequisites exist. In optimisation, a geometric constraint may first reduce two variables to one; only then should the objective be differentiated.

Trying to differentiate an unreduced two-variable expression can create work that the question architecture was designed to avoid.

15. Conditions can tighten as the question progresses

A first part may establish x>0. A later geometric condition may require x<5. The current admissible state is then

0<x<5.

Conditions accumulate by intersection unless a later statement explicitly changes the domain.

16. Track approximation status

If part (a) produces an approximate value, mark it as approximate. A later exact-looking expression built from a rounded input is still approximate.

Use ≈ where appropriate and avoid silently converting a numerical approximation into an exact equality.

17. Track sign information

In kinematics, a velocity root divides direction intervals. In trigonometry, a principal value may need quadrant information. In square-root equations, a side may need to be non-negative before squaring.

Sign is often part of what must travel across a handoff.

18. If an earlier part is wrong, later parts may still be salvageable

In many linked problems, the method of a later part can still be shown using the candidate result you obtained, even if the earlier arithmetic contains an error. In an examination, continue logically rather than abandoning the whole question.

However, do not invent a stated earlier result if the paper does not provide one. Use the information actually available and show the later method clearly.

19. “Show that” results can be used even if your derivation failed

If a question explicitly supplies a target result in part (a), such as “show that f′(x)=…”, that printed result may become usable in a later part even if you could not complete the derivation.

The later stage should still be solved from the result the question has established as its intended handoff.

20. Verify at interfaces, not only at the end

A multi-stage solution is vulnerable at handoff points. Before passing a result onward, ask:

• Is the sign plausible?
• Is the unit correct?
• Is the value exact or approximate?
• Does it satisfy the domain?
• Is this the parameter or variable the next part expects?
• Is the representation useful for the next operation?

Small interface checks can prevent one early error from spreading through the entire question.

21. A worked multi-stage chain

Suppose s(t)=t³−6t²+9t+2 for 0≤t≤4.

• Part (a): v(t)=3(t−1)(t−3).
• Part (b): rest times t=1,3.
• Part (c): velocity signs are +,−,+, so both are direction changes.
• Part (d): positions are s(0)=2,s(1)=6,s(3)=2,s(4)=6.
• Part (e): total distance=4+4+4=12.

Every stage uses the state created by the previous one. The question is one dependency system, not five unrelated exercises.

22. A reliable handoff routine

1. After each part, label the result by meaning, not only symbol.
2. Keep exact form and full precision if later reuse is likely.
3. Attach all domain, sign, interval and unit conditions.
4. Inspect the next target and determine what form it needs.
5. Convert the earlier output only as much as necessary for that next stage.
6. At “hence”, explicitly show how the earlier result enters the new argument.
7. Check the interface before continuing.
8. If an earlier stage fails, salvage later method marks using any supplied result or your best consistent state.

23. Common failure patterns

• Treating every part as independent and re-solving what an earlier result already prepared.
• Rounding a part (a) value before it is reused.
• Copying candidate roots forward without applying the original domain.
• Dropping sign or units during a kinematics handoff.
• Expanding a factorised or completed-square form that was intentionally prepared for the next step.
• Using a stationary time in the wrong function.
• Forgetting that conditions accumulate across parts.
• Writing “hence” without showing the logical connection.
• Abandoning all later parts because one earlier result is uncertain.
• Checking only the final answer rather than the high-risk interfaces between stages.

24. Practice set

1. What does “hence” usually signal?
2. Why should exact values often be preserved between parts?
3. If a log equation gives candidates ±3 but the domain is x>1, what is passed forward?
4. If v=−5 m/s, what information should travel to a later motion question?
5. Why might a completed-square result be intentionally requested before a minimum question?
6. If part (a) gives f′(x)=3(x−1)(x−3), what next task is that form especially useful for?
7. If a tangent gradient is found, what else is needed for the tangent equation?
8. If a stationary time t=2 is found and the next part asks for displacement, where is t=2 substituted?
9. What happens to conditions x>0 and x<5 when both apply later?
10. Why should ≈ be preserved after an approximate handoff?
11. What is the tangent threshold condition for a quadratic intersection equation?
12. Why should a factorised polynomial not automatically be expanded in the next part?
13. What does an interface check inspect?
14. If part (a) is wrong, should all later parts be abandoned?
15. If a printed “show that” result is given, can it support a later part if your derivation failed?
16. In total-distance motion problems, why are velocity sign changes needed before distance is summed?
17. Why can a bare parameter value such as k=3 be dangerous?
18. What should be done before passing a rounded value into a later calculation?
19. Why is a multi-stage question well viewed as a dependency graph?
20. What is the final purpose of a handoff?

Answers

1. An earlier result is intended to be reused to obtain the next conclusion.
2. They avoid unnecessary accumulated rounding error and preserve algebraic structure.
3. x=3.
4. Velocity is −5 m/s: speed5 m/s in the negative chosen direction.
5. It exposes the vertex and minimum directly.
6. Derivative sign intervals, stationary points and monotonicity.
7. A point on the tangent.
8. Into s(t).
9. They combine to 0<x<5.
10. Because later calculations remain approximate even if written in more elaborate form.
11. Discriminant zero for a repeated real intersection.
12. The factorised form may already expose roots or sign structure required next.
13. Meaning, sign, unit, precision, domain, parameter identity and whether the representation fits the next stage.
14. No. Continue with a consistent result where possible and show later methods.
15. Yes, where the question explicitly establishes the result as the intended handoff.
16. Total distance must be split where direction changes; the sign chart identifies those boundaries.
17. The number can be confused with another quantity unless its role is retained.
18. Keep more precision internally if possible and mark the value as approximate.
19. Each later result depends on earlier outputs and conditions, so order and interfaces matter.
20. To deliver the correct, sufficiently precise and admissible mathematical state into the next operation.

25. What mastery looks like

Mastery means the learner sees a multi-part question as one connected system. They preserve exactness, domain, sign, units and parameter meaning across stages, recognise when an earlier form was deliberately prepared for later use, and recover sensibly when one part is uncertain.

The transfer test is to give a long question in which each part changes mathematical language. If the learner can explain what state is being passed from one stage to the next and verify the interfaces before errors propagate, result handoffs have become reliable.

---

Continue through Batch 11

• Guide 41: Representation Switching — Words, Equations, Graphs, Geometry and Rates
• Guide 42: Backward Reasoning and Target Decomposition — Let the Required Answer Choose the Route
• Guide 44: Mathematical Modelling — Formulation, Variables, Assumptions, Parameter Meaning, Validation and Return to Context
• Additional Mathematics Directory
• BTT Mathematics Hub