Visa Attestation vs ERAS Data: Prevent IMG Interview Rescinds

Every cycle, strong IMG applicants lose interview offers they were already holding. Not because a score dropped. Not because a letter soured. Because a program coordinator noticed that the visa statement in one document did not match the data in another, and nobody on that side of the desk wanted to sign their name to the uncertainty.

Let me define the core term before anything else. In the IMG residency context, "attestation" is any sworn statement of fact and intent you certify as true: the certification statement you accept when you submit ERAS, the NRMP Match Participation Agreement, ECFMG-related declarations, and the program-level or GME-office questionnaires where you restate your visa status and sponsorship needs. Programs treat these as high-stakes because they are also signing documents, rank lists, contracts, sponsorship requests, under institutional and federal compliance rules. Your words become their legal exposure.

Here is what follows: a practical compliance workflow you can actually execute, the specific failure modes that get offers pulled, and an exam-style checklist mindset for catching mismatches before a stranger does. One position I will state upfront and defend throughout: most rescinds I have seen were not fraud. They were sloppiness that looked like fraud, and programs cannot afford to tell the difference.

This guide is for educational purposes only. It is not financial advice, not legal advice, and not tax advice; immigration categories, ECFMG policies, and program-level rules change frequently, and the relevant timelines and figures vary by institution and jurisdiction. Before you sign, amend, or act on any sworn statement, consult a qualified professional such as an immigration attorney, your ECFMG advisor, or your medical school's international office.

Know the Data Sources: What Programs Actually Compare

Programs do not review one document. They run a pipeline, and each stage is an opportunity for your file to contradict itself.

The typical review chain looks like this:

1. MyERAS application fields, citizenship, the visa sponsorship question, work authorization statements.
2. ECFMG status report, certification status, pathway, and the certified date.
3. USMLE transcript, attempts and exam dates.
4. Education and experience entries, your full timeline since medical school entry.
5. NRMP registration data, which carries its own accuracy obligations.
6. Program supplemental forms and GME intake forms, a second attestation, often completed weeks after the first.

The fields that get cross-checked most aggressively: visa/work authorization status, ECFMG certification and its date, medical school graduation date, prior graduate medical education, timeline gaps, and name consistency across documents. These are eligibility fields. Errors there read as risk, not typos.

Programs rescind for three reasons, and only one of them is about you. First, compliance exposure: the NRMP can investigate inaccurate information as a Match violation, and ECFMG treats false statements as a threat to certification itself. Second, reputation: the program director's signature sits under everything. Third, timing: an interview offer is a bet that you will be fully eligible on a fixed start date in July, and anything that makes that bet harder to price, an uncertain H-1B, a pending pathway, a vague status, tilts the committee toward "no."

I have watched a coordinator print an ERAS visa answer and a supplemental form, place them side by side, and rescind within ten minutes. The applicant was honest. The paperwork was not.

Visa Attestation: What It Is, Why It's Worded Carefully, and How to Read It

An attestation is a sworn statement of fact and intent at a fixed point in time. It carries three obligations at once: a truthfulness duty, a compliance assurance to the institution, and, the part applicants underestimate, a timing commitment about the future.

That is why the wording is so careful. The institution is allocating risk. It is saying: tell us exactly where you stand, so we can make promises on your behalf to the NRMP, to ECFMG, to our own counsel. Vague answers transfer the risk back to them. They respond by removing the risk. Which is you.

So read attestation language the way you would read a contract you are about to sign, because you are. My method:

• Circle every verb. Certify, will, may, expect, intend, hold, am. Each verb commits you to a different evidentiary standard.
• Underline every time qualifier. Currently, by July 1, at the time of matriculation, upon offer. These are the tripwires.
• Bracket every condition. If, provided that, subject to. Conditions are where mismatches breed.

A worked example. Take the clause: "I currently hold valid work authorization and will maintain it through the start of training." The phrase currently hold means documents in hand today. Will maintain means no gap between today and July 1. If your EAD expires in March and the renewal is pending, the first clause may be technically true while the second is a promise you cannot guarantee. The truthful answer requires that caveat, or a different status selection entirely.

The three risk patterns I see repeatedly: overly broad statements ("I am eligible for any visa category", no one is), ambiguous future intent ("I expect to have permanent residency" when the petition is at an early stage), and answers that match your hope rather than your documents.

The most dangerous sentence in any application is the one written from memory.

ERAS Data Integrity: The Fields That Must Match, Down to Dates and Definitions

Four ERAS data domains create eligibility and credibility concerns. Treat each as a system under audit:

1. Biographical data. Legal name exactly as on your passport, citizenship, and any AKA entries after a name change.
2. Education and training timeline. Medical school start and graduation, internships, prior residency, observerships, externships, research positions, everything, in order.
3. Licensure and ECFMG signals. Certification status, pathway, certified date, exam dates and attempts.
4. Visa-related fields. Sponsorship need, current status, category, phrased identically everywhere they appear.

Date math is where good applicants get burned. Three specific pitfalls. First, format ambiguity: 06/07/2019 means June 7 in the United States and July 6 almost everywhere else, and IMGs of all people should know better than to trust an ambiguous date. Second, granularity mismatch: ERAS works largely in month/year, your diploma carries a day, your MSPE references an academic year, three documents, three resolutions, endless chances for apparent contradiction. Third, timezone drift: an exam sat at a Prometric center abroad can carry a report date that does not match the month on your CV.

