Evaluating and annotating: making thinking visible through annotation; critical evaluation of your own work and progress; reflecting on decisions to drive development and evidence the objectives.

What this dot point is asking

Evaluating and annotating is how you make your thinking and judgement visible, and it is what AO3's "reflecting critically on work and progress" rewards. This dot point is about making thinking visible through annotation, critically evaluating your own work, and reflecting on decisions to drive development and evidence the objectives. Good annotation reveals reasoning and judgement; it is not labelling or empty praise.

Annotation makes thinking visible

A moderator marks the work and the thinking behind it, but the thinking is only visible if you make it so. Annotation is how you put your reasoning on the page: why you chose a technique, what an experiment showed, how an artist study informed a decision. Without annotation, much of the thinking that the objectives reward (the analysis, the reviewing, the reflection) is invisible. With it, the moderator can see the investigation, the refining and the reflection that the marks are for.

Description versus critical evaluation

The single biggest weakness in annotation is description: labelling what the work is ("this is a charcoal drawing of a tree"), which the work already shows and which adds nothing. Critical evaluation instead judges: it weighs what worked and what did not against the intention, and explains why. "The charcoal caught the rough bark, but the composition is too central" reflects and decides, where the label does not. The objectives reward reflection and judgement, so evaluation earns marks that description does not.

Evaluation drives development

The most valuable feature of annotation is that it drives development. An evaluation that ends with a next step turns reflection into the engine of the project: "the wet-in-wet caught the light better than the flat wash, so next I will build the outcome wet-in-wet". This is what connects the line of enquiry and sustains development; without the forward step, reflection only describes the past. Every evaluation should therefore end by deciding what to do next.

Evaluation across the project

Beyond annotating individual pieces, you should evaluate the project's progress as a whole at points along the way: stepping back to assess how the enquiry is going, what is working, and where to take it next. This bigger reflection guides the development and is itself the critical reflection AO3 rewards. A short evaluation at key stages, and a final evaluation of the resolved outcome against the intentions, makes the reflective thread complete.

Try this

Q1. Explain the difference between describing and critically evaluating work in annotation. [Knowledge recall]

• Cue. Description labels what the work is or shows (its medium, subject), which the work already conveys; critical evaluation judges the work against its intention (what worked, what did not, why) and decides the next step, which is the reflection AO3 rewards.

Q2. Explain why effective evaluation should end with a next step. [Short explanation]

• Cue. An evaluation that ends with a next step turns reflection into the engine of the project, feeding the following work and sustaining the line of enquiry, so the reflection drives development rather than only describing the past, which is what AO3's "reflecting critically on work and progress" and sustained development reward.