The Reflection That Isn't Reflective
Dev has completed a strong 30-hour project building a school garden. His log is detailed: dates, tasks, hours. But his reflection draft is a list of what happened - 'I built beds, I planted seedlings, I organised a watering roster' - with a final line: 'Overall it went well and I learned a lot.' His teacher says the folio must show how his understanding of himself and his capabilities changed, with specific evidence. Dev argues that the log already shows everything he did, so reflection is 'just repeating it.' He has one week before submission and is reluctant to rewrite.
1. Is Dev right that his log already provides sufficient evidence? Justify your answer.
Read the worked answer
No. The log and the reflection answer different questions.
What the log shows: activity - what he did, when, for how long. It is strong on description.
What the folio requires: evidence of changed understanding of himself and his capabilities - analysis. 'I learned a lot' asserts learning without demonstrating it.
Why the log is insufficient:
- It cannot show why decisions were made, what went wrong, or what he would do differently.
- It gives no evidence of self-awareness - the core of the reflection requirement.
Judgement: Dev's log is necessary but not sufficient. The reflection is not repetition; it is the layer that turns activity into evidenced learning. Without it, a busy log reads as attendance, not development. His reluctance is understandable given time pressure, but the gap is fixable with targeted revision rather than a full rewrite.
2. Dev has one week. What is the most efficient way to strengthen his reflection, and what should he prioritise?
Read the worked answer
With one week, he should target the weakest points rather than rewrite everything.
Efficient method:
- Pick 3–4 concrete moments from the log (a problem, a decision, a surprise) and for each write: what happened, what I assumed, what I now understand, what I'd change.
- Replace 'it went well' with specific claims tied to evidence (e.g. 'I underestimated the watering roster; I learned I plan tasks but not maintenance').
Priorities:
- Specificity over length - a few well-evidenced moments beat a long vague narrative.
- Connect to self-understanding, not just the garden.
- Keep the log as an appendix so claims are traceable.
Judgement: The highest-value change is converting description into analysis at a few key points. This is achievable in a week and directly addresses the teacher's feedback, whereas a full rewrite risks running out of time and losing the strong log he already has.