💡 Automated Post-Market Wrap-Up Reports for Grant Compliance

[github-actions[bot]]

Summary

After each market day closes (auto-checkout triggers via Cloud Scheduler), automatically generate a structured summary report: vendor attendance rate, check-in/checkout timeline, exception events, estimated customer engagement metrics, and notable trends. Reports are exportable in formats aligned with FMPP/LFPP grant compliance reporting requirements, saving managers hours of manual compilation per market day.

Market Signal

USDA announced $32.4M in FMPP/LFPP grants for FY2026, all requiring detailed impact reporting. Market managers currently compile reports manually from fragmented data sources (texts, emails, spreadsheets, memory). Seen Markets offers basic data export but not grant-formatted reporting. Marketspread focuses on invoicing and booth tracking, not impact metrics. The Farmers Market Evaluation Quick-Start Tool confirms that standardized market evaluation is an active area of investment. The grant compliance reporting gap is a significant unmet need across ~8,000 USDA-registered farmers markets.

User Signal

The PRD's Maria journey (Journey 4) centers on reducing manager coordination overhead — "By 8am on a normal Saturday she's already received 12 texts and 3 calls." The post-market reporting burden is the other side of the same problem: after a long market day, Maria must manually reconstruct what happened for her grant funder. Existing Discussion #450 (USDA Grant Reporting Dashboard) covers the seasonal dashboard angle; this proposal focuses on the per-market-day operational wrap-up — the atomic unit that feeds into seasonal reports. Discussion #389 (Market Health Analytics) covers trend insights; this covers the concrete, exportable daily record.

Technical Opportunity

All data needed already flows through the system: vendor check-ins (FR14), exception statuses (FR15), auto-checkout events (FR20c), and the append-only audit log (FR35-36). The Go domain event bus can trigger report generation on the auto-checkout event. Reports aggregate audit log data that is guaranteed to exist (PostgreSQL triggers, not application code). Cloud Scheduler (already planned for FR20c auto-checkout) can trigger wrap-up generation 30 minutes after market close. The report model is a materialized view over the audit log, queryable by market and date range for seasonal aggregation.

Assessment

Dimension	Score	Rationale
Feasibility	high	All required data already captured by existing architecture; report generation is a view over audit log data
Impact	high	Directly reduces manager pain (hours saved per market day); unlocks continued grant funding; differentiates from Seen Markets and Marketspread
Urgency	high	FMPP/LFPP grants have annual reporting deadlines; managers are compiling reports NOW with manual processes

Adversarial Review

Strongest objection: The data captured by early platform adoption (5 markets, 40 vendors) will be too sparse for meaningful grant reporting. Managers still need to supplement with external data, making the auto-generated report feel incomplete.

Rebuttal: Even partial automation saves significant time — a report that's 70% auto-generated and 30% manager-supplemented is dramatically better than 100% manual. The value scales linearly with adoption: as more vendors check in through the platform, reports become more complete. Early templates can include editable placeholder sections for manually-entered data (customer headcounts, revenue estimates) that become auto-populated as the platform matures. The "fill in the blanks" experience is still far better than "start from scratch."

Suggested Next Step

Review FMPP/LFPP grant reporting templates (available at ams.usda.gov/services/grants/fmpp) to identify required data fields. Design the wrap-up report data model as a materialized view over the audit log. Define the Cloud Scheduler trigger for post-market report generation (30 min after scheduled market close).