How to Stop PDs From Misreading Your ERAS 'Other' Entries

"Other" is where good applicants accidentally make themselves look sloppy, inflated, or worse, untrustworthy.

I've seen this happen. A strong applicant has real work, real effort, real substance. Then they dump it into ERAS "Other" with mushy wording like participated in research projects or involved in leadership initiatives. That's how you get misread. Program directors are moving fast. They are not stopping to decode your meaning, rescue your phrasing, or give you the benefit of the doubt when the wording is vague.

This is the fix. Write "Other" entries so they are clear on first read, consistent with the rest of your application, and sturdy under scrutiny. No guessing. No accidental overclaiming. No lazy ambiguity that makes a real experience look fake.

This article is for educational purposes only. It is not financial advice, not legal advice, and not tax advice. Figures vary by individual circumstances, so consult a qualified professional before acting.

Why PDs Misread "Other" Entries (And What Triggers It)

Let's be blunt: "Other" already starts at a disadvantage. It sounds miscellaneous. Secondary. A holding bin. If your wording is even slightly fuzzy, the reader's suspicion goes up.

The biggest triggers are predictable:

• Ambiguous category

  • Is this research?
  • Teaching?
  • Service?
  • Shadowing?
  • A personal project?

  If I can't tell what bucket it belongs in, I immediately wonder whether you didn't know either.

• Missing timeline

  • No month/year
  • No duration
  • No sense of whether this happened for two afternoons or two years

  That's a problem. A lot of things sound impressive until the timeline shrinks.

• Unclear scope

  • What did you do?
  • What did the team do?
  • What did the institution do around you while you stood nearby?

  This is one of the most common mistakes. Applicants borrow the organization's accomplishments and make them sound like personal accomplishments. Bad move.

• Mismatch with the rest of the application

  • Your CV says "data analyst"
  • ERAS "Other" says "researcher"
  • Your letter writer calls you a volunteer
  • Your dates don't match your transcript timeline

  That's exactly how trust gets damaged.

Here's what raises red flags fast:

• Buzzwords without proof: leadership, innovation, consulting, advocacy, research
• "Consulting" that was really informal advice
• "Research" with no poster, abstract, manuscript, protocol, data product, or defined task
• Unpaid roles described like formal appointments
• Descriptions that can't be verified by a mentor, output, or timeline
• Scope inflation: saying developed program when you helped deliver one session

Program directors aren't hunting you personally. They're filtering risk. Vague entries signal one of three things:

1. weak substance,
2. poor judgment,
3. exaggeration.

None of those help you.

The "Other" Entry Quality Checklist (Write Like You're Being Cross-Referenced)

Assume every "Other" entry will be cross-checked against your activities section, CV, transcript timing, MSPE, and interview answers. Because it might be.

Use this checklist every single time:

1) Start with the basic facts: who, what, where, when

If those four aren't clear, the entry is not ready.

Include:

• Role title
• Organization or setting
• Dates
• Frequency or duration, if relevant

Bad:

• Worked on community health project

Better:

• Student volunteer, refugee health screening initiative, City Free Clinic, Aug 2023-Jan 2024

Already safer. Already easier to trust.

2) State your exact role

This is where applicants get themselves in trouble.

Don't write:

• Supported research efforts
• Assisted with leadership activities
• Participated in curriculum work

That language hides the actual task. Name the task.

Better:

• Extracted chart data for retrospective hypertension study under faculty supervision
• Coordinated 12 student volunteers for monthly blood pressure screening events
• Drafted two case-based teaching modules for intern orientation

Specificity protects you.

3) Define scope

Scope means how much, how often, and at what level.

Add details like:

• Number of sessions
• Number of participants
• Hours committed
• Size of team
• Number of modules, charts, cases, presentations, or events

Not because numbers are magic. Because numbers stop readers from inventing their own interpretation.

4) Lead with deliverables

If there was an output, say it.

Examples:

• Poster presented
• Dataset cleaned
• Protocol drafted
• Educational module delivered
• Resource guide created
• Workshop taught
• Volunteer schedule managed
• QI dashboard updated

