If you have been doing this for a few years, you know the obvious things to check before you certify a Form 471. Service eligibility. Discount percentage. Form 470 requirements. Filing deadline. You watch all of it, and you have probably built habits and checklists around the parts of the application most likely to bite you.
The problem is that the denials that hurt the most rarely come from any of those places.
When a well-prepared application gets denied, the cause is almost always something that happened before the filing or after it. A procurement step that did not quite line up. A document nobody thought to keep. A change to the project that seemed routine at the time. Many of these issues never surface during the initial review. They show up down the road, during selective review or audit, after the equipment is installed and the funding has been disbursed. At that point, the conversation is not about approval. It is about recovery.
Here are five of the patterns I see most often on applications that looked clean at filing.
The first is using a contract that expires before the funding year starts, or one that doesn’t last the full year. You can fill out every online form correctly, but if the contract isn’t properly renewed, extended, or rebid, your application has a problem. We see this a lot with evergreen contracts. Service rolls on month after month, but without the right action on paper, you’re operating outside an E-rate-procured agreement. The oversight usually comes from one of three places: auto-renewal language never formally invoked, an extension option never exercised in writing, or a month-to-month continuation never reprocured. Any one of them can lead to a denial or a cost allocation. Operationally, nothing changed. With E-rate, you don’t have a valid contract for the year you’re claiming. For another look at how contract date issues are showing up in current Funding Year 2025 reviews, see E-rate Guide Todd Lawrence’s recent article on USAC’s contract date scrutiny.
The second is a procurement that followed every E-rate rule but ran afoul of state or local law. Reviewers increasingly look at whether the underlying procurement was legally valid in your state. Exceeding a state bid threshold while only collecting informal quotes, skipping a required board approval, or stretching a cooperative purchasing limit can all trigger an E-rate denial, even when the Form 470 process was handled correctly. E-rate rules sit on top of your local rules, not in place of them.
The third is documentation. Most applicants keep the contract and the winning proposal. Far fewer keep the losing bids, the supplemental notes that show how the decision was made, or the email trail documenting the procurement timeline. The first reviewer may never ask for any of it. A later reviewer almost certainly will, and by then the people who made the decisions may have moved on.
The fourth involves cooperative and state master contracts. The assumption that a state contract is automatically E-rate compliant is one of the most expensive assumptions in the program, and it is a denial category that keeps growing. Many cooperative agreements were not procured with E-rate language in the original solicitation, do not have a compatible Form 470 on file, or restrict who qualifies as an authorized user. If any of those is true, the contract does not protect you, even if you followed every step in the cooperative’s process.
The fifth is what happens after the award. A project that grows substantially in scope, adds sites that were not in the original solicitation, switches platforms, or converts from a build to a managed service can reach the point where the original procurement no longer covers what was actually delivered. The funding can be pulled even when the change was an improvement, because the question is not whether the new approach is better. It is whether the vendor you ended up with would have won the bid for the work you did.
There is a thread running through all five. None of them are eligibility problems. They are documentation and process problems. You may be fully compliant and still not be able to prove it years later, when proof is finally what you are asked for. And starting in FY2028, as my colleague Patrick Burke explains, more of that proof will be uploaded upfront through the new bidding portal.
I’ve always said, “Anyone can fill out the forms.” The key is knowing what goes into them. The protection is unglamorous, and it is not complicated. Keep more documentation than you think you need. Write down the procurement story while it is fresh, not when somebody asks for it. And before you certify, have someone outside the filing process look at the file with the question reviewers will eventually ask: not “is this eligible,” but “can we prove every step of how we got here.”
Want someone with experience across all five of these patterns to walk through your file with you? Schedule time to learn what working with a Guide Team could look like.
About the Author: Sean Lock is a veteran E-rate Guide at Funds for Learning with nearly two decades of industry experience. Since entering the field during the 2007 financial collapse, Sean has dedicated his career to helping clients—from individual charter schools to the nation’s largest districts—maintain compliance and maximize their E-rate benefits. When he’s not untangling federal funding regulations, Sean enjoys spending time outdoors and staying active, whether it’s running socially with his local group or training for a new personal best.
