Nine minutes a file
Talk to anyone who has worked an admissions cycle and you’ll hear the same number, give or take: nine minutes a file. That’s roughly what’s left once you divide the season’s applications by the people and the days available to read them.
Nine minutes to open a transcript, an essay, two recommendation letters, a list of activities, and a personal statement — and to form a fair, defensible read. Do that forty, fifty, sixty times a day, for weeks, and the work stops being about students. It becomes about the stack.
The stack is the enemy, not the applicant
Every reviewer we’ve spoken to wants to give each file a careful look. The constraint isn’t care — it’s volume. The first pass through a file is mostly mechanical: confirm the documents are all there, reconcile the numbers, get the shape of the story. That mechanical pass is where fatigue accumulates, and fatigue is where inconsistency creeps in. The applicant read at 9am and the one read at 6pm deserve the same bar.
That’s the part we think software should carry: the reading, not the deciding.
The line we won’t cross
ProgramApply prepares files. It summarizes, it scores against a rubric you control, it flags what’s missing or inconsistent, and it routes each file to the right reader. It does not admit anyone. It does not deny anyone. Every recommendation arrives with its reasoning attached, traceable to the source line, so a human can agree, override, or dig in.
We built it this way because admissions is high-stakes, audited, and personal. An opaque model that hands down verdicts is the wrong tool. A transparent assistant that gives your team back its hours — and its evenings — is the one we’d want if we were still reading the stack ourselves.
More notes soon on how we handle the parts that matter most: bias, privacy, and the audit trail.
← All field notes