What should the application narrative include?

• A. Goals, description of activities, impact metrics, evidence, partnerships, sustainability plan, team structure, and reflections
• B. Robot hardware discounts
• C. List of all events only
• D. Only a glossary of terms

Answer: (A)

A strong application narrative shows the full story: why you started, what you did, what happened as a result, and how the work will endure. Including goals sets out the purpose and what you aimed to achieve. The description of activities details the actual steps you took to reach those goals. Impact metrics translate your results into numbers or clear indicators, so judges can see the extent of change. Evidence strengthens claims with data, testimonials, or artifacts that back up what you report. Partnerships highlight collaboration and how others helped extend reach or resources. The sustainability plan explains how the impact will continue beyond the current effort, showing long-term value. Team structure demonstrates who did what and that you have the capacity to carry projects forward. Reflections reveal what you learned and how you’d improve next time, signaling growth and readiness for future work.

This is why the other options don’t fit the narrative purpose: focusing on robot hardware discounts misses the impact and collaboration pieces; listing only events provides activity without outcomes or partnerships; and a glossary of terms omits the story of actions, results, and learning.