GrantConsoleWhat "compliance" means once the money has landed
For a recipient, compliance is not an abstract virtue. It is the set of obligations written into an award you have already accepted, plus the rules that come with the funding source, plus your own policies. Concretely, it usually means: report on the funder's calendar, spend restricted money on what it was restricted to and within the period it was restricted to, keep proof that the work happened, get approval before you change something material, and close the award out cleanly.
For federal awards, part of that calendar is set in regulation rather than by the program officer. Financial reports are collected no less than annually and no more than quarterly; quarterly and semiannual reports are due no later than 30 calendar days after the reporting period, annual reports no later than 90 (2 CFR 200.328). Performance reporting follows the same cadence (2 CFR 200.329). Everything final — reports and the liquidation of financial obligations — lands within 120 calendar days of the end of the period of performance (2 CFR 200.344). Foundation and corporate awards set their own dates, and there the award letter controls.
The regulation also puts the watching itself on you: recipients "must monitor their activities under Federal awards to ensure they are compliant with all requirements and meeting performance expectations" (2 CFR 200.329). That is the sentence software can help with. It cannot help with the sentence before it.
This page is for the person who has to answer for that monitoring — a grants manager, a finance lead, an executive director with 5 to 25 restricted awards and no appetite for a surprise. It describes what a recipient-side compliance tool should do, how GrantConsole does it, and where the tool stops and your judgment starts.
Why explainable rules beat a compliance score
Most tools that watch grants eventually offer a number: a health score, a compliance percentage, a coloured dial. The number is appealing in a board deck and useless at a desk, for three reasons.
It compresses unlike things. A grant with a report due tomorrow and no evidence collected, and a grant whose budget is drifting 18 points ahead of the period, can produce the same score. They need completely different responses on completely different timescales.
It hides the responsible record. "72% compliant" does not tell you which deliverable, which line, which person. Someone still has to go looking, which is the work the tool was supposed to remove.
It cannot be audited later. Six months on, nobody can reconstruct why the score was 72 that week. A warning that says what triggered it survives in the record; a number does not.
The alternative is a rule that states its own threshold and shows its evidence. "Spending ahead of schedule by 18 points" is checkable: you can see the elapsed share of the grant period, the share of the budget spent, and the difference. If you disagree with the rule, you can argue with a stated threshold. You cannot argue with a dial.
The rules GrantConsole runs on every grant
GrantConsole evaluates eleven rules against each grant record. Every warning names the rule, states the numbers behind it, and links to the underlying records — the deliverable, the task, the budget line, the report.
| Rule | Fires when | Why it exists |
|---|---|---|
| Deliverable past due | An open deliverable's due date has passed | The single most expensive failure, and usually the most visible to a funder |
| Tasks overdue | Internal tasks on the grant are past due | Missed reports are usually a chain of small internal slips |
| Evidence gap, urgent | A report is due within 14 days with evidence items still missing | The last two weeks are when evidence becomes impossible to reconstruct |
| Evidence gap | A report due within 30 days is missing evidence | Early enough to still collect it from the people who have it |
| Spending ahead of period | Burn exceeds the elapsed share of the grant period by more than 15 points | Restricted money spent early becomes a shortfall later in the period |
| Burn behind period | Burn trails the elapsed share by more than 15 points | Underspending is a real risk: unspent restricted funds, and questions at renewal |
| Grant period ended, work open | The period of performance has ended with deliverables still open | Closeout cannot proceed honestly while obligations remain |
| Closeout window | Closeout falls within 30 days and work is still open | 120 days sounds generous until the last two weeks |
| Renewal unplanned | A renewal window opens within 90 days with nothing scheduled | The reapplication conversation has its own clock |
| Application due | An application is due within 14 days | Pipeline work competes with post-award work for the same people |
| No owner assigned | The grant has no named internal owner | Most missed deadlines were known dates that belonged to nobody |
Two design choices behind that table are worth naming. Burn is measured against the elapsed grant period, not the fiscal year or the calendar — a grant 58% spent at 42% elapsed is running hot in March or in September. And money is stored and summed as integer cents, so the totals a report shows are the totals the export contains.
Evidence lives on the obligation that needs it
The usual evidence failure is not that documents are missing. It is that they exist, scattered, and nobody can prove which document supports which claim two years later.
GrantConsole attaches evidence to the deliverable that requires it, so the question "what is still missing for the Q3 report?" has an answer that a rule can check — which is exactly what the two evidence rules above read. When a report is assembled, the reporting packet is built from those attachments rather than from a folder someone has to remember to look in, and CSV exports carry the same underlying records out.
Alongside that sits an activity history: a record of what changed on the grant and when. This is the quiet feature that matters during an audit or a leadership handover. Access is role-based — owner, manager, member, viewer — and enforced by the server rather than by hiding buttons in the interface. The specifics of how the application protects accounts and uploads are on the security page, and they are deliberately modest: GrantConsole holds no certification of any kind, and this page will not imply one.
Where this software stops
An honest scope is part of the product, so here is the boundary in plain terms.
- It tracks what you enter. If a reporting deadline was never recorded, no rule will fire for it. The first month with any tool of this kind is data entry, and it is the month that determines whether the rest works.
- It does not read your award. Extracting obligations from an award letter or a federal terms-and-conditions attachment is human work.
- It does not judge allowability. Whether a specific cost may be charged to a specific award is a question for your finance lead and, on federal awards, for the cost principles and your auditor.
- It is not your accounting system. Budgets and burn here are for managing the grant; your general ledger remains the system of record for the books.
- It does not make you compliant, and it does not satisfy an audit. It helps you notice, in time, the things an auditor would later ask about.
If your situation is mainly "we cannot agree what the award requires," you need a careful read of the terms with your auditor or a grants attorney before any tool will help. If it is mainly "we know what we owe and we keep finding out late," that is the problem this category solves.
One more scoping note, since it changes what "current" means: a proposed rewrite of 2 CFR part 200 was published in the Federal Register on 29 May 2026, with comments closing on 13 July 2026. It is a proposal, not law, and nothing in it is in force today — the dates and thresholds on this page are the ones currently in the CFR. Re-check the sections you rely on rather than trusting a summary, including this one.
How to evaluate any tool in this category
Whatever you end up choosing, these five questions separate a compliance tool from a dashboard.
- When it warns you, does it name the rule, the threshold and the record — or just change a colour?
- Is budget progress measured against the grant period, or against the calendar?
- Can evidence be attached to the specific obligation that requires it?
- Is there a durable record of who changed what, available after the person has left?
- Can you get your data out — as reports and as plain CSV — without asking anyone?
You can check all five against GrantConsole without a sales conversation: the live demo is seeded with two example organizations and eighteen grants, and it needs no sign-up. Look at a grant that is already at risk and read the reasons it gives.
If you want the wider category first, the grant tracking software page covers deadlines, budgets and evidence as a workflow, and the post-award grant management checklist is the process this software is meant to support — worth reading first if you are still deciding whether you have a tooling problem or a process one.