Grant compliance instrument · Rules —
Purchase
Eligibility
Ledger
Test a purchase against your award before the money leaves the account, then issue a signed and dated eligibility record as a PDF for your grant file. Every determination runs on the device, so it works parked behind a commissary with no bars of service.
Grant snapshot
$125,000 Enterprise Rising Initiative
WWW WASHME TV, INC Period of performance October 1, 2026 – September 30, 2027
- Approved award
- $0.00
- Committed
- $0.00
- Remaining
- $0.00
| Budget category | Approved amount | Spent so far |
|---|---|---|
| Total award | $0.00 | — |
Your grant file
Stamped onto the header of every record you issue.
Photograph the receipt
Start with the vendor’s paper while you are still at the counter — the reader fills in the purchase for you. No receipt yet? Skip ahead.
No receipt attached yet. Photograph the paper, or drag a PDF invoice here. The record can still be issued — the exhibit is optional, but a monitor will ask for it.
Read off the receipt
Check a purchase
Describe what you are about to buy. Anything read off the receipt is already filled in — check it against the paper.
Determination
Findings cite the authority they come from, so a monitor can follow your reasoning.
No determination yet. Fill in station 03 and the finding sheet prints here.
Sign & date
What turns a determination into a record you can file.
Run a check first. The signature block unlocks once there is a determination to attest to.
Issued records
One ledger for the whole award, on every device.
The program ledger is empty. Issued records land here — from this device and from every other install on the award — with their verdict, digest, and sync state.
This month’s reimbursement draw
The award pays in arrears: you spend, then ask for the money back on a Form SF-270 for one monthly billing cycle, with the paper behind every cost. This panel builds that request out of the records above — every box of the form, the monthly budget report, the itemized expense schedule, and one signed determination per line, in a single archive. Nothing is retyped and nothing is estimated: the figures are the ones the signed records carry. You key the boxes onto the official form, sign it, and send it.
The package will not be produced while these stand
Read before certifying
The form, box by box
Box 2 is the agency’s own use, box 12 is for advances, and box 13 is signed by hand on the printed form. Nothing here signs anything.
Details the ledger cannot know
Saved on this device only, alongside your grant file. None of it goes to the program database and none of it reaches the open SF-270 feed — an identification number on a public address is a disclosure, not a convenience.
What the envelope has to contain
The app drafts the covering email into your own mail app — send it from jefffiffie@wwwwashmetv.org — addressed to the program office with the package named in it, and stops. It does not send it, and it does not sign box 13. A request for federal funds is certified by the person whose name is on it, from their own account, after they have read what is attached.
The program office’s SF-270
The request for advance or reimbursement is filed from the intake portal, and its SF-270 tab reads this ledger live at the address below rather than having the figures typed into it a second time. Each claimable record arrives as one expense line — the date of the cost, the approved category it was charged to, the vendor, the invoice number, and a link to the receipt photographs behind it — so the form totals what the records say. There is no copy: the feed is computed from the ledger every time it is read.
Read-only, and open to anyone with the address. It carries vendor names, invoice numbers, and grant figures — the same standing as the program ledger it is read from. It carries no signature image and no receipt photograph, and nothing the portal does can reach back and change a record.
Share the app
Six ways onto the next phone, and a setup link that saves retyping the award.
Set up a second device on this award
A plain invite gets the app onto a phone with nothing in it — the award document then has to be typed into station 01 by hand. A setup link carries this device’s grant file inside it instead, so the second phone opens already on the right award. Everything it carries is listed here before you make one.
Treat a setup link like the award document it copies: send it to one person, not to a channel anyone can read. It carries no signature, no record, and no receipt, and it goes stale on its own after seven days.
Taking it off the grid
Install it
Add the ledger to the home screen and it opens full-screen like any other app, with no address bar.
Share the app with another phone — a link, a QR code, or a setup link that carries the grant file so the second device does not have the award document retyped into it.
Then lose the signal
The rules engine, fonts, logo, and PDF writer are cached on first visit. Checks, receipt photographs, signatures, and PDF downloads all run on the device — nothing round-trips to a server.
Sync catches up
Issued records queue locally and push to your program record the next time you have service. The record number is the idempotency key, so nothing duplicates.
And it tells you when it changes
Because the app is cached, it would otherwise keep running an old copy for weeks. When a build with new features is published, a notice names what changed and a Refresh button appears in the header. Your records, saved drafts, and photographs are untouched by it.
The manual travels too
The Operating Manual & Definitions — roles, the numbering system, verdict and finding definitions, and a full glossary — is cached with the app and downloads as a PDF with its own table of contents.