Writing an activities entry that isn't a job description

Applicants spend months on the personal statement and then write fifteen activity entries in a weekend. It shows. The activities section is often the first thing a reader encounters in detail, it's where your actual experience lives, and most entries waste their limited space describing duties that were obvious from the job title.

The default failure

The typical entry reads like a posting: responsibilities, tools used, hours contributed. It tells a reader what the role involved. It tells them nothing about you, which is the only reason they're reading it.

Compare 'Assisted patients with mobility, recorded vitals, and communicated with nursing staff' against an entry that spends its last two lines on the specific thing you didn't expect to learn, or the patient interaction you still think about. The first is a job description. The second is evidence.

A structure that works

1. One line establishing what the role actually was, if it isn't obvious from the title — scope, setting, and your degree of responsibility.
2. One or two lines of specifics that only someone who did it would know. Numbers, constraints, an unusual detail.
3. The rest on meaning: what changed in how you think, what you got wrong, why you stayed.

That ordering matters because the space is tight and readers are fast. Front-load orientation, then spend your remaining characters on the part no one else could have written.

Choosing what to designate as most meaningful

The instinct is to pick the most impressive activities. The better filter is which ones you can write about with genuine specificity — where you have a real moment, a real mistake, and a real change in your thinking. An extended entry about a modest role you can describe vividly does more for you than a longer treatment of a prestigious one you experienced at a distance.

Practical constraints worth respecting

• Character limits are strict and are enforced by the form, not by your word processor. Write against the real limit from the start rather than cutting a beautiful paragraph in half at the end.
• Hours should be honest and defensible. You may be asked about them, and an inflated figure is a bad thing to have to explain in an interview.
• Descriptions of ongoing activities need a date-forward framing — you'll be reading these back months later, in an interview, and they should still be accurate.
• Entries feed later work. The strongest secondary answers are often expansions of an activities entry, so writing them carefully once pays off repeatedly.

A final pass

Read every entry and ask: could someone else with the same job title have written this exact text? If yes, you've written a job description. The fix is almost never more adjectives — it's one concrete detail and one honest sentence about what it meant.