AHeadline PerformanceAll Views
BData Quality & Improvement TargetsInternal Only
Be honest about what's not yet captured well. These are the year-over-year improvement targets for the team — they should not appear in the Funder or Public views.
CForm 10 — Performance MeasuresFunder Primary
The funder-facing summary required by the SCFA contract. Each category counts only the activity types that map to that performance measure — community engagement (events, surveys, volunteer outreach) sits outside Form 10 and is reported in Tab 2.
DClient DemographicsAll Views
Age Group
Ethnicity
Insurance Status
Cross-Tab: Age × Ethnicity
Cross-Tab: Age × Insurance
ZONE COMPARISON Tucson · Phoenix · Other AZ · Virtual
Service Units by Zone
Clients vs Form 10 Services by Zone
Zone Detail Table
ETelehealth EngagementAll Views
Clients Served via Telehealth
Telehealth Channel Breakdown
FTotal Service UnitsAll Views
Every encounter type SCFA logged this reporting year, grouped by purpose. Form 10 covers most categories below except Community Engagement (events, surveys, volunteer outreach — see Tab 2).
GClient Encounter DetailPhase 2 Live
Every client/family encounter the SCFA team logs — site, contact channel, outcome, and whether the person is new to the program. These dimensions live in the SCFA Data Collection template today; the Activity Tracker will write them straight to this dashboard.
Visits by Site / Hospital Partner
Contact Channel & Outcome
New Contacts & Newborn Screening (NBS)
HService Performed ByPhase 2 Live
Splits each logged service by who delivered it — SCFA staff, Community Health Worker, or volunteer — so the funder can see workforce reach and the BWYAP CHW model in action.
Services by Staff vs. CHW vs. Volunteer
CHW Reach by Zone
⌘Notes & DefinitionsReference
📑Official Source ReportsReference
The funder filings of record this dashboard is built from. Open any report to verify the numbers above against the original HRSA submission.
ACommunity Encounters & Events — At-a-GlanceTab 2
Activity outside the Form 10 client-services scope: medical/general community touches and events SCFA hosted or sponsored.
BCommunity EncountersPhase 2 Live
Audience Mix
By Region
How They Heard of SCFA
CEventsPhase 2 Live
Events by Type
Events by Location
Hosted vs Sponsored
DTop Event PartnersTab 2
EMass Communication & OutreachPhase 2 Live
Broadcast outreach that isn't a one-to-one encounter — newsletters, social posts, texts, and email blasts — plus how many individuals each touched and how many opted into the contact list. Captured in the Mass Communication section of the SCFA Data Collection template.
By Channel & Individuals Reached
Contact List Used
Category & Email Sign-ups
Currently shown: realistic stub data so the Board can see what this tab will look like. Phase 2: replace the wide CSV template with a mobile-friendly logging form keyed by Service Date + Zone + Performed-By, auto-tagging to community/event categories. Live writes to this dashboard, no Excel re-keying.
A360 SCD Hub MembershipTab 3
BMembers by Group & RoleTab 3
By Role Type
By Region
By Group Type
CSickleSense Coin LeaderboardsTop 10 · De-Identified
Leaderboards display de-identified handles only — actual member identities live behind WP login. Reset monthly. Sorted by total coins per type.
DCoin Totals & Level DistributionTab 3
Coins Awarded by Type
Member Level Distribution
EStreak Badges EarnedTab 3
FTracker Snapshot (Aggregate)De-Identified
Entries by Tracker Type
Pain-Level Distribution (Entries)
GWebsite Analytics (GA · MonsterInsights)Phase 2 Live
Top Pages by Views
Referral Source Mix
HBuddyBoss App EngagementPhase 2 Live
Top App Screens
Push Notification Performance
ITest Drive FeedbackReviewer · Admin Only
🎯 Tester completion
⭐ Per-feature summary
📊 Data visualizations
📋 Full comment log
AContract Review — Response & StatusInternal · Board
In response to the board technical review (Kevin Johnston, June 2026) on the 360° SCD Hub General Contract for Services (July 27, 2023). Each item below shows FFH's position and current status. Full detail lives in the companion Response & Resolution Log and Technical Documentation Packet.
BThe 7 Points — Position & Status
| # | Point raised | FFH position & status | Class |
|---|---|---|---|
| 1 | Source code unchanged 2–3 yrs | By design (wrapper vs. plugin layer); architecture map to be delivered | CONTEXT |
| 2 | No build instructions (Exhibit B #12) | Owed — committed; build runbook in closeout packet | ACTION |
| 3 | Bugs unresolved / response time | 12 items already logged & tracked; triage within 48-hr window | ACTION |
| 4 | iOS vs Android ~1.5-yr gap | Different store regimes + SCFA-held Apple account; resync committed | CONTEXT |
| 5 | Google health-apps declaration | Owed maintenance; status + resolution in Android pass | ACTION |
| 6 | Google Play 16 KB page size | Owed maintenance; confirm / remediate in same pass | ACTION |
| 7 | Texas SB 2420 (age verification) | New law post-dating scope; applicability assessment to be delivered | FORWARD |
2 points are context (defensible by design), 4 are committed deliverables, 1 is forward-looking. Concede the fair, provide context on the misread, never admit breach.
CDocumentation & Paper Trail
DWhat We're Delivering & Companion Documents
- Architecture map — where every piece of functionality lives
- iOS + Android build runbook (point #2)
- Status sheet for the store-compliance items (4–6), resolved in one Android pass
- Triage of the 12-item issues register, within the 48-hour window
- Texas SB 2420 applicability assessment
- A 45-minute technical working session before Kevin steps off the board