Grant compliance · human in the loop

Grant compliance, extracted from the source and turned into work.

Upload or paste a grant agreement. The system proposes every deadline, report, restriction, and match requirement — each cited to its contract section — for a human to review before anything touches your records.

Start with one grantSee how it worksA missed report isn’t paperwork — it’s a clawback.
FSC_25-26_contract.pdf · p. 14
§601  REPORTING

601.B.b  Monthly Cash Request on
         City forms, due the 5th.
601.B.a  Grantee shall submit a Monthly
         Expenditure Report on City
         forms no later than the 15th
         of each month.
§403.B  Unallowable costs: lobbying,
         entertainment, fines...
Extracted · proposed
reportneeds review

Monthly Expenditure Report

schedule
monthly · day 15
source
§601.B.a
confidence
92%
Approved · tracked
Jul 15Aug 15Sep 15Oct 15Nov 15Dec 15Jan 15

12 dated tasks — assigned, on the calendar, and audit-logged.

35
pages in one award contract
51
dated obligations inside it
25
distinct requirements
0
high-stakes fields auto-approved
JULAUGSEPOCTNOVDECJANFEBMARAPRMAYJUN51DATED OBLIGATIONSone contract · one year

Hover any point — each is a real obligation, cited to its contract section.

reportreviewhard deadline
Drawn from the contract’s actual terms by the same recurrence engine that tracks your deadlines — no chart library, just data and geometry.

Every obligation, dated

Enter each schedule once. Every occurrence is generated.

“Expenditure report, 15th of every month” becomes twelve dated tasks across the grant year. Quarterly reviews, one-time closeouts, and the hard deadline where a late invoice simply isn’t paid — all plotted, all tracked.

Every point on this dial is a real obligation from a real $1.5M city contract, drawn by the same recurrence engine that runs your deadlines.

From contract to control

One pipeline, and a human gate where it counts.

  1. 01

    Upload

    PDF, pasted text, or a forwarded email.

  2. 02

    Extract

    Proposals with a verbatim source citation.

  3. 03

    Review

    A person confirms every high-stakes field.

  4. 04

    Track

    Approved obligations become dated tasks.

  5. 05

    Audit

    Every change, immutable and attributable.

Review before records change

AI can propose. Only a person can approve a high-stakes field.

Deadlines, dollar restrictions, and match requirements never enter your records until a human confirms them. It isn’t a policy we hope holds — the database itself rejects any unreviewed write to a canonical field.

  • No inbox scanning — you forward or upload, never connect a mailbox.
  • Every proposal traces to the exact contract sentence it came from.
  • The audit log is append-only; /activity and /changes are derived from it.
  • One-click export of everything. Software you can leave is software you can trust.
Proposed · awaiting approval
deadlinehigh-stakes

Final closeout invoice due

§406 · Aug 14, 2026 · 96% confident

ApproveReject

Until approved, it exists only as a proposal.

Source-backed review

Each proposal links to the verbatim clause it came from — verify in one click.

Portfolio tasks

Everything your org owes any funder, in one list, sorted by what's due next.

Calendar & timeline

Recurring schedules expand into every dated occurrence, automatically.

Change history

Before → after on every field, with who and when — built for the auditor.

Spreadsheet import

Bring the Excel file you track grants in today; columns map themselves.

Reminders that find you

Digests and escalations reach the right person before a deadline slips.

See your grant obligations before the next deadline.

Start with one grant — upload the contract, review the obligations, and watch a year of deadlines lay itself out.

Start with one grant