Still need help?
Get in touch with the LX.lab team by logging a ticket via ServiceConnect. We'll be in touch shortly.
Log a ticketWant to provide feedback on this resource? Please log in first via the top nav menu.
There are different schools of thought around the construction of a block of feedback. Here we look at some of the methods you can use.
The feedback sandwich is a framework that is often recommended for constructing a paragraph feedback comment.
The structure is:
The aim of the format is to ‘soften the blow’ of negative points by cushioning them with positive ones. While this can help you make sure that you are keeping a positive tone, the increasing fear in practice is that this format is overused. The result is that students are conditioned to it and will feel like any positive comments are there for show, merely to fill the space in this equation and do not hold any weight of their own. For this reason, it’s worth exploring other methods of giving clear and useful feedback.
The following is an alternate suggestion based on a framework used for audio/video feedback. You can read more about that in this article on the video feedback process.
While there are a number of elements here, hopefully, you can also see how there are opportunities to make use of comment banks to save time while still providing a rich comment, as described in the practical recommendations below.
While the knee jerk reaction might be that this feels like ‘cheating’, in reality, students often err in ways that can be captured by similar comments. So rather than spending the time trying to craft content that effectively says the same thing, using standard phrases gives you the opportunity to add further information and more nuanced comments around these points. Ultimately, it is a commonly used practice and one of the things that are generally advised by experienced tutors. There are even comment bank functions that you can use in Canvas Speed Grader to facilitate this.
If you are concerned that students might feel hard done by if they discover the use of similar comments/phrases, between their own and a peers’ work, keep in mind that you can explain it to them with the above (i.e., standard comments leave space for more unique feedback).
Also noting here that developing a bank of feedback comments is very different from copy-pasting a students feedback comment in full – if your feedback would fit two different student assignments without adjustment this indicates that the level of detail is not appropriate.
In the case of in-progress feedback, you may also wish to keep a range of go-to phrases ‘in your back pocket’ for guiding conversations (“You’re on the right track. What would happen if …”). You will likely build up this set of phrases during your experience of working with students, but it is useful to think about how you might develop these (and retain the good ones) if you are new to teaching.
The rubric (where present) is the framework used by students to understand what is expected. Being able to articulate where a student’s work falls in relation to this standard is part of marking, but also gears into the feedback. Introducing the rubric as part of the assignment framing can further reinforce its importance for students as a focal point. In relation to in-progress feedback, referring to the rubric will again allow students to understand the connections to endpoint goals and how they can target them effectively.
Depending on the flexibility you have in your tutorials/contact time, you may have the opportunity to communicate to the cohort collective strengths and misconceptions/areas where improvement is needed around a particular assignment (preferably before they get access to their assignment feedback). There are a number of reasons why putting together collective feedback is a good idea:
As part of this interaction, it’s good if you can get students who understand the concept to provide some explanation as well. The more collaborative/interactive you can make this experience the less it feels like you are the one communicating opinions, and more that you are identifying the best practices together.
Get in touch with the LX.lab team by logging a ticket via ServiceConnect. We'll be in touch shortly.
Log a ticketWant to provide feedback on this resource? Please log in first via the top nav menu.