IB DP Social Impact: How to Build a Social Initiative Website and Proof Archive

Why a website and proof archive matters for your IB DP social initiative

When you set out to create a social initiative as part of your IB Diploma Programme, you’re doing more than running a project—you’re creating a story of impact. That story lives in the planning, the community relationships, the outcomes, and the careful reflection you record along the way. A simple website paired with a well-organized proof archive not only showcases that story to assessors and partners, it protects your evidence, clarifies your learning, and helps you reflect more honestly.

This guide walks you through practical choices—what pages to build, how to name and store files, what kinds of evidence count, and how to keep things ethical and accessible. Think of it as a student-centered manual that helps your CAS portfolio and overall IB student portfolio feel intentional and authentic instead of chore-like.

Start with purpose: define the learning and social outcomes

Before you open a website builder or create a folder, clarify why this initiative exists. Ask: What problem are we responding to? Which part of the community benefits? How will this connect to CAS learning outcomes and your personal goals? When your purpose is clear, every piece of evidence you collect will have context and meaning.

Write a one-paragraph mission statement that you can reuse in your website’s About section and in reflective pieces. Make sure it ties to:

• Community need and stakeholder voices
• Specific CAS outcomes and how your activities align to them
• Measurable indicators of success—numbers, stories, or both

Example mission paragraph

“We collaborate with local primary schools to run weekly literacy workshops that increase reading confidence among students while creating peer-led learning opportunities for volunteers.” Use that sentence as the kernel of all your documentation: it tells assessors what you set out to do, and anchors reflections to that goal.

Plan your website structure: clarity beats flash

Your website doesn’t need flashy animations or custom code. It needs clear navigation and durable pages that can be archived or exported. Aim for a lightweight structure that highlights intent, evidence, and reflection.

• Home: One-line mission + recent impact snapshot.
• About: Project background, partners, and roles.
• Activities: A timeline or calendar of events with short summaries.
• Evidence archive: The organized proof files, described below.
• Reflections: Student reflections linked to specific activities.
• Contact / Acknowledgements: Consent statements and partner recognition.

Keep each page focused. For assessors, a single link to an evidence folder that’s well-labelled is far more valuable than a page full of vague photos.

Design principles that serve IB assessment

• Simplicity: Use readable fonts, clear headings, and consistent formatting.
• Durability: Exportable content (PDFs, zipped folders) beats ephemeral widgets.
• Transparency: Note who created each piece of evidence and when.
• Accessibility: Add alt text and transcripts for videos and audio.

What to include in your Evidence Archive

A proof archive is a structured collection of files that supports the claims you make in reflections and in CAS documentation. Think in categories: planning, activity evidence, outcomes, and reflection. Each item should answer at least one of these: what happened, who participated, when it happened, and what you learned.

• Planning documents: Project proposals, risk assessments, and meeting notes.
• Activity evidence: Photos with captions, short videos, attendance sheets, workshop materials.
• Outcome data: Pre/post surveys, attendance stats, community testimonials.
• Reflections and verification: Reflective logs, supervisor notes, and third-party verification.

File naming, metadata, and one tidy table that saves hours

Consistent file names and metadata make your archive searchable and inspector-friendly. Below is a compact convention you can adapt. Store a README inside your archive that documents the naming convention so any assessor or teacher understands your system.

Note: adapt the date format and detail level to match your team’s needs, but be consistent. If you choose to include times, use 24-hour format. If you include initials, document that in the README to respect privacy.

Quality of evidence: depth beats breadth

A pile of unlabeled photos doesn’t persuade. A few well-captioned photos, a short video with a transcript, an attendance list that shows involvement, and a supervisor note tied to a reflection are much more effective. Aim to pair every major claim in your reflection with at least one piece of verifiable evidence.

Examples of strong pairings:

• Claim: “Attendance grew from 8 to 22.” Evidence: attendance sheet CSV file + a short chart made from those numbers.
• Claim: “Volunteers led peer-reading sessions.” Evidence: a 60-second clip of a peer leading a session + reflection describing facilitation skills learned.
• Claim: “We reduced waste in the community event.” Evidence: before/after photos, vendor notes, and a short audit spreadsheet.

Reflective practice: structure your reflections to show learning

Reflection is where purpose and evidence meet assessment criteria. If reflections are generic, assessors will struggle to see your growth. Use a consistent reflection template so your archive is readable and each entry reliably links to evidence.

