The Tutor Handbook Vol No.0062 | The Receiving Check

The Tutor Handbook · Volume 0062 · Series ID THB-0062

The new tutor has the packet.

Now what?

Alicia’s continuity note says her algebraic execution is stable, an earlier sign-control weakness has moved to maintenance, and the active problem is method selection in mixed questions.

The receiving tutor could trust the note and continue immediately.

Or the tutor could ignore it and start from the beginning.

Both choices can be wrong.

Beatrice’s packet says she usually finds the correct evidence in comprehension but over-expands her answers beyond the question scope.

The new tutor might be tempted to test everything: vocabulary, inference, literal retrieval, summary, grammar, writing.

That feels thorough.

It may also waste the first lesson rebuilding a learner model that already exists.

Denise’s packet says her Additional Mathematics knowledge is stable untimed and the active problem is whole-paper performance under time.

The new tutor may prefer a different timed-paper method.

Should the tutor replace the old route immediately?

No.

Should the tutor promise never to change it?

Also no.

A Receiving Check is the receiving tutor’s bounded verification of an inherited learner state, learning claim, active route and support boundary before the tutor widens, contradicts, replaces or intensifies that route.

The previous volume, The Tutor Handbook Vol No.0061 | The Continuity Packet, asked what must survive when one tutor hands a learner to another.

This volume owns the next responsibility:

How should the receiving tutor verify the inherited route without resetting the learner, blindly trusting the packet, or replacing a working system merely because the new tutor prefers another one?

Quick Read

The Receiving Check begins after a real tutor-to-tutor handoff. It is not a cold-start First Lesson.
The continuity packet is prior evidence, not inherited truth.
The receiving tutor should verify the smallest number of claims that would materially change the next route.
Do not retest the whole subject when one boundary is enough.
Verify the current learner state before contradicting the previous tutor.
Verify the support boundary before adding help.
Verify the active weak link before restarting old repairs.
Verify the direction of support: install, hold, fade or retire.
Verify one current school condition because the environment may have changed since the packet was written.
Use fresh evidence where possible. Familiar tasks can make an inherited claim look stronger than it is.
Use changed conditions only where they test the exact boundary under review.
The receiving tutor should actively look for one piece of disconfirming evidence.
A packet can be accepted, narrowed, expanded, revised or rejected.
Rejecting one inherited claim does not require discarding the whole packet.
The first receiving lesson should usually preserve more than it changes.
The tutor classification model still governs the job: Class 0–6 describes what tutoring function is needed now.
Learning, studying, training, education and improvement each require different receiving checks.
Repair, Alignment and Frontier tuition require different receiving cautions.
Three-student tutorials need individual verification even when the group remains intact.
The strongest receiving tutor inherits evidence without inheriting obedience.
The final test is simple: can the new tutor update from reality without charging the learner the full cost of adult turnover?

1. What This Volume Owns

This volume owns the receiving tutor’s first verification cycle after a learner arrives with an existing tutoring history and a usable continuity packet.

The broader continuity law remains owned by eduKateSG’s ILT Tutor Guide v1.0: the tutor should continue the correct repair corridor instead of becoming a second conflicting teaching system.

The Tutor Classification Model by eduKateSG remains the canonical owner of the Class 0–6 tutor functions.

This handbook volume is narrower.

What should the receiving tutor test first, what should remain untouched, and what evidence is strong enough to justify changing an inherited route?

2. What This Volume Does Not Own

Volume 0009 | The First Lesson owns the cold-start problem: what a tutor should learn before teaching too much when no reliable learner model exists yet.

Volume 0010 | The Second Lesson owns pressure-testing the first hypothesis after an initial lesson.

The Continuity Packet owns what the sending tutor transfers.

The Receiving Check begins from a different condition:

There is already a learner model. The question is how much of it deserves to survive first contact with the receiving tutor.

3. The Receiving Tutor Inherits a Prior, Not a Verdict

Suppose the packet says:

Method selection is the active algebra bottleneck. Execution is stable.

The receiving tutor should begin with higher confidence in that explanation than they would have with no packet at all.

But higher confidence is not certainty.

The packet may be excellent.

The learner may have changed yesterday.

The school may have changed the topic.

The old tutor may have interpreted one condition incorrectly.

The correct posture is:

Respect the prior. Verify the boundary. Update from reality.

