Scholarship Review: Awards That Stay Inside the Budget and Every Program Cap

A fixed fund, four program caps and letters that arrive late

A scholarship cycle starts with a fund that has a fixed budget and a cap for each program. Applicants are scored on a rubric that weighs academic record, need, the essay and two recommendation letters, ranked within their program, and awarded down the list until the budget or the cap runs out. The hard calls come after that, when a letter arrives late, a cap changes or an awarded student withdraws.

Packets and recommendation letters arrive through a Dropbox file request, the rubric and budget sheet are in Google Drive, applicants and recommenders write to the scholarship inbox in Gmail, the financial aid office works in Outlook, and close-out files go to the office's SharePoint library. With no single tool holding the awards, the running total often lives in a spreadsheet that someone recomputes each time, and settled amounts drift.

Who works in the room

The office keeps the award register as a Database App in the room, so the committee and the agents read and write the same records. Questions about scores or awards go to Ada, the room's default agent. Budget and cap questions reach Myco, and every message from an applicant or recommender goes to Ryan. When a late letter lands, Ryan files it to the packet and opens a thread for Ada whose first message names the applicant and the letter, and Ada re-scores that applicant alone.

The award cycle at a glance

Every stage ends with the committee chair. Nothing changes in the register or leaves the office without that approval.

Late letters, a cap change and a withdrawal

Late letters are the most common change. An automation flags every applicant record in the register still missing a letter when the deadline passes. When two recommenders send letters a week late, the coordinator confirms the committee will accept them and Ryan files each one to its packet. Ada re-scores those two applicants only. Awards already made are not re-ranked, so a student told yes on Monday is not moved by someone else's letter on Friday.

A withdrawal runs the other way. An awarded student takes another offer and declines. Ada marks the award withdrawn, and Myco confirms that under the fund's policy the freed amount does not return to the pool this cycle. The thread records the decision and the reason, so nobody re-awards the money in a hurry before the close-out.

What the checks catch

• A budget total rebuilt by recomputing awards instead of summing the amounts already stored on the register
• A late letter used as a reason to re-rank applicants who already hold awards
• Budget or cap room treated as free after a withdrawal, when the policy keeps it unallocated this cycle
• A close-out that skips a program because it made no awards

What stays with people

• Approving every score, award and withdrawal before the register changes
• Deciding whether a late letter is accepted at all
• Sending award notices and replies, which Ryan drafts in Gmail and Outlook
• Signing the close-out file for each program

Integrations in this workflow

Kylon is not a scholarship management system and it does not replace one. It holds the award register as a Database App and coordinates the files and mailboxes the office already uses.

• Dropbox
• Gmail
• Google Drive
• Outlook
• SharePoint
• Slack

• Dropbox collects application packets and recommendation letters through the office's file request
• Google Drive keeps the rubric, the budget sheet, the program caps and the committee summary
• Gmail is the scholarship inbox for applicants and recommenders, and every reply from it is sent by a person
• Outlook carries award confirmations to the financial aid office, each sent by a person
• SharePoint holds the office library, where one close-out file per program is filed after the chair approves
• Slack is where committee members discuss packets and the coordinator posts the summary

Where to start

The first cycle needs one thing built: the award register as a Database App in the room. Connect the Dropbox folder where packets land, and let the room guidelines carry one rule: stored award amounts are never recomputed or re-ranked, and the committee chair approves every change to the register.

“Once a student has been told yes, the cycle works around that award, not through 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.