The fastest way to prove I can do this brief is to do it. Below are three real Canva designs I created and edited for this application — built live through Canva, then text-corrected and brand-aligned by hand. Each one opens in Canva. Underneath: the asset pipeline, a naming convention and a version-control system — the "organised repositories" the brief asks for, shown as a working system.



The two highlighted gates — documentation and review — are what turn a pretty file into a training-ready, brand-safe asset. That's the part of this brief most pure designers skip, and it's where my AI-annotation discipline lives.
| Status | What it means | Who acts | Suffix |
|---|---|---|---|
| Draft | First build in Canva; text & layout in progress | Creator | _draft |
| Review | Brand & accuracy check; placeholder text removed | Creator → lead | _review |
| Final | Approved, exported, logged with metadata | Lead sign-off | _final |
| Archived | Superseded version kept for traceability | Auto | /_archive/ |
Every asset carries one status at a time. Old versions move to /_archive/ rather than being deleted — so the history is auditable, which matters when assets feed an AI training set.