4. The Receiving Check Is Not a Full Reassessment

Full reassessment feels safe because it removes dependence on the previous tutor’s judgement.

It also imposes a cost.

The learner repeats old diagnostic work.

Previously repaired weaknesses return to centre stage.

Old scaffolds may be reinstalled.

The receiving tutor spends time proving things already well supported.

Good receiving practice is selective.

5. Verify the Claims That Can Change the Route

Not every inherited statement deserves equal checking.

Suppose the packet contains twenty facts.

Only three may materially alter the next lesson:

the active weak link;
the current support boundary;
the next discriminating move.

Start there.

6. The First Receiving Question

The receiving tutor’s first useful question is not:

What chapter are you weak at?

It is closer to:

What does the current packet say the learner can already do, and where does it say the route still breaks?

That question protects both progress and uncertainty.

7. The Second Receiving Question

Next ask:

Which one observation would most efficiently tell me whether this inherited boundary is still true today?

This is the anti-reset question.

It turns the first lesson into verification rather than reconstruction.

8. Read Before You Teach

A receiving tutor should read the continuity packet before launching into explanation.

That sounds obvious.

It is often violated.

The tutor sees one error and explains.

The error may already be on maintenance.

The tutor sees hesitation and prompts.

The hesitation may be the exact unsupported window the previous tutor was intentionally creating.

Reading first prevents helpfulness from becoming route interference.

9. Preserve the First Attempt

The first fresh attempt under the new tutor is unusually valuable.

Do not contaminate it too quickly.

Let the learner read.

Let the learner choose.

Let the learner begin.

Let enough of the route become visible before the tutor’s style changes the performance.

This first attempt is not a test of the learner’s worth.

It is a test of the packet’s predictive usefulness.

10. Use a Fresh Task, Not the Famous Example

A learner may know the packet’s favourite example by memory.

Verification should use the same mechanism under a fresh surface where possible.

If the packet says the learner can select between two algebraic methods, use a fresh mixed pair.

If it says Beatrice finds evidence accurately but over-expands answers, use an unseen passage.

Freshness reduces the chance that familiarity masquerades as continuity.

11. Keep the Verification Narrow

The packet says:

Execution stable; method selection fragile.

Do not give a full paper.

Give enough mixed items to observe selection.

If selection holds, the claim strengthens.

If execution suddenly fails, the inherited state may need revision.

Narrow tests produce cleaner updates.

12. Verify the Positive State Too

Receiving tutors often focus only on weakness.

That is a mistake.

If the packet says a capability is stable, sample it lightly.

Why?

Because protecting confirmed gains is part of continuity.

The receiving tutor should know what not to reteach.

13. Verify the Support Boundary Before Adding Help

The most common receiving error is over-helping.

The learner pauses.

The new tutor has no emotional history with that pause and assumes the learner is stuck.

But the packet may say:

Allow ninety seconds on unfamiliar surfaces. Faith often self-starts after restating the task. One task-restatement cue is the present support ceiling.

The receiving tutor should test that boundary before restoring stronger prompts.

14. Verify the Direction of Support

Support has direction.

Install: a new scaffold is being introduced.
Hold: current support is still needed.
Fade: support is deliberately reducing.
Retire: special support no longer deserves routine use.

If the receiving tutor misses the direction, continuity reverses.

A fading prompt becomes a permanent prompt.

A retired checklist returns.

A temporary model answer becomes the default.

15. Verify the First Weak Link Before Restarting Old Repairs

The packet may contain historical weaknesses.

Historical does not mean active.

Alicia once had sign-control instability.

It is now maintenance.

If the new tutor sees one negative-sign error and immediately restores full sign drills, the learner has been pulled backward by adult memory.

One old signature should trigger a check, not automatic resurrection.

16. Verify What Has Already Failed

The packet should name failed or low-yield routes.

The receiver should read them.

If generic comprehension volume failed to change Beatrice’s answer-scope problem, the new tutor should not restart generic volume merely because that is their familiar programme.

If a seven-step checking list made Alicia too slow, the new tutor should not recreate the same intervention under a new name.

Past failure is not a ban.

It is a reason to demand a new mechanism before repeating the route.

17. Verify the School Environment

A continuity packet can become stale because school moved.

The chapter changed.

A new assessment format appeared.

A teacher introduced a different notation.

A prelim is now two weeks away.

