Annotating a project plan
A short dated note on a project plan that records what changed and why, and keeps the original plan visible next to the actual dates.
Understanding Annotating a project plan in VCE Data Analytics U4O1
What it does: The note starts with the date it was written and then records the change, so the timeline of changes is clear. The reason (client requested extra chart) is what lets someone later judge whether the change was necessary. A good annotation is dated and records what changed and why. It should also show the original date and the new date. The first note has no date, no original or actual dates and no reason. The second note has all of these. Showing the original bar beside the actual bar means the plan is not overwritten, so the change can be seen and judged later.
Common mistakes: An annotation must be dated and record what changed. This note has no date and no size of change. It should read something like 'Note: 19 Aug, data late, +7d'. The original date has been overwritten with the actual date. The original plan must stay visible, so this should still say 'Original end: 5 Sep'.
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 85–105) and word search (Modules 63–105).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
annotationFill in the Blanks
Spot the Error
Student with a class code? Join your class →