Bow Valley · Alberta

Know what's moving
through the valley.

One official wildlife channel for the Bow Valley, built to keep people safe, keep wildlife alive, and put real tools in a warden's hand.

Built here Priced like infrastructure, not software
Corridor app icon
Corridor
Why Corridor exists

Three things a phone line can't do, and lives depend on all three.

🐾

Wildlife lives

Habituation and human contact are documented drivers of bear deaths. Corridor attacks the causes, no crowd-summoning sightings, attractants routed fast, closures reaching phones at the trailhead.

🛡️

Human safety

The family that gets the closure alert before the trailhead. The tourist who reaches the right dispatch in two taps instead of googling. Fewer surprise encounters at the moments that matter.

🧭

Rangers empowered

A triage queue, one-tap advisories, follow-ups and a live dashboard. Corridor decongests the phone line so wardens spend their hours on the field, not the call log.

The problem, in your own words

You already wrote this problem statement.

Most

Elk cause the greatest number of human–wildlife occurrences in Banff, and increasingly occupy Canmore's golf courses, playing fields and school yards.

Documented
~197

Bear removals recorded in the valley across the reporting period, road and rail mortality, translocations, destructions.

Documented
5 + 1

Five black bears and one wolf killed on the Trans-Canada in a single year.

Documented
Direct
link

Grizzly mortality correlates directly with the rate of human contact.

Documented

Sources: Bow Valley Human–Wildlife Coexistence Report · Coexistence Status Report 2019.

The system today

Two phone numbers and a Friday blog post.

Phone-only

Sightings go to Kananaskis Dispatch and Banff Dispatch by voice call. No map. No memory.

A week late

Public safety info arrives as a weekly written bear report and periodic advisories, not at the moment of relevance.

Four authorities

Which office to call depends on where you're standing. Tourists, the majority of encounters, know none of them.

No loop

Reports vanish into call logs. Reporters never hear back. The next family on the trail knows nothing.

What Corridor is

The phone line for the 5% that's urgent. Corridor for the 95% that isn't.

Public app

For everyone in the valley

  • Advisory map, areas, never pins
  • Guided, structured reporting
  • Species-tiered alerts
  • What-to-do education, in the moment
Warden

For the people who protect it

  • Triage queue
  • One-tap advisories
  • Follow-ups that close the loop
  • Live coexistence dashboard
Your systems

Never a bypass

  • Dispatch-first triage
  • Report A Poacher routing
  • Data exports you own

An aggressive bear in a schoolyard produces one thing: a full-screen button that dials your dispatch.

Why nothing else comes close

Six things no competitor, or status quo, can match.

01

Dispatch-first by architecture

Emergencies reach your line in two taps, correct number auto-selected. A layer over your system, never a bypass.

02

Built against the attract paradox

Areas not pins, species-tiered delays, no photos-with-locations, no browsable feed. The app that can't create a bear jam.

03

The closed loop

Every reporter gets a status trail and a follow-up. Trust compounds; repeat calls stop.

04

You hold the keys

Advisory authority, sensitivity-matrix sign-off, data ownership and a community-layer kill switch, yours, in writing, day one.

05

Structured coexistence data

Every report feeds the maps and annual reports you already produce by hand.

06

Priced like a utility

The entire hosting stack costs less than a coffee a month. The next slide proves it.

Where it saves lives

Wildlife lives, measured. Human safety, reduced where it matters.

Wildlife, where the bodies are counted

A fed bear is a dead bear. Corridor removes the crowd-summoning sighting, routes attractant reports fast, and delivers closures to phones at the trailhead instead of a week later.

People, stated honestly

Serious attacks are rare, so we won't claim a body count. What Corridor changes is exposure at the tail: fewer surprise encounters, the right dispatch in two taps, the schoolyard elk reported in 40 seconds instead of never.

Grizzly in the Bow Valley
Grizzly mortality correlates directly with the rate of human contact. Corridor attacks that variable.
Infrastructure priced like a utility

Annual infrastructure: ~$40.

Not a typo.
Photos processed on the reporter's phone, 95% smaller, location-stripped → Cloudflare R2: 10GB free tier, zero egress fees.
Pilot math: ~50 reports/day peak × 1.5 photos × 250KB ≈ 7GB/year → inside the free tier. Calculated
Database (Neon) free tier · maps on open tiles ($0 API) · app distribution $0, Apple waives developer fees for government and eligible nonprofits.
Typical civic vendor build for a two-app system
$150K+
plus five-figure annual hosting.
Corridor runs on free tiers by design.
Precedent & autopsy

