A title tells us less than what you actually did.

Put the detail to work

Consider a hypothetical school library project. “Led a literacy initiative” sounds substantial, but leaves almost everything unanswered. A clearer account would explain that you organised returned books every Thursday, noticed younger pupils struggled to find suitable stories, and helped the librarian create shelf labels. Your contribution now has a setting, a decision and a visible action.

If you counted something, say exactly what it measures. Forty books relabelled is different from forty pupils improving their reading. Do not turn attendance into educational impact, or a team result into an individual achievement. You can explain that three volunteers worked together while you designed the labels and checked the catalogue.

Yale’s admissions discussion of activities encourages applicants to communicate an activity’s importance and their impact. This does not require a spectacular outcome. Reliability can be the point: perhaps you covered a weekly shift while someone else handled publicity. Explain why that responsibility mattered to the people depending on you.

Try writing the experience as a short sequence: what needed doing, what you personally did, what happened, and what you learned. If the first version of the labels confused pupils, describe the change you made after listening to them. The adjustment can reveal more judgment than an uninterrupted success story.

The same approach works for paid work, caring responsibilities, sport and research assistance. Be accurate about the setting and the time available to you. A part-time job should not become a startup; entering experimental results should not become designing the experiment.

Before reusing the experience, check dates, hours and your role. Give the reader a coherent account across the application. Keep useful evidence privately, without uploading other people’s personal information just to make your own activity appear more impressive.