1. Start with the problem
Explain what the client or service user wanted to achieve, the difficulty they faced and the scope you accepted. If a name cannot be published, use an approved general description of the situation.
Record constraints such as timing, budget or an existing system. Context helps the reader understand what a decision addressed and why a particular approach was chosen.
2. Describe work your team actually owned
Separate lead responsibility, collaboration and externally supplied work. Use concrete actions such as interviewing, designing, testing and handing over, rather than claiming every result of a shared project.
Choose one important decision. Explain the options considered and the reason for the final choice. This makes professional judgement visible without relying on broad service slogans.
3. Separate outputs from outcomes
A delivered document, completed workshop or launched page is an output. Later usage and business changes need their own supporting information. Keep the two categories separate before deciding which results are established.
If delivery is all you can verify, describe it clearly. For any number, include its period, method and source, together with other factors that might affect interpretation.
4. Select two pieces of relevant evidence
Ask which sentence each item supports. An agreed scope, approved version comparison or dated acceptance record may answer different questions. Place the page reference or link near the relevant paragraph.
Check the original wording, date and permission before using a client quotation. When an original cannot be public, use an approved summary and retain an internal reference. Do not assemble an anonymous testimonial from fragments.
5. Close with a reusable improvement
Describe one method the team retained and one adjustment for future work, such as earlier information checks or an additional test. A useful lesson changes a later action.
Ask a colleague to identify the problem, your work and its evidence from the single page. If an answer is missing, repair the connection before adding more images.
A worksheet you can copy
| Part | What to record | Evidence question |
|---|---|---|
| Context and constraints | Audience, objective, period and scope | Is this background approved for use? |
| Team contribution | Three actions and one important decision | Are partner roles distinct? |
| Outputs | What was delivered and when accepted | Is there a delivery record? |
| Observed outcomes | Tracked changes, period and limitations | Is coincidence being presented as causation? |
| Next improvement | One action for the next project | Can an owner put it into practice? |
Before sharing
- Context comes before company description
- Partner roles are clear
- Outputs and outcomes are separate
- Each evidence item supports a claim
- The lesson leads to a practical action
Common questions
What if the client cannot be named?
Agree an appropriate general description and summary first. Keep an internal evidence reference without adding identifying details for dramatic effect.
Does a case need a growth figure?
No. A verified delivery, decision and explanation of constraints can demonstrate capability without inventing untracked results.
Official reference and year
These guides provide original preparation methods. The 2026 material is a historical reference; formal 2027 requirements depend on the relevant edition's announcements. The worksheets do not replace official rules, eligibility decisions or professional advice.
- Awards and judging: 2026 edition reference — checked 2026-11-01