The receiving tutor should confirm one current-school condition before assuming that yesterday’s allocation still fits today.

18. Verify the Learner’s Own Account

The learner is not an unreliable witness merely because they are a student.

Ask:

What has become easier recently?
What kind of help is useful?
What kind of help now feels like too much?
What still breaks when you are alone?
What did your previous tutor ask you to keep practising?

The learner’s answer does not replace performance evidence.

It helps locate where verification is most valuable.

19. Ask for One Disconfirming Result

A receiving tutor can become too respectful of the packet.

Professional continuity is not deference.

For every important inherited claim, ask:

What result would make this claim less plausible?

If the packet says retrieval is stable, delayed failure weakens the claim.

If it says method selection is the bottleneck, strong mixed selection but poor execution points elsewhere.

If it says one prompt is enough, repeated failure after that prompt may require a different support state.

20. Do Not Manufacture Contradiction

Looking for disconfirmation does not mean making the test artificially cruel.

If the packet says the learner is stable on current Secondary Mathematics work, giving an Olympiad problem does not meaningfully falsify that claim.

The test should preserve the construct.

Change the condition that matters.

21. The Receiving Check Ladder

Read: understand the inherited state before teaching.
Locate: identify the one or two claims that control the next route.
Observe: preserve one fresh first attempt.
Verify: test the active boundary under appropriate conditions.
Disconfirm: look for one result that could weaken the inherited claim.
Compare: check whether school context or learner state has changed.
Decide: accept, narrow, expand, revise or reject the inherited route.
Update: write the new receiving state so continuity continues forward.

22. Five Possible Receiving Decisions

Accept: the inherited state is supported; continue the route.
Narrow: part of the claim is too broad; preserve the useful core.
Expand: the learner is stronger than the packet suggests; widen carefully.
Revise: the route is partly right but needs a different mechanism, support level or priority.
Reject: the inherited claim no longer fits current evidence; reopen diagnosis.

These decisions are more useful than “agree” or “disagree”.

23. Accept

The packet predicts the learner accurately.

The receiving tutor sees the same boundary on a fresh task.

Continue.

Do not add novelty merely to prove value.

The value of the receiving tutor may initially be continuity itself.

24. Narrow

The packet says Beatrice has answer-scope difficulty across comprehension.

The receiving tutor finds the problem only on inference questions, not literal evidence questions.

Narrow the claim.

Do not discard the whole diagnosis.

More precise boundaries usually produce better interventions.

25. Expand

The packet says Alicia is only beginning mixed method selection.

She handles three fresh mixed sets accurately and explains why each method fits.

The receiving tutor can expand the claim carefully.

Perhaps the next job is integration or moderate timing.

Continuity should not freeze the learner below current capability.

26. Revise

The inherited state is broadly correct, but the route no longer fits.

Denise still has a performance problem, but full-paper timing is producing too much accuracy loss.

The receiving tutor keeps the Class 5 diagnosis and revises the training dose.

Revision preserves continuity while improving implementation.

27. Reject

Sometimes the packet is simply wrong or stale.

If the receiving tutor collects clear contradictory evidence, reopen diagnosis.

Reject the claim, not the learner.

Preserve the packet as history because understanding why it was once plausible may still matter.

28. A Receiving Tutor Should Change Less in the First Lesson

The first receiving lesson is an information-rich transition.

Changing too much makes it harder to know whether differences come from the learner, the new tutor, the new materials or the changed route.

A useful rule is:

Preserve the route while verifying the learner; change only where evidence earns the change.

29. Tutor Style Is Allowed to Change

Continuity is not performance theatre.

The new tutor can explain differently.

Use different examples.

Ask different questions.

Bring different strengths.

The protected object is not teaching style.

It is the learner’s current state and the logic connecting evidence to the next route.

30. Different Explanation, Same Boundary

The receiving Explainer may see a cleaner way to teach the concept.

Fine.

But if the learner already reconstructs the concept accurately, the explanation may not be the current bottleneck.

Improving the explanation is not automatically improving the learner’s next limiting operation.

31. Different Worksheet, Same Learning Job

The new tutor does not need the same worksheets.

They need tasks that test the same underlying job.

If the active job is method selection, the worksheet must require method selection.

If the job is delayed retrieval, the task must contain delay.

If the job is whole-paper pacing, isolated easy drills are not equivalent.

32. The Receiving Tutor Should Protect Maintenance

