Lead a Volunteer Team for 3 Months

Proof required

Submit: a team roster listing each volunteer's name, their specific assigned role, how they were recruited (where they heard about the team and why they agreed to join), and the team's stated goal and 3-month target outcome.

What gets checked

• At least 3 volunteers are named with distinct roles — a team where everyone does 'general support' has no real role structure and no accountability; each role must be specific enough that if one person stopped contributing, you would know exactly what was no longer being covered
• Recruitment source is described for each person — 'I asked my friend' is sufficient, but 'my manager told them to join' is a disqualifier; voluntary recruitment is the GOVERNANCE baseline
• Team goal is concrete and time-bounded — 'make a positive impact' does not pass; 'deliver 12 community meals by month 3' or 'run 4 public workshops by December' does; the goal must be specific enough to verify at milestone 3

Common mistakes

• Recruiting people who feel socially obligated — friends who agree because they cannot easily say no, classmates who feel peer pressure, or colleagues who misunderstand the ask as a work requirement; the first sign is that volunteers are unresponsive or disengaged after agreeing; pre-empt this by being explicit at recruitment that declining or leaving later is genuinely fine
• Assigning roles without discussing them with the volunteer — roles assigned by the leader without the volunteer's input tend to be misaligned with what the volunteer actually wants to do or is capable of; role assignment should be a short conversation, not a unilateral decision
• Setting a goal so vague that it cannot be measured at 3 months — 'support the community' or 'raise awareness' are not goals for this outcome; the goal must produce a specific artifact or outcome at the end that a third party could verify

Resources

What a verifier looks for

• Check that at least 3 volunteers are named with distinct, specific roles — 'helper' or 'team member' is not a role; ask 'what would not happen if this person stopped contributing?' If the answer is unclear, the role is not specific enough
• Verify the recruitment was voluntary for each person — ask 'how did you recruit each volunteer?' and listen for signs of obligation (employer request, course requirement, social debt); one coerced recruit changes the GOVERNANCE standard for the whole team
• The goal must be concrete enough to evaluate at milestone 3 — if you cannot already picture what 'done' looks like from reading the stated goal, flag it now; a vague goal at milestone 1 becomes a milestone 3 dispute about whether the team succeeded

Proof required

Submit: an outcomes log covering (1) a summary of work completed in weeks 1–6 against the team's stated goal, (2) a retention snapshot showing which original volunteers are still active, who has left and why, and whether any new members have joined, and (3) one specific thing you have changed about how you lead or coordinate the team based on what you have learned.

What gets checked

• Outcomes log names specific work completed — 'we made progress' does not pass; 'we completed the first two workshops and recruited 45 attendees' does; at least one concrete deliverable or milestone toward the team's 3-month goal must be reported
• Retention snapshot is honest — if a volunteer has left or become inactive, it must be stated; a check-in that reports perfect full attendance for 6 weeks on a purely voluntary team is a signal worth probing; some attrition or difficulty is normal and honest
• Leadership reflection names something specific that changed — 'I learned a lot' does not pass; 'I stopped assigning tasks in meetings and started sending a written list the day before, which reduced confusion' does; the reflection must name a concrete behavioural change

Common mistakes

• Waiting until week 6 to check in on volunteers rather than maintaining regular contact — a 6-week check-in log produced from a single week 6 conversation will be thin and miss early problems that had already resolved; the log should reflect 6 weeks of ongoing engagement, not a single retrospective session
• Ignoring volunteer attrition or reframing it as irrelevant — if a volunteer left because the work was unclear, the commitment was underestimated, or the leader was unresponsive, that is important data; rationalising it as 'they were too busy' without examining what could have been different misses the GOVERNANCE learning
• Reporting only what the leader personally did rather than what the team produced — a log that focuses entirely on the leader's activities ('I organised, I coordinated, I ran meetings') rather than the team's collective output misses the point; the proof must show the team produced outcomes, not just that the leader was active

Resources

What a verifier looks for

• The outcomes log must name specific work completed — ask 'what did the team produce in weeks 1–6?' and expect a concrete answer (a deliverable, an event, a product, a service provided); if the only answer is process activities (meetings held, plans made), the team may not have moved toward its goal yet
• Probe the retention honestly — ask 'has anyone on the team become less active or stopped contributing?' and compare the current team state to the milestone 1 roster; volunteer teams always have some friction; a check-in that claims zero issues is worth questioning
• The leadership reflection must name something specific — ask 'what did you do differently after week 3 than you did in week 1?' A genuine answer demonstrates adaptive leadership; an inability to name any specific change suggests the leader operated in a fixed mode for 6 weeks, which is unusual in any real team

Proof required

Submit: (1) final roster with current members and a note on anyone who left or joined since milestone 1, (2) outcomes delivered — stated goal from milestone 1 and what was actually achieved with evidence (photos, links, counts, testimonials), and (3) a 200+ word GOVERNANCE reflection covering one decision the team accepted, one it pushed back on or ignored, and what you would do differently.

What gets checked

• Outcomes delivered are compared to the original goal — a report that describes what the team did without referencing the original milestone 1 goal does not pass; the reader must be able to see both what was planned and what was achieved
• Evidence of outcomes is specific and externally verifiable — links, photos, attendance counts, testimonials, or delivery records; 'the team worked hard and made a difference' is not evidence
• GOVERNANCE reflection addresses all three questions: one decision the team accepted, one it pushed back on or ignored, and one thing the leader would do differently — a reflection that only reports successes has missed the GOVERNANCE learning; every real volunteer team includes at least one moment where the leader's proposal was modified or rejected, and that moment is important

Common mistakes

• Reporting against a revised goal rather than the original one — if the team missed its original target and the report describes a different, smaller achievement as if it were the goal all along, this is post-hoc rationalisation; the report must be transparent about what the original goal was and how the actual outcomes compare, even if the comparison shows underperformance
• A GOVERNANCE reflection that mentions only successful influence — 'I led the team and they did everything I asked' is the hallmark of a reflection written from authority rather than GOVERNANCE; volunteer teams always include moments where the leader's judgment was questioned or overridden by the group; if the reflection cannot name one, it is almost certainly incomplete
• Omitting volunteers who left from the final roster — a final report that only lists current members without noting who left omits important GOVERNANCE data; attrition in a voluntary team is data, not an embarrassment; the report should list who left and offer a brief honest account of why

Resources

What a verifier looks for

• Compare outcomes to the original milestone 1 goal explicitly — the report must state the original goal and what was actually delivered; if the report only describes what happened without referencing the original goal, return it for revision; a goal comparison is required
• Verify the evidence is externally accessible — links must load, photos must show the claimed activity, attendance counts must come from a source other than the leader's own count; ask for one piece of evidence you can independently check
• GOVERNANCE final test: ask 'was there a moment when you proposed something and the team did not do it, or did it differently than you asked?' Every real volunteer team over 3 months has at least one such moment; if the leader cannot recall any, either the team had no real autonomy (it was directed, not led) or the reflection is incomplete; probe further