Suggested reflection template

• Activity title and date
• What I did (concrete actions)
• What I observed (evidence referenced by filename)
• What I learned (skills, values, perspectives)
• How this connects to CAS outcomes and next steps

Keep reflections specific. Instead of “I learned leadership,” write “I learned to delegate tasks during setup by assigning three roles and checking in at 10-minute intervals—this improved start-time punctuality by 30 minutes across two events (see Attendance_Log_2023-11.csv).” That level of detail links evidence to learning and demonstrates evaluative thinking.

If you want extra coaching on structuring reflections or practicing interviews, consider 1-on-1 guidance from Sparkl or similar trusted mentoring that helps tailor study plans and sharpen presentation skills. For example, Sparkl‘s tutors can help you practice linking evidence to learning in a concise way.

Privacy, consent, and safeguarding—non-negotiable

When your initiatives involve people, especially minors, ethical considerations must guide how you collect and share evidence. Obtain written consent from participants or guardians before you publish photos, videos, or personal stories. Where possible, anonymize sensitive information and store consent forms in a secure, access-controlled folder.

• Keep a consent log with: name (or anonymized ID), contact, consent date, scope of consent (photos, quotes, video), and expiration if applicable.
• Offer opt-out options and be clear about how the material will be used.
• When in doubt, blur faces or use recipient-verified screenshots for private verification instead of public publishing.

Technical choices that make archiving painless

Pick tools you and your teammates can maintain. A simple static site or a small content directory exported as PDFs is more durable than a complex platform that requires constant updates. For file storage, use a combination: a cloud folder for raw files and an exported zipped archive for final handover.

Key practices:

• Back up raw files in two places (cloud + an external hard drive or a second cloud provider).
• Export text reflections as PDFs to preserve formatting and time-stamp metadata.
• Transcribe short videos or add captions so assessors can access the content without audio.
• Keep a README that explains folder structure, naming conventions, and verification contacts.

Storage and export checklist

• Active working folder with originals (images, raw video, spreadsheets)
• Processed folder with compressed files suitable for upload
• Archive folder with final PDFs and a zip file for submission
• README + consent log + supervisor contact list

How to present evidence to different audiences

Different viewers need different formats. A teacher assessing CAS might prefer a zipped archive with a README and clear file names. A community partner might appreciate a short web page summarizing outcomes. A university admissions tutor skimming your portfolio will look for concision and reflective depth.

Try these presentation formats:

• Assessors: One zipped archive titled with your name and project title, plus a single-page summary that links each reflection to file names.
• Community partners: A one-page public report (PDF) with images and key numbers.
• Personal portfolio: A curated website page with two case studies—one in-depth and one short highlight.

Assessment-ready tips: make evidence easy to verify

Assessors don’t enjoy guessing. Make verification easy by:

• Linking each reflection to at least one file name in the archive.
• Including supervisor contact details in the archive README.
• Adding short captions to photos that name date, place, and activity, and list the filename.

For interviews or group assessments, rehearse talking about one case study in three minutes: context, action, outcome, and learning. Practice pairing a sentence about learning with the filename of supporting evidence so you can answer questions confidently.

Common pitfalls and how to avoid them

• Pitfall: Unlabeled photos. Fix: Caption immediately with date, names/roles, and brief context.
• Pitfall: Missing consent records. Fix: Keep a digital consent log and a PDF copy of forms in the archive.
• Pitfall: Overly long videos. Fix: Edit to 60–120 seconds and provide a transcript.
• Pitfall: Scattered evidence. Fix: Use the naming convention and a README so everything can be found in two clicks.

Final checklist: what to hand in

• One-line mission statement on the Home/About page.
• Evidence archive zipped and labeled with your name and project title.
• README explaining file naming, folder structure, and verification contacts.
• Consent log and supervisor verification PDFs.
• At least three reflections that follow the template and directly reference archive files.
• Accessibility notes: alt text and transcripts included where relevant.

Wrapping up: making your digital story durable and honest

Building a social initiative website and a proof archive is as much about your learning as it is about the community impact you record. Stay disciplined with naming and metadata, prize clarity over ornament, and make ethical choices around consent and privacy. With a clear mission statement, a compact website, and a neatly organized archive, you’ll communicate both the work you did and the thinking behind it—exactly what IB assessors and future reviewers need to see.

This completes the guidance on constructing a social initiative website and proof archive for the IB DP context.