What a committee reads first

Files aren’t read the way they’re assembled. Knowing the order changes what you put where.

The exact process varies, but the pattern is consistent enough to plan around.

First: the eligibility check. Often administrative, sometimes automated. Degree, GPA against the minimum, test scores, required documents present. No judgement — just whether the file proceeds. A missing transcript stops everything here, and nobody will chase you for it.

Then: a quick scan. A reader with many files spends a short time forming a first impression. Transcript, CV, and the opening of your statement. This is where “does this person look plausible for this programme?” gets provisionally answered.

Then, if it survives: the statement, properly. This is the only document where you choose what’s said, and by the time it’s read carefully the reader already has an impression from the scan. Your statement is either confirming that impression or correcting it.

Then: letters. Read for specificity and for anything that contradicts the picture. A letter that’s warm but vague is a soft negative — it suggests the writer didn’t have much to say.

For research programmes: a supervisor’s opinion, which can override much of the above in either direction.

Three practical consequences:

Front-load your statement. The first two lines are read in the scan phase; the rest may not be. Your strongest, most specific claim goes at the top — not a paragraph of build-up.

Your CV is scanned, not read. Relevant items visible in the top third. Ordering matters more than completeness.

Nothing should contradict. If your statement claims a research focus your CV and letters don’t support, the mismatch is more damaging than either document being weaker. Consistency is checked, informally, at every stage.

Committees are reading to allocate limited attention. Making that easy is a real advantage, and most applicants make it harder without realising.