How to List Collaborator-Embargoed Research on ERAS (No Paper Yet)

You have real research work. You contributed. The project matters. But there is no paper yet, and the collaborator or study lead has put limits on what can be disclosed.

That is exactly where people get sloppy on ERAS.

They overclaim. They call something “submitted” when it is still a draft in somebody’s Dropbox. They list a multicenter study with enough detail to break an embargo. They assume being “involved” automatically means they can present themselves as a co-author. Bad move. Program directors notice inflated entries, and collaborators remember who ignored confidentiality.

Here is the practical fix: you can often list the work, but you must do it with permission, with the right category, and with wording that is both truthful and embargo-safe.

“Collaborator-embargoed” usually means one of three things:

• A collaborator asked that the project not be publicly detailed yet
• The work is pending submission and the team wants information held closely
• There is a formal or informal non-disclosure expectation tied to the data, institution, sponsor, or authorship plan

Your job is not to hide the work. Your job is to describe it accurately without leaking what you do not own.

Understand ERAS constraints + embargo constraints (the rulebook you must follow)

ERAS is not asking for marketing copy. It is asking for a truthful record. Specific, accurate, and aligned with the actual status of the work.

That means you need to separate research into the right bins:

• Published/accepted publication: final citation-level material
• Abstract/poster/presentation: conference-related output, if actually submitted, accepted, or presented
• Manuscript in preparation: drafting exists, but no submission claim
• Work in progress/research experience: active project involvement without a publication milestone
• Proprietary or collaborator-controlled work: details may be limited even if the science is real

The mistake I see most often is treating all productivity like a publication. It is not. “I worked hard on this” does not equal “this is a submitted manuscript.” ERAS entries live or die on milestone accuracy.

Use this compliance checklist before you type anything:

1. Confirm you have permission to list the project

   • Ask the corresponding author, PI, or study lead.
   • Email is enough if it is explicit.

2. Confirm what details are allowed

   • Can you name the institution?
   • Can you say “multicenter retrospective cohort”?
   • Can you mention manuscript status?
   • Can you list collaborators?

3. Confirm who owns the embargo

   • PI?
   • Senior author?
   • Sponsor?
   • Multi-institution consortium?

4. Confirm the actual milestone

   • In progress?
   • Data analysis complete?
   • Manuscript drafted?
   • Abstract submitted?
   • Under review?
   • Accepted?

5. Confirm your authorship status

   • Author order final?
   • Not final?
   • You are a contributor but not confirmed as a named author yet?

This is the clean rule: if you do not have permission and milestone clarity, do not force the project into a publication-style entry. Put it under research experience instead, or leave it out until you can support the wording.

The core strategy: list without oversharing (embargo-safe wording patterns)

Here is the strategy I recommend every time: state the truth at the lowest defensible level of specificity.

That means enough detail to show real work. Not so much that you create a confidentiality problem or accidentally exaggerate the milestone.

Good wording is conservative. Conservative wins.

Safe phrasing templates

If the project is being written but not submitted:

• “Manuscript in preparation on retrospective cohort analysis of [general topic], with contributions to study design, data abstraction, and drafting.”
• “Contributed to an ongoing multicenter study on [general condition/topic]; data analysis complete, manuscript in preparation.”
• “Research experience in [topic area], including literature review, statistical analysis, and manuscript development for an embargoed collaborator-led project.”

If analysis is still ongoing:

• “Ongoing research in [general topic]; contributed to data collection and preliminary analysis for collaborator-led study.”
• “Active involvement in dataset analysis for a multicenter project examining [broad topic]; results not yet publicly disclosed.”

If an abstract has truly been submitted:

• “Abstract submitted on [broad topic]; contributed to data analysis and abstract drafting.”
• “Submitted abstract for collaborator-led study in [field/topic]; author role confirmed, further details withheld per project embargo.”

If the work is under review and you are allowed to say so:

• “Manuscript under review on [general topic], with contributions to methodology and drafting; listed with permission under collaborator embargo restrictions.”

Better vs worse wording

Good

• “Manuscript in preparation”
• “Abstract submitted”
• “Ongoing data analysis”
• “Collaborator-led multicenter cohort study”
• “Contributed to study design and chart review”

Bad

