Why Your Awards Program Is Harder to Run Than It Should Be
You didn’t ask for an audit. But if someone sat down with you for an hour and mapped out exactly how you’re currently managing your awards or grant program — every tool, every workaround, every folder structure, every email thread you’ve quietly decided to leave unread until Thursday — what would they find?
I’ve seen enough of these programs to make a reasonable guess. And the picture is almost never as clean as the process documentation suggests.
What’s Actually in the Folder
Let’s start with the submissions. You’re probably collecting them through one of three methods: a form builder that was never designed for award applications, an email inbox that doubles as both intake and support channel, or a spreadsheet that someone built three years ago and nobody is quite confident enough to change.
The spreadsheet is the most interesting artefact. It’s where award program management gets quietly expensive. Not because spreadsheets are inherently bad — they’re not — but because they were built for data storage, not program coordination. Every time a new cycle starts, someone copies the old one, deletes half the rows, and spends forty minutes reformatting columns that shouldn’t need reformatting. The institutional knowledge lives in whoever built it, and if that person is on leave during judging week, you’ll feel it.
That’s observation one.
The Review Process, Which Is Several Processes
Now let’s look at how you handle evaluation. Most programs I see at this stage have a review process that technically works but generates a disproportionate amount of coordination overhead. Judges receive a link, or a PDF packet, or a spreadsheet with a scoring tab — and then someone has to chase them. Individually. Sometimes twice.
The follow-up emails are usually written fresh each time because last cycle’s email lives in someone’s Sent folder and copy-pasting feels like it should take ten seconds but somehow never does. Conflict of interest tracking, if it happens at all, is manual — a checkbox in a form, or a quick conversation that may or may not have been documented.
Scoring data comes back in different formats. Someone aggregates it. That someone is you, or a colleague who has other things to do, and the aggregation happens in a spreadsheet that is different from the submissions spreadsheet but needs to talk to it.
That’s observation two.
The Applicant Experience Nobody Talks About
Here’s something worth paying attention to: applicant drop-off. It’s one of the most under-tracked metrics in grant administration, and it’s almost always higher than program managers expect. People start applications and don’t finish them. They email asking whether they submitted correctly. They miss the deadline because the confirmation email went to spam or because there was no confirmation email.
You probably don’t have a clean number for this because the data isn’t in one place. You might know how many complete submissions you received. You’re less likely to know how many people started and abandoned, or why. That missing information is costing you program quality — you’re selecting from whoever made it through the process, not necessarily whoever was best positioned to apply.
Most programs also offer no meaningful communication between submission and decision. Applicants sit in silence for weeks, then get a templated email that took thirty minutes to personalise and send in batches. The experience of being an applicant is largely invisible to the people running the program, which makes it hard to improve.
That’s observation three.
Reporting That Requires Its Own Project
At the end of the cycle, someone needs to report. To a board. To a funder. To senior leadership. To the public, if there’s a transparency obligation.
That report does not exist anywhere. It needs to be assembled from the submissions spreadsheet, the scoring spreadsheet, the notes from the deliberation call, and whatever was written in the email thread that became the de facto decision record. If you want to show year-over-year trends — applicant volume, demographic breakdown, award distribution — you’re comparing two spreadsheets that don’t share a schema, possibly from two different program coordinators with two different column-naming conventions.
This is not a minor inefficiency. The time it takes to produce a credible post-cycle report in a manually managed program is routinely underestimated, and it grows every year you don’t standardise the data structure.
That’s observation four.
What a Better Baseline Looks Like
None of this requires a dramatic transformation. The programs that run cleanly aren’t necessarily more sophisticated — they’ve just resolved the coordination layer.
Submissions come through a structured intake process that captures consistent data. Reviewers access everything in one place, scores are logged automatically, and conflicts of interest are flagged before they become problems. Applicants receive timely, accurate communications without someone manually triggering each one. At the end of the cycle, the data is already in a state that supports reporting — because the structure was built in before cycle one, not reconstructed after cycle three.
The operational load doesn’t disappear, but it shifts. Less time on logistics. More time on the parts of the program that actually require human judgment — like deciding who deserves to win.
This is what modern grants and awards administration can look like when the tooling is built for the actual workflow rather than adapted from something adjacent to it.
The Honest Takeaway
If the audit I’ve walked through sounds accurate — not exaggerated, not a worst-case scenario, but accurate — that’s worth sitting with. Not because the way you’re doing it is wrong, but because the friction is optional. Most of it is.
AwardScience was built specifically for this: AI-native award and grant management that handles the coordination layer so you can focus on the program itself. If you’re heading into a new cycle and the spreadsheet is already open, it might be worth a look before you copy last year’s template.
