Tutor Students from Underserved Communities

Proof required

Share written confirmation from the programme coordinator that you have been accepted and cleared to tutor. Share your session logs for sessions 1–5: each log must include the date, session duration, subject area, what was covered, and one observation about how the student engaged or struggled.

What gets checked

• Programme is an accredited or registered organisation — not a self-arranged tutoring agreement. Coordinator confirmation is provided.
• Five session logs span at least 3 different dates — all 5 sessions completed in a single weekend do not satisfy the standard.
• Each log records a specific student observation, not just a topic list ('student confused equivalent fractions; responded to a visual model' — not 'taught fractions').

Common mistakes

• Compressing all 5 sessions into one day — rapid completion without sustained relationship is the opposite of what this outcome demonstrates.
• Logging activities rather than observations: 'covered algebra' is not a session log.
• Self-arranged tutoring rather than an organised programme — the programme's oversight is required to ensure safeguarding.

Resources

What a verifier looks for

• Confirm the programme is a named accredited or registered organisation — ask for its name and verify it exists before accepting the submission.
• Check that 5 session logs span at least 3 different dates — compressed logs suggest the relationship was not sustained.
• Each log should have a student observation, not just a content list. If all logs say 'covered topic X', ask for one specific example of how the student responded.
• The programme's acceptance email confirms safeguarding prerequisites were met by the programme — do not ask the submitter to document background checks independently.

You'll sign in first, then come straight back here.

Proof required

Share your session logs for sessions 6–10. Share a 150-word progress note about one returning student: what they could not do at the start, what happened during a session that marked a shift, and what they can do now that they could not before. Include the programme coordinator's mid-point confirmation that your attendance has been consistent.

What gets checked

• Session logs 6–10 span at least 5 different dates — not compressed into one or two days.
• Progress note names a specific student (first name or pseudonym), a specific skill or concept, and describes an observable before-and-after change.
• Coordinator mid-point confirmation is included and confirms consistent attendance — not just that the sessions happened.

Common mistakes

• Progress note describes the tutor's development ('I learned how to explain fractions better') rather than the student's progress — the subject is the student, not you.
• No returning student at session 10 — if every session has been with a different person, no tutoring relationship has formed.
• Logs are near-identical session to session — genuine sessions with real students always produce variation in what's covered and how the student responds.

Resources

What a verifier looks for

• The progress note must be about the student, not the tutor's feelings about how it went — ask 'what can the student do now that they could not do in session 1?' as a follow-up if the note is unclear.
• Confirm that at least one student appears in both session-1 logs and session-10 logs — no returning student means no relationship was formed.
• Check that session logs 6–10 span at least 5 different dates — 5 sessions in 2 days is a red flag.
• The coordinator's mid-point confirmation should specifically say attendance was consistent — a generic 'thanks for volunteering' email does not count.

You'll sign in first, then come straight back here.

Proof required

Share your complete session logs for sessions 11–20. Share the formal coordinator sign-off confirming: (1) 20 sessions completed, (2) consistent and reliable attendance, (3) their assessment of student benefit. Write 200 words on what you would do differently: name one tutoring approach that worked better than expected and one that worked less well than expected, with a specific example of each.

What gets checked

• Session logs 11–20 are individual dated entries — not a summary table.
• Coordinator sign-off explicitly addresses all three points: completion, attendance consistency, and student benefit — a generic thank-you email does not satisfy this.
• 200-word reflection names specific examples of what worked and what did not — generic observations about communication or patience do not count.

Common mistakes

• Coordinator sign-off that only confirms hours without commenting on student benefit — ask for a fuller statement.
• Reflection is generic: 'I improved my patience' rather than 'Using Socratic questions instead of direct explanations worked for algebraic reasoning; relying on worksheets worked less well because student needed verbal practice to retain material'.
• Long unexplained gaps in the session log — consistent commitment over time is the core signal this outcome demonstrates.

Resources

What a verifier looks for

• The coordinator sign-off must come from the programme, not from the student's parent — parent confirmation does not substitute for institutional sign-off.
• Check that at least one student appears in 10 or more session entries across the full log — sustained relationship with one student is the primary proof signal.
• If there are long gaps in the session log (2+ weeks with no sessions), ask what happened — holiday breaks and illness are fine if noted; unexplained absences are a concern.
• The reflection's credibility comes from specificity — a detailed honest reflection that names one thing that worked less well is more credible than a purely positive account.

You'll sign in first, then come straight back here.