OlenHub — Community Reach & Wellbeing Report

287

residents reached
≈ 1 in 38 people region-wide

8 / 8

North Slope villages
with users

473

Utqiaġvik events
published

307

questions asked
(events · jobs · "who do I call")

use the app
on their phone

active in one week
— record high

For scale: the entire North Slope is about 11,000 people spread across eight roadless communities (Utqiaġvik itself ≈ 4,900). Reaching 287 residents in the first three months ≈ 2.6% of the whole region — the same penetration as an app reaching ~110,000 people in metro Phoenix.

Reach, week by weekWeekly active residents — and the natural experiment that proves the channels work

88peak week

Reach, week by week

Unique residents per week · app + web

App on phoneWebsitea resident using both in one week counts once in the total, so app + web can exceed it

Why the dip matters: for five mid-summer weeks the automated outreach (push alerts, the weekly Facebook digest) was offline — weekly reach fell from 39 to 6. The first full week after it came back set the all-time high (88, including 84 residents reached for the first time), the next full week held 61, and the current week (Aug 23) has reached 30 residents in its first four days — 16 of them for the first time. Reach here is driven by working outreach channels a program can plug into, not luck.

What residents come forThe calendar is the product; village choice makes reach personal

100use the calendar

What residents come for

Surface	Residents
Community calendar	100
Event pages (lunches, health fairs, trainings…)	92
Notices & alerts (weather, closures, safety)	70
Ask Olen — AI community assistant	54
Resource directory	47
Volunteer	10

201 residents carry a self-chosen home village — reach is personal, not drive-by traffic.

Residents by self-chosen home village

Utqiaġvik

169

Wainwright

Kaktovik

Point Hope

Anaktuvuk Pass

Nuiqsut

Atqasuk

Point Lay

Counts are floors: residents who haven't picked a village yet aren't shown.

Community events — Utqiaġvik≈5 events a day, every day · monthly & weekly trend since launch

473since June 1

Community events on the calendar — Utqiaġvik

Published events by the week they took place, since the platform went live (June 2026)

473

Utqiaġvik events published
June 1 – Aug 27

108 → 169

June → July
monthly events

196

