Giving feedback on submitted assignments
A submitted assignment deserves a response. How to react quickly and concretely without falling into hours of correcting.
A submitted assignment is a signal: someone worked here. If the response is missing, the assignment loses meaning – and the next one is done with less seriousness.
Feedback does not have to be elaborate. This article shows how to react to submissions quickly and concretely.
Why submissions deserve an answer
A submission is an invitation for feedback. Whoever leaves it unanswered signals: it does not matter whether you did this. Exactly that undermines the next assignment.
A short reaction – even a small one – shows instead: your work is seen and counts.
Quick is more important than detailed
The quality of feedback does not depend on its length. A short, concrete comment shortly after the submission works more strongly than a detailed one that comes days later.
The closer the feedback is to the submission, the better the student can connect it to their work.
Addressing the goal of the assignment
The best feedback refers to what the assignment was meant to achieve. Was the goal reached? What went well, what still needs work? That keeps the response focused.
That turns “good” or “so-so” into an answer that shows the next step.
Include the next step right away
As with feedback in general, the next step makes the difference. “The rhythm sits – now raise the tempo slowly” is worth more than any assessment.
The next assignment then builds directly on the feedback.
Review and prioritise submissions first
When several assignments or recordings arrive, start with a quick check: does the file open, is the task complete and is there a question that needs answering before the next lesson? This helps you spot urgent cases without having to assess every submission in detail immediately.
Set a realistic response window and communicate it. A brief receipt confirmation may come first; subject feedback can follow when you have time to listen or read attentively. Reliability does not mean being available at all times, but making the next step clear.
Give specific feedback on one passage
A recording benefits from a limited focus. Refer to a bar, phrase or specific moment and describe what you hear: “The entrance is secure, then the tempo speeds up.” Follow that with a manageable task, such as repeating the phrase with a metronome and keeping the ending steady.
Name what worked well too, in concrete terms. The student then knows which approach to keep. One strength and one next focus are often more helpful than a long list of corrections to apply at once.
Consider technical and personal aspects
Not every submission can be reviewed immediately. A file may be incomplete, a recording too quiet or a link inaccessible. Ask for a new version neutrally and avoid interpreting a technical problem as a lack of preparation.
Recordings often contain personal information. Use them only for the agreed teaching purpose, limit access and decide how long they need to be kept. Sensitive feedback may be better discussed in an appropriate conversation than in a short message that can be misunderstood without tone of voice.
How MUSIRIS carries feedback on submissions
In MUSIRIS submissions and feedback stay on the same assignment. You see what was handed in, react directly there, and the student finds your response exactly where they continue working.
You can try MUSIRIS for free. React to the next submission with a short, concrete comment – and watch how the following week goes.
No credit card · Ready in a few minutes