💡 Regulatory-grade treatment logbook with structured compliance export

[github-actions[bot]]

Summary

Auto-generate regulatory-compliant treatment records from voice inspection logs, with structured export (PDF, CSV, machine-readable XML/JSON) meeting EU Regulation 2023/564 requirements for electronic plant protection product records. Country-specific templates for treatment documentation including batch numbers, withdrawal periods, application methods, and dosage tracking.

Market Signal

EU Regulation 2023/564 became effective January 1, 2026, mandating electronic, machine-readable records for plant protection products — including varroa treatments used by beekeepers. Over 60% of beekeepers now use digital software for record-keeping (source), but no beekeeping app specifically addresses regulatory-grade structured export for government submission. Growing regulatory pressure across EU and US markets creates a compliance-driven demand regardless of user feature requests. Competitors like Apiary Book and HiveTracks offer basic treatment logging but nothing formatted for regulatory submission.

User Signal

Existing Discussion #85 covers treatment compliance and PHI alerts but focuses on in-app tracking rather than regulatory export. Sideliners selling honey must comply with treatment record requirements. Beekeeping associations increasingly recommend digital record-keeping to members. The PRD already defines data export resolvers (Story 4.5) — this extends them with regulatory-specific formatting.

Technical Opportunity

Treatment data is already captured in Broodly's voice-driven inspection flow (observations table with structured_data JSONB). The work is adding regulatory-specific fields to the treatment logging schema, building an export template engine, and country-specific format mappings. Minimal new infrastructure — primarily data formatting and export generation via Cloud Run worker. The existing ExternalSignal adapter pattern in the architecture could serve as a model for country-specific export adapters.

Assessment

Dimension	Score	Rationale
Feasibility	high	Treatment data already captured; primarily formatting/export work on existing data model
Impact	high	Regulatory mandate creates non-optional demand; premium feature for EU expansion; competitive differentiator
Urgency	high	EU 2023/564 already in effect; beekeepers face penalties for non-compliance now

Adversarial Review

Strongest objection: Most hobbyist beekeepers (Broodly's primary Newbie segment) don't think about regulatory compliance. This could be a solution looking for a problem in the core target audience.

Rebuttal: True for backyard hobbyists with 1-2 hives, but sideliners (10-100+ hives) and anyone selling honey MUST comply. EU 2023/564 is non-optional. The feature is low-cost since treatment data is already captured — it's primarily formatting and export. It becomes a premium selling point for EU market expansion and a competitive differentiator that no beekeeping app currently offers. Beekeeping associations recommending Broodly to members as "compliance-ready" is a powerful acquisition channel.

Suggested Next Step

Audit EU 2023/564 and US state-level treatment record requirements to define the minimum structured fields needed. Design an export template engine supporting PDF/CSV/XML formats. Add regulatory fields (batch number, withdrawal period, application method, dosage per hive) to the treatment observation schema in the existing structured_data JSONB model.