Collecting and Documenting Evidence

Purpose Collecting and documenting multiple sources of evidence is essential to make valid assessment claims about learner achievement in project‑based learning (PBL). Well‑organised evidence demonstrates attainment against CAPS assessment standards, supports School‑Based Assessment (SBA) records and moderation, and enables teachers to reflect and iterate on project design.

What to gather — evidence types and purposes

• Artefacts (final products and process work)
  • Purpose: show what learners produced and how ideas developed.
  • Examples: models, posters, reports, prototypes, kits, design sketches, lab books, drafts.
• Portfolios
  • Purpose: longitudinal view of learner progress and growth across phases of the project.
  • Examples: curated collection of artefacts, drafts, reflections, feedback and assessment records.
• Observation notes and anecdotal records
  • Purpose: capture teacher judgements about collaboration, inquiry skills, approach to task and soft skills.
  • Examples: structured observation checklists, short descriptive notes, time/date/ context.
• Recordings (audio, video, photographs)
  • Purpose: document oral presentations, group interactions, fieldwork, practical demonstrations and outdoor learning.
  • Examples: video of group presentations, photos of fieldwork, audio of interviews with community partners.
• Assessment instruments and outcomes
  • Purpose: show measured achievement against criteria.
  • Examples: completed rubrics, checklists, tests, quizzes, marked assignments (formative and summative).
• Learner reflection and self/peer assessment
  • Purpose: evidence of metacognition, ownership and ability to judge learning.
  • Examples: learner journals, self‑assessment sheets, peer feedback forms.
• External/community evidence
  • Purpose: triangulate authenticity and real‑world impact.
  • Examples: letters from community partners, media clippings, photographs from community events.
• Process logs and time‑stamped drafts
  • Purpose: show progression, problem‑solving and iteration.
  • Examples: research notes, meeting minutes, version history of digital files.

How to collect — practical methods

• Plan evidence collection at design stage
  • Specify which evidence items you will collect, when and by whom. Build collection into the assessment plan and rubric.
• Use structured tools during the project
  • Observation checklist aligned to success criteria.
  • Short weekly progress logs completed by learners.
  • Photo/video capture of key performance moments.
• Capture drafts and iteration
  • Require learners to keep dated drafts or use version history (Google Docs, OneDrive).
• Integrate reflection moments
  • Schedule short reflective prompts at milestones (What worked? What did I learn? Next steps).
• Combine formative and summative evidence
  • Keep formative feedback records (marking comments, developmental conferences) alongside the final summative assessment.
• Use sample‑based moderation collection
  • For moderation, collect full portfolios for a sample of learners plus anonymised rubrics and observation notes.

Documenting evidence — metadata and annotation Every evidence item should be annotated so it is interpretable and auditable. Include the following metadata fields where possible:

• Learner name and Grade / class
• Project title and brief description
• Date and time
• Evidence type (artefact, photo, observation, reflection, rubric)
• CAPS learning outcome / assessment standard referenced
• Task / milestone linked to the evidence
• Teacher’s comment / justification for its assessment value
• Authenticity statement (who contributed what)
• Mark/level awarded (if applicable)
• File name and storage location

Sample file naming convention YYYYMMDD_Grade_ProjectShortTitle_LearnerSurname_Type (e.g., 20260510_Gr8_WaterFilter_Moloi_Photo1.jpg)

Linking evidence to CAPS and assessment criteria

• Map each evidence item to specific CAPS outcomes and assessment standards. Maintain a simple matrix: Evidence item → CAPS standard → Rubric descriptor.
• Use rubrics with clear descriptors (Beginning/Developing/Proficient/Exemplary) and record the descriptor achieved for each evidence item.
• Ensure summative assessment folders include the formal task sheet, rubric used, learner work and teacher moderation notes.

Ensuring authenticity and academic integrity

• Require drafts, research notes and process logs to substantiate individual or group authorship.
• For group projects, document individual contributions (self/peer assessment forms, observation notes).
• Note any accommodations or modifications provided for learners with special needs and how these affected assessment.

Ethics, consent and data protection (POPIA)

• Obtain written consent from learners and parents/guardians for photographs, audio and video recordings. Keep consent forms filed with the evidence.
• Limit personal data access to authorised staff. Store sensitive files on secure, school‑managed platforms; password protect or encrypt where possible.
• Adhere to the school’s retention policy and POPIA guidelines when sharing evidence externally for moderation or publication.
• When publishing learner work externally, anonymise learners unless explicit consent has been obtained.

Organisation and storage

• Create a consistent folder structure (by term → project → class → learner or by learner → project).
• Use both physical and digital storage: keep originals of critical artefacts and scanned copies for moderation.
• Back up digital evidence regularly to the school’s approved cloud service or network drive.
• Maintain a central index (spreadsheet or LMS gradebook) that links to each learner’s evidence files and records rubric scores.

Moderation and sampling

• For internal moderation: select a representative sample of learner work across performance levels and include observation notes and recorded assessments.
• For external moderation: follow provincial/district requirements; prepare anonymised evidence packages if required.
• Record moderator decisions, adjustments to marks and rationale in the evidence folder.

Using evidence for reporting and iteration

• Use the annotated evidence and mapped CAPS links to complete SBA records and term reports.
• Analyse evidence patterns to identify curriculum, assessment or classroom management adjustments for future projects.
• Document lessons learned and recommended changes to the project brief, scaffolding or assessment criteria.

Templates and quick examples (use/adapt in your LMS)

1. Evidence Item Log (columns)

   • Date | Learner | Project | Evidence Type | CAPS Standard | Brief description | Link/Location | Teacher comment | Mark/Descriptor | Authorship note

2. Observation note (short)

   • Date/time | Group/learner | Activity observed | Behaviour/skill noted | Evidence of CAPS outcome | Next steps recommended

3. Learner reflection prompt (short)

   • What did I try? What was successful? What problem did I face? What will I do differently next time?

4. Rubric excerpt (example for collaboration)

   • Beginning: Rarely contributes; needs frequent prompts.
   • Developing: Contributes; sometimes listens to others and acts on feedback.
   • Proficient: Regular contributor; collaborates and helps resolve issues.
   • Exemplary: Leads inclusively; negotiates roles; elevates group outcomes.

Quality checklist for each evidence folder

• Evidence items correspond to planned assessment map
• Each item annotated with metadata (date, CAPS reference, teacher comment)
• Drafts/process work included to demonstrate authenticity
• Learner reflections and peer/self‑assessments included
• Consent forms for multimedia present
• Digital files named consistently and backed up
• Moderation notes and adjustments recorded
• Evidence sufficient to justify summative judgment and report grades

Concluding guidance Plan evidence collection as part of the project design. Prioritise a mix of artefacts, process work, observations and learner reflections so claims about learning are triangulated. Keep records transparent, clearly linked to CAPS outcomes, and ethically managed to support assessment, reporting and continuous improvement.