Maintenance items should remain cheap.

If the packet says a repaired sign-control weakness needs two retrieval checks a week, the receiving tutor should not expand it into a thirty-minute drill block without evidence.

Maintenance exists to protect gains while freeing capacity for the active priority.

33. The Receiving Tutor Should Protect Retired History

Retired weaknesses are history.

They can become relevant again.

They should not remain permanent centrepieces.

A new tutor who resurrects every old problem turns continuity into a museum of weakness.

34. The Receiving Tutor Should Protect the Learning Budget

A new tutor often wants to add value quickly.

That can produce extra work.

Extra diagnostic work.

Extra homework.

Extra routines.

Extra practice.

The Learning Budget still applies.

Newness does not create more learner capacity.

35. The Receiving Tutor Should Protect the Scope Boundary

A packet can contain observations that touch family, school, access or wellbeing.

The receiving tutor should preserve the educational observation without expanding authority.

The Scope Boundary remains unchanged by transfer.

36. The Receiving Tutor Should Protect the Learning Claim

If the inherited claim says “stable untimed, unstable timed”, do not collapse that into “weak at Additional Mathematics”.

If it says “accurate with one task-restatement cue”, do not call the learner independent without the cue or dependent with full support.

Conditions belong inside the claim.

37. The Receiving Tutor Should Protect the Decision Record

Recent route changes usually happened for a reason.

Read the reason before reversing the change.

A different tutor preference is not, by itself, evidence that the previous decision was poor.

New evidence may justify a different choice.

38. The Receiving Tutor Should Protect the Stability Window

A new route may still be inside its planned observation window.

Changing it immediately because a new tutor has arrived destroys interpretability.

If the route remains safe and the planned evidence has not yet matured, continue long enough to read it.

39. Learning Receiving Check

Learning concerns understanding, retrieval, representation and reasoning.

The receiving tutor should verify:

one current understanding claim;
one delayed retrieval claim if durability matters;
one representation or misconception boundary;
one current support condition.

Do not re-explain everything merely to discover what the learner knows.

40. Studying Receiving Check

Studying concerns planning, allocation, retrieval, resources and self-management.

The receiving tutor should observe the learner operating the current system before redesigning it.

Can the learner choose a priority?
Can unfinished work be reallocated?
Does the system survive a real school week?
Where does parent or tutor ownership begin?
Which part is still externally regulated?

41. Training Receiving Check

Training concerns repeated reliability.

The receiving tutor should verify the training state, not restart the training programme.

Current accuracy?
Current speed?
Current cue dependence?
Current mix or spacing?
Current transfer boundary?
Current cost signal?

42. Education Receiving Check

Education places the learner inside school stages, assessments, formal demands and transitions.

The receiving tutor should verify the current institutional environment:

school topic now;
next assessment;
teacher feedback;
important notation or format conventions;
transition pressure;
what tuition is supporting rather than replacing.

43. Improvement Receiving Check

Improvement asks what part of the Observe → Diagnose → Prioritise → Repair → Practise → Connect → Perform → Review loop the learner can increasingly run themselves.

The new tutor should be careful not to take those controls back.

If the learner already identifies a recurring error, chooses an appropriate practice task and brings a precise question, the receiving tutor should build from that agency.

44. Class 0 · Homework Helper Receiving Check

Class 0 should verify task-flow independence before adding organisation support.

Can the learner locate the task?

Can they identify the first action?

Can they record uncertainty instead of waiting?

Class 0 receiving rule: do not rebuild an external task manager until the learner has shown what they already manage.

45. Class 1 · Explainer Receiving Check

The Explainer should verify whether explanation is still the job.

Ask the learner to reconstruct the idea before launching a new explanation.

If reconstruction is strong and execution is weak, the receiving job may actually be Class 2.

46. Class 2 · Drill Builder Receiving Check

The Drill Builder should verify which variable is unstable.

Accuracy?

Fluency?

Retrieval?

Selection?

Do not prescribe repetition before identifying what repetition is meant to stabilise.

47. Class 3 · Diagnostic Tutor Receiving Check

The Diagnostic Tutor should inherit the previous differential, not only the final diagnosis.

Which alternatives were considered?

What probe separated them?

What evidence would still overturn the current explanation?

This makes diagnostic continuity falsifiable rather than dogmatic.

48. Class 4 · Route Designer Receiving Check

