A rejection tells you almost nothing

A rejection feels like a verdict on you. It’s usually a statement about a fit, a year, and a budget.

That isn’t consolation. It’s what actually happened.

What a rejection genuinely can mean:

The cohort filled with people whose interests matched the faculty available that year. The one professor working in your area had no funding this cycle, or took a student already. The programme received more strong applications than places — which is normal, and means most strong applicants are rejected. A required element was missing or arrived late. Your file was strong and someone else’s was slightly better aligned.

What it usually does not mean:

That you aren’t capable. That you’d have been rejected last year, or would be next year. That every similar programme will decide the same way.

The same file, sent to the same programme in a different year, can get a different answer — because who is hiring, what is funded, and who else applied all change.

The genuinely useful thing to do:

Look at the pattern, not the individual result.

Rejected everywhere, including your safeties → the shortlist was miscalibrated, or something in the file was systematically weak. That’s real information and it’s fixable.

Rejected at reaches, admitted at targets → the list worked exactly as intended. That’s a success, not a partial failure.

Rejected at one programme, admitted at a comparable one → fit, not quality. Nothing to fix.

Waitlisted → you were competitive. Respond promptly, confirm continued interest, and if there’s a genuine update — a completed project, an improved score — send it once, briefly.

If you’re reapplying: ask for feedback where it’s offered; some programmes give it. Then change something real. The same file resubmitted is a coin flip on circumstances you can’t see. A file with a new project, a stronger letter, or a better-calibrated list is a different application.