Report Card format inspection-ready • evidence you can actually pull

Stop “we do this”.
Start “here’s the trail”.

The Evidence Map is a one-page structure that turns your delivery into defensible, pullable evidence across Behaviours & Attitudes, Inclusion, and Personal Development — without staff building packs from scratch.

Behaviours & Attitudes
Inclusion
Personal Development
Designed for quality assurance Consistent across cohorts/centres Evidence you can export and share
Thank you!

What you get

Not a template you fill in once. A repeatable evidence system: the structure, the reporting pull-points, and the prompts that generate proof.

Included
Evidence Map (Report Card)
One page that forces clarity: who engaged → what changed → who drifted + what you did. Built to be talked through under scrutiny, not just filed.
Use it for: QI cycles, audits, inspection prep, and centre-level consistency.
Included
Reporting pull-points
Clear guidance on what to pull from Fledglings: learner-level and cohort-level views, engagement signals, progress/completion, and exportable reporting for internal sign-off.
So evidence isn’t “who can find the right screenshot”. It’s consistent every time.
Included
Proof prompts (not waffle)
Short, structured prompts that generate usable evidence: learner voice, scenario reasoning, and next-step actions — designed to be quick for learners and easy to evidence.
Minutes to capture. Powerful to evidence.
Get the Evidence Map Read the FAQ

Inspection-ready evidence FAQs

Straight answers on evidence strength, reporting, inclusion, safeguarding sensitivity, and how this fits into your quality cycle — without extra workload or “pack-building”.

The Evidence Map is built around observable signals and repeatable outputs:
  • Engagement + participation: consistent interaction patterns by cohort/programme/centre
  • Learning signals: completion/progress status, knowledge-check outcomes where used, activity participation
  • Learner voice: structured reflections capturing “what I’d do differently and why”
  • Inclusion in practice: drift/gap → action taken → what improved afterwards
Rule of thumb: every line in the map should point to a view, an export, or a sample — not “we believe”.
Behaviours & Attitudes is evidenced through habits over time: engagement, participation, consistency, and learning culture. The map prompts you to evidence:
  • where engagement is strong (and where it drops)
  • which cohorts/programmes/centres drift
  • what you changed to improve re-engagement
  • what improved after the change
Translation: you’re evidencing behaviour as patterns + response — not a single attendance figure.
Yes — inclusion evidence is strongest when it shows gap → action → impact. The map helps you structure it around:
  • Gap: which learners/cohorts are under-engaging (by group/centre/programme)
  • Action: what you changed (support plan, adjusted delivery, targeted prompts)
  • Impact: what improved afterwards (re-engagement, progress movement, completion lift)
This is the difference: “we’re inclusive” vs “here’s what we did and what changed”.
The map is designed for segmented reporting because “overall” hides problems. Your evidence trail should let you evidence:
  • cohort differences (who engages vs who drifts)
  • programme differences (where extra support is required)
  • centre consistency (what’s strong, what’s variable)
Practical: pull from Fledglings reporting views and exports (as enabled in your setup) so it’s shareable for QI/boards.
The Evidence Map separates learning evidence from personal disclosure. Strong evidence here comes from:
  • scenario-based prompts (demonstrates safe thinking without “tell us what happened to you”)
  • structured reflections focused on choices, knowledge, and next steps
  • clear signposting to institutional safeguarding routes
Net result: you can evidence safeguarding-linked learning without turning the platform into a disclosure inbox.
Week one should be operationally simple:
  • Assign the relevant Fledglings course(s)
  • Set a light rhythm (one module per week + a short reflection)
  • Pull a baseline snapshot (engagement/progress) so you can compare later
  • Record early drift and actions in the map (so it’s not rebuilt at the end)
Why this matters: evidence is strongest when it’s captured as you go — not reconstructed later.
Yes — add an optional Evidence Index page that links each line of the map to the exact view/export your team should pull.
Outcome: “we can evidence this” becomes “we can show it in 30 seconds”.
Get the Evidence Map Back to “What you get”