Submitted three weeks ago, still waiting
An apprentice uploads a piece of work to their portfolio on Sunday evening. It lands in their coach's e-portfolio inbox alongside work from forty other learners. The coach is out on reviews most of the week, and the pile grows. One learner submits five pieces in a burst before their gateway. Another submits nothing for months, then panics.
Three weeks later the apprentice emails to ask whether anyone has looked at their work. Their motivation has dipped. Meanwhile another coach on the team has a light week and would happily mark some of it, but nobody can see where the backlog is.
Why feedback is slow even with a good team
- Each coach only sees their own inbox, so the team cannot share the load.
- The e-portfolio shows submissions but not how long each has waited in a way managers can use.
- Submissions arrive in bursts around reviews and deadlines.
- Marking competes with reviews, travel and teaching, and it is the task most easily put off.
- Learners cannot see where their work is, so they chase by email, adding to the pile.
What slow feedback costs
Feedback that arrives weeks late is feedback the learner can barely use. Progress stalls, resubmissions pile up near gateway, and some learners disengage altogether. Your coaches feel permanently behind, and the backlog is invisible to managers until learners complain. By then, the fix is usually a weekend of catch-up marking, which is exactly when feedback quality suffers most.
Where internal quality assurance samples marking, a rushed backlog also makes it more likely that feedback quality varies.
A shared marking queue
- Submissions are read from your e-portfolio as they arrive, through its API or regular export, with learner, unit and submission date.
- Each submission gets a target date based on the turnaround your team sets, with shorter targets for learners near gateway.
- A team queue shows every piece of work waiting, how long it has waited and who it is allocated to.
- Allocation starts with the learner's own coach; when a coach's queue passes a level you set, work can be offered to colleagues qualified for that standard.
- Work near or past its target date raises an alert to the coach and then to the manager.
- Learners see a simple status for each submission: received, being marked, feedback given.
| Queue view | Who uses it | What it answers |
|---|---|---|
| My marking | Each coach | What is waiting and what is most urgent |
| Team queue | Delivery manager | Where the backlog is and who has capacity |
| By standard | Lead assessors | Which standards have the longest waits |
| Learner status | Apprentices | Where my work is |
Marking itself stays in your e-portfolio. We add the queue and the visibility around it.
A team that shares the load
On Monday the delivery manager sees one coach with a heavy queue after a round of reviews and another with a light week. With two clicks, some of the heavy queue is offered to the colleague, who is qualified in that standard. The learner's own coach still sees the work and the feedback.
The coach's own week changes too. Instead of an inbox that only ever grows, they see a queue ordered by what is most urgent, with the work of a learner two months from gateway at the top and a routine submission from a new starter lower down. Marking gets done in the gaps between reviews, in the right order, and nothing silently ages past its target date.
Learners stop emailing to ask where their work is, because they can see it. Near gateway, submissions from learners close to their planned end date jump the queue automatically.
Do your learners wait for feedback?
- Learners email to ask whether their work has been marked.
- Some coaches have large marking piles while others have capacity.
- Managers cannot see marking waiting times without asking.
- Submissions pile up before gateway.
- Feedback often arrives weeks after submission.