← Summarising the development of a digital outcome
The Achieved/Merit/Excellence ladder, applied to every part
The exact question wording changes between years, but the underlying ladder — describe, then explain in depth, then connect comprehensively — is identical every year, confirmed in every published assessment schedule.What each level actually requires, in the schedule's own words
- ACHIEVED: describes/names/lists the required elements — the outcome's purpose, the software used, the key stages of development. A factual account.
- MERIT ("in-depth"): explains WHY, with detail and specific examples — clearly explaining two or more decisions in detail, or discussing how two requirements were addressed with specific examples.
- EXCELLENCE ("comprehensive"): evaluates and CONNECTS — how decisions affected the outcome and what the flow-on effect was, discussing trade-offs and reflecting honestly on what could be improved.
Why "comprehensive" is about connection, not just extra content
A response that answers every part correctly but treats each as a separate, disconnected item stops at Merit. Excellence requires showing how the parts relate — the requirement served a named end user, the trade-off reflects what mattered most FOR that user, and the reflection shows genuine learning that connects back to the same requirement or decision.One preparation habit that lifts every part at once
- For each requirement, decision, and implication you plan to write about, pre-write the SAME connecting thread — which named user it serves — so every part of the summary already points back to that one thread on the day.
A fast check against the ladder before submitting
- Have I described the required elements factually (Achieved), THEN explained why with detail (Merit), THEN connected decisions to outcomes and reflected honestly (Excellence)?
- Does every part point back to the same named end user, rather than treating each part in isolation?
Practice for this standard covers the whole topic — flashcards and quiz.