Read a sample: 1. The Work Begins After the Award
The award notice arrives, and for a moment the hard part appears to be over. You prepared an application, explained what your business wanted to accomplish, gathered the requested documents, and waited for a decision. Now someone has said yes.
That yes matters. It may also mark the beginning of a different kind of work.
A grant award usually comes with expectations about how the money may be used, what activities the recipient will carry out, what records must be kept, and what information must be reported. The details vary by award. Some funders ask for a short narrative and a spending summary; others require specific forms, supporting documents, milestone updates, or prior approval for certain changes. Your job is not to guess which approach applies. It is to find out what your award requires and build a manageable way to follow it.
For a small business owner, this work can feel like one more administrative burden competing with customers, employees, and cash flow. But grant reporting does not have to mean reconstructing months of activity the night before a deadline. A simple system, started early and maintained regularly, can turn reporting into a series of small tasks.
This chapter introduces those tasks and a fictional business that will appear throughout the book. Its situation is hypothetical, but its questions are familiar: What did we agree to do? Which expenses belong to the project? How can we show what happened? And what should we do when the plan changes?
A grant can support work that might otherwise be difficult to undertake. It can also create responsibilities that continue after the money has been received—or after the project itself has ended.
As the recipient, you may need to show the funder:
- How the award money was spent, or how reimbursement was calculated.
- Whether the spending fit the approved purpose and applicable conditions.
- What work was performed during a reporting period.
- Which milestones were completed, delayed, or changed.
- Whether an issue requires notification or approval.
- Where the underlying records can be found if questions arise.
Not every award requires every item on this list. The point is to treat the list as a set of questions, not as a substitute for your agreement.
Reporting also serves a practical purpose for your business. When expense records, project notes, and deadlines are kept together, you can see whether the work is progressing as expected. You can notice a missing invoice while the vendor still remembers the transaction, rather than discovering the gap months later. You can identify a delayed delivery while there is still time to ask the funder about its effect on a milestone.
Good reporting is not about making a project look flawless. It is about giving an accurate account that the funder can understand and that your records can support.
Throughout this book, we will follow Harbor Light Bakery, a fictional small business owned by Maya Chen. The bakery sells bread and pastries and has a small team. Maya handles many of the administrative tasks herself, with help from Luis, a part-time operations assistant.
In this hypothetical example, the bakery receives a $20,000 grant from a fictional local business development fund. The award supports a project to purchase a commercial oven and provide related staff training. The funder approves the following project budget:
The hypothetical agreement establishes an award period, requires a progress report during the project and a final report after it, and directs the bakery to request written approval before making certain budget or project changes. It also describes the records the bakery must retain. The precise terms of this fictional award will matter whenever Maya decides what to spend, what to report, or whether to contact the funder.
Maya is pleased to receive the award. She is also busy. The oven supplier wants a decision, Luis is juggling deliveries, and the bakery has customers to serve. It would be easy to save the award email, buy the oven, and assume the reporting details can wait.
Instead, Maya pauses long enough to ask a few foundational questions:
1. Which documents govern the award?
2. What work and spending have actually been approved?
3. When must the bakery report, and what must each report cover?
4. What evidence should the bakery collect as the project unfolds?
5. Who will keep track of the work?
She does not need a sophisticated grant-management department to begin answering them. She does need a clear place to keep the answers and a habit of updating it.
The application tells an important part of the story. It describes what you proposed and, often, why the project matters. But the application alone may not tell you what was ultimately approved.
A funder might approve less money than requested, revise a budget category, set a different project period, or add conditions before issuing the award. The final documents may also explain reporting procedures that were not included in the application. Depending on the award, the application or parts of it may be incorporated into the agreement, so it should not be discarded. But neither should it be treated automatically as the final word on every requirement.
Consider Maya’s hypothetical project. Suppose her application requested funds for an oven, installation, training, and a marketing campaign announcing expanded production. The approved budget shown above includes the oven and related installation and staff training;…