💡 Citizen science research bridge with personalized colony outcome benchmarking

[github-actions[bot]]

Summary

Enable structured, opt-in, anonymized data contributions to established research programs (Bee Informed Partnership annual survey, COLOSS international monitoring, university studies) directly from existing Broodly inspection and management data — eliminating redundant manual survey entry. In return, Broodly enriches the individual beekeeper's view with contextualized regional benchmarks: 'Your winter loss rate was 15% vs. your state's 38% average — here's what you did differently.'

Market Signal

The Bee Informed Partnership annual colony loss survey (now in its 19th year with Auburn/Oregon State/AIA) relies on voluntary retrospective questionnaires with low completion rates due to manual data entry friction. BIP's ArcHive app attempts to address this but remains a separate, standalone tool. Over 60% of beekeepers now use digital management software, yet none integrates structured research contribution. The gap between data-rich apps and data-hungry research is an untapped differentiation opportunity.

User Signal

Existing idea #366 (regional colony context dashboard with anonymous peer benchmarking) addresses the benchmarking display but not the structured data contribution mechanism. The PRD's outcome metric 'season-over-season improvement' depends on exactly this kind of longitudinal comparison. Broodly's product brief emphasizes community trust and recovery-oriented guidance — positioning as a contributor to the science that improves all beekeeping reinforces brand trust and public benefit narrative.

Technical Opportunity

Broodly's GraphQL API and structured inspection/treatment/outcome data maps well to the BIP survey schema (hive count, loss count, loss timing, management practices, treatment types/dates). A Go service adapter can transform Broodly data into BIP survey format for batch submission. The anonymization layer strips PII while preserving region, management patterns, and outcomes. Benchmarking return data enriches Broodly's recommendation engine context — regional loss rates and successful management patterns become inputs to confidence scoring.

Assessment

Dimension	Score	Rationale
Feasibility	med	Data mapping is straightforward; BIP API availability unknown — may start with export format
Impact	med	Differentiates through public benefit; enriches recommendation accuracy via regional baselines
Urgency	med	BIP survey runs annually in April; timing integration for the 2027 survey cycle

Adversarial Review

Strongest objection: BIP may not have a public API for automated data submission — they may require manual survey completion. Privacy concerns around even anonymized data sharing could spook users. Benchmarking data is only valuable with sufficient regional user density.

Rebuttal: Start with export-format compatibility (generate a pre-filled BIP survey PDF that the user submits manually) before pursuing API integration. Privacy is addressed through explicit opt-in, clear data inventory disclosure, and the existing local-only privacy architecture. Regional benchmarking can start with BIP's publicly available state-level loss data (published annually) — Broodly user density is not required for the initial version.

Suggested Next Step

Map Broodly's inspection/treatment/outcome data schema to BIP annual survey fields. Build a survey-export function that pre-fills BIP's questionnaire from Broodly data. Design the personalized benchmarking card using BIP's published state-level loss data as the initial comparison baseline.