Writing a reflection a rubric can score

A reflection is not a diary entry

Several engagement checks and, very likely, part of the unconfirmed remainder of the grade are reflections — short pieces on something you did. Learners lose marks on them for one reason: they write feelings ("the meeting was frustrating but I learned a lot") where the marker is looking for evidence and a decision. A reflection the rubric can score has four parts, and this course marks it with R-reflect — a Memra rubric that mirrors the criteria the open sources on reflective writing agree on (the official SAF rubrics are not public):

1. A specific event — one thing that happened, with when and who.
2. An honest evaluation with evidence — what went well or badly, and the facts that show it.
3. One transferable lesson — a rule you can apply to a different situation.
4. One dated next step — a behaviour, with a date, that a reader could check happened.

Worked example — the first group meeting

Event. Our first group meeting for the PSP case, Thursday 2 October, 4–5:10 pm, all five of us present.

Evaluation with evidence. It ran forty minutes over and ended with no decisions. Evidence: there was no agenda — three topics (roles, the case facts, the deadline) were raised in the order people thought of them; the roles discussion alone took thirty-five minutes; nobody was timing; and the only outcome recorded in the shared document was "meet again Monday".

Lesson. A meeting without an agenda item phrased as a decision produces discussion instead of decisions. The transferable rule: every agenda line names the decision to be made, and one person is timing.

Next step. I will send the agenda for the 9 October meeting — three lines, each phrased as a decision, with a time box — to the group channel by Tuesday 7 October, 6 pm.

Notice what the fourth part is not: "I will try to be more organised" is an intention, not a step. A reader can check whether an agenda was posted by Tuesday at six; nobody can check whether you tried.

The evidence line is the one that fails

"I learned a lot" fails part 2, because there is no evidence — nothing a reader could verify. The fix is always the same: replace the adjective with the fact. Not "it went badly" but "forty minutes over, no decisions recorded". Not "I prepared well" but "I had a page of notes with the three key facts and one question".

Planning a low-content, high-cadence term

The other half of this lesson is the calendar. AFM 111 has almost no content to learn but a great deal to do, on a fixed cadence: a weekly engagement check every week; two Kritik windows (each a create deadline followed by an evaluate window); the ethics MCQ; the group case; the email; the memo. In a typical term (the Fall 2022 pattern as indexed — dates move year to year; check LEARN) the MCQ falls around week 3, the first Kritik cycle around weeks 5–6, the group case around week 8, the second Kritik cycle and the email around weeks 9–10, and the memo in week 12. The failure mode is obvious from the figure: weeks 9–12 stack three assessments on top of the weekly checks. A plan that is systematic (everything on one calendar, with the drafting week before each deadline blocked) and flexible (a spare evening each week for what slips) is the difference between a term that runs and one that runs you.

Draft your own next-step line for a second event — a Kritik evaluation you rushed in twenty minutes the night it was due — before you type the skeleton below.