• “Publication pending”
  Too vague. Often inflated.

• “Accepted soon”
  Ridiculous. Nothing is accepted “soon.”

• “Submitted to top journal”
  Unnecessary and often prohibited.

• “Co-author” when authorship is still under discussion
  This is how you create avoidable trouble.

• Full dataset names, site names, or collaborator identities when restricted
  Needlessly risky.

The do/don’t list

Do

• Use broad, scientifically meaningful descriptors
• Match wording to the real milestone
• Describe your role specifically
• Keep a copy of permission
• Be prepared to explain the project verbally in an interview within approved limits

Do not

• Claim submission without confirmation
• Claim acceptance without proof
• Suggest authorship order if not finalized
• Name restricted collaborators, datasets, or journals
• Pad the entry with pseudo-precision like dates and venues you were not authorized to disclose

I have seen applicants burn credibility over one line. One line. They write “submitted manuscript” because the team talked about submitting it next week. Then the mentor gets contacted. Now everyone looks bad. Do not do dumb things to sound productive. Accurate wording is productive.

Step-by-step protocol: from embargo question to ERAS entry

Here is the exact protocol. Follow it in order.

Step 1: Get explicit permission

Ask the lead author, PI, or corresponding author a direct question:

• “I am preparing my ERAS application. May I list my work on this project, and if so, what level of detail is acceptable?”

That is enough. Keep it simple.

What counts:

• Email approval
• Written message from the project lead
• A clear statement on what you can say

What does not count:

• “I assume it is fine”
• “They seemed okay with it”
• Silence

If the answer is vague, ask again. You need a usable answer.

Step 2: Ask for the allowed scope

This is where most people fail. They get permission in principle but never clarify boundaries.

Ask:

• Can I name the study topic?
• Can I name the institution?
• Can I describe it as multicenter?
• Can I state “manuscript in preparation”?
• Can I say “abstract submitted”?
• Can I list collaborator names?
• Can I mention my role in analysis, drafting, or data collection?

You are trying to define the safe perimeter. Once you know the perimeter, writing the entry becomes easy.

Step 3: Confirm your authorship status

This part matters more than students think.

There is a difference between:

• contributing to a project
• being expected to be an author
• having confirmed authorship
• having a finalized author order

If authorship is not final, do not imply certainty you do not have.

Safer options:

• “Contributor to collaborator-led manuscript in preparation”
• “Participated in data collection and analysis for ongoing manuscript”

Use “co-author” only if that status is established and permitted to disclose. Otherwise, stick to your role.

Step 4: Choose the right ERAS category

Do not jam every project into “Publications.”

Pick the category that matches truth.

Typical matching logic:

• Accepted/published paper → publication entry
• Submitted or presented abstract/poster → abstract/presentation entry
• Manuscript in preparation → if your ERAS structure allows meaningful research description, often better framed under research experience unless a manuscript-specific section clearly fits
• Active project without submission milestone → research experience/work in progress

If there is no paper yet, many embargoed projects are best represented as a research experience with a concise status note. That is cleaner and less likely to overstate things.

Step 5: Draft the entry conservatively

Use this simple structure:

• Project type/topic: broad but real
• Your role: what you actually did
• Current status: in preparation, submitted abstract, ongoing analysis
• Embargo-safe limits: omit restricted identifiers

Example draft:

• “Collaborator-led multicenter retrospective study in heart failure outcomes. Contributed to chart review, data cleaning, and preliminary statistical analysis. Manuscript in preparation; details limited per collaborator embargo.”

That works because it says something real without pretending the project is further along than it is.

Step 6: Run the embargo leak check

Before finalizing, review the entry for hidden leaks:

Remove or verify:

• journal names
• conference names
• exact submission dates
• site names
• database names
• patient cohort identifiers
• collaborator names
• sponsor details
• authorship order

A lot of leaks happen by habit. People think naming the consortium makes them sound serious. Maybe. It also may violate the agreement.

Step 7: Verify the final wording with the lead

Send the exact line if the project is sensitive.

Example:

• “I plan to list it this way on ERAS: [paste text]. Please confirm this wording is acceptable.”

That extra step prevents awkwardness later.

Step 8: Save the documentation

Keep:

• permission email
• version of approved wording
• later update if status changes

