eduKate SG

The A-Math Daily Study Runtime | Retrieve → Solve → Explain → Repair → Return

The A-Math Daily Study Runtime

Studying Additional Mathematics every day does not mean doing a random pile of questions every day.

A useful daily session should perform several different jobs: recover older knowledge, solve something independently, expose the student’s reasoning, repair what failed and return important mathematics later so that it survives time.

The daily goal is not activity. It is to leave the student’s mathematical system slightly stronger than it was before the session.

A compact daily loop is:

Retrieve → Solve → Explain → Repair → Return.

1. Retrieve: Begin Without the Notes

Start by asking the brain to produce mathematics before giving it mathematics to look at.

  • write a formula from memory;
  • reconstruct a method learned earlier;
  • redo one old question without the worked solution;
  • state the conditions under which a method is valid;
  • explain what a familiar notation means.

This matters because familiarity can disguise forgetting. A student may look at a worked example and feel that the method is known while still being unable to generate the first step independently.

Retrieval exposes that gap early.

2. Solve: Work Without Immediate Rescue

The next part of the session should require genuine mathematical action.

Choose a small number of questions that match the student’s current state. A recovering student may need standard questions that rebuild control. A stable student may need mixed questions. A strong student may need unfamiliar transfer or comparison of solution routes.

Do not interrupt every hesitation immediately. A short period of productive struggle reveals whether the student can recognise the structure and initiate a route without external prompting.

3. Explain: Make the Reasoning Visible

A correct answer can still hide weak understanding.

Ask the student to explain one or two decisions:

  • Why does this method apply?
  • What mathematical object are you working with?
  • What condition must remain true?
  • Why is this route preferable to another route?
  • How would the problem change if one condition changed?

Explanation is useful because it exposes the difference between pattern imitation and mathematical control.

4. Repair: Fix the First Important Failure

When something goes wrong, do not automatically prescribe more questions.

Classify the failure first. Was it a concept, retrieval, recognition, method, execution or examination-control problem?

Then repair the smallest upstream weakness that can explain the error.

  • If the concept is wrong, rebuild meaning.
  • If retrieval is weak, remove prompts and return later.
  • If recognition is weak, mix question types.
  • If the method is poor, compare alternative routes.
  • If execution is unstable, train a specific checking behaviour.

The repair should make future work easier, not simply make the present answer correct.

5. Return: Make Yesterday’s Learning Survive Tomorrow

A-Math knowledge decays when it is learned once and then abandoned.

Important mathematics should return after a delay. The return does not need to be long. One carefully chosen old question can reveal whether a method remains accessible.

Over a week, the student should repeatedly encounter older mathematics among newer work. This creates a network rather than a row of completed chapters.

What a 45–60 Minute Session Can Look Like

The exact timing should change with the student, but one simple structure is:

  • 5–10 minutes: retrieval of older material;
  • 20–25 minutes: current or targeted problem solving;
  • 5–10 minutes: explanation or route comparison;
  • 10–15 minutes: repair of the most important failure;
  • 2–5 minutes: record what must return later.

The point is not to obey those minutes mechanically. The point is to make sure the session contains more than one cognitive function.

Do Not Turn Every Day into a Full Paper

Full papers test the whole system. They are not always the best tool for building the system.

If a student has a clear algebraic weakness, a full paper may spend two hours rediscovering that weakness in several places. A shorter targeted repair can be more efficient. Once the repair is stable, the student can return to mixed and full-paper conditions to see whether it holds.

Do Not Turn Every Day into Topic Drilling Either

Topical practice is useful while a method is being installed. It becomes dangerous when the chapter heading does too much of the thinking.

As soon as the student is sufficiently stable, include mixed questions so the student must decide which mathematics belongs to the problem.

The Daily Runtime Changes with the Student

A recovering student may spend more of the session repairing foundations. A Secondary 3 student may spend more time building and retrieving new methods. A Secondary 4 student may spend more time mixing, timing and converting capability into marks. A distinction-level student may need fewer routine questions and more transfer, route selection and error compression.

The loop stays useful, but the content inside the loop changes.

What to Record After Each Session

  • What could be retrieved independently?
  • What failed first?
  • What kind of error was it?
  • What repair was attempted?
  • What needs to return tomorrow, later this week or next week?

This makes the next session easier to design because the student is no longer starting from a blank page.

The End Goal Is Independence

At first, a tutor or teacher may provide the sequence externally: retrieve this, solve that, explain this step, repair this error.

Over time, the student should begin running the loop alone.

Retrieve → Solve → Explain → Repair → Return.

That is a much stronger daily habit than simply asking, “How many questions did I finish today?”

Explore the connected learning guides

Choose the question that brought you here. Open one useful guide, try a small task, and stop when you have what you need.

Take one question further

The same learning habit can travel across subjects, while each subject keeps its own methods. These routes help you notice a difficulty, understand one part of it, and return to something you can do.

A word is familiar, but using it is difficult.

Move from recognising a word to retrieving it in a new context. Understand vocabulary plateaus.

Try it without the guide: Choose one word you already know. Close the guide and use it in a new sentence. Explain why it fits; try another context tomorrow.

A piece of writing has ideas, but the reader loses the thread.

Make the order of events and the links between sentences clear. Explore composition writing.

Try it without the guide: Choose one short paragraph. Read the relevant explanation, close it, and revise the paragraph. Ask someone to tell you what happened and why.

The Mathematics seems familiar, but marks still disappear.

Find the first point where the working stops being reliable. Find Secondary 4 A-Math mark leakage.

Try it without the guide: For a Secondary 4 A-Math question you have attempted, locate the first uncertain line. Repair that step, then try a comparable question without the worked answer.

A Science fact is remembered, but the explanation is incomplete.

Connect the evidence to a scientific idea and the resulting change. Follow the Primary Science learning route.

Try it without the guide: Choose a familiar Primary Science example. Explain the evidence, the idea and the result without notes. Then change one condition and explain your prediction.

Two accounts of the world seem to disagree.

Check the question, source, date and evidence before combining claims. Explore the World Knowledge research library.

Try it without the guide: Take one claim. Find the source best placed to support it, note its date, and state what remains uncertain. Return to your original question.

There is plenty of help, but independence is hard to see.

Check what the learner can understand and do after support is removed. Understand how education works.

Try it without the guide: Choose one small task the child has practised. Agree on a calm, brief attempt without prompts. Use what happens to choose one next step, then stop.

For the structure behind these connections, read the eduKateSingapore runtime manifest and the eduKate ecosystem boot contract. The reader map describes public navigation; those manifests preserve the wider ownership and return rules.