Label the Goal
Write a short sentence about what the student was trying to learn or improve.
Python evidence guide
Python evidence should show how the student's coding ability developed, not just that a lesson happened.
Use this orientation to match the advice with the student's DofE Skills section decision.
Parents and students comparing this route for a DofE Skills section activity.
The evidence should match the student's route and level of challenge.
Screenshots of beginner programs using variables, decisions, loops and simple functions, plus notes explaining what changed.
Examples using functions, lists, debugging notes and GCSE-style algorithm explanations.
Richer problem-solving tasks, final project files and reflections on efficiency or strategy.
Evidence becomes more useful when it shows the student's thinking.
Write a short sentence about what the student was trying to learn or improve.
Keep screenshots or files that show the actual Python work, not just the output.
A debugging note can show real learning when the student explains the mistake and solution.
A final reflection should explain what the student can do now that they could not do at the start.
Good evidence can include code screenshots, program outputs, debugging notes, logic explanations, completed tasks and a final project.
Students should follow their DofE Leader's guidance. Keeping weekly evidence is useful even if only selected examples are uploaded later.
Yes. Debugging evidence can be very strong because it shows problem-solving and progress.
The coding pathway is structured so students produce visible Python progress across Bronze, Silver and Gold.