Program Admissions: Waitlist Offers Made in Order, Cohort by Cohort

Offers, deposits and a waitlist that has to move in order

An admissions round has a fixed shape. Withdrawals and duplicate applications come out first, the rest are scored against the rubric from transcripts and test reports, and each cohort fills its seats from the top. Then deposits come due, some offers lapse, a cohort gains seats, a few admitted students defer, and every empty seat has to go to the next person on that cohort's waitlist and nobody else.

Applicant records are in Salesforce, transcripts and test reports sit in Box, the rubric and the officers' note on withdrawals and duplicates are in Google Drive, letters go out from the office's Outlook mailbox, and the committee talks in Slack. The usual failure is quiet: a seat backfilled from the wrong cohort, or a file re-scored when someone should have read the status the committee already set.

Who works in the room

The office keeps one Kylon room per admissions round. Nova is the default agent and takes questions about a file or a score. For the first read it splits the Box files across parallel helpers and gets one scored list back. Anything about seats, deposits or the waitlist reaches Fin, which already owns that work in the thread, and Ada picks up the committee summary when the chair posts it. When Fin frees a seat, it mentions Nova with the cohort and the next waitlisted applicant so Nova can confirm the file has not changed since scoring.

A round from first read to final offers

Every agent scores and seats from the same rubric and seat counts, both named in the room guidelines. Every status change in Salesforce waits for the admissions director.

When deposits lapse and seats move

The deposit deadline is where the round changes most. An automation runs the deposit check the morning after the deadline, officers confirm which deposits arrived, and Fin lists every unpaid offer by cohort. Each released seat goes to the next applicant on that cohort's waitlist, in order, and the thread shows who moves up and who stays. If the evening cohort loses three offers, three evening applicants move up, even if a full-time applicant has a higher score.

A seat increase and a deferral follow the same rule. The director posts that the full-time cohort can take two more students, and Fin proposes offers to the top two on that waitlist. A student who defers frees a seat in the cohort they were admitted to. In every case Fin reads the stored statuses instead of re-running the rubric, so a decision the committee settled is never quietly changed.

What the checks catch

• A withdrawal or duplicate named only in the officers' note, which has to come out before anyone is ranked
• A seat count rebuilt by re-scoring applicants instead of reading the status already on the record
• A waitlisted applicant the committee summary never mentions, which the check lists anyway
• A backfill taken from another cohort's waitlist, or out of waitlist order

What stays with people

• Approving each status change, release and offer before Salesforce is updated
• Settling borderline files and any rubric question the committee raises
• Sending every offer, release and waitlist letter, which Fin drafts in Outlook
• Signing the final offer list

Integrations in this workflow

Kylon is not an admissions CRM and it does not replace the office's Salesforce setup. It sits across the records, files and mailbox the office already uses and holds the coordination between them.

• Box
• Google Drive
• Outlook
• Salesforce
• Slack

• Salesforce holds applicant records, statuses, waitlist positions and the final offer records
• Box stores transcripts and test score reports, read file by file during scoring
• Google Drive keeps the rubric, cohort seat counts, the officers' withdrawal note and the committee summary
• Outlook is the admissions mailbox, where offers and notices go out as drafts a person sends
• Slack is where the committee discusses files and the chair posts the summary

Where to start

Try one round with one cohort first. Connect the Salesforce object that holds applicants, give Nova read access to the Box folder of transcripts, and write the rule that matters in the room guidelines: seats are filled only from the same cohort's waitlist, in order, and the admissions director approves every offer before a letter is drafted.

“The waitlist is a promise about order, and every backfill keeps it.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.