Deliverables are the antidote to vague self-promotion.

5) Show how it fits your application story

Not with cheesy branding. Just with coherence.

If you're applying into pediatrics and your "Other" entry is adolescent health education, that should read as part of a pattern. If your app theme is community care, health equity, teaching, or research methods, your wording should reinforce that honestly.

6) Use the same terminology everywhere

This mistake is so common it's painful.

If it's quality improvement, don't call it research somewhere else. If it's data cleaning, don't upgrade it to study design in another section. If you were a volunteer coordinator, don't become a program director in your interview.

Pick accurate language. Keep it stable.

Common "Other" Misread Patterns (And How to Rewrite Them Safely)

These are the repeat offenders. I've seen versions of each one tank clarity for otherwise solid applicants.

1) Vague descriptions

Bad:

• Worked on projects related to health education.

What PD hears:

• I have no idea what this person actually did.

Safer rewrite:

• Developed and delivered 3 blood pressure education sessions for Spanish-speaking adult patients at a community clinic, Sept-Nov 2023.

Now the role is visible. The task is visible. The scale is visible.

2) Inflated labels

Bad:

• Conducted research in oncology.

That can mean anything from entering spreadsheet values to running a funded trial. Don't play games with scale.

Safer rewrite:

• Performed chart abstraction and preliminary data cleaning for a retrospective breast oncology outcomes study under Dr. Patel; contributed to poster submitted to regional meeting.

That's honest. Specific. Defensible.

3) Role confusion: you vs the organization

Bad:

• Created a mentorship program for premedical students.

Did you really create it from scratch? Or did you help one existing branch run?

Safer rewrite:

• Served on a 4-student planning team for an existing premedical mentorship program; matched 18 mentees with mentors and led 2 advising sessions.

That's much better. Humble, but not weak.

4) Missing context

Bad:

• Volunteer at clinic.

That tells me almost nothing.

Safer rewrite:

• Volunteer interpreter assistant at Saturday free clinic, Jan-May 2024; supported intake for approximately 15 Spanish-speaking patients per session and helped staff connect patients to follow-up resources.

The context explains why it mattered.

5) Inconsistent dates or duration

Bad:

• Research assistant, 2022-2024 But your transcript shows you were abroad half that time and your other entry says the project ended in 2023.

That kind of mismatch creates avoidable suspicion. Even if innocent.

Safer rewrite:

• Research assistant, Sept 2022-May 2023 and Jan-Apr 2024; paused during international rotation.

See the difference? You're not weaker because you told the truth. You're stronger because the timeline now makes sense.

Use this protective sentence template when you're stuck:

• I performed X under Y mentor; deliverable was Z; impact was A.
• Served as X at Y site from A to B; responsibilities included C and D; output included E.
• Contributed to X as part of a Y-person team; my role focused on Z; result was A.

And one warning: don't overcorrect into false modesty. Saying just helped with or only assisted can make real work disappear. Be accurate, not apologetic.