The Route Designer should verify the opportunity-cost logic.

Why is this priority ahead of the next one?

What has been deliberately deferred?

What school demand constrains the route?

Class 4 receiving rule: do not mistake an inherited sequence for habit; test the dependency that justified the sequence.

49. Class 5 · Performance Coach Receiving Check

Performance coaching is especially vulnerable to tutor preference.

One tutor likes strict time checkpoints.

Another likes section order changes.

Another prefers aggressive skip-and-return.

The receiving coach should first verify where time is actually being lost and which routines already preserve accuracy.

50. Class 6 · Learning Architect Receiving Check

The Learning Architect inherits the largest system and therefore needs the strongest discipline against redesign enthusiasm.

Verify the controlling constraint first.

Then verify learner-owned controls.

Then verify school operability.

Only after that should broad architecture change.

Class 6 receiving rule: preserve coherence before adding sophistication.

51. Repair Mode Receiving Check

In Repair Mode, verify the weak-link chain.

Does the proposed prerequisite still control downstream performance?

Does the repair still change the learner’s state?

If yes, continue.

If not, reopen diagnosis rather than performing repair by inertia.

52. Alignment Mode Receiving Check

Alignment Mode depends heavily on current school reality.

The receiving tutor should verify what school is doing now before preserving an old allocation.

Alignment can become stale faster than Repair because the external curriculum keeps moving.

53. Frontier Mode Receiving Check

Frontier work should be verified against core stability.

The learner may have been ready for extension last month and now be entering a high-load assessment period.

The receiving tutor should confirm that extension still earns capacity.

54. Temporary Cover Requires a Minimal Receiving Check

A tutor covering one or two lessons should not run a full receiving protocol.

Verify only what is necessary to avoid damaging the active route.

current target;
support ceiling;
what should not be changed casually;
one evidence item to return to the regular tutor.

Temporary cover is continuity-heavy and redesign-light.

55. Permanent Tutor Change Requires a Fuller Receiving Check

A permanent receiver becomes the new owner of the route.

That requires deeper verification over one or two lessons.

Not a full reset.

Not blind inheritance.

A staged acceptance of responsibility.

56. The First Twenty Minutes

Read the current claim aloud or silently.
Ask the learner what they think is currently working.
Run one fresh task at the claimed boundary.
Do not help before the packet’s stated support threshold unless necessary.
Observe whether the failure signature matches.
Record one agreement and one uncertainty.

The first twenty minutes should reduce uncertainty without making the learner prove their entire education again.

57. The Rest of the First Lesson

If the packet is broadly supported, continue the route.

The receiving tutor now gets to teach.

Use the tutor’s own examples and explanations where appropriate.

Keep the active learning job intact.

The lesson should feel like continuation with a new adult, not interrogation by a new system.

58. The Second Receiving Lesson

One lesson can still be noisy.

The second receiving lesson should check whichever uncertainty mattered most after the first.

Change one condition.

Use delay.

Reduce one prompt.

Mix one neighbouring method.

Use one school-generated task.

Then update the learner model.

59. The Handoff Review

After one or two receiving lessons, the tutor should be able to answer:

What did the packet predict correctly?
What was too broad?
What was too narrow?
What has changed since the packet was written?
Which support is actually necessary?
Which route should continue?
Which claim should be updated?

This is the receiving tutor’s formal acceptance of the live learner model.

60. Update the Packet; Do Not Start a Second File

Continuity fails when every tutor creates a separate learner story.

After verification, update the current state.

Version it.

Retire stale claims.

Preserve relevant history.

One learner should not accumulate incompatible packets simply because adults changed.

61. Alicia · Mathematics: Verify Method Selection, Not the Entire Algebra Curriculum

Alicia’s packet says execution is stable and mixed selection is the active target.

The receiving tutor gives four fresh mixed questions covering two familiar algebraic methods.

Alicia chooses correctly three times and hesitates on the fourth.

The tutor asks no method cue.

Alicia re-reads and selects correctly.

Receiving decision: accept with a narrower support note.

Method selection remains the job, but the learner’s independent recovery is stronger than the old packet suggested.

62. Beatrice · English: Verify the Answer Boundary on an Unseen Passage

Beatrice receives an unseen passage and one evidence question.

She underlines the correct source line.

Her answer adds one unsupported inference.

The inherited diagnosis still predicts the failure.

