Why Reviewers Reject Your Proposal

A common reason why grants don't get funded is because even though you have milestones, they don't describe how you're reducing your risks. And I saw this pattern with Sarah when she was working on her ARPA-H full application and she was trying to translate a diagnostic platform towards clinicals. Now, on the surface of her ARPA-H federal contract, everything looks so structured, like milestones, timelines, and clear progression. But if I put my reviewer hat on and you read the proposal closely, you can see your milestones being described as demonstrate feasibility, optimize assay performance. And that's where her proposal broke down because as the reviewer, you're not asking if progress will happen. Rather, you're asking what success actually means. For instance, reviewers want to know, for example, after you do these experiments, is sensitivity going to increase from 70 to 90%? Is the limit of detection going to be increased by twofold? At what point does your experiment fail? And without these quantitative descriptions, frankly, your milestones don't tell reviewers how you plan to reduce your risks. They just describe motion, and motion for these federal grants and contracts simply is not enough. So bottom line, if your milestones aren't quantitative for any federal grant or contract and they can't define success, then they don't reduce your technical risks. So when you're writing your application, make sure to turn every milestone into a measurable technical gate with clear success metrics and failure criteria. Because at the end of the day, reviewers aren't just funding your idea simply. They're funding your ability to de-risk and remove the doubt in their mind. That's how funding decisions get made in federal grants and contracts. So let me know what you think, if this is helpful, but curious to know what your thoughts are in the comments below.