When You Get a New Achievement After ERAS: When to Update Programs

Scenario: You Get the News After Submission

You submitted ERAS in September. October rolls around, and you find out your research poster won a competitive award at a national conference. Two days later, a manuscript you co-authored gets accepted for publication in a solid journal. Then your clerkship director taps you for a new student leadership role overseeing peer mentoring.

Now you're staring at your inbox, wondering: should I email programs about this? If yes, when? How much is too much?

This is one of the most common post-submission dilemmas, and applicants routinely get it wrong, either by over-emailing every program with minor updates or by sitting on meaningful achievements until they're stale.

Timing matters because programs review applications in waves. Some filter quickly in September and October. Others revisit files in November when interview slots open up. By December, many programs have locked in their interview pools. Your goal is to communicate meaningful changes while programs are still actively making decisions, not to flood coordinators with noise.

Here's the decision framework I use: significance of the achievement, where you are in the interview cycle, and whether the update changes your application narrative. If the news moves the needle on one or more of those, send it. If not, hold it for interview conversations.

At This Point You Should Decide Whether the Update Is Worth Sending

Not every achievement deserves an email. I've seen applicants send updates for "completed a sub-I", which was already on their ERAS, and then wonder why they got no response. Programs aren't impressed by restating what they already know.

First, classify the achievement:

• Major new publication, first-author or significant role, peer-reviewed, accepted or in print
• Award or honor, national or regional recognition, competitive selection
• Board score change, this is rare but high-impact if Step 2 CK posts after ERAS
• Leadership role, new, substantive responsibility with measurable scope
• Conference presentation, especially at a national specialty society meeting
• Meaningful clinical or volunteer responsibility, new longitudinal role, not a one-off shift

Set a hard threshold: send only updates that are material, recent, and relevant to the specialty or your candidacy. "Material" means it changes how someone reads your file. "Recent" means it happened after ERAS submission. "Relevant" means it ties to the program's mission or your stated interests.

If the achievement is strong but not differentiating, say, another poster acceptance in a long line of posters, it's better saved for interviews or a letter of intent context rather than an immediate update. You don't want to dilute the signal.

Week-by-Week Timing: When to Update Programs

The practical rule: update as soon as the achievement is verified and you can describe it accurately. Don't wait months. A stale update looks like you forgot, or worse, like you're scrambling to stay relevant.

That said, timing shifts depending on where you are in the cycle.

Early interview season (October-November): Programs are actively reading files and sending interview invites. At this point you should send updates promptly, within a week of verification. This is the highest-yield window. Programs are still forming impressions, and a new publication or award can push you from "maybe" to "interview."

Mid-season (November-December): Interview pools are solidifying but not locked. Send updates for major achievements only, a first-author publication, a board score, a national award. Mid-tier updates (regional poster, new volunteer role) are less likely to move the needle here. Keep messages tight.

Late season (January-February): Most programs have finished interviewing or are wrapping up. At this point you should be extremely selective. Reserve updates for genuinely significant news that could affect rank order, a major award, a leadership appointment with clear scope. Don't send routine updates. They annoy coordinators.

Post-interview / near rank list deadlines: If you've already interviewed, updates become part of your thank-you and letter of intent strategy. Bundle them. Don't send a standalone update email two weeks after your interview unless the news is extraordinary.

One update or many? Don't send every small accomplishment in separate emails. If you have two meaningful updates close together, a publication acceptance and a leadership role, bundle them into one concise message. Repeated emails signal disorganization.

Day-by-Day: How to Draft and Send the Update

Once you've decided to update, don't fire off an email at 11 p.m. the same night. A four-day process keeps you accurate and professional.

Day 1, Confirm the facts. Verify the achievement is official. For publications, confirm acceptance status, journal name, and your role. For awards, get the exact title and selecting body. For leadership roles, confirm the start date and scope. Don't email based on a verbal "you got it", wait for written confirmation or a verifiable source.

Day 2, Choose recipients. Don't email every program you applied to. Prioritize:

• Your top-choice programs
• Programs where the achievement is especially relevant (e.g., a research publication for a research-heavy program)
• Programs that have already invited you to interview, if the timing is strategic
• Programs you're waitlisted at, if the update is strong enough to reposition you

Day 3, Draft the email. Keep it to four or five sentences:

• Clear subject line: "Update from [Your Name], AAMC ID [####]"
• One-sentence context: "I'm writing to share a recent update to my application."
• The achievement, stated plainly: "My first-author manuscript, [Title], was accepted for publication in [Journal]."
• Why it matters: one line connecting it to your interests or the program.
• Thank you and signature.

Day 4, Proofread and send. Check tone, grammar, length. Send during business hours, Tuesday or Wednesday morning is ideal. Track which programs you emailed and any responses. If you don't hear back, that's normal. Don't follow up asking if they received it.

Etiquette reminders: One email per program, sent to the program coordinator unless the program specifies a portal. No mass-blast tone. No "Dear Program Director" if you're emailing the coordinator. No overexplaining why you didn't include this originally.

What to Include, What to Avoid, and When to Use Other Channels

Here's the update formula I recommend:

Dear [Coordinator or PD name],

I'm writing to share a brief update to my application. [Achievement, one sentence.] This is relevant to my interest in [specific aspect of the program or specialty].

Thank you for your time and consideration.

[Your name, AAMC ID]

That's it. No long preamble. No emotional appeal.

What not to include:

• Long personal stories about why this achievement matters to you emotionally
• Pressure tactics, "I hope this strengthens my candidacy for an interview"
• Comparisons to other applicants or other programs
• Repeated follow-up asks, "Please let me know if you need anything else"
• Multiple updates in one email unless they're closely related

When to use other channels instead:

• Interviews: If you've already been invited, save minor updates for interview day conversations. Mention them naturally.
• Letter of intent: If you're declaring a top-choice program post-interview, fold the achievement into that letter.
• Thank-you notes: Post-interview thank-yous can include a one-line update if it's recent and relevant.
• Program-specific portals: If a program explicitly directs applicants to submit updates through a portal or form, use that channel instead of email.

Updates should support your application narrative, not replace it. They should feel timely, professional, and intentional. A scattered update email undermines the competence you're trying to project.

Common Mistakes and a Final Action Plan

The mistakes I see most often:

1. Updating too late, sending a January email about an October publication. Useless.
2. Sending weak updates, every small accomplishment treated as breaking news.
3. Over-emailing, three update emails in six weeks. Programs remember, not fondly.
4. Failing to tailor, identical email to 30 programs with no program-specific relevance line.
5. Forgetting to verify facts, emailing about a publication that gets rejected a week later.

Final checklist:

• Confirm the achievement is significant, recent, and relevant
• Verify the facts in writing
• Choose recipient programs deliberately, don't blast everyone
• Draft a 4-5 sentence email with a clear subject line
• Send during business hours within a week of verification
• Save the phrasing for interviews or LOI context if needed

Next 24 hours after a new achievement appears:

1. Verify it, get written confirmation or an official source
2. Classify it, major, mid-tier, or minor
3. Decide, send now, save for interview, or skip
4. If sending: draft today, proofread tomorrow, send Wednesday morning

The principle is simple. Update programs only when the news is meaningful, current, and strategically useful. Everything else is noise.