The Nightmare: The Email Says Yes, the Portal Says No
The email lands at 9:02 a.m. Subject line: congratulations. A program wants you. You click the portal link with your heart doing something deeply unprofessional in your chest, and the screen slaps you back. Access Denied. Or worse: the position sits right there in the Match list, grayed out, stamped Pending, while your credentials work everywhere else.
Take a breath. This is fixable.
Here's what's actually happening: you're staring at one of two problems wearing the same costume. Either it's a technical lock, a glitch, a session conflict, an automated security flag, or it's an administrative hold, which means an actual human at the program has gated your access pending review. They look identical on your screen. They are wildly different problems with wildly different fixes.
And the clock matters. You have roughly a 72-hour window to resolve the lock before it starts eating your rank list entry timeline. Not because the Match vanishes, but because programs move on, coordinators get buried, and you don't want to be the name they couldn't reach.
Here's your timeline.
Day 1 Morning: Immediate Troubleshooting & The Reset
Hour zero to hour four. At this point, you should be doing the boring stuff first, because the boring stuff fixes this more often than anyone admits. I've watched students sit on hold with support for three hours when the answer was a stale browser session. Don't be that story.
Work this checklist in order:
- Clear your browser cache and cookies. Frontend glitches are the number-one cause of phantom lockouts. The portal may be authenticating you correctly and then loading a broken cached session on top of it.
- Switch browsers. Chrome to Safari, Safari to Firefox. If it opens in one and not the other, congratulations, you never had an account problem. You had a browser problem.
- Switch devices. Laptop to phone, phone to tablet. This rules out account specificity. If you're locked everywhere, the issue is on the account side, and that tells you something important.
- Try an incognito/private window. Extensions, especially password managers, love to autofill old credentials into new login fields. I've seen a student locked out because her browser kept submitting her expired ID from a previous cycle while she typed the correct one. Maddening. Real.
- Check your email, including spam, for a fresh password reset link. If the system flagged a suspicious login attempt (new city, new device, VPN), it may have locked you out preemptively and sent a reset link you're ignoring. The reset flow is the portal's way of saying it panicked. Oblige it.
- Screenshot everything. Every error message, every timestamp, every status label. You'll want this paper trail by this evening.
By late morning, you'll know which universe you're in. One browser works? Glitch. Done. Locked on every device, every browser, after a clean reset? Move to the afternoon.
Day 1 Afternoon: Diagnosing the Cause (The Process Flow)
At this point, you should stop troubleshooting blindly and start diagnosing. The question is simple: Technical Lock or Administrative Lock?
Technical locks resolve in hours. Administrative locks resolve when a human decides they resolve. Your job this afternoon is to figure out which one you have, and you do that with three checks:
- Verify your User ID matches exactly how the program sees it. Not "close enough." Exactly. One transposed digit, one old ID lingering in your profile, and the system treats you as a stranger knocking on the door.
- Check your document transmission status. Look at your DEGs (documents electronically received) and your Caspar transmission status. If either shows incomplete or stalled, the program's system may be auto-gating access until the file is whole. That's administrative, and it's more common than the tech issues everyone assumes.
- Check whether the position status reads "Pending" versus "Access Denied." Pending usually points to a process still running on their side. Access Denied more often points to credentials or a flagged account.
Follow the flow. Don't skip steps because you're anxious, anxious skipping is how Day 1 problems become Day 3 problems.
Day 1 Evening: The Tactical Call to the Coordinator
By evening, if the lock persists, at this point you should pick up the phone. Yes, the phone. Email is a fine paper trail, but coordinators triage their inboxes like an ED during flu season, and a polite call cuts the line.
Before you dial, have three things in front of you:
- Your ERAS User ID
- Your Application ID
- Your Case Number (from any support ticket you opened this morning, you did open one, right?)
Now, the call itself. Be warm. I mean this as strategy, not etiquette: coordinators control the gate you're stuck behind, and they remember the applicant who was gracious under pressure. They also remember the other kind.
Ask two specific questions:
- "Has my application been manually reviewed, or flagged for further screening?" This tells you whether a human hold exists.
- "Does my status show as 'Under Review' or 'Locked' in your internal system?" These are not the same thing. Under Review means a person is reading your file, that's often a good sign wearing an ugly mask. Locked means a system rule is blocking you, and someone needs to flip a switch.
Write down the name of whoever you speak with and what they promise. "It should clear by tomorrow" from a named human is worth ten automated replies.
Day 2 Morning: Document Transmission & Verification
Day 2. At this point, you should assume the lock is document-related until proven otherwise, because that's where most Day 2 mysteries live.
Open your MyERAS application and audit every required CAF section:
- Transcripts, marked Received?
- Letters of Recommendation, all assigned writers' letters actually in?
- Photo, personal statement, MSPE, complete and transmitted?
If anything shows as missing or pending, that's almost certainly your trigger. Programs' systems routinely auto-lock applications with incomplete files, it's not personal, it's a workflow rule doing its dumb, diligent job.
Your morning checklist:
- Upload any missing files immediately. Not this afternoon. Now.
- Confirm the transmission status changed after upload, don't assume it did.
- Build a list of the specific missing items (DEGs, LoRs) that may have caused the initial lock, and email that list to the coordinator you spoke with yesterday so they know it's resolved. Make their job easy. Easy gets unlocked.
Set your expectations on timing, because it differs sharply by cause:
Technical locks typically clear in 2-4 hours once support touches them. Administrative holds run 24-48 hours because they depend on a human's review queue. Knowing which clock you're on saves you a day of refreshing the portal every six minutes. It changes nothing. I've tested this extensively, against my will.
Day 3 Morning: Unlocking & Acknowledging the Offer
Morning three. At this point, you should see movement, and your job shifts from fixing to confirming.
Run the final checklist:
- Verify the position still shows as available and your status now reads Active or Accepted. Screenshot it. Frame it emotionally.
- Read the rank list instructions on the program's specific page inside the MyERAS portal. Programs bury real requirements there, deadlines, supplemental confirmations, quirks that vary by institution.
- Acknowledge the offer. This is the step people fumble: you must formally acknowledge the position before you can edit your overall rank list. Unlocking the portal isn't the finish line. Acknowledgment is.
Conclusion: Summary of the Scramble
Seventy-two hours. That's the whole arc: reset and rule out glitches on Day 1, diagnose and call by evening, fix documents on Day 2, confirm and acknowledge on Day 3. The applicants who lose ground aren't the ones who got locked, locks happen constantly, they're the ones who panicked, skipped the boring checks, and burned their window.
Administrative errors are common, fixable, and almost never personal. Stay systematic, keep your screenshots, be kind to coordinators.
Your takeaways, pinned above the desk:
- Verify your User ID and Match ID the moment you see a lock. Exact match. No assumptions.
- Know your lock type. Technical glitches resolve in hours; administrative holds need a coordinator's hand.
- Confirm your document transmissions (CASPAR/DEGs) are active before you expect full access.
And one last thing: stay calm. In this process, a locked door usually means someone on the other side is still reading your file, which is more than half the applicants can say.