If a program asks about the project, or if the embargo lifts, you have a clean paper trail.

ERAS formatting playbook: what to write in each relevant field

Here are practical templates by scenario.

A. Manuscript in preparation

Template

• “Collaborator-led study on [broad topic]. Contributed to [2–3 concrete tasks]. Manuscript in preparation; additional details withheld per project embargo.”

Example

• “Retrospective study of perioperative outcomes in vascular surgery patients. Contributed to data abstraction, literature review, and manuscript drafting. Manuscript in preparation; listed with collaborator approval.”

B. Abstract submitted

Template

• “Submitted abstract on [broad topic]. Role included [specific contributions]. Further identifying details omitted under collaborator disclosure limits.”

Example

• “Submitted abstract on predictors of readmission in a multicenter internal medicine cohort. Contributed to statistical analysis and abstract writing. Details limited per study lead guidance.”

C. Dataset analysis ongoing

Template

• “Ongoing research in [field/topic] using collaborator-controlled dataset. Responsible for [specific role]. Analysis in progress.”

Example

• “Ongoing outcomes research in neurocritical care using a collaborator-controlled multicenter dataset. Performed data cleaning and preliminary regression analysis. Analysis in progress.”

D. Collaborator-embargoed multicenter study

Template

• “Contributed to a collaborator-led multicenter [study type] examining [broad topic]. Responsibilities included [role]. Manuscript status: [in preparation / under review if permitted]. Project details restricted pending embargo release.”

Example

• “Contributed to a collaborator-led multicenter cohort study examining emergency department sepsis triage. Responsibilities included chart review and methods drafting. Manuscript in preparation; project details restricted pending embargo release.”

Mini-review rubric before you submit

Ask four questions:

• Clarity: Would a reviewer understand what kind of work this was?
• Truthfulness: Does every status word match reality?
• Permission: Did the lead approve this level of detail?
• Non-disclosure: Did you omit restricted names, venues, and identifiers?

If one answer is no, revise it.

Common failure modes and exact fixes

These are the usual traps. Here is how to fix them fast.

Failure mode 1: Claiming submission or acceptance without confirmation

Problem: You wrote “submitted” because the team planned to submit.

Fix:

• Change it to “manuscript in preparation” or “draft manuscript in development”
• Remove journal names and submission dates
• Reconfirm status with the lead

Failure mode 2: Listing too many identifiers

Problem: Your entry names the hospital system, consortium, and internal dataset.

Fix:

• Generalize it
• Replace with “multicenter cohort,” “collaborator-led dataset,” or “retrospective outcomes study”
• Keep the science, drop the identifiers

Failure mode 3: Wrong authorship representation

Problem: You called yourself a co-author, but authorship order is unresolved.

Fix:

• Replace with “contributor” or describe your role directly
• Claim authorship only when it is established and approved

Failure mode 4: No documentation of permission

Problem: You got a verbal “sure” months ago.

Fix:

• Send a short follow-up email now
• Save the response
• Update the wording if the lead narrows the scope

This is not bureaucratic nonsense. It protects you.

After submission: what to do when embargo lifts

Once the embargo lifts or the manuscript advances, update carefully.

Use this transition plan:

• Before submission/while drafting: keep wording conservative
• After true abstract submission: update to “abstract submitted” if appropriate and allowed
• After manuscript submission: update only if your application system or later communications permit it
• After acceptance/publication: replace the placeholder description with the correct citation details

For interviews, use a disciplined answer:

• Briefly describe the topic
• Explain your role
• State the current milestone accurately
• Add that some details were restricted at the time of ERAS submission due to collaborator embargo

If pressed for details, do not improvise beyond what is shareable. A calm answer beats a leaky one.

Summary

Here is the fix in one sentence: get explicit permission, define the allowed scope, and use milestone-accurate conservative wording.

That is the whole game.

The highest-yield move is asking the lead author exactly what you may say on ERAS. After that, your job is simple:

1. Confirm the true status
2. Pick the right ERAS category
3. Describe your role specifically
4. Avoid restricted identifiers
5. Save the permission email

Embargoed research can absolutely strengthen your application. But only if you list it like a serious person. Not like someone trying to sneak an unfinished paper past the reader.