Homework in five places
Your course asks students to submit three assignments: a draft offer, a sales page outline and a first email sequence. Feedback is a big part of what they pay for. Submissions arrive as a form on your platform, as email attachments, as links posted in the community, and as Google Docs shared with you directly. Two coaches help with feedback, and each checks a different place.
A student emails, politely, three weeks after submitting her sales page. She has had no feedback. You find her submission in a Google Drive notification you had archived. Neither coach saw it.
Why submissions slip
Course platforms often have an assignment feature, but students do not always use it, and it rarely handles coaches, deadlines and routing well. So submissions arrive wherever students find convenient, and each person checks the places they know about. There is no single list, no owner for each submission and no clock showing how long anyone has waited.
- Students submit through whatever channel is closest.
- Coaches check different places and assume someone else has the rest.
- Nobody can see how long each submission has been waiting.
- Feedback is given in different formats, some of it lost in email.
- Completing an assignment does not update the student's progress.
What slow feedback costs
Feedback is often the reason a student chose your course over a cheaper one, so missing or late feedback cuts straight into what they paid for. Students who wait weeks lose momentum and stall. Coaches who cannot see a fair share of work get frustrated. And refund requests that mention 'no feedback' are hard to argue with.
One feedback queue for every submission
- A single submission form is linked from each assignment lesson, asking for the file or link and any questions the student has.
- Submissions that arrive another way (email, community, shared docs) are forwarded or added to the queue in one step, so nothing lives outside it.
- Each submission is assigned to you or a coach by your rules: by assignment, by cohort, by coach capacity or in turn.
- The queue shows each submission's age, and anything waiting longer than your target is raised to you.
- Reviewers leave feedback in the queue, as text, a marked-up document or a short video link, and mark it complete.
- The student receives their feedback by email and in their course account, and their progress updates on the platform.
- A weekly view shows each coach's load and the average wait, so you can rebalance.
| Submission | Routed to | If waiting too long |
|---|---|---|
| Draft offer | Coach A | Raised to you |
| Sales page outline | Coach B | Raised to you |
| Email sequence | You | Reminder to you |
| Resubmission after feedback | Same reviewer as before | Raised to you |
An optional step can draft first-pass notes against your marking guide using a language model such as Anthropic Claude, which the reviewer edits. Feedback always comes from a person.
Feedback that arrives
Every submission is in one place with an owner and a clock. Coaches see their own list and nothing falls between them. Students get feedback where they expect it, and their progress moves on. The student who waited three weeks would, under this setup, have been raised to you after a few days, well before she had to email.
You also build up a library of submissions and feedback over time, which shows the common mistakes at each assignment and helps you improve the lesson before it.
Is feedback slipping in your course?
- Assignments arrive by email, forms, community and shared docs.
- Students have waited weeks for feedback.
- Coaches are unsure which submissions are theirs.
- You cannot see how long anything has been waiting.
- Assignment completion does not show in student progress.