One row per opportunity, one named owner
A grant tracker fails for predictable reasons: three partial copies exist, “status” means something different to each person who edits it, and rejected applications get deleted, taking their lessons with them. The countermeasures are rules, not features.
One file. Not one per program, not a personal copy per fundraiser. Every question of the form “where are we with that funder” is answered by this file or the file is broken.
One row per opportunity per cycle. A renewal is a new row, not an edit to last year’s, because last year’s row is now a record. The tracker must preserve both wins and losses so the organization learns without rewriting history: a funder that declined you twice with feedback is a different prospect from one you never approached, and only intact rows show that.
One named owner per row. A person, not a team. The owner is whoever answers for the next action, which is different from doing all the work.
Two things stay out. The tracker is not a second accounting system: award spending lives in your bookkeeping, and the tracker holds only the award amount, period, and report dates. It also never holds participant data. Names of people your programs serve do not belong in an operations file that half the staff can open.
Eight stages with entry criteria
Stages are the core of the tracker, and a stage without entry criteria is just a mood. This table is the decision gate for every move:
| Stage | An opportunity enters when… | Moved by |
|---|---|---|
| Research | Someone names the funder and a plausible program match | Anyone |
| Qualified | All six gates pass and the fit score clears your threshold in the eligibility matrix | Owner |
| Drafting | A go decision is recorded, the deadline is confirmed on the funder’s site, and an internal deadline is set | Owner |
| Submitted | The application is in and the confirmation evidence (receipt email or portal screenshot) is saved to the artifact folder | Owner |
| Awarded | A written award notice exists, with amount and period | Owner |
| Declined | A written decline exists, or the stated decision date passed 60 days ago with silence | Owner |
| Active | The award agreement is signed and report due dates are entered in the row | Owner |
| Closed | The final report is accepted, or a declined row has its outcome notes completed | Owner |
The single most common corruption is stage drift under deadline pressure: a prospect jumps from research to drafting because the deadline is Friday, and the eligibility screen happens retroactively, if ever. The entry criteria exist precisely to make that visible. If the criteria for qualified are not met, the row does not say qualified, whatever the calendar says.
Two boundary notes. Declined-by-silence needs the 60-day rule because some funders never write back, and a row stuck in submitted forever poisons your pipeline numbers. And the active stage is where most small organizations lose track of obligations: grantmakers’ own practice surveys, like PEAK Grantmaking’s review of grant reporting practice, show how varied reporting requirements are across funders, which is exactly why each award’s specific report dates belong in the row instead of in someone’s memory.
The columns that matter and why
Every column earns its place by feeding a decision. The tracker has 18:
| Column | Why it exists |
|---|---|
| Funder | The relationship you are managing |
| Opportunity | One funder can have several programs; screen each separately |
| Cycle year | Makes renewals new rows instead of overwritten history |
| Stage | The one-word answer to “where are we” |
| Stage entered | Exposes stuck rows; 90 days in drafting is a signal |
| Owner | The person who answers for the next action |
| Ask amount | Pipeline value and size-match sanity checks |
| Deadline | The funder’s date, confirmed on their site |
| Decision expected | Powers the 60-day silence rule |
| Next action | A verb and an object, “confirm receipt with program officer” |
| Next action due | The date the weekly review sorts by |
| Artifact folder link | One link to the submission, budget, and confirmations |
| Award amount | What was actually granted, often not the ask |
| Award period start / end | The window your reports and spending must cover |
| Report due dates | The obligations that outlive the celebration |
| Outcome | Awarded, declined, withdrawn, no response |
| Notes | Feedback, contacts, and the reason behind the outcome |
What is deliberately absent: probability percentages (small samples make them theater), a “priority” column (the fit score already ranks), and any budget detail beyond the ask and award (that lives in the grant budget workbook).
Grant tracking spreadsheetAll 18 columns from the table above, plus one clearly labeled fictional example row showing a completed submitted-stage entry. Import into Google Sheets or Excel and delete the example row once yours exist.
CSV templateWhen a CRM actually earns its cost
The weekly review that keeps it honest
A tracker decays without a rhythm. Twenty minutes a week, same day, owner present, three passes:
- Sort by next action due. Anything overdue gets done, rescheduled, or explicitly dropped. An overdue action with no decision is the first crack in the single source of truth.
- Scan stage entered dates. Rows stale for more than 30 days get a question: what criterion is unmet, and is anyone actually working on it? Some honest answers move rows backward, which is allowed and healthy.
- Check upcoming deadlines and report dates. Every deadline inside the next 45 days needs its internal deadline and its submission checklist started. Report dates get the same treatment as application deadlines, because to the funder they are the same kind of promise.
Handle declines in the same session, while the row is open. Close the record, write the outcome notes, and where the funder permits it, ask for feedback; Candid’s guidance on what to do after a rejection offers usable questions that respect the funder’s constraints. Then make a fresh fit decision for next cycle instead of assuming resubmission. A tracker full of honest declined rows is the cheapest funder research you will ever own.
One boundary, stated plainly: a tracker disciplines your process and protects your obligations, but it cannot guarantee awards, renewals, or any funder’s decision. What it guarantees is narrower and worth having anyway: that nothing is lost, nothing is ambiguous, and every hour you spend on grants is spent on a row that deserved it.