Documenting Changes

Overview

In this lesson, students explore how professionals document the development process of digital imaging projects, focusing on clarity, versioning, and traceable decisions. Students then create and practise documenting a short “project story” for an editing task from the unit.

Learning intentions

• Students will be able to explain why industry documentation supports collaboration, quality, and review.
• Students will be able to use a consistent structure to record changes across drafts (ideas, edits, outcomes).
• Students will be able to communicate technical decisions clearly using suitable language and visual evidence.
• Students will be able to reflect on how documentation improves future iterations.

Success criteria

• I can identify what needs to be documented (purpose, changes, tools/techniques, results, and next steps).
• I can create a dated, versioned development log for a digital imaging draft.
• I can justify at least two editing decisions using evidence from before/after outcomes.
• I can check my documentation for clarity so another person could follow the changes.

Curriculum links

• Digital systems and data concepts through documenting the creation process and handling digital files responsibly.
• Design, creation and evaluation: documenting iterations and evaluating improvements.
• Using technology to communicate solutions and justify choices with evidence.
• Responsible digital practices, including file management and academic integrity.

Lesson structure (60 minutes)

1. 0–5 min: Hook and context

• Teacher shows a short example (printed or projected) of an effective development record from a digital imaging workflow (before/after plus notes).
• Students discuss: “What information is most useful and why?”

2. 5–12 min: Industry documentation patterns

• Teacher models a simple documentation structure on the board: goal, baseline image, changes made, settings/tools (where relevant), outcome, and reflection/next step.
• Emphasise traceability: a reader should be able to understand what changed and why, not just what the final image looks like.

3. 12–20 min: Inspect and classify

• Students look at two provided mini-examples of documentation (one clear, one vague).
• In pairs, they classify what’s missing or unclear (e.g., no dates, no reasons, missing before/after, inconsistent wording).

4. 20–35 min: Build a development log (independent)

• Students select one draft of their project work from the unit and create a “versioned” development record.
• Required elements for today’s log:
• Version name or number and date
• What the aim was for this draft
• Baseline reference (link/label to the earlier image file)
• What they changed (edits performed and any key settings/filters used, described clearly)
• Evidence of outcomes (before/after thumbnails or screenshots)
• Brief justification (why this change improved the image)
• Next step for the next iteration

5. 35–48 min: Peer review using a checklist

• Teacher provides a short checklist (teacher-created) focusing on clarity, completeness, traceability, and justification with evidence.
• Each student gives feedback to one peer (focus on one “strength” and one “specific improvement suggestion”).

6. 48–55 min: Revision and finishing

• Students revise their log based on peer feedback, ensuring wording is specific and the sequence of changes is easy to follow.
• Teacher circulates to confirm each record includes evidence and reasons, not only descriptions.

7. 55–60 min: Exit reflection

• Students write a one-sentence reflection: “The documentation detail I will keep improving is… because…”
• Collect logs for teacher assessment.

Resources

• Students’ existing digital imaging drafts from “Digital Imaging Mastery” (images and any screenshots of edits)
• A teacher-created development log template (paper or digital) with date/version sections
• Example documents: one strong and one weak development record (printed or projected)
• Access to a computer and a file folder structure for versioned saving
• Checklist for peer review (clarity, completeness, evidence, justification)
• Marking/feedback tool (rubric notes or quick checklist)
• A projector/TV for demonstrating the documentation structure
• Pen/paper for quick notes during peer review

Assessment

• Formative assessment: teacher observes student completion of the required development log elements during the independent and peer-review phases.
• Product assessment: review of each student’s development log for clarity, versioning, evidence of before/after outcomes, and justification of decisions.
• Quick reflection check: exit sentence indicates whether the student understands what makes documentation useful for future iterations.

Differentiation

• Support:
• Provide a partially completed template for students who need structure (e.g., already include date/version and aim prompts).
• Offer sentence starters for justification (“I changed … because …”; “This improved … by …”).
• Extension:
• Require an additional “risk/issue” note (e.g., what didn’t work as expected and what was tried instead).
• Ask students to include a brief evaluation against a success target (e.g., improved exposure, colour balance, sharpness).
• EAL/SEN:
• Allow notes using simpler language while still requiring evidence and sequence.
• Provide a word bank of technical verbs (adjust, crop, enhance, correct, refine, export) and a model paragraph.
• Small-group support:
• Teacher meets briefly with the group to check file naming and version consistency before they start documenting.