BC built the first one. It proved the demand, then it died. Corridor is designed around why.

3,600+
WARP alert
subscribers
467K+
alerts
delivered
30K+
wildlife calls/yr
to the COS line
Why WARP died (public record, inferred)
Why Corridor can't die that way
Orphan ownership. A side project inside an education nonprofit; no agency owned it, no budget line named it.
Published under your account and data, with a paid maintainer contract and a handover clause. Institutionalized on day one.
Dependent data. Lived off a once-daily COS feed it didn't control.
Corridor generates its own primary data: reports come to it. Dispatch integration is additive, never foundational.
No operational users. A public window, not a working tool; nothing inside an agency broke if it vanished.
Warden is how coordinators work daily: triage, advisories, follow-ups. Kill the app and you kill a workflow.
Dead-end reporting. Public submissions were never sent to the COS; they sat on a map.
The closed loop is the architecture: triage, right authority, review, advisory, follow-up to the reporter.
Unaffordable rebuild. Died mid-way through a stalled v2 beta; tech debt outran an education budget.
Deliberately boring stack, coffee-priced infrastructure, tiny surface area, and a named annual renewal metric so the funding conversation stays small and evidenced.

The appetite didn't die, the operating model did. Corridor is the corrected experiment, and the Bow Valley can host the only living system of its kind in Western Canada.

The pilot & the ask

Six months, Canmore-anchored, ~$25K all-in, split four ways.

Where the money goes
Build & design (2-person, under your Apple account)$18–22K
Bug-fix bank · ops & tooling$4.5K
Insurance & legal (E&O + data-sharing agreement)$2.5K
Market comparison for the build alone: $90–120K. Pilot-priced because the builder lives in this corridor.
Suggested split, conference-booth money
Canmore
~$8K
Alberta Parks
~$8K
MD of Bighorn
~$4K
Biosphere (in-kind)
~$8K
The easy yeses: a named coordinator · your data-sharing template · sensitivity-matrix authority stays yours · letters of support for matching grants. Year 2 (~$28–35K) renews only if the deflection metric is met.
Who's asking

A Cochrane resident with a decade of government-grade software.

  • Senior product designer for healthcare practice software.
  • UK Government Digital Service alumnus, work projected to save £300M.
  • Designer-engineer: the prototype in your hands is his build, supported by a named second engineer.
  • Lives in the corridor this app serves, with a kid and a dog who hike it.
Corridor
Built here, for here.
Architecture · the sync loop

One event moves through both apps as a single closed loop.

Public app
Visitor reports a sighting
Guided, structured form — species, behaviour, area
Photo compressed on-device · 95% smaller
Privacy gate: exact GPS stripped before upload
upload
Shared core
Sort, dedupe, hold the truth
Cluster nearby reports
Auto severity tier
Precise coords held secure
Every record logged
Emergency? A full-screen button dials your dispatch — never routed around you.
triage
Warden
A coordinator acts
Review in the queue, merge duplicates
Publish one advisory — area, severity, guidance
Follow-up sent to the original reporter
The loop closes back to the public. The published advisory lands on nearby phones as a soft zone with guidance — the same event the visitor reported, now protecting the next family on the trail.
Architecture · where data travels

A deliberately boring stack — which is why it costs ~$40 a year.

1 · On the device
The phone does the heavy lifting
Photo resized & compressed — 95% smaller
EXIF & exact GPS stripped locally
≈ 250 KB leaves the phone
2 · In transit
A thin API layer
Tiny JSON payload + one small image
Same endpoints serve app & Warden
3 · At rest — free tiers
Cloudflare R2 — images$0 egress
Neon Postgres — recordsfree tier
Open map tiles$0 API
App distribution$0 gov
Precise coordinates gated. Public apps receive a soft zone; only Warden resolves the exact point.
Partners own the data. Clean exports feed the coexistence maps and reports you already produce.
The system in action

One report. Two surfaces. A closed loop.

Not a mockup, the live prototype you can open from the next slide.

Corridor public app
Public app
Advisories, guidance, one Report button
Corridor Warden dashboard
Warden
Triage the queue, publish an advisory, close the loop
Corridor

The question isn't whether this can exist.

It's whether it exists with your name on it.

The prototype you just used is live today. Scan to open it, the deck's only job was to get the phone out of your pocket.

Corridor
/corridor · public app
Warden
/corridor/warden · ranger tool
Password BOWVALLEY