August so far
(through Aug 27 — already past July's total)

Week of Aug 9 —
busiest week yet

633

Across all 8 villages
combined

Counts are events published to the public calendar (community posts, flyers, feeds — reviewed before publishing), bucketed by the week the event took place, Alaska time. Early-June weeks partly reflect the pipeline still ramping up its source coverage; the underlying community activity didn't triple — our capture of it matured. Weekly cadence since: roughly 25–45 events in a typical week, with peaks in late June (Nalukataq season) and the week of Aug 9 (school start).

What residents ask forThe demand signal behind referrals — events, jobs, "who do I call", food, utilities

307questions

What residents ask for when no one is watching

Questions typed or tapped into the AI assistant, grouped by need — the demand signal behind referrals

What’s happening / events

Jobs, training & money

Food & meals

Children, youth & school

Elders & seniors

Heating, energy & utilities

“Who do I call?” / getting help

Health & clinic

Housing & rent

307 questions from 76 residents so far. "What's happening" leads — that is the front door — and right behind it sit jobs and money, "who do I call", utilities and food: exactly the calls a social-services program answers by phone today. Real examples from the log: "I need help finding a babysitter" (asked 4 times), "Will there be a Walking Wednesday tomorrow?".

Rails a program can use todayPush · SMS · digest · calendar · crisis protocols — working now

6channels live

The rails a program can use today

Working, in production now — each one is a referral or outreach pathway

Channel	What it does	Status
Free-food & meal alerts	A flyer that says "lunch provided" pushes to opted-in phones the day of the meal, linked to the event	Live
Safety & weather alerts	Urgent notices push to every subscribed phone + SMS	Live
Weekly community digest	Multi-photo calendar post into the community Facebook group every week	Live
Program events on the calendar	A program flyer becomes a dated, village-tagged event card — same-day, no IT needed	Live
Crisis resources	Crisis-line numbers surfaced with care protocols in the assistant	Live
Village SMS digests	"Text your village name" → weekly texted roundup for low-bandwidth households	Live (soft launch)

Example from this week: a tribal school's enrollment schedule went from a paper flyer to three dated calendar cards, live to every village, the same afternoon.

Concept: a Program WorkspaceWhat a customized social-services dashboard could look like (illustrative)

concept

Concept preview — a Program Workspace on top of this reach

What a highly customized social-services dashboard could look like, connected to the same community rails. Illustrative data — not real records

Social Services — Program WorkspaceConcept preview

128

Active cases across programs

New intakes this week

Referrals completed this month

Funder reports due in 30 days

8/8

Villages served

Needs attention

General Assistance recertification — 6 households dueDue this week

VR referral pending 9 days — training placementFollow up

Title VI quarterly — meals-served count ready to fileReady

Burial assistance case — documents complete, awaiting approvalIn review

Services by village · this quarter

Utqiaġvik

Point Hope

Wainwright

Anaktuvuk Pass

4 more villages

Digital intake — General Assistance (concept)

Head of household · name, tribal enrollment

Household members & ages

Income this month · other assistance applied for (payer-of-last-resort check)

Need type · food / clothing / shelter / utilities / emergency

Village · auto-tagged for per-village reporting

One intake feeds every downstream count — no re-typing into spreadsheets, no separate tally at report time. Works on a phone, in the village, on slow connections.

Ideas for where this could goOptions, not commitments — shared so you know what's possible

8directions

Ideas for where this could go

The platform is highly customizable. None of this is required or planned — these are simply options programs sometimes find useful, shared so you know what's possible

Federal report automation

The 477 Statistical/Narrative/Financial package, Tribal TANF data reports, SF-425, Title VI meal counts, RSA-911 — generated from day-to-day case entries instead of a year-end spreadsheet scramble.

FYI — programs often fund this through the TANF IT-cost exemption (45 CFR 286.55(c)) or a 477 consolidated budget

One client record across programs

Intake once — General Assistance, burial, emergency, Homemakers, VR, elder services all see the same household record. Ends the "five spreadsheets, one family" problem.

FYI — typically covered as program administration

Eligibility & payer-of-last-resort screening

Rules-based checks (household size, income, other assistance applied for) computed at intake, per the program's own policies.

FYI — typically covered as program administration

Per-village dashboards

Every count in this report split by the 8 villages — services delivered, unmet requests, outreach reach — because programs are funded and reported village by village.

FYI — part of each grant's existing reporting work

Elder services module

Title VI meals-served and caregiver-support counts collected as they happen; quarterly numbers ready to file.

FYI — Title VI administration commonly covers this

Surveys & community needs assessments

Push a survey to 100+ app users and SMS subscribers across all villages; results roll into the same per-village views.

FYI — broadband-adoption and planning funds commonly cover this

Outcome & spend tracking

Job placements, training completions, per-service cost against line-item budgets — the numbers funders actually score.

FYI — part of routine grant management

Community front door — already live

The reach in this report (calendar, alerts, AI navigator, free-food pushes) becomes the program's outreach and referral rail on day one. This part isn't a concept — it's running.

Already running — no build needed

No pitch here — the community platform above stands on its own, and it stays free for residents either way. If any of these directions is ever useful to a program, we'd start small and shape it together with the people who run the program. Whatever gets built: the program owns and can export its data. No lock-in. We don't resell it, and we don't train models on it.

What we don't have yet — and would build with a program partner: closed-loop referral counts (how many residents actually reached a service after seeing it here). Today we can show demand (help-seeking questions), reach (287 residents, all 8 villages) and delivery rails (push, SMS, digest). A partner program's services, contacts and events would plug into those rails, and we would count the taps and calls that follow — real referral numbers, reported back to the program.

Weekly detail (data table)The numbers behind the charts

Weekly detail

Week of	Residents	App	Web
2026-06-14	18	3	15
2026-06-21	38	5	33
2026-06-28	22	10	12
2026-07-05	24	8	16
2026-07-12	11	1	10
2026-07-19	12	2	10
2026-07-26	6	1	5
2026-08-02	37	9	28
2026-08-09	88	33	55
2026-08-16	61	26	35

How these numbers are countedReal-person counting standard; Alaska figures are floors

How these numbers are counted

Counted: unique people using the app or site, measured by product analytics (PostHog), with bots, link-preview crawlers and our own testing removed, and the founder's home state excluded entirely. Weeks are Alaska time. Alaska figures are undercounts — rural Alaska traffic often exits through Anchorage/Seattle relay nodes, so we also show village self-selection, which the resident does by hand. We would rather show you a smaller true number than a bigger soft one. Village counts are the one exception to the geography filter: choosing a village by hand is itself proof the person is local, so those are counted wherever the network says they are. Push reach is counted separately from app use — 81 residents have used the app, and 30 devices are currently subscribed to push notifications.