It happens fast. You submit ERAS in September. You feel decent about your application, especially the research section. One manuscript isn't published yet, but your team thinks it'll be soon, so you label it "In Press." Then an interview invite comes. Great. A week later, somebody at the program checks your citations, looks for the paper, can't verify acceptance, and now you've created a problem that did not need to exist.
I've seen this backfire. Not because the applicant was dishonest in some grand, malicious way. Usually it's sloppier than that. They used "in press" as a placeholder for "submitted," "under review," or "probably accepted soon." That's the trap. And on ERAS, it's a bad one.
Programs don't read your application like your friends do. They read it like screeners. Fast. Skeptical. Looking for signal. Research status is part of that signal. If your listed status doesn't match what can be verified, reviewers stop thinking about your science and start thinking about your judgment. That's the real damage. Trust erosion.
Scenario: The "In Press" Label That Backfired
Here's the classic timeline mistake.
- August: manuscript is submitted
- Late August: coauthor says, "This should be accepted soon"
- September: ERAS opens, applicant writes "In Press"
- October: faculty reviewer searches the paper title, DOI, journal site, PubMed, maybe even asks the PI
- Nothing confirms acceptance
Now the problem isn't just the manuscript. It's you.
The common failure mode is simple: applicants use publication language loosely. They treat submitted, under review, minor revisions, accepted, and in press like they're all shades of the same thing. They are not. In academic publishing, those labels have different meanings. In residency applications, they carry different credibility risks.
Why is this uniquely dangerous on ERAS?
Because programs are making decisions with incomplete information, and they use consistency as a shortcut for trust. A mismatch in publication status can make an otherwise strong file look:
- exaggerated
- careless
- poorly supervised
- or flat-out unreliable
Don't make them wonder whether you inflated one line item. Once that thought enters the room, it spreads to the rest of your application. One bad label can contaminate the whole research section.
What "In Press" Really Means (and Why It's Not a Personal Preference)
"In press" is not vibes. It's not optimism. It's not "the journal has had it for a while."
It means the manuscript has been accepted by the journal and is in the publication pipeline. Not just received. Not just being reviewed. Not just revised after peer review. Accepted.
Here's the clean breakdown:
- Submitted: the journal received the manuscript
- Under review: peer review is in progress
- Revisions requested: editors want changes before a final decision
- Accepted: the journal has formally accepted the manuscript
- In press: accepted, with publication pending
- Epub ahead of print: available online before final issue assignment, usually with DOI
The red flag I keep seeing: applicants borrow language from email threads or journal portals without checking what it actually means. A coauthor says, "It's basically in press." A portal says "with editor." A cover letter template includes "forthcoming publication." None of that is enough.
Your protective rule is blunt because it needs to be:
That means one of these:
- formal acceptance email
- editor letter confirming acceptance
- portal screenshot showing accepted status
- DOI assignment with online publication details
- official online article page
If you don't have that, don't upgrade the label. Wishful translation is how people get burned.
The ERAS Pitfall: Trust Erosion From Status Mismatch
Applicants often imagine programs won't bother checking. That's naive.
Verification can happen in very ordinary ways:
- a coordinator notices a journal title and gets curious
- a faculty interviewer works in the same niche and recognizes the paper isn't out
- a reviewer searches PubMed, Google Scholar, Crossref, or the journal website
- your personal statement or interview comments mention the project, inviting a closer look
- your letter writer describes the manuscript differently than ERAS does
This doesn't require a formal investigation. It takes two minutes.
And the consequences are rarely announced out loud. No one emails you saying, "We downgraded your professionalism score because your manuscript wasn't actually in press." That's not how this works. Instead, the notes say things like:
- "Research status unclear"
- "May have overstated publication"
- "Needs clarification"
- "CV seems padded"
That's enough. Quiet damage. The kind you can't easily fix later.
Here's the mistake people make: they think a stronger-sounding label improves optics. Wrong. In residency applications, credibility beats optics every time. I would much rather see an applicant write "Under review" accurately than "In Press" sloppily. Conservative wording reads as mature. Inflated wording reads as insecure.
That's my rule, and you should borrow it: understate uncertain items rather than overstate verifiable ones.
Decision Framework: What You Should List (and What You Must Not)
Use this framework. It will save you from dumb, avoidable damage.
1. If acceptance is formally confirmed, you may list it as "In Press"
Acceptable proof includes:
- acceptance letter from the journal
- editor email explicitly stating the paper is accepted
- portal status clearly marked accepted
- online journal page indicating accepted/in press status
If the journal explicitly uses "in press," great. Use it. If the journal says accepted but not in press, the safer wording is often:
- Accepted (publication pending)
- Accepted; awaiting publication
That is accurate and low-risk.
2. If it has a DOI or is online as epub ahead of print, list that status accurately
Do not convert one status into another because "it sounds better."
If the article is online already, use language like:
- Epub ahead of print
- Published online ahead of print
- include the DOI if available
That's stronger than "in press" anyway because it's directly verifiable.
3. If it is not accepted, do not label it "In Press"
This includes:
- submitted last week
- under review
- with editor
- revisions requested
- resubmitted after revision
- "looks promising"
- "my PI said the reviewers liked it"
- "conditional acceptance" that is not actually final acceptance
None of those equals in press. Don't blur them together.
4. Borderline cases: this is where applicants get sloppy
Revisions requested
Not accepted. Full stop.
Use:
- Under review
- or Revise and resubmit only if your application format allows detail and you can defend it
Conditional acceptance language
Be careful. Some journals send language that sounds favorable but isn't final. If the message says publication depends on satisfactory changes, forms, approvals, or editorial review, then you are not safe calling it in press yet.
Author proofs received
Usually a good sign. Still not enough by itself unless acceptance was already confirmed. Proofs often follow acceptance, but don't infer status from workflow fragments.
Awaiting final issue assignment
If the article has been accepted and is just waiting for issue placement, you may be able to list:
- Accepted (publication pending)
- In press only if that status is confirmed by the journal
That's the distinction. Small on paper. Big in consequence.
Safe ERAS language templates
Use these instead of improvising:
- Manuscript submitted
- Under review
- Accepted (publication pending)
- Published online ahead of print
- Epub ahead of print; DOI: [insert DOI if verified]
- In press only with acceptance/publication confirmation
The safest applicants aren't the ones who sound the most impressive. They're the ones whose entries survive scrutiny.
Documentation: How to Prove Your Status Without Guessing
If you list research on ERAS, keep a proof folder. Yes, really. I recommend a plain folder on your computer or cloud drive with subfolders by manuscript title.
Save these items:
- acceptance emails
- formal acceptance letters
- editor correspondence confirming status
- screenshots of the manuscript tracking portal
- DOI assignment notices
- online publication pages
- issue scheduling notices, if available
What should you not rely on?
- your memory
- a coauthor's casual summary
- "I'm pretty sure"
- old drafts of the CV
- the fact that proofs arrived
- the fact that the lab has been talking like it's done
I can't say this strongly enough: do not infer acceptance. "I think it's accepted" is not evidence. "My senior author said it's basically accepted" is not evidence. If you can't pull up documentation in 30 seconds, your label is too aggressive.
Do a quick internal audit before you certify ERAS:
- Open every manuscript entry.
- Compare the listed status against the latest journal portal update.
- Check the most recent editor email.
- Confirm title, author order, journal name, and DOI if applicable.
- Downgrade any uncertain status immediately.
That last step matters. Downgrading a label doesn't weaken your application. It protects it.
Common Applicant Mistakes (and the "Don't Do This" Fix)
I've seen the same errors over and over. Don't join that club.
Mistake #1: Writing "In Press" because the manuscript is "waiting for issue"
This is only safe if acceptance is explicit. Waiting for issue assignment after acceptance is fine. Waiting in some vague editorial limbo is not.
Fix: Relabel to Accepted (publication pending) if you have acceptance proof. If you don't, use Under review or whatever the portal actually shows.
Mistake #2: Confusing "epub ahead of print" with "in press"
These are related but not interchangeable. If the paper is already online with a DOI, that's a specific publication status. Use it.
Fix: List the work as Published online ahead of print or Epub ahead of print and include the DOI when verified. Don't translate it into something else because you think ERAS reviewers will prefer the phrase.
Mistake #3: Inflating multiple manuscripts at once
This is the ugly one. An applicant marks three papers as in press, one is really under review, one is in revision, one maybe accepted but undocumented. Now the whole section looks padded.
Fix: Audit every entry line by line. If one status is uncertain, downgrade it. If several are uncertain, downgrade all of them to their exact status. One discrepancy can taint perceived rigor across everything else.
Mistake #4: Copying language from manuscript drafts, biosketches, or cover letters
Author templates are full of fuzzy language like "forthcoming," "accepted," or "in press" because they get reused badly. That doesn't make them accurate today.
Fix: Never copy old CV language blindly into ERAS. Rebuild each citation from current source documents.
Mistake #5: Talking bigger in interviews than you wrote in ERAS
This is how applicants trap themselves twice. They list a conservative status, then casually say, "Yeah, it's basically accepted," when it isn't.
Fix: Keep your spoken description matched to the same verified status:
- "It's currently under review."
- "We received revision requests."
- "It has been accepted and is awaiting publication."
- "It's available online ahead of print."
Clean. Accurate. Defensible.
How to Handle Updates: Timing, ERAS Constraints, and Messaging
ERAS timing is awkward. Manuscripts evolve while applications are already out. That's normal. What matters is how you handle updates without overreaching.
A safe strategy:
- Submit with the most conservative verified status
- Save all new journal correspondence as it arrives
- Update when the platform and program communication norms allow
- Make sure your interview language matches the latest verified reality
If a paper gets accepted after submission, great. Then you can say, accurately:
- "Since submitting ERAS, this manuscript was accepted and is awaiting publication."
- "The paper is now published online ahead of print with DOI available."
That sounds strong because it is strong. No embellishment needed.
What you must not do is promise future publication during interviews. Don't say:
- "It should be in press any day now"
- "We basically have acceptance"
- "It will definitely be published this season"
No. Future-casting is applicant poison. If asked, give the current verified status and stop there.
Summary
Here's the rule I want burned into your application habits: don't list "In Press" on ERAS unless you can prove it.
Not because committees are hunting you. Because credibility is fragile, and this is a stupid place to lose it.
If the manuscript is:
- submitted, say submitted
- under review, say under review
- accepted, say accepted, publication pending if needed
- online ahead of print, say that and include the DOI
- truly in press, only then use In Press
Be conservative. Be precise. Be boring, even. That kind of boring wins. The applicants who get in trouble usually aren't less talented. They're just looser with details than the moment allows.
Don't make that mistake.
