Why this exists

A program director is at her kitchen table at 9:40 on a Tuesday night, comparing a stack of member timesheets against a payroll report, trying to figure out whether a discrepancy she found is a typo or a finding.

She is not underqualified. She is under-resourced, and she is holding a federally funded program together with a level of care nobody outside her office will ever see. What she needs isn’t a training webinar three weeks from Thursday. She needs an answer, tonight, from someone who has read the regulation.

That’s the whole idea here.

What you’ll find

One piece most weekday mornings, on a rotation through the subjects that actually generate findings:

Member Timesheets — Time and attendance documentation that survives a monitoring visit: what has to be on the record, who signs it, when corrections are allowed, and how hour categories get counted.
Member Files — Eligibility documentation, criminal history checks, enrollment and exit paperwork, and the retention rules that decide how long all of it has to stay put.
Progress Reporting — Writing progress reports that hold up: narrative that matches the data, performance measure results you can trace, and the discipline of reporting what actually happened.
Financial Reporting — Federal Financial Reports, match and cost share documentation, drawdowns, allowable costs, and reconciling what you reported to what your books say.
Performance Measurement — Building measures you can actually defend — instruments, data collection, documentation of results, and the difference between an output and an outcome.
Subgrantee Monitoring — Risk assessment, monitoring plans, site visits, timesheet and member file reviews, findings, and corrective action — the pass-through entity's whole job.
OIG Findings — What the AmeriCorps Office of Inspector General has actually flagged in recent audits, and what it means for how you run your program on Monday morning.
2 CFR 200 Basics — The Uniform Guidance, translated.

Every regulatory claim is cited so you can go read the source yourself. Where practice varies by grant or by commission, the article says so instead of pretending there’s one right answer.

How the writing gets checked

Before anything is published, each draft goes through a fact-check pass in which two separate AI models — one from OpenAI, one from Google — independently review the piece for regulatory accuracy, citation errors, and overstated claims. Their critiques get reconciled, and anything either model flags as unverifiable either gets a source or gets cut.

Then I read it. A machine can catch a wrong section number. It cannot tell you whether a paragraph will help a real person on a real Tuesday. That part is still mine.

Who I am

I’m Gary Kosman. I’ve spent about two decades around national service programs and the people who run them, mostly listening to what breaks.

In my day job I’m ceo, america learns. I’m telling you that up front because you should know who’s writing and what they do, and because a site that hides its author’s background hasn’t earned your trust.

This site is not an America Learns publication and it isn’t a marketing channel for one. Nothing here is a pitch. There is no product mentioned, no demo request, no gated download, no newsletter capture in exchange for a checklist. If a piece ever reads like an advertisement, I’ve failed and I’d like you to tell me.

What this isn’t

It isn’t legal advice, accounting advice, or an audit opinion. I’m not your grants officer and I’m not the Inspector General. The Uniform Guidance gets revised, AmeriCorps grant terms and conditions change every year, and your commission may impose requirements stricter than the federal floor.

Read the article. Then read the regulation. Then check your own terms and conditions. In that order.