The fix is normalization, and it is unglamorous. Build one master timeline in month/year format. Adopt a single rounding rule, an activity starting on or before the 15th counts for that month, otherwise the next, and apply it everywhere without exception. Copy institutional names character-for-character across every document. And label every gap. "Exam preparation" is a label. Blank space is a red flag.

High-Risk Failure Modes That Lead to Interview Rescinds

The sponsorship flip-flop. A candidate with a pending adjustment of status checks "no" to the sponsorship question in ERAS because an EAD exists, then requests H-1B sponsorship on a program's supplemental form because an attorney advised it. Both answers are defensible in isolation. Together, they are a contradiction, and the GME office cannot reconcile them without a phone call nobody has time to make. Offer rescinded.

Future-status confusion. "Will obtain ECFMG certification by the rank list deadline" while the transcript shows the pathway requirement still incomplete. "H-1B will be filed" without Step 3 passed, at a program whose state licensure rules make the timeline nearly impossible. Programs read future-tense claims as risk, not optimism. If the verb is will, the unspoken question is what if you do not, and if your file contains no answer, the program supplies its own.

The training timeline trap. An unexplained nine-month gap between graduation and the first observership. Dates in the wrong order, with an end month before the start month. A position described as a "clinical fellowship" in ERAS and a "research fellowship" in the CV, which to a tired reviewer looks like unreported clinical training. I reviewed a file once where ERAS said graduation was May 2019, the diploma read 21 June 2019, and the MSPE referenced the "Class of 2019", three documents, three stories, zero intent to deceive. It still cost the applicant an interview.

The mitigation is applicant-level and entirely within your control. Preempt the confusion: one clarifying line in the experience description for anything a stranger would question. Attach documentation that supports the unusual entries. And answer the question asked, not the question you wish had been asked. Do not get creative with eligibility fields. Creativity belongs in the personal statement.

Programs do not rescind because they are cruel. They rescind because you made their compliance office do extra work for an uncertain payoff. The rescind is almost never about the visa itself. It is about the trust collapse.

A Step-by-Step Compliance Playbook (That You Can Actually Execute)

Here is the workflow, in order:

1. Build the master timeline. Every activity since medical school entry, in month/year, gaps labeled. One page. This is the source of truth for everything downstream.
2. Write a field dictionary. Your canonical answers, visa status phrasing, certification status, graduation date, prior training description, composed once, verified against documents, and pasted into every form thereafter. Never retype. Retyping is how drift happens.
3. Reconcile before certifying. Read every attestation clause against the dictionary. Verbs, time qualifiers, conditions. Fix the data or fix the statement, but they must agree.
4. Run the stranger audit. Read your file as a coordinator who has never met you and has forty more files today. Anywhere a question could arise, it will arise. Clarify it now.
5. Maintain version control. Save timestamped PDFs of every submission. Keep a short rationale packet, one page per potentially confusing item, so every answer you give later can be defended identically.

Edge cases deserve explicit handling. If a renewal is pending, state the current status exactly and note the renewal filing date; do not describe the status you hope to have. If your name changed after marriage, use the AKA fields and keep the passport name as the anchor. If you are on OPT approaching a cap-gap transition, describe each stage with its own effective dates rather than blurring them into one claim.

Communication Strategy: If Something Changed After Submission

Status changes after submission are normal. Handling them badly is what rescinds offers.

The rules are simple. If the ERAS field is still editable, update it. If it is locked, email the programs. And never let an interview answer contradict the file, update the file first, always.

The message format is what I call minimal disclosure with maximal clarity. Four elements, nothing more: what changed, the effective date, the evidence attached, and a one-line statement of consistency with prior submissions. No narrative essay. No apology tour. A structured note a coordinator can file in ninety seconds.

What not to do: say nothing and hope. Silence reads as concealment, and concealment reads as fraud. Unfair, but true.

For interview day, carry a printed one-page timeline and rehearse a forty-five-second explanation of any gap or status change until it bores you. Calm, consistent, identical every time. That is the entire skill.

Exam-Style Self-Testing: Treat Consistency Like a Clinical Workup

Approach your file the way you approach a question stem. The stem every reviewer is silently answering is this: Is this applicant's eligibility file trustworthy? Mismatches are the pathology on your differential. Your job is to rule them out systematically, with evidence, before someone else finds them, the same way you rule out the dangerous diagnosis first.

Rapid self-check questions. Run them in order:

• Does every attestation verb match my current, documented status?
• Are all dates internally consistent to the month, across every document?
• Do ERAS, NRMP, ECFMG materials, and supplemental forms use identical visa phrasing?
• Could I defend every entry under oath-like scrutiny, with a document in hand?
• Would a stranger find zero unexplained gaps?

The scoring is brutal by design: all-pass is the only acceptable result. One fail is a full stop and a return to the audit.

The method, in summary: master timeline, field dictionary, reconciliation before certification, stranger audit, version control, structured updates when anything changes. The applicants who keep their interview offers are not the ones with the cleanest immigration histories. They are the ones whose paperwork tells one story, the same story, everywhere a program bothers to look.

Key Takeaways

• Treat visa attestation like a contract. Align every verb, every time qualifier, and every condition with your ERAS data and your supporting documentation before you sign anything.
• Most rescinds come from preventable mismatch optics, status wording, date rounding, unexplained gaps. A single master timeline and a field-by-field consistency audit eliminate nearly all of them, for less effort than one more round of proofreading.