The letter arrives about six weeks out. A federal program monitor is coming to review how the district used its Title I funds, or its IDEA funds, or whichever award happens to be up this cycle. Six weeks sounds like plenty of time, but it rarely is.
The monitor's list gets real specific, real fast: documentation connecting one purchase order to one allowable use, time and effort logs for staff paid partly out of the grant, proof that a particular professional development session tied back to the goals in the approved application. None of it is an unreasonable ask. It's just scattered across three departments, two of which have had turnover since the money was spent.
Somebody remembers the invoice for the reading intervention materials sitting in a shared drive somewhere, though not which folder, since the person who filed it moved districts last spring. Somebody else is fairly sure a justification for a mid-year budget amendment exists somewhere: an email thread, a filing cabinet, maybe a personal Google Drive nobody thought to check. The district never set up a system where the answer to "why did we spend this" outlives the person who made the call in the first place.
So six weeks turns into a scramble, first to find the data, then to make sense of it together. A finance clerk and a program coordinator end up pulling threads that should take minutes instead of days, because the expenditure record, the grant terms, and the outcome data have never lived in the same system. The monitor is doing their job, asking a fair question the district was never built to answer on short notice, and the cost of that shows up as staff time that could have gone anywhere else.
Districts that clear these visits without the scramble tend to share one habit. Every dollar carries its justification from the moment it's spent, instead of getting reconstructed six weeks later under a deadline. A purchase order links back to its grant, and the grant carries its own allowable-use terms with it, so whoever spent the money doesn't have to be the one explaining it a year later, because the explanation got captured automatically instead of sitting in someone's memory, or on their hard drive.
This is the layer Eddi builds. If the next monitoring letter already makes your stomach drop a little, see what it looks like when the answer's easy to find at eddi.org.
