Project management for grant-funded organizations
Project management built for federal grant teams
Run your awards like programs — tasks, milestones, timelines and status reports. Kharazm turns that everyday work into the audit record 2 CFR 200 requires, built as you go instead of rebuilt the week before your Single Audit.
How it works
Four steps, about thirty minutes to set up
If you have used any project tool, this will be familiar. The difference is what comes out the other end.
-
Set up the award
Funder, award number, Assistance Listing, period of performance — copied straight off your Notice of Award. Mark whether you pass money through to subrecipients.
-
Plan and assign the work
Tasks with owners and due dates, milestones on a timeline, a board and a list view. Your reporting deadlines sit on the same timeline as the work, so nobody discovers a due date the week it lands.
-
Publish your status report
Draft the period report from what actually happened, then publish it. On publication it is fixed and versioned — and you can give a funder or auditor read-only access to that one award, nothing else.
-
Export the audit pack
One printable document plus CSV: every published report, the evidence index, decisions with written resolutions, and the subrecipient monitoring log. Assembled, not reconstructed.
Why it matters
What you get that a generic project tool cannot give you
Generic task trackers hold none of these in a form that survives scrutiny, because everything in them can be changed after the fact by anyone with edit rights.
Immutable performance reports
You draft a period report, then publish it. On publication it becomes a fixed, versioned snapshot with the evidence that justified it frozen alongside — attributed to a named person at a recorded time. It cannot be edited afterwards. A correction becomes a new version; the original still stands.
Subrecipient monitoring file
Each subrecipient carries a written risk determination and the basis for it, a monitoring plan proportionate to that risk, and a dated log of monitoring events with findings and corrective action. Built as you go, not reconstructed the week before the audit.
Decisions with written resolution
Risks, assumptions, issues and decisions each carry an owner, a due date and a written resolution. When a monitor asks why you rebudgeted in March or why a milestone moved, the answer is a record with a name on it — not a search through somebody's mailbox.
Scoped external access
A funder, an auditor or a subrecipient can be given a read-only view of one award and nothing else. Access is decided on the server from the session, never from the request — so a scoped viewer cannot reach another award by editing a link.
Uniform Guidance
What the regulation asks for, and where it lives in Kharazm
Kharazm does not interpret the Uniform Guidance for you and is not legal or audit advice. It gives each obligation a place to live so the record exists when somebody asks for it.
| Citation | What is required | Where it lives |
|---|---|---|
| 2 CFR 200.329 | Monitoring and reporting program performance for the period. | Published performance report, fixed on publication and versioned. |
| 2 CFR 200.332 | Pass-through entities must risk-assess and monitor subrecipients, and follow up on findings. | Subrecipient record with written risk basis, monitoring plan and dated monitoring log. |
| 2 CFR 200.303 | Effective internal control over the award, with evidence that it operated. | Server-enforced roles and a per-organization audit log of material actions. |
| 2 CFR 200.334 | Records retained three years from submission of the final expenditure report. | Retention policy per workspace, with legal hold blocking deletion while active. |
| 2 CFR 200.337 | Awarding agencies and auditors must have access to records. | Scoped external viewer for a single award, and audit pack export. |
Citations are provided so you can check our work. Confirm your own obligations with your awarding agency and your auditor.
Scope, stated plainly
What Kharazm is not
A tool that claims everything is harder to trust on the things that matter. These are deliberate exclusions, not a roadmap.
Not a grants accounting system
Kharazm holds no general ledger, no budget-versus-actual engine, no drawdowns and no indirect cost calculation. Your accounting system knows where the money went. Kharazm records what the program did, who decided it, and what evidence supports it — and will not become an accounting system later.
Not a document store
Kharazm links to evidence where you already keep it and records what it is, who added it and when. It does not host a second copy of your files. That keeps your documents under your own retention policy and keeps Kharazm out of the business of guarding them.
Not a pre-award tool
No prospect research, no proposal assembly, no submission workflow. Kharazm begins at the Notice of Award and covers the period you are accountable for afterwards.
Not a blank canvas
Kharazm is a project management tool — but one where the grant work is already modelled. Awards, reporting deadlines, subrecipients and evidence are built in, not custom fields you configure for a fortnight. If you want a general-purpose tool to shape however you like, buy one of those instead.
Who uses it
Built for the organizations that carry the obligation
Federal grant recipients
Nonprofits, tribal organizations and research groups running several concurrent awards with quarterly narrative reporting and a Single Audit at year end.
Fiscal sponsors and pass-throughs
Organizations that move money onward and therefore carry subrecipient risk assessment and monitoring duties for every project under their EIN.
Foundation grantees
Teams reporting to program officers who increasingly want the same evidence discipline federal funders ask for, without the federal paperwork.
Try it on a real award for 14 days
Set up a single award, publish one report, and see whether the record holds up. Paid tiers begin when you add a second and third award. External viewers — funders, auditors, subrecipients — are always free.