Preserve source truth
Tracker totals and reconciled manual attendance stay distinguishable. Combined figures are conservative rather than cosmetically perfect.
Operational intelligence03 / 04
GoCreate Insights
Turn messy operational evidence into decisions you can trust.
MEMBERSAPPLICATIONSTRACKERPAPER
→RECONCILIATION LAYERConfidence, not guesses.
source-aware · reviewable · privacy-safe
2,383member records2,125application rows513paper sign-ins
ROLE / OWNERSHIP
Data model · reconciliation logic · analytics UX · privacy controls
STATUS
Operational analytics
TIMELINE
2026
Operational reporting becomes dangerous when unlike data sources are flattened into one apparently precise dataset. GoCreate had master records, applications, tracker data, and historical paper sign-ins with different levels of certainty.
The system needs to make the information useful without hiding uncertainty, inventing matches, or exposing private data to every browser that needs aggregate reporting.
KEY DECISIONS
The work behind the screen.
Turn uncertainty into a product state
High-confidence matches can count automatically; possible matches become review work; unreadable rows remain unresolved instead of guessed.
Design privacy into the payload
Bulk browser analytics omit direct contact details, exact birthdates, medical-alert contents, emergency contacts, and raw assistance questionnaire text.
Make numbers inspectable
Important aggregates are connected to records or source explanations so a decision-maker can understand why the number exists.
A single “perfect” attendance number would look cleaner but would be less truthful. The system keeps source differences and review queues explicit.
WHAT THE BUILD PROVES
Evidence, not adjectives.
- Ambiguous records remain visible instead of being silently guessed
- Leadership reporting preserves the difference between tracker data and reconciled manual evidence
- Bulk analytics payloads omit sensitive contact, medical, and emergency data
Next.js 16React 19TypeScriptPython data pipelinesRechartsOCR reconciliation workflowVercel
VERIFIABLE EVIDENCE
Inspect the work.
- 2,383 master member records represented in the documented build.
- 2,125 application rows and 513 detected paper sign-in rows are reconciled as distinct evidence.
- Browser analytics payloads are deliberately PII-safe.
Have something complicated that needs to feel simple?