Build "Deliverables-First" Descriptions (So PDs Don't Have to Guess)

Here's the cleanest rule in this whole article: if the reader can see the output, the reader doesn't have to guess the value.

Strong deliverables include:

• Publications
• Abstracts or posters
• Presentations
• Datasets created or cleaned
• Protocols drafted
• Screening tools validated
• Curricula built
• Workshops taught
• Leadership systems implemented
• Policy documents or resource guides
• Measurable process changes

This works because deliverables are harder to inflate. They anchor the entry in reality.

If there's no formal product, don't panic. But don't hide behind vague prestige words either. Use quantifiable outputs:

• Hours completed
• Patients served
• Sessions led
• Modules created
• Volunteers coordinated
• Participants trained
• Events organized
• Cases reviewed

And if the experience truly had no formal deliverable, write the part you can defend under interview pressure:

• the skill you practiced,
• the scope of your involvement,
• the measurable activity you completed.

For example:

Bad:

• Learned about healthcare disparities through community engagement.

Better:

• Completed 40 hours with mobile outreach team serving unsheltered adults; performed intake support, tracked referral completion, and helped distribute follow-up appointment instructions.

That's grounded. It sounds real because it is real.

Verification, Tone, and Consistency: The Mistake Avoider Rules

This is where applicants sabotage themselves with style.

Rule 1: Don't sound defensive

If an entry reads like you're arguing for its importance, you've already lost ground.

Bad tone:

• This important and highly meaningful experience significantly impacted many patients.

That's fluff. Worse, it sounds like compensation for weak specifics.

Better tone:

• Coordinated monthly medication access workshops for uninsured patients; created bilingual handouts used at 4 sessions.

Facts first. Always.

Rule 2: Don't make claims you can't survive in an interview

Every line should remain true when someone asks:

• What exactly did you do?
• How often?
• Who supervised you?
• What came out of it?

If your wording would force you to backpedal live, fix it now.

Rule 3: Don't let "Other" contradict the rest of ERAS

Check these conflict zones carefully:

• activity descriptions
• gap explanations
• degree timeline
• research section
• letters of recommendation

If your letter writer says you assisted with data collection, but your "Other" entry implies independent study leadership, that's a credibility wound. Small maybe. But unnecessary.

Rule 4: Cut every buzzword that can't stand alone

Delete or replace:

• passionate
• impactful
• leadership-focused
• innovative
• involved in
• exposed to
• participated in

Those words are not evidence. They're decoration. Program directors don't score decoration.

A Practical Rewrite Playbook: Before/After Examples You Can Copy

Use this four-step rewrite process.

Step 1: Identify the real category

Before writing, decide what the experience actually was:

• Research
• Teaching
• Leadership
• Service
• Clinical exposure
• Personal milestone or structured learning

A bad entry often starts with category confusion.

Step 2: Add specifics

Include:

• role
• setting
• dates
• duties

Step 3: Add outcomes

Include:

• deliverable
• measurable output
• result

Step 4: Tighten to ERAS field limits

Trim adjectives. Keep nouns and verbs doing the work.

Here are examples.

Leadership/service

Before:

• Helped run student service initiative.

After:

• Volunteer coordinator, student-run food insecurity initiative, Jul 2023-Mar 2024; scheduled 14 volunteers for monthly distribution events and built a referral sheet used by clinic staff.

Research-adjacent work

Before:

• Worked in neurology research.

After:

• Research assistant, neurology outcomes project, Oct 2022-Jun 2023; performed REDCap data entry and chart review under faculty supervision for a retrospective stroke study; contributed data for departmental poster presentation.

Clinical exposure/volunteering

Before:

• Volunteered in free clinic.

After:

• Intake volunteer, Eastside Free Clinic, Jan-Apr 2024; obtained intake information for approximately 10-15 patients per session and assisted with follow-up scheduling and interpreter coordination.

Personal/learning experience

Before:

• Independent study in medical Spanish.

After:

• Completed structured independent medical Spanish study, Aug-Dec 2023; practiced weekly patient-interview scripts with faculty feedback and developed a 20-phrase clinical reference sheet used during volunteer clinic sessions.

Notice the pattern. Every stronger version answers:

• What was it?
• What did you do?
• When did you do it?
• What came out of it?

Here's a compact formula you can borrow:

Role + setting + dates; responsibilities included X and Y; output/result was Z.

Example:

• Peer educator, diabetes prevention outreach program, Sept 2023-Feb 2024; led small-group counseling sessions and tracked attendance; delivered 6 workshops reaching 80 community participants.

That's clean. That's trustworthy. That's easy to read at speed.

Summary, Make "Other" Easy to Understand, Hard to Misread

PDs are busy. That's not unfair. It's reality. So don't make them decode your "Other" section, and definitely don't make them wonder whether you're stretching the truth.

Your protection is simple:

• be specific,
• include dates,
• name your actual role,
• lead with deliverables or quantifiable outputs,
• keep terminology consistent across the whole application,
• remove anything that forces the reader to guess.

Don't use "Other" as a dumping ground. That's the mistake. Use it as a precision section for experiences that still deserve clear, verifiable representation. If a stranger can understand it in one read and you can defend every word in an interview, you're doing it right.