Advanced Technique: Building a Quantified Impact System

Elite submissions don't just cite numbers — they reveal a system that produces numbers year over year. Study 5985's metric vocabulary and you'll see the categories every advanced team should be measuring.

1. Outcome rates, not just counts. Anyone can say '70 students.' 5985 says: '100% plan tertiary education and 95% seek STEM careers,' '67% of alumni return as 5985 mentors,' and '100% of alumni enter tertiary education or STEM careers (vs 48% of city).' Rates with a comparison baseline (vs the local 48%) prove causation-flavored impact. Build it: run an annual alumni survey; track graduation, tertiary, STEM-career, and return-as-mentor rates; find a public local baseline to compare against.

2. Growth percentages over time. 'Growing global participation by 593% to 563 youth'; 'Weekly STEM classes growing attendance 27%.' A growth rate proves momentum, which judges weight heavily within the 3-year emphasis. Build it: store the same metric each year so you can compute year-over-year deltas. The TBA-API mini-project automates part of this for mentored-team counts.

3. Equity and reach breakdowns. '57% overall membership' female, '73% with disabilities,' '27% low-income families,' '32% female engagement' in classes. Demographic breakdowns directly answer the equity, diversity, and inclusion summary with data instead of platitudes. Build it: collect (optional, privacy-respecting) demographic data on sign-in forms and report percentages.

4. Dollars mobilized. '$675k+ in grants and material,' '$125k government grant,' '$512k STEM project.' Money raised for others and for sustainability is concrete, verifiable impact. Build it: log every grant and in-kind donation with amount and recipient.

5. Longitudinal anchors. 'A PB class has run every school day since 2015'; 'Since 2015, PB has mentored 212 FLLC teams (starting 108) globally.' Long-run cumulative figures, paired with recent activity, prove sustained commitment without violating the recency emphasis.

The measurement plan — make it explicit. One executive summary literally asks 'How does your team measure impact?' Advanced teams answer with their actual instrument: 'We survey alumni annually; we run pre/post exit slips at every demo; we track mentored-team activity via The Blue Alliance.' Naming your method is itself a credibility signal — it says you treat impact like engineers treat data.

Avoid the vanity-metric trap. Raw 'Instagram followers' or 'impressions' are weak; the official Definitions even spell out that Reach means people who engaged, e.g. 'Social Media post to 1,000 followers, with 500 who engaged with it... has reached 500 people.' Prefer metrics tied to inspiring young people into STEM: students reached, teams started, retention, demographic reach, outcomes. If a metric wouldn't impress a grant committee, it probably won't impress Impact judges.

Deliverable for your team: define 6-8 core metrics across these five categories, decide your collection instrument for each, and assign an owner. Then you can produce, every January, a defensible dashboard that turns a year of work into the language of impact.