Receiving decision: accept.

The new tutor continues minimum-complete-answer training instead of launching a generic comprehension programme.

63. Ciara · Science: Verify Mechanism Before Model Language

Ciara’s packet says model-answer language is strong but should come after causal reconstruction.

The receiving tutor changes one condition in a familiar Science mechanism.

Ciara pauses, rebuilds the causal chain and changes the answer appropriately.

Receiving decision: expand.

The learner may be ready for a wider changed-condition set with less language support.

64. Denise · Additional Mathematics: Verify the Performance Claim, Not the Topic

Denise’s packet says untimed knowledge is stable; timing is the active job.

The receiving tutor first gives one untimed fresh item from a supposedly weak topic.

Denise solves it accurately.

Then a moderate timed section shows the same old pacing bottleneck.

Receiving decision: accept.

The tutor avoids unnecessary reteaching and continues Class 5 work.

65. Emily · Studying: Verify the System Under a Real Week

Emily’s packet says she runs a rolling three-day plan independently.

The new tutor could ask her to build a new timetable on the spot.

That would test planning presentation, not studying continuity.

Instead, the tutor asks Emily to show how she reallocated after a school project moved forward.

Receiving decision: accept with one new watch item.

The plan works, but retrieval is being crowded out during busy weeks.

66. Faith · Independence: Verify the Pause Before Restoring the Prompt

Faith sees an unfamiliar problem and pauses.

The receiving tutor waits.

Faith reads again and states what the task is asking.

She begins correctly.

The inherited support boundary was conservative.

Receiving decision: expand independence.

The task-restatement cue moves from routine support to optional rescue.

67. Parent Communication: “The New Tutor Is Checking, Not Restarting”

A parent may worry that the new tutor is wasting time by testing the old tutor’s work.

Or the parent may worry that the new tutor is trusting too much.

A clear explanation is:

I am not restarting the learner and I am not inheriting the old route blindly. I am checking the few claims that control what we do next, using fresh work where possible. If they hold, we continue. If they do not, I update the route from the new evidence.

68. Learner Communication: “You Do Not Need to Prove Everything Again”

The learner should hear:

Your previous work matters. I am going to check a few important points so I know where to continue. You do not need to start from the beginning. If I see something different, we will update the plan together.

This reduces the social cost of tutor change.

69. The Receiving Check Card

Packet date: How fresh is the inherited state?
Current claim: What is the strongest inherited learner claim?
Route-controlling boundary: Which claim changes what we do next?
Fresh task: What new evidence will test that boundary?
Support condition: What help is allowed before the test stops being informative?
Disconfirming result: What would weaken the inherited claim?
School update: What external condition may have changed?
Learner report: What does the learner say is working or breaking?
Receiving decision: Accept, narrow, expand, revise or reject?
Updated route: What happens next?

70. The Thirty-Second Receiving Check

What does the packet say? What fresh task tests the boundary? What support must stay out of the way? What result would change my mind?

That is enough for many ordinary handoffs.

71. Research Foundation: Monitor Progress and Adjust Teaching

The Australian Education Research Organisation’s Monitor Progress guide emphasises checking what students understand and can apply, identifying gaps and adjusting teaching, guidance or feedback where necessary.

The Receiving Check applies that principle at a tutor boundary.

The inherited packet supplies prior evidence.

The receiving tutor checks what is true now.

Teaching then changes only where the current evidence requires it.

72. Research Foundation: Scaffolds Must Follow Current Proficiency

AERO’s Scaffold Practice guidance describes planned and responsive support and the gradual removal of scaffolds as proficiency develops.

This is why the receiving tutor must verify support need instead of assuming that a visible scaffold is still necessary.

The learner may have outgrown the support between packet creation and receiving lesson.

73. Research Foundation: Small-Group Tuition Benefits From Targeting

The Education Endowment Foundation’s Small Group Tuition evidence summary notes positive average effects and highlights the value of targeting support to pupils’ specific needs.

A tutor handoff threatens targeting because specific need can collapse back into broad chapter labels.

The Receiving Check protects targeting by verifying the current need before adding or removing intervention.

74. Research Foundation: One-to-One Tuition Should Link With Normal Learning

The EEF’s One to One Tuition summary notes that tutoring is more likely to have impact when it is explicitly linked with normal lessons.

