\n| Independence claims (“I did it alone”)<\/td>\n | Likely untrue in formal contexts<\/td>\n | State what you did independently and what support you had<\/td>\n | Mentor notes, citations of resources, timelines showing milestones<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\nPractical steps for writing with accuracy and impact<\/h2>\n1. Begin with a precise role statement<\/h3>\nOpen your project description with one or two sentences that say exactly who you were and what you did. Avoid vague leadership claims; name the tasks you carried out.<\/p>\n \n- Good: “I designed and delivered three community workshops on basic digital literacy, focusing on seniors in my neighbourhood.”<\/li>\n
- Less good: “I ran a community-wide campaign to increase digital access.”<\/li>\n<\/ul>\n
2. Anchor claims in process rather than grand outcomes<\/h3>\nDescribe what you tried, how you tried it, and what you observed. The spotlight should be on your method and learning, because process is where assessors find validity.<\/p>\n \n- Explain the steps you took and why you chose them.<\/li>\n
- Include an honest appraisal of what worked, what didn\u2019t, and what you would change next time.<\/li>\n<\/ul>\n
3. Use measured, evidence-backed language<\/h3>\nPrefer verbs like “piloted,” “facilitated,” “coordinated,” “evaluated,” and “collaborated” to verbs that imply total success. When you describe impact, attach a piece of evidence or explain how you measured it.<\/p>\n \n- Quantify when appropriate: number of participants, hours spent, pre\/post reflections.<\/li>\n
- When you don\u2019t have numbers, describe observable effects: participant feedback themes, changes in behaviour, or a notable quote from a participant.<\/li>\n<\/ul>\n
4. Be explicit about collaboration and support<\/h3>\nIf teachers, community leaders, or peers helped, say so. Explain the specific contribution they made \u2014 mentoring, funding, venue support \u2014 and which parts you led. That clarity strengthens the credibility of your claim instead of weakening it.<\/p>\n 5. Show limitations as part of the learning<\/h3>\nAssessors appreciate mature reflection. When you talk about limits \u2014 small sample size, short timeline, variables you couldn\u2019t control \u2014 pair each limitation with what you learned and what you would test next. That transforms a limitation into evidence of critical thinking.<\/p>\n Concrete phrasing swaps: what to write instead<\/h2>\nHere are side-by-side phrasing swaps to make your writing more accurate and stronger.<\/p>\n \n- Instead of “I solved the problem of X,” try “I tested an approach to reduce X and observed Y in a small pilot.”<\/li>\n
- Instead of “I single-handedly led the initiative,” try “I coordinated the planning team and was responsible for X activities.”<\/li>\n
- Instead of “This project changed attitudes,” try “Participant feedback suggested a positive shift in understanding in the short term.”<\/li>\n<\/ul>\n
How to document evidence for your portfolio<\/h2>\nGood documentation is simple, organized, and directly tied to claims you make in your reflection. Think of evidence as the notes that let a reader verify what you say; it doesn\u2019t have to be perfect, but it must be honest and accessible.<\/p>\n |
<\/p>\n
<\/p>\n