New

Now in Claude, ChatGPT, Cursor & more with our MCP server

Back to docs
research-methods10 min read

Did the Course Build Students Who Can Use Feedback? Feedback Literacy as an Evaluation Lens

Carless and Boud's feedback-literacy framework reframes a course-quality question: not "was feedback given?" but "did the course develop students who can appreciate, judge, manage, and act on feedback?"

Koji Education Team

Product

In brief

Carless and Boud (2018) define student feedback literacy as the understandings, capacities, and dispositions students need to make sense of feedback and use it to improve — built on four features: appreciating feedback, making judgments, managing affect, and taking action. For course evaluation this reframes the standard question. Instead of asking only "did you receive feedback?", a feedback-literacy lens asks whether the course design developed students who can actually use feedback. That is a question about teaching practice and course architecture, and it is far more diagnostic of quality than a satisfaction rating about feedback timeliness.

What the research says

For decades, "feedback" in higher education was treated as a transmission problem: give students more comments, faster, and learning would follow. The National Student Survey's persistently low "assessment and feedback" scores across the UK are a symptom of that framing failing. Carless and Boud (2018), in Assessment & Evaluation in Higher Education, argued the framing itself is wrong. Feedback only "works" when students can receive, interpret, and act on it — and that capacity, feedback literacy, has to be deliberately developed.

Their conceptual framework identifies four inter-related features of a feedback-literate student:

  1. Appreciating feedback — understanding feedback as an active process in which the student has a role, recognising that comments come in many forms (peer, self, technology, exemplars), not just teacher marking.
  2. Making judgments — developing the evaluative capacity to appraise the quality of one's own and others' work, so feedback can be internalised rather than simply obeyed.
  3. Managing affect — maintaining emotional equilibrium in the face of critical comments, avoiding defensiveness, and staying agentic rather than discouraged.
  4. Taking action — the decisive step: acting on feedback to improve subsequent work. Uptake, not receipt, is the point.

Carless and Boud show how two well-established practices — peer feedback and analysing exemplars — can be re-purposed to build these capacities, moving feedback from something done to students toward something students do.

The framework has been developed further. Molloy, Boud, and Henderson (2020) analysed students' own accounts of feedback across two large universities and proposed a learning-centred framework that expands the picture with concrete student behaviours and the enabling conditions courses must provide. Both papers build on a longer tradition — Nicol and Macfarlane-Dick (2006), whose seven principles of good feedback practice reframed feedback as a driver of self-regulated learning rather than a one-way judgement. The through-line is consistent: the quality of feedback in a course is not measured by how much is dispensed, but by how much students are equipped and prompted to use.

Why it matters for course evaluation in practice

Most course-evaluation instruments ask feedback questions at the wrong altitude. Typical items — "Feedback was timely," "Feedback was helpful," "I received enough feedback" — measure satisfaction with delivery. They can be high in a course that produces no feedback uptake at all (fast, pleasant, ignored comments) and low in a course that develops deep evaluative judgement (demanding peer critique that students resent in the moment but learn from). Satisfaction with feedback and the educational value of feedback are different things.

A feedback-literacy lens repositions the evaluation around the four features:

  • Instead of "Was feedback timely?", ask whether students used feedback to improve later work (taking action).
  • Instead of "Was feedback clear?", ask whether the course helped students judge the quality of their own work (making judgments) — the capacity that outlasts any single course.
  • Ask whether the course used peer feedback and exemplars, the practices the literature identifies as literacy-building.
  • Ask about affect — whether students felt able to engage with critical feedback rather than shutting down.

This matters for three reasons. First, it aligns the evaluation with what actually drives learning gains, connecting to the broader point that satisfaction is a weak proxy for learning (see desirable difficulties). Second, it produces actionable evidence: "students don't act on feedback because assessments are one-shot with no opportunity to apply comments" points to a fixable design flaw, whereas "feedback score = 3.4/5" points nowhere. Third, it closes the loop on a well-documented problem — students often doubt their feedback is even used (see students willing but doubtful feedback is used); a literacy lens makes uptake, on both sides, visible.

Limitations and honest caveats

The feedback-literacy framework is powerful but has real limits a rigorous QA office should acknowledge.

  • It is a conceptual framework, not a validated scale. Carless and Boud (2018) is a theory paper. There is no single canonical, psychometrically validated "feedback literacy" instrument that all institutions use; measurement is still developing. Any items you write are, for now, locally constructed and should be pretested (see cognitive interviewing).
  • Self-report of "taking action" is fallible. Students may over-report uptake, or lack the metacognitive insight to know whether they acted on feedback. Ideally, uptake is triangulated with artefacts — draft-to-final improvement, resubmission data — not inferred from a survey item alone.
  • Attribution is hard. Feedback literacy develops across a whole programme, not one course. A single module cannot claim credit (or blame) for a student's overall evaluative capacity; course-level items should ask about this course's contribution, not the trait in absolute terms.
  • Affect is sensitive. Asking students about emotional responses to critical feedback touches on wellbeing and can be confounded with grades received; interpret with care and never in a way that pressures instructors to soften standards.
  • Cultural variation. Norms around receiving and acting on critique differ across educational cultures, which matters for the diverse, multilingual cohorts common in European higher education.

How Koji incorporates this

Koji for Education is well suited to a feedback-literacy lens precisely because it moves beyond fixed Likert items into structured conversation.

  • Probing uptake, not just receipt. Koji's AI-moderated interview can ask an open_ended question — "Think of feedback you got on an early assignment: what, if anything, did you do differently afterwards?" — and follow up adaptively when a student is vague. This targets taking action, the feature that a satisfaction item cannot reach.
  • Question types mapped to the four features. Appreciating feedback, making judgments, managing affect, and taking action can each be operationalised — scale items for perceived capacity, open_ended for concrete examples, single_choice for whether peer feedback and exemplars were used. Koji supports open_ended, scale, single_choice, multiple_choice, ranking, and yes_no question types, so the instrument matches the construct rather than forcing everything into agree/disagree.
  • Automatic thematic analysis. Free-text answers about feedback use are clustered into themes automatically, so a QA officer sees patterns — "no opportunity to apply feedback before the next assessment" — instead of hand-coding hundreds of comments (compare our note on inter-rater reliability in thematic analysis).
  • Formative, mid-cycle collection. Because feedback literacy is about acting on comments within a course, Koji can run a mid-semester check while there is still time to change the design, not just a post-mortem after grades are in.
  • Closing the loop. Koji's action-tracking is designed to record what the department changed in response — turning the evaluation itself into a feedback-literate act at the institutional level, and mitigating the students-doubt-it-is-used problem the literature documents. Framed honestly: Koji is designed to surface and support feedback uptake, not to guarantee it.

For research beyond the classroom, Koji's core platform at koji.so uses the same AI-moderated interview engine for product and customer research, where "did the user act on what they learned?" is an equally central question.

Related resources

References

  • Carless, D., & Boud, D. (2018). The development of student feedback literacy: Enabling uptake of feedback. Assessment & Evaluation in Higher Education, 43(8), 1315–1325. https://doi.org/10.1080/02602938.2018.1463354
  • Molloy, E., Boud, D., & Henderson, M. (2020). Developing a learning-centred framework for feedback literacy. Assessment & Evaluation in Higher Education, 45(4), 527–540. https://doi.org/10.1080/02602938.2019.1667955
  • Nicol, D. J., & Macfarlane-Dick, D. (2006). Formative assessment and self-regulated learning: A model and seven principles of good feedback practice. Studies in Higher Education, 31(2), 199–218. https://doi.org/10.1080/03075070600572090

Related articles