When Your Only Output Is a Preprint or Abstract: How ERAS Views It

Opening Scenario: You Have a Preprint, an Abstract, and an ERAS Deadline

It is late August. You are staring at ERAS, toggling between your CV, a preprint server page, and a PDF of a conference abstract. One project made it onto a preprint server last month. Another was accepted to a national meeting and presented as a poster. The full manuscript for that one is still drifting through revisions, somewhere between your senior resident, a statistician, and a faculty mentor who replies every nine days.

Now the question hits: what exactly can you list, and what will residency programs think it means?

That is the real issue. Not whether your work was hard. Not whether your project matters scientifically. It probably does. The issue is classification. ERAS is brutally literal. Programs are busy, skeptical, and very capable of spotting puffed-up scholarship. If you label a preprint like a publication, that is a problem. If you hide a legitimate abstract because you think it “does not count,” that is also a mistake.

I have seen applicants hurt themselves both ways. One undersold solid work because it was “only a poster.” Another listed a manuscript as if it were already published because it had a DOI on a preprint server. That is exactly the kind of sloppy inflation that makes reviewers distrust the entire application.

This article is about getting it right. Specifically: what ERAS actually lets you report, how program directors tend to read preprints and abstracts, and how to describe your scholarship with precision. No games. No fake polish. Just accurate reporting that still presents your work strongly.

What ERAS Actually Lets You Report

ERAS is a reporting platform. That sounds obvious, but applicants forget it every year. ERAS does not certify that your scholarly output is prestigious, rigorous, or especially meaningful. It simply gives you structured places to report academic work. Programs then decide what weight to give each entry.

The research-related sections are usually interpreted through a few practical buckets:

• Peer-reviewed publications
• Abstracts
• Poster presentations
• Oral presentations
• Research experiences or scholarly projects
• Other works in progress or submitted items, depending on the application field and cycle structure

The first big distinction is this: a publication is not the same as a presentation.

A peer-reviewed publication usually means the manuscript has been reviewed, accepted, and formally published by a journal. That is the strongest conventional signal because somebody outside your research group vetted the work. Not perfect. Peer review has flaws. Plenty of weak papers get published. Still, in application review, peer-reviewed publication remains the cleanest shorthand for completed scholarship.

An accepted abstract is different. It means a conference accepted a summary of your work for dissemination. That matters. Especially if it was accepted to a credible specialty meeting. But it is not the same as a full journal article, and you should not blur the line.

A poster presentation means the work was accepted and displayed in poster format. That typically signals completion of a project phase, conference participation, and at least some level of external review. An oral presentation often carries slightly more weight because selection is usually more competitive. Not always, but often.

A preprint sits in a separate lane. It is publicly posted scholarship, usually with a DOI, but not yet peer reviewed in the traditional journal sense. That makes it real academic output, but not a published peer-reviewed article. The distinction matters. Deeply.

There is also the category problem. A project may generate several outputs:

• a research experience entry,
• an abstract accepted at a meeting,
• a poster presentation,
• and later a journal article.

That does not mean you should duplicate the same work carelessly across sections to make the application look longer. If you list multiple outputs from the same project, each entry must represent a distinct scholarly product. Different title, different format, different venue, different status. Otherwise it looks padded. Because it is padded.

Here is the clean way to think about it: ERAS captures what happened, not what you hope committees will assume happened.

Preprints: Real Scholarship, but Not the Same as Peer-Reviewed Publication

Let me be direct: preprints are legitimate, but they are not publications in the way residency committees use that word.

A preprint is a manuscript posted publicly before formal peer review. Platforms like medRxiv, bioRxiv, arXiv, and specialty-specific servers exist for rapid dissemination. That is useful for several reasons:

• the work becomes visible quickly,
• other researchers can read and cite it,
• the authors can establish precedence,
• and the timeline is not held hostage by a six-month journal review cycle.

This is especially common in fast-moving fields, data-heavy projects, public health work, and collaborative research where getting the information out matters.

So no, a preprint is not fake. It is not “nothing.” But it is also not vetted in the same way a journal article is. That is why programs usually assign it less weight than a peer-reviewed paper.

Here is how most committees read it, whether they say it out loud or not:

