<\/p>\nThe CAS portfolio is more than a scrapbook. It\u2019s your learning story: a balanced record of creativity, activity and service that shows growth, impact and thoughtful reflection. But it\u2019s easy to fall into two traps \u2014 either hoarding dozens of photos and receipts that dilute the message, or collecting so little evidence that assessors can\u2019t see the learning. This guide walks you through how to choose, organize, and present photos, logs, and proof in a way that is honest, efficient, and compelling.<\/p>\n
<\/p>\n
Begin by remembering why evidence matters. Assessors want to see:<\/p>\n
If every piece of proof you add answers at least one of those bullets, you will avoid clutter. If it doesn\u2019t, question why it\u2019s there.<\/p>\n
Photos are powerful because they capture context faster than words. But more isn\u2019t always better. A few strong images will communicate atmosphere, roles and outcomes far more clearly than dozens of repetitive shots.<\/p>\n
Practical photo rules to follow:<\/p>\n
Example caption: \u201cLeading warm-up games with 12 local children to improve confidence \u2014 I planned three cooperative activities (Activity session 2 of 6).\u201d A caption like this connects the image to your role, the activity, and the purpose.<\/p>\n
Logs are the backbone of your portfolio because they show consistency and chronology. Rather than a stream of long diary entries, adopt a compact, repeatable structure you can use every time you record an event.<\/p>\n
A simple log entry structure:<\/p>\n
This format keeps entries readable and makes it easy for an assessor to scan for progress across the whole portfolio. Aim for clarity: a strong log entry can be read in 20\u201330 seconds and still show learning.<\/p>\n
Proof is anything that confirms the activity happened and that you took part. Types of proof include photos, signed witness statements, event flyers, attendance sheets, certificates, short video clips, screenshots of planning documents, or simple before\/after comparisons for projects.<\/p>\n
Best practices for proof:<\/p>\n
| Evidence type<\/th>\n | When to use<\/th>\n | Ideal file example<\/th>\n<\/tr>\n<\/thead>\n |
|---|---|---|
| Photo (action)<\/td>\n | To show role and activity in progress<\/td>\n | BeachClean_Action.jpg<\/td>\n<\/tr>\n |
| Photo (overview)<\/td>\n | To show scale or setting<\/td>\n | Festival_Overview.jpg<\/td>\n<\/tr>\n |
| Witness statement<\/td>\n | When a teacher or community leader can confirm your role<\/td>\n | Coach_Signoff.pdf<\/td>\n<\/tr>\n |
| Planning doc<\/td>\n | To show preparation and leadership<\/td>\n | ProjectPlan_Summary.pdf<\/td>\n<\/tr>\n |
| Short video clip<\/td>\n | When process or result is best shown dynamically<\/td>\n | Workshop_Highlight.mp4 (30s)<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n The table above is a quick reference when you\u2019re deciding what to attach. Common sense applies: too many items of the same type add noise; a single, well-chosen piece of proof adds clarity.<\/p>\n Reflections: connect proof to learning outcomes<\/h3>\nPhotos and logs show that you did something. Reflections are the part of your portfolio that show what you learned and why it matters. A reflection should do three things:<\/p>\n
|
<\/p>\n