Introduction
In IB Design Technology, your process is just as important as your final product. Examiners aren’t only looking for polished prototypes — they want to see how you got there. Strong documentation shows your creativity, critical thinking, and ability to apply the IB Design Cycle.
Unfortunately, many students lose marks by underestimating this part of the assessment. Forgetting to capture sketches, skipping reflections, or leaving documentation until the last minute can all cost valuable points. This guide will show you exactly how to document your IB Design Technology process so your hard work is recognized.
Quick Start Checklist for Documentation
- Keep a design journal or logbook from day one.
- Capture photos and sketches of every stage.
- Write short weekly reflections on progress and setbacks.
- Organize your notes into the Design Cycle stages.
- Store everything digitally and back it up regularly.
- Use annotations to explain decisions in context.
- Show how user feedback shaped your design.
- Don’t wait — document continuously, not at the end.
Step 1: Start with a Design Journal
Your design journal is the backbone of your documentation. Whether you keep it digital or physical, it should record everything: ideas, research findings, sketches, and reflections.
Tips for building a strong design journal:
- Consistency over perfection: Write regularly, even if entries are short.
- Date every entry: This helps examiners see your progress over time.
- Mix visuals with text: A page of sketches with annotations often communicates more than a long paragraph.
- Reflect on setbacks: Examiners value critical thinking, not just success.
Step 2: Align with the Design Cycle
The IB Design Cycle includes research, design, development, and evaluation. Organize your documentation under these categories to keep it structured and easy for examiners to follow.
- Research: Include problem analysis, surveys, interviews, and secondary sources.
- Design: Add sketches, CAD models, and initial concepts.
- Development: Document prototypes, materials used, and testing methods.
- Evaluation: Show results of testing, user feedback, and reflections on improvements.
By mapping your work to the cycle, you prove that your project meets IB criteria systematically.
Step 3: Capture Visual Evidence
Photos and sketches are essential. They not only make your documentation more engaging but also prove your originality.
Best practices for visuals:
- Photograph prototypes from multiple angles.
- Scan or photograph hand sketches instead of redrawing them digitally.
- Annotate images with labels and arrows to highlight key features.
- Use before-and-after photos to show changes during development.
Remember: if you don’t record it, examiners can’t give you credit for it.
Step 4: Write Reflections Along the Way
Reflection is at the heart of IB assessments. Instead of waiting until the end, reflect after each stage. Ask yourself:
- What worked well in this stage?
- What didn’t go as planned?
- How did user feedback change my design?
- What will I do differently in the next stage?
Even short reflections of three to four sentences can make a big difference when accumulated over time.
Step 5: Include User Feedback
Strong projects demonstrate user-centered design. To document this effectively:
- Record surveys, interviews, or focus group notes.
- Include photos of users testing prototypes.
- Annotate feedback quotes directly onto sketches or prototypes.
- Show how you adapted your design in response.
This demonstrates that your project wasn’t created in isolation but evolved through real-world input.
Step 6: Keep Your Work Organized
Messy documentation is hard to follow and may cost marks. Keep things neat and logically structured.
- Use folders named by Design Cycle stage.
- Add page numbers to digital journals.
- Highlight key findings in bold or color-coded notes.
- Create a table of contents if your documentation is long.
Examiners should be able to easily trace your project journey without confusion.
Step 7: Back Up Everything
Many students have lost marks due to lost files or corrupted documents. Avoid this by:
- Using cloud storage like Google Drive or OneDrive.
- Keeping a second copy on a USB or external drive.
- Saving scanned copies of physical sketches.
It’s a small step that can save weeks of effort.
Tips for Strong Documentation
- Start early and stay consistent.
- Think like a storyteller. Your documentation should narrate the journey, not just present outcomes.
- Don’t over-edit. Examiners want authenticity, not a perfect portfolio.
- Integrate feedback. Show how each round of testing informed your next step.
- Link evidence to criteria. Regularly check if your documentation addresses IB assessment points.
Frequently Asked Questions
Q1: Do I need to document every single detail of my IB DT project?
Not every small detail, but you should capture anything that shows evidence of thought, testing, or progress. For example, you don’t need to record every screw you used, but you should note why you chose one material over another.
Q2: Should my documentation be handwritten or digital?
Either works, but digital is easier to organize and submit. Hand sketches and notes can always be scanned. Many students use a mix — handwritten sketches combined with digital reflections and photos.
Q3: How long should my documentation be?
There’s no set length, but quality matters more than quantity. A well-structured 25–30 page document with strong evidence is better than 70 pages of filler. Focus on clarity, not volume.
Q4: What happens if I forget to document something important?
If you realize late, you can still add it, but don’t fabricate evidence. Be honest and reflect on what you would have done differently. Examiners value authenticity and reflection over perfection.
Q5: How do examiners actually use documentation in assessment?
Examiners check documentation to ensure you’ve followed the Design Cycle, applied critical thinking, and adapted to challenges. It’s your proof of effort and learning. Without it, your final product alone won’t earn top marks.
Conclusion
In IB Design Technology, documentation isn’t just extra work — it’s your ticket to higher marks. By keeping a consistent journal, aligning with the Design Cycle, capturing visual evidence, and reflecting regularly, you’ll create a portfolio that demonstrates both your creativity and discipline.
Remember, the best projects don’t just show what you built — they tell the story of how you got there.
Call to Action
Want to ensure your IB Design Technology documentation is complete and ready for examiners? Use RevisionDojo’s expert strategies to stay on track and make your process as strong as your final product.