The receiving tutor therefore verifies not only the learner’s internal state but also the current school route.

Continuity that ignores the school environment can become continuity with an obsolete problem.

75. The ILT Continuity Principle

eduKateSG’s ILT Tutor Guide v1.0 warns against a tutor becoming a second conflicting method system and repeatedly restarting the learner.

The Receiving Check operationalises the first moments of that continuity.

Continue from the inherited route only after the route proves it can still describe the learner in front of you.

76. The Tutor’s Receiving Checklist

How old is the packet?
What can the learner already do?
Where does the packet say performance still breaks?
Which claim controls the next route?
What fresh task will test that claim?
What support must I withhold long enough to see the learner’s actual state?
What support ceiling should I respect?
Is support being installed, held, faded or retired?
What old weakness is only maintenance?
What history is retired?
What failed route should not restart casually?
What one result would contradict the inherited explanation?
What school condition may have changed?
What does the learner say is working?
What does the learner say still breaks?
Does the tutor class still fit?
Does the tuition mode still fit?
Should I accept, narrow, expand, revise or reject the packet?
What should the updated learner model say?
What should the next tutor now inherit from me?

77. The Parent’s Receiving Checklist

Is the new tutor reading the existing learner state before starting over?
Are they checking the important boundaries rather than retesting everything?
Are they preserving skills that have already stabilised?
Are they avoiding old interventions that previously produced flat returns?
Are they respecting support that is being faded?
Are they checking current school needs?
Can they explain what evidence would make them change the inherited route?
After one or two lessons, can they state what they accepted and what they updated?

78. The Learner’s Receiving Checklist

What does my new tutor already know about what I can do?
What are they checking instead of assuming?
What do I no longer need help with?
What help is still useful?
What old problem should not automatically come back?
What route am I currently practising?
What has changed at school since the packet was written?
What do I want the new tutor to understand?
What new evidence would make us change the plan?

79. What the Receiving Check Is Not

It is not a full cold-start assessment.
It is not blind trust in the previous tutor.
It is not a loyalty test for the previous method.
It is not permission to redesign everything in the first lesson.
It is not a competition between tutors.
It is not an excuse to resurrect every historical weakness.
It is not a requirement to use identical worksheets or explanations.
It is not a permanent acceptance of the packet.
It is not a reason to ignore the learner’s own account.
It is not a substitute for fresh evidence.
It is a bounded verification that protects continuity while giving the receiving tutor professional freedom to update from reality.

80. The Ethical Standard

A learner should not be forced to restart because adults changed.

A learner should not be trapped because adults once wrote something down.

The receiving tutor has two obligations that pull in opposite directions.

Respect accumulated learning intelligence.

Remain willing to change it.

That balance is professional continuity.

Read before teaching.

Observe before prompting.

Verify before contradicting.

Disconfirm before becoming loyal to the inherited story.

Change only what current evidence earns.

The ethical Receiving Check gives yesterday’s evidence enough respect to prevent a needless reset, today’s learner enough authority to correct yesterday’s story, and the new tutor enough professional freedom to continue the route without becoming either a copy of the old tutor or a competing system.

Evidence and Connected Reading

Final Compression

The packet arrives.

Read it.

Do not obey it blindly.

Do not ignore it proudly.

Find the claim that controls the next route.

Use one fresh task.

Preserve the first attempt.

Respect the support ceiling.

Check the direction of support.

Sample one stable capability so you know what not to reteach.

Test the active boundary, not the whole subject.

Look for one result that could prove the inherited explanation wrong.

Check the current school environment.

Listen to the learner.

Protect maintenance.

Protect retired history from resurrection.

Protect the Learning Budget from new-tutor enthusiasm.

Accept what still fits.

Narrow what was too broad.

Expand what the learner has outgrown.

Revise what is partly right.

Reject what current evidence no longer supports.

Then update the packet.

The learner should feel continuity.

The tutor should retain judgement.

The evidence should remain in charge.

The Receiving Check is how a new tutor enters an existing learning system without either resetting it or becoming captive to it. Inherit the evidence, verify the boundary, preserve what still works, and let the learner in front of you—not the adult transition—decide what happens next.

That is the Receiving Check.

That is Tutor Handbook Volume 0062.

Small Group Tutorials

The Tutor Handbook Vol No.0062 | The Receiving Check — How a New Tutor Verifies an Inherited Learning Route Before Changing It