Are texts actually riskier than emails during Match season?
Short answer: sometimes, but not for the reason people think. The problem usually isn't the phone. It isn't Gmail. It's the message. A ranking ask sent by email is still a problem. A pressure-filled text is still a problem. And a perfectly normal scheduling text is usually just that—a scheduling text.
What changes between texts and emails is tone, traceability, and how fast things go sideways. I've seen applicants obsess over whether they can send a thank-you text while completely missing the bigger issue: the content sounds like a pledge, a pressure campaign, or a ranking discussion. That's where people get burned.
This article is for educational purposes only and isn't legal advice. NRMP policies can change, facts matter, and if you're dealing with a possible violation or formal complaint, talk to your dean's office, advisor, or qualified legal/compliance professionals.
What Does "Violation" Mean Under NRMP Rules?
Here's the plain-English version: an NRMP violation is communication or conduct that undermines a fair Match.
That includes behavior that:
- pressures applicants or programs,
- asks for information that shouldn't be requested,
- makes promises that shouldn't be made,
- misrepresents ranking intentions,
- or breaks confidentiality and professionalism rules tied to the Match.
At the applicant level, people often imagine violations as dramatic threats or explicit quid-pro-quo language. Sometimes it is that obvious. More often, it's sloppier than that. Casual. "Hey, just checking if you'll rank us highly." Still a problem. "If you rank us #1, you'll match here." Also bad. "We plan to rank you to match if you're committed to us." Not clever. Still bad.
Three buckets you should use
1. Actual violation
This is the easy category. The message includes:
- a request to reveal rank order,
- a promise about rank order,
- pressure to commit,
- coercive follow-up,
- misleading statements meant to influence ranking.
If the communication would make a reasonable applicant feel cornered, manipulated, or pushed into revealing preferences, that's not harmless.
2. Gray-area interaction
This is where people get confused. Examples:
- "We were very impressed and hope to stay in touch."
- "You'd be a great fit here."
- "Let us know if you have questions as you finalize your list."
These can be normal expressions of interest. They can also feel loaded, depending on timing and context. Gray area doesn't automatically mean violation. It means pay attention.
3. Harmless administrative communication
This is the boring stuff. Usually safe:
- interview date confirmations,
- Zoom links,
- parking instructions,
- thank-you for attending,
- "Please send your updated transcript,"
- "Your second-look starts at 8 a.m."
No rank talk. No pressure. No problem.
And that brings us to the real question: are texts riskier than emails? My answer is yes in some practical ways—but not because texts are inherently forbidden. They're riskier because they're faster, sloppier, more informal, and easier to misread. But if you're judging whether something is an NRMP issue, content and context matter more than the channel.
What the Data Says About Texts vs Emails
We don't need to pretend there's a magical line where text = violation and email = safe. That's nonsense. A bad message is bad in either format.
What the reporting pattern usually suggests is this:
- Texts often create more ambiguity
- Emails create a cleaner record
- Either one can support a complaint if the content crosses the line
Why texts feel riskier:
- they're informal,
- people type too fast,
- off-hours messages feel more intrusive,
- shorthand strips away nuance,
- and a "quick question" can turn into prohibited rank talk in three bubbles flat.
Why emails feel safer:
- they're slower,
- more formal,
- easier to edit before sending,
- and easier to document later.
But email has its own problem: because it's formal, people sometimes put truly dumb things in writing with way too much confidence. I've seen versions of: "We intend to rank you highly and hope you will do the same." That's not rescued by a signature block and hospital logo.
The practical differences that matter
1. Traceability
Email wins. Full stop.
Email usually preserves:
- sender identity,
- timestamp,
- subject line,
- thread history,
- forwarding path.
Texts can also be preserved, obviously, but they may be fragmented, deleted, screen-cropped badly, or missing context.
2. Permanence
Both are permanent enough. Don't fool yourself.
Applicants often think texts are casual and temporary. They aren't. Screenshots exist. Device backups exist. Program coordinators save things. If you send it, assume it can be reviewed later.
3. Tone
Texts are more likely to sound too personal, too familiar, or too pushy without the sender realizing it.
A text saying:
- "Any chance I'm your top pick too? :)"
may be meant as light banter. It reads very differently in a complaint file. Emojis don't rescue bad judgment.
4. Timing
This gets underestimated.
An 11:47 p.m. text to an applicant from a faculty member feels different from a daytime email from the coordinator. Same words, different impact. Texting intrudes into a person's personal space in a way email often doesn't.
5. Misinterpretation risk
Higher in text. Always.
Short messages remove context:
- "Call me when free"
- "Need your thoughts before rank list"
- "Are we your first choice?"
Those can land hard. Especially when an applicant is already stressed and reading every word like it's life-or-death. Which, for them, it kind of is.
Simple comparison
Here's the clean takeaway from that comparison:
- Texts: higher informality, higher misinterpretation risk, often more perceived pressure
- Emails: stronger documentation, stronger traceability, usually more controlled tone
So no, the data story isn't "text bad, email good." It's this: texts are more likely to produce messy, ambiguous, pressure-feeling interactions, while emails are easier to document and review.
Common Scenarios: Which Messages Are Most Likely to Cross the Line?
This is where people need concrete examples, not vague professionalism speeches.
Usually fine
Interview thank-you email
Something like:
- "Thank you for the opportunity to interview. I appreciated learning more about your program and the residents."
Fine. Polite. Normal.
Scheduling update
- "Thank you. I can attend on Friday at 1 p.m."
Also fine.
Clarifying logistics
- "Could you please confirm whether dinner is virtual or in person?"
Totally harmless.
Brief thank-you text, if the program already used text
- "Thank you again for today. I appreciated meeting everyone."
Usually okay if the channel was already opened by the program and you're keeping it brief. Not my favorite move, but not automatically a problem.
Where things start getting risky
Asking about rank position
- "Will I be ranked to match?"
- "Where do I stand on your list?"
- "Am I in your top group?"
Bad idea. Direct ranking inquiry. Don't do it.
Revealing rank preferences in a way that invites reciprocity
- "I'm ranking you #1 and hope that helps."
This gets people into trouble fast. Even if applicants are allowed in some settings to voluntarily express preference, this kind of message often drags the other side into improper territory or creates pressure where none should exist. It's not smart.
Program asking for your rank intentions
- "Can you let us know where we're likely to fall on your list?"
- "Are you ranking us first?"
- "We need to know your level of commitment."
That is a glaring red flag.
Program making promises
- "Rank us first and you'll match here."
- "We'll rank you to match if you commit."
- "You're guaranteed a spot if you tell us we're #1."
This is exactly the kind of thing that triggers complaints. It's coercive and improper.
Why texts can cross the line faster
A text is built for speed, not caution. That's the problem.
I've seen this happen:
- A chief resident gives an applicant their number "in case you need anything."
- The applicant sends a thank-you text.
- The chief replies warmly.
- Then one side gets too comfortable.
- Suddenly someone asks, "So are we high on your list?"
That's how a normal exchange mutates into a problem. Not because anyone sat down to engineer misconduct. Because texting invites impulsive, under-edited communication.
Texts also create these extra hazards:
- off-hours messaging feels more personal and more pressuring,
- wrong-recipient sends happen all the time,
- shorthand makes intent murky,
- emoji and joking tone blur seriousness,
- threaded back-and-forth escalates quickly.
A formal email at least forces a pause. You see the subject line. You see the institution. You have a chance to think, "Maybe I shouldn't write this ridiculous sentence." Texting removes that speed bump.
Common misreads
Applicants and programs misread each other constantly during Match season.
A few examples:
- "We loved meeting you" is usually just friendliness, not a promise.
- "You're a great fit" is not the same as "we will rank you highly."
- "Stay in touch" is not an invitation to discuss rank order.
- A smiley face is not harmless if the actual content is improper.
- Silence after your thank-you email doesn't mean you're doomed.
And here's the ugly truth: stressed applicants often over-interpret everything, while overly casual program representatives under-appreciate how much weight their words carry. Bad combo.
If a message touches ranking, commitment, leverage, or reciprocal promises, stop calling it "informal." It's just risky.
How to Protect Yourself: A Practical Decision Framework
You don't need a legal memo every time you contact a program. You need a filter.
Use this before sending anything.
The four-question screen
Ask yourself:
Is this necessary?
- Is there a real purpose?
- Or am I sending it because I'm anxious and want reassurance?
Is it factual?
- Scheduling, logistics, clarification, thank-you. Good.
- Fishing for ranking intel. Bad.
Is it polite and professional?
- No pressure.
- No emotional leverage.
- No overfamiliar tone.
Is it free of ranking language, promises, or preference asks?
- If not, don't send it.
If a message fails any one of those, revise or drop it.
Which channel should you use?
My rule is simple:
Use email for:
- interview scheduling,
- thank-you notes,
- updates,
- questions,
- anything you may need to reference later,
- anything even slightly formal.
Use text only for:
- brief logistics,
- same-day timing changes,
- urgent coordination,
- situations where the program already opened that channel.
And even then:
- keep it short,
- keep it factual,
- don't improvise,
- don't drift into Match talk.
If a coordinator texts, "Your interviewer is running 10 minutes late," replying by text is fine. If you're tempted to use that same thread to ask how competitive you are on their rank list, that is a spectacularly bad idea.
Document everything that matters
Do this like a grown-up:
- save screenshots,
- keep full email threads,
- note dates and times,
- don't crop out context,
- back up anything concerning,
- write down who sent what and when.
If something feels off, preserve it immediately. Not three weeks later when messages have disappeared and memories have become mush.
What to do if you receive a questionable message
- Don't respond emotionally.
- Take screenshots or save the email.
- Preserve the full thread.
- Talk to your advisor, dean's office, or student affairs office.
- Consider whether the message was merely awkward or actually improper.
- If needed, use official NRMP reporting channels.
Not every weird message is a reportable offense. Some are just clumsy. But clumsy can still matter if it asks for rank information or applies pressure.
The simplest rule
If you would not want your message read out loud in a review meeting, don't send it.
That's the rule. It's blunt because it works.
Summary
Here's the answer you're looking for.
Texts are not automatically NRMP violations. Emails are not automatically safe. The medium matters, but the message matters more.
What the real-world pattern shows is:
- texts are more informal,
- more easily misread,
- more likely to feel intrusive or pressuring,
- and more likely to drift into sloppy, risky territory.
Emails, on the other hand:
- are easier to document,
- usually encourage more careful wording,
- and create a better record when questions come up.
Best practice is boring for a reason:
- keep Match communication factual,
- keep it brief,
- avoid ranking talk,
- avoid promises,
- avoid pressure,
- and save records of anything important.
If you want one final rule, use this one: If the message is necessary, professional, and free of ranking or coercive language, you're usually fine. If it feels like lobbying, fishing, or cornering, don't send it.