• Positive signal: You completed a manuscript and got it into public form.
• Caution signal: It has not cleared peer review.
• Interpretive question: Will this eventually publish, or did it stall here?

That middle point is why transparency matters so much. A preprint can absolutely strengthen your application if it is clearly labeled and if you can discuss the study intelligently. It shows productivity, initiative, and follow-through. But the minute you try to smuggle it into the “publication” category without clear status labeling, you lose credibility.

And credibility is the real currency here.

I have reviewed applications where the entry title looked polished, the authorship looked legitimate, and then the citation ended in a preprint server DOI with no indication that it was unpublished. That is not clever. It is misleading. A reviewer who catches that starts wondering what else you exaggerated: authorship order? degree of involvement? whether the data were even yours? All because of one inflated label.

The biggest errors with preprints are predictable:

1. Calling the preprint a published paper
2. Implying journal acceptance when the manuscript is only submitted
3. Using “in press” when nothing is actually in press
4. Omitting the preprint platform so the status looks ambiguous
5. Listing a preprint and a manuscript submission as if they are separate completed products

Do not do any of that.

The right approach is brutally clear. If it is a preprint, call it a preprint. If it is submitted to a journal but not accepted, say submitted only if the field allows that status and if it is true. If the same manuscript exists as both a preprint and later a publication, the status should evolve over time, not magically rewrite history.

Programs vary in how much they care about preprints. Research-heavy academic programs, especially in specialties with strong publication culture, are usually familiar with them and may view them favorably if the work is substantive. Community-focused programs may care less about the format distinction and more about whether you can speak coherently about the project. But no serious reviewer mistakes a preprint for peer-reviewed output if it is labeled honestly.

That is the standard I recommend: accurate but not apologetic.

You do not need to downplay a preprint. Just do not cosplay as a published author if the journal has not accepted the paper.

Abstracts, Posters, and Conference Presentations: Why They Still Matter

Applicants often dismiss abstracts and posters because they are not full papers. That is a mistake.

Accepted abstracts are legitimate scholarly dissemination. Full stop. If your work was accepted to a national specialty meeting, regional scientific session, or respected institutional research day, that tells programs something useful: you did enough work to package findings, meet a deadline, and present them publicly. That matters.

Not all conference outputs are equal, though. Programs tend to read them in a loose hierarchy:

• Oral presentation: usually strongest among conference formats
• Poster presentation: solid and common
• Abstract-only acceptance: still valid, but lighter signal

Why the difference? Effort, selectivity, and visibility.

An oral presentation usually suggests the conference selected your work for a more prominent format. A poster still reflects accepted scholarship and often substantial involvement. Abstract-only acceptance can be meaningful, but if there was no actual presentation and minimal review, programs may treat it as a lighter accomplishment.

That does not mean you should obsess over the micro-ranking. It means you should label the output precisely.

The strategic value of abstracts is underrated. They can show:

• productivity during medical school,
• ability to collaborate,
• familiarity with deadlines,
• evidence that a project moved beyond “we are collecting data,”
• and in many cases, ownership of a niche topic.

For applicants without multiple full publications, abstracts and posters often provide the best evidence of academic momentum. And momentum matters. A file with one first-author poster, one abstract at a national meeting, and one clearly labeled preprint can read much better than a file with vague claims of “manuscripts in preparation.”

Because “in preparation” is often academic fantasy. I have seen dozens of those entries evaporate on follow-up. A real abstract beats a hypothetical paper every time.

How Program Directors Tend to Read These Entries

Program directors and faculty reviewers are not just counting lines. They are reading for pattern.

What they want to know is simple:

• Are you honest?
• Do you finish things?
• Do you understand the work you listed?
• Could you contribute to scholarship during residency?

That is the hidden rubric.

Context changes everything. In dermatology, orthopedics, neurosurgery, radiation oncology, or academic internal medicine tracks, research entries may receive heavier scrutiny. In other specialties, they still matter, but reviewers may care more about whether the work reflects seriousness and reliability than about impact factor. A first-author publication in a modest journal can be more persuasive than being eighth author on five giant consortium papers you can barely explain.

Ownership matters. A lot.

