Writing activities with evidence

A short activity description has a practical job: help a reader understand what the student did. Grand language makes that job harder when it hides the role, the scale or the outcome.

Start with a factual record before compressing anything. This is useful across applications, although each platform has its own fields and limits. Common App's first-year guide explicitly includes work, hobbies, clubs, community engagement and other responsibilities in its discussion of activities. A student should therefore begin by considering how they spend their time, rather than only looking for named awards or formal leadership titles.

Write the full version first

For each activity, record the setting, dates, role, actual tasks and any outcome the student can substantiate. Keep separate fields for the team's work and the student's contribution.

A record might say that a student joined a coding group, wrote a data-import function, tested it against sample files and documented two known errors. This is more informative than beginning with “technology leader”. If leadership was part of the role, explain the responsibility: organising work, making decisions, teaching others or resolving a specific problem.

Keep records privately where appropriate. This exercise does not require publishing evidence, naming other students or making personal material available online.

Choose verbs that describe the work

Words such as “built”, “tested”, “organised”, “analysed” and “maintained” can make a contribution easier to understand when they are accurate. A title alone rarely explains the work behind it.

Here is a hypothetical revision, not an account of a client result:

• Vague: “Innovative founder transforming STEM education.”
• Specific: “Organised weekly problem-solving sessions; prepared exercises and revised explanations after peer feedback.”

The second version names observable actions. It does not claim that the sessions transformed anyone's education, and it does not need an invented result to make the work worthwhile.

Use the wording that fits the student's actual role. Someone who attended sessions should not adopt the organiser's description.

Put numbers in context

Numbers can clarify scale when there is a reliable basis for them. Explain what a number measures. Downloads, registrations, people who tried a tool and people who continued using it are different quantities.

If a student cannot verify a result, remove it or describe the uncertainty accurately. Do not turn a guess into an exact total. For hours and duration, consult calendars or other records and follow the form's instructions for estimates. Check that simultaneous activities do not create an implausible account of the student's week.

A project can be useful to discuss even when the outcome is limited. “Tested with a small peer group and revised the instructions” is a defensible description if that is what happened. It should not become “launched a platform serving a global community”.

Include responsibility without manufacturing prestige

Paid work and family responsibilities can involve sustained effort and real judgement. Describe the tasks without apologising for their lack of a certificate or public title.

For example, a hypothetical student working in a family shop might explain that they maintained stock records and investigated discrepancies. The description should stay within what the student actually handled. It need not become a claim to have managed the entire business.

Avoid sharing sensitive information about family members to make a responsibility sound more significant. Include only the context needed to understand the student's experience.

Edit for the particular application

Once the full record is accurate, select the details that answer the form's question. Do not assume that an activity description can be pasted unchanged into an achievement field or a reflective short response.

Check the current limits in the live form. Use separate fields for dates, roles and hours where the form provides them, so the description can focus on contribution. Expand unfamiliar abbreviations when space allows, and cut adjectives before cutting the facts that make the work understandable.

Read the entry beside the rest of the application. Names, dates, responsibilities and outcomes should agree across essays, records and interview explanations. A concise description is ready when the student can explain every part of it in ordinary language, including the limits of what they accomplished.