HOW IT WORKS

One connected progression workflow.

From pathway choice to submitted application, every step is visible and owned. Students draft, AI gives advisory feedback that staff can see in full, and deadlines stay in view for everyone.

Outleap · Teacher Dashboard Greenfield Academy
Outleap Teacher Dashboard
j.morrison@greenfield.sch.uk
Sign out
Total students 24
Submitted 7
Drafting 11
Not started 6
Search by name or email...
All statuses
All progress
Sort by name
Asc
Student Pathway Risk Next action Owner
Sophie Thompson s.thompson@greenfield.sch.uk
University On track Round 2 ready Ms Patel
Daniel Patel d.patel@greenfield.sch.uk
Apprenticeship No evidence Capture evidence Mr Cole
Amara Okafor a.okafor@greenfield.sch.uk
University Deadline near Final check Ms Patel
Ryan Chen r.chen@greenfield.sch.uk
University On track Awaiting student Ms Patel
Hannah Khan h.khan@greenfield.sch.uk
Employment No applications Discuss routes Mr Cole
Jake Williams j.williams@greenfield.sch.uk
Undecided Undecided pathway Careers meeting Unassigned
Mia Doyle m.doyle@greenfield.sch.uk
University Drafting Submit draft 1 Ms Patel
Student loopStaff loopFull staff visibilityDeadlines
BEFORE AND AFTER

The same season, run two ways.

The work doesn't change. Who can see it, and when, does — and that is what moves support earlier.

Run from inboxes and spreadsheets
  • Drafts sit in email threads and shared folders; nobody is sure which version is current.
  • Feedback depends on who chases whom, and a strong student gets it before a quiet one.
  • You see who submitted, not who is stuck — and the deadline arrives before the gap does.
Run through one workflow
  • Each student has a current draft, a pathway and a status, in one place.
  • Every student gets structured feedback on the same footing, visible to staff.
  • Risk surfaces while there is still time to act, and the next action has a named owner.
THE STAFF LOOP

See who is on track, who is stuck, and what has been done.

Staff work from a live cohort view rather than tutor memory and chasing. Every student carries a status, a risk flag and a next owner.

A cohort you can read at a glance

Year 13 in one view: pathway mix, who has submitted a draft, who has feedback pending. No rebuilding the spreadsheet every September.

Risk flags that surface early

Concrete reasons, not a vague worry: no evidence entries, undecided pathway, statement not started, deadline near. The 20 who look fine until October are visible in September.

Interventions with an owner

When a student needs support, staff log it against the record. The next action has a named owner, so nothing falls between a tutor and a coordinator.

FEEDBACK STAFF CAN SEE IN FULL

Advisory AI feedback, with staff watching over the whole cohort.

This is the load-bearing rule. AI feedback is advisory and bounded to the student's own draft, staff can see the feedback every student receives through normal product views, and safeguarding escalation stays with the school's usual route — there is no verdict, grade or score on a child's work.

Drafted, then locked

A student submits a draft for a feedback round. The submitted version is locked, so staff and student are looking at the same text.

Advisory, bounded feedback

Feedback is a headline summary, priority actions, and section strengths and improvements on the student's own draft. It suggests and explains; it does not decide. There is no single-word grade and no black-box score, and staff can see what every student receives.

Rounds, with a clear state

Students see a process-state chip — submitted, feedback published, round two — never a quality band. Each round shows what to change next, and the work stays the student's own.

THE WORKFLOW, END TO END

Four steps, one trail of evidence.

Each step leaves a record the next step can use, and a leader can see. The student writes, AI gives advisory feedback staff can see, staff apply their judgement, and deadlines hold it all to time.

Step 1

Choose a route and build evidence

Every student records a pathway and adds to their evidence bank, so support starts from what they have actually done — UCAS, apprenticeship, employment or undecided.

Step 2

Draft, submit, get feedback

The student drafts the three questions in their own words and submits for a feedback round. Advisory feedback is generated against each section, and staff can see it on the record.

Step 3

Act on the feedback

The student receives advisory feedback with priority actions for the next round. Staff log any intervention, and the next action carries a named owner.

Your progression Amira · Year 13 · Healthcare
Owned by · Ms Patel
Your next action

Draft your “why healthcare?” answer using your hospital-volunteering evidence.

Open workspace →
Pathway chosen
Evidence saved
Opportunity saved in development
Application started in development
Feedback received
Next action owned
DEADLINES AND REMINDERS

Deadlines stay in view, and reminders go out in time.

Key dates sit in the workflow rather than a separate calendar, so a student knows what is due next and staff can see who is approaching one. UCAS deadlines and the milestones for CVs and non-university applications sit alongside each student's progress. The point is simple: a deadline becomes visible while there is still time to act, not after it has passed.

SEE IT WITH YOUR COHORT

Walk the whole workflow with your own season in mind.

A consultative walkthrough of the connected workflow — student loop, staff loop, advisory feedback with full staff visibility, and deadlines — mapped to how your sixth form runs the season today.

Book a walkthrough