A Primary 3 learner reads:
There are 1,250 books in a library. The library buys 375 more books and then gives 420 books to another school. How many books remain?
The arithmetic is not difficult.
The reasoning demand is different.
The learner must know that the final subtraction cannot be completed meaningfully until the new total after buying the books is known.
A multi-step problem is not several calculations placed in a paragraph. It is a dependency chain: one result becomes information needed for the next step.
First:
1,250 + 375 = 1,625.
Then:
1,625 − 420 = 1,205.
Answer:
1,205 books remain.
The important skill is not merely addition followed by subtraction.
It is recognising the order in which unknown quantities become knowable.
The current Singapore Primary Mathematics syllabus includes, at Primary 3, solving up to 2-step word problems involving addition and subtraction. MOE learning experiences also call for a variety of one-step, two-part, two-step and non-routine problems so learners become familiar with the problem-solving process. That makes planning a core mathematical skill, not an optional presentation technique.
The quick answer: find the hidden intermediate question
Most two-step problems contain a quantity that is not asked for directly but must be found before the final answer is possible.
Call it the intermediate result.
In the library problem:
- final question: how many books remain?
- hidden intermediate question: how many books are there after buying 375 more?
Once the intermediate quantity is identified, the order becomes clear.
Ask: What must I know before I can answer the question being asked?
Read once for the story, once for quantities, once for dependencies
A useful three-read routine is:
- Story read: What is happening?
- Quantity read: What does each number refer to?
- Dependency read: Which unknown must be found first?
This prevents premature arithmetic.
Many errors begin because a learner sees two numbers, performs an operation, then tries to fit the result back into the story.
Planning reverses that process.
Understand the story first.
Then choose the mathematics.
Label every number by what it counts
Suppose a problem says:
A shop sold 236 notebooks on Monday and 148 on Tuesday. It had 600 notebooks before sales began. How many notebooks were left?
The numbers are:
- 236 notebooks sold Monday;
- 148 notebooks sold Tuesday;
- 600 notebooks initially.
Before calculating, ask:
What quantity must be combined first?
The two sales amounts can be added:
236 + 148 = 384 notebooks sold altogether.
Then subtract from the initial stock:
600 − 384 = 216.
The unit labels make the logic visible.
Two-step does not always mean two different operations
A learner may think every two-step problem must be “add then subtract”.
Not so.
Example:
A school collected 1,245 cans in Week 1, 986 in Week 2 and 775 in Week 3. How many cans were collected altogether?
One route:
1,245 + 986 = 2,231.
2,231 + 775 = 3,006.
Both steps use addition.
The number of steps describes the reasoning chain, not the number of different operation symbols.
The first operation should create a useful quantity
A strong planning question is:
“If I do this calculation first, what will the answer mean?”
If the learner cannot name the intermediate result, the step may be arbitrary.
For the notebook problem:
236 + 148 = 384.
What is 384?
Total notebooks sold.
That quantity is useful because it can be compared with the initial 600.
Every intermediate answer should have a name.
Bar models can expose the dependency chain
Consider:
A charity had $950. It received another $275 and then spent $430. How much money remained?
A change model can show:
- start = $950;
- increase = $275;
- new total = unknown;
- decrease = $430;
- final amount = unknown.
The model makes it clear that the first unknown becomes the start of the second change.
Step 1:
950 + 275 = 1,225.
Step 2:
1,225 − 430 = 795.
Answer: $795 remains.
Comparison problems may hide the first quantity you need
Ali has 320 stickers. Ben has 85 more stickers than Ali. Together they give away 140 stickers. How many stickers do they have left altogether?
The final question asks about both children after giving away stickers.
But Ben’s quantity is not yet known.
First:
320 + 85 = 405.
Ben has 405 stickers.
Then total before giving away:
320 + 405 = 725.
Then:
725 − 140 = 585.
This is three calculations even though the conceptual structure can be organised in two major subgoals: determine the combined amount, then account for the decrease.
It is a useful reminder that real problems do not always fit a rigid “two equations only” template, even when classroom scope focuses on up to two-step cases.
Do not use keywords as an operation scheduler
A learner sees “more” and adds immediately.
Then sees “left” and subtracts.
Sometimes that works.
Sometimes it does not.
The words describe relationships, but the unknown position determines the solving operation.
For example:
Ben has 85 more stickers than Ali. Ben has 405. How many does Ali have?
The word “more” appears, but the calculation is:
405 − 85 = 320.
Planning from quantity relationships is safer than keyword sequencing.
Worked example: find a total, then find a remainder
A shop had 2,000 balloons. It received 475 more balloons and sold 860 balloons. How many balloons remained?
Question: how many remain?
Need first: how many balloons after delivery?
2,000 + 475 = 2,475.
Then:
2,475 − 860 = 1,615.
Answer:
1,615 balloons.
Reasonableness check:
About 2,500 − 900 ≈ 1,600.
The exact result is plausible.
Worked example: find a difference, then add it
Class A collected 680 cans. Class B collected 145 fewer cans than Class A. How many cans did the two classes collect altogether?
Need first: Class B’s collection.
680 − 145 = 535.
Then total:
680 + 535 = 1,215.
Answer:
1,215 cans.
The first subtraction creates the missing comparison quantity needed for the final addition.
Worked example: combine two parts, then compare
A school has 425 red chairs and 378 blue chairs. A hall can hold 900 chairs. How many more chairs can still be placed in the hall?
First find chairs already present:
425 + 378 = 803.
Then compare with capacity:
900 − 803 = 97.
Answer:
97 more chairs.
The word “more” appears only in the final question, but the first operation is addition.
A planning table can make dependencies explicit
For difficult questions, write three columns:
- What I know
- What I need
- How to get it
Example:
Know: 425 red, 378 blue, capacity 900.
Need: unused capacity.
Need first: chairs already used.
How: 425 + 378.
Then: capacity − used.
This small planning structure prevents the learner from treating calculations as disconnected lines.
Intermediate results should be carried with units
After 425 + 378 = 803, write:
803 chairs are already in the hall.
Do not carry only the naked number 803 into the next line.
The label reminds the learner why 900 − 803 is meaningful.
Units and quantity labels act as semantic memory between steps.
Estimate the final answer before detailed calculation
In the hall problem:
425 + 378 is about 800.
900 − 800 is about 100.
So the final answer should be around 100.
Exact answer: 97.
If a learner obtained 703, the estimate would expose the error immediately.
Estimation helps monitor the whole chain rather than only individual arithmetic steps.
Check dependencies backwards
After solving, ask:
- Does the final answer answer the actual question?
- Did the second step use the correct intermediate quantity?
- Did the first step create that quantity legitimately?
- Are all units consistent?
- Is the answer reasonable relative to the original numbers?
This backward audit is often more powerful than simply redoing every calculation in the same order.
Common misconception 1: use every number exactly once
Some problems include contextual information that does not belong in the calculation.
A learner trained to “use all the numbers” can create nonsense operations.
Repair: ask what each number represents and whether it is needed to answer the question.
Common misconception 2: the order of numbers in the story is the order of operations
Text order and dependency order are not always identical.
Repair: identify the final unknown, then work backwards to the quantity needed first.
Common misconception 3: the first correct calculation must be useful
A learner may correctly subtract two numbers that are not meaningfully comparable.
Repair: require the sentence “This answer represents…” after every intermediate calculation.
Common misconception 4: two-step means two keywords
Keyword counting does not reveal the dependency chain.
Repair: ask what is unknown and what must be known first.
Common misconception 5: if each arithmetic line is correct, the solution is correct
Correct arithmetic can operate on the wrong quantities.
Repair: audit meanings and units, not only calculations.
A diagnostic ladder for multi-step planning
- Can the learner identify the final question?
- Can the learner label what each number represents?
- Can the learner identify the unknown quantity?
- Can the learner state what must be known first?
- Can the learner choose an operation for the first subgoal?
- Can the learner name the intermediate result?
- Can the learner use that result in the next step?
- Can the learner preserve units across steps?
- Can the learner estimate the final answer?
- Can the learner check the chain backwards?
- Can the learner solve a similar problem with different wording and no familiar keyword pattern?
A five-minute home routine
Use a short two-step problem.
Before allowing arithmetic, ask the child to complete these sentences:
- “The question wants me to find…”
- “Before I can find that, I need to know…”
- “I can find that by…”
- “My first answer will mean…”
- “Then I will…”
This makes the plan verbal before it becomes symbolic.
What parents should listen for
- “I cannot answer the final question yet because I do not know the new total.”
- “This first answer means the number sold altogether.”
- “I am subtracting from 600 because 600 is the starting stock.”
- “My estimate says the answer should be around 200.”
- “I checked that the second step used the result from the first step.”
How this fits Singapore Primary 3 Mathematics
The current MOE Primary Mathematics syllabus includes solving up to 2-step word problems involving addition and subtraction in Primary 3. Its learning experiences explicitly include one-step, two-part, two-step and non-routine problems so students become familiar with the problem-solving process.
This means Primary 3 is not only a year for larger-number algorithms.
It is also a year when learners must begin organising several correct operations into one coherent solution.
The deeper lesson: problem solving is dependency management
A complex problem feels difficult when several unknowns are entangled.
Planning makes the structure explicit:
find A so that B becomes knowable; use B so that C becomes solvable.
This idea extends far beyond Primary 3.
Algebra, geometry proofs, calculus, programming, engineering and project planning all depend on identifying prerequisites and subgoals.
A multi-step solution is a small plan whose calculations happen to be mathematical.
Where this leads next
Primary 4 and upper-primary problems increase the number of representations and relationships that may need to be coordinated.
Comparison bar models become more complex.
Fractions and decimals enter multi-step chains.
Working backwards, unitary reasoning and model methods become increasingly important.
The planning habit established here remains the same:
identify the final unknown, expose the first necessary subgoal, and make every intermediate result carry meaning.
Final thought
A two-step problem is often described as “harder because there are two operations”.
That misses the important part.
The real difficulty is deciding which piece of knowledge must be created before the final question can be answered.
Do not ask, “What calculation comes first?” Ask, “What must become known first?”