If you are first author, say so accurately. If you built the database, performed chart review, and drafted the methods section as third author, that is still respectable work. Just do not inflate it. Reviewers can smell fake ownership instantly, especially in interviews.

The classic red flags are always the same:

• vague or generic project titles,
• duplicate listing of the same work across multiple sections without distinction,
• missing status labels,
• suspiciously inflated author roles,
• and inconsistent timelines between ERAS, CV, and interview answers.

I have watched applicants sink themselves by describing a “published study” in ERAS, then admitting during an interview that it was actually “still under review” or “on medRxiv.” That mismatch is worse than having fewer research entries. The problem is not the preprint. The problem is trust.

How to List a Preprint or Abstract in ERAS Without Overclaiming

This is where applicants either look sharp or look slippery.

Your description should follow a simple hierarchy:

1. What the work is
2. Where it appears
3. What stage it is in
4. What your role was

That structure prevents accidental exaggeration.

For example:

• Preprint: “Smith J, Patel R, YourName A. Title of Manuscript. medRxiv preprint. Posted August 2026. First author.”
• Accepted abstract: “YourName A, Chen L, Gomez P. Title. Accepted abstract, Society of Hospital Medicine Annual Meeting, 2026.”
• Poster presentation: “Poster presentation: Title, American Academy of Neurology Annual Meeting, 2026. Second author; data analysis and poster design.”
• Submitted manuscript: only use this if the application field permits it and if it is actually submitted.

Exact status terms matter:

• preprint
• accepted abstract
• poster presentation
• oral presentation
• submitted manuscript
• published
• in press only when truly accepted and awaiting publication

Never substitute a stronger label because it “sounds better.” That is amateur behavior.

Consistency also matters across every application surface:

• ERAS entry
• CV
• personal statement if mentioned
• signals or supplemental essays
• interview answers

If ERAS says “preprint” and your CV says “publication,” you created a credibility problem for no reason. Clean records read well. Messy records invite suspicion.

A practical rule I give students: if a tired faculty interviewer asks you, “Tell me about this paper,” your one-sentence answer should match the exact status listed in ERAS. No scrambling. No awkward correction. No “well, technically…”

What to Do If the Manuscript Publishes After Submission

This happens all the time. You submit ERAS with a preprint or abstract listed honestly, and then three weeks later the paper gets accepted or published. Good. That is a real upgrade. Handle it like an adult.

Do not rewrite history. At submission, it was a preprint or abstract. Afterward, it became a publication. Preserve that timeline.

Depending on the season and the program, you may be able to update programs through:

• a formal application update if allowed,
• a brief email to programs of highest interest,
• interview-season discussion,
• or an update letter to your dean’s office or advising structure, depending on local process.

The goal is accuracy, not spam. One clean update is enough. Five emails about the same paper is annoying and makes you look desperate.

Best format: concise, factual, and dated.

Example:
“Since my ERAS submission, our manuscript previously listed as a medRxiv preprint was accepted/published in Journal X on October 12, 2026. I wanted to provide this update for accuracy.”

That works. No drama. No overselling.

Closing Action Steps: The Safe, Strong ERAS Strategy

Here is the rule: list every legitimate scholarly output, label it by its real status, and let the committee decide the weight.

That is the strongest strategy. Not the most inflated. The strongest.

Use this checklist before you submit:

• Verify the ERAS category rules for the current cycle.
• Standardize titles, author order, and dates across ERAS and your CV.
• Label status exactly: preprint, accepted abstract, poster, oral presentation, published.
• Keep proof of acceptance emails, conference listings, and preprint links.
• Remove duplicate or padded entries.
• Prepare a 30-second explanation of each project for interviews.
• Update published work later only if the timing and program policies make sense.

A preprint is not “nothing.” An abstract is not a consolation prize. Both can show momentum, execution, and scholarly seriousness. But only if you present them cleanly. That is the whole game.

Key Takeaways

• ERAS is about accurate reporting; a preprint or abstract can be listed if it fits the category rules, but it should never be portrayed as a peer-reviewed publication.
• Residency programs usually value transparency and momentum more than inflated labels. Clear status, exact authorship, and consistent timelines matter.
• If a project publishes after submission, update thoughtfully and keep the application narrative honest from start to finish.