Your planning + decision record

Keep a small record that helps someone understand your decisions. Images/PSDs stay in your project folder; record their filenames here.

Use a project code rather than a name on a shared device. Keep a downloaded backup. Typing here saves only on this browser/device and does not submit work.

1. Client choice or equivalent proposed client; audience, viewing encounter and communication problem.2. One observable communication goal and feasible checkpoints. What will a viewer be able to understand or do?3. Two genuine references: maker/date/source, visible form, one sourced contextual fact, one interpretation and the comparison limitation.4. Mood-board file and reasons for imagery, colour/value and typography. Distinguish study references from permitted production assets.5. Three genuinely distinct concepts; selected direction, reason and one rejected option. Link the thumbnails.6. Two colour/type treatments; exact palette roles, relevant readability comparison and selected trade-off.7. Decision 1: intent → actual control/file evidence → visible effect → reason. Record the consequential choice, not every click.8. Decision 2: a technical mismatch, likely cause, one recoverable change and the checked result. Link relevant screenshots.9. Decision 3: how print and phone priorities differ, and why the arrangement was changed.10. Two actual viewers: intended viewing condition, their first reading/message (no names), mismatch with intent and limits of this small test.11. Before/after files, the change made because of actual feedback, its checked effect and one remaining limitation.12. Used asset paths, creator/source/licence, modifications, AI tool/prompt/date and extent of assistance. Include original work too.13. Editable source/export/planning folder; files reopened and dimensions checked; private teacher sharing and registered Form confirmation.14. Teacher feedback, criterion, next action and fresh revisit evidence linked to the earlier attempt.

Hand in through the existing project route

Create a Design a Story folder in your school Google Drive. Include print/screen PSDs and PNGs, mood-board source/view, thumbnails/treatments and this downloaded response record.
Share that folder with cwadden@gnspes.ca for teacher viewing; keep general access Restricted. Do not publicly share student work.
Open the registered Form. Use Proposal and planning for the plan; Final reflection and evidence handoff for the final file link and decision evidence. Copy the relevant concise answer from this record. Use Knowledge check after teaching, and Design Lab reflection after your focused study.
Confirm the Form's submission screen. Retain your folder and downloaded record for teacher feedback/revisit.

Open Design a Story Knowledge + Reflection Form

The existing Form routes were owner-QA tested on 10 October. Intended-student access, private file handoff and released Student OS feedback still need a current school-device check. The local journal does not send or synchronize.