Same 27 indicators. Peacetime or crisis. The system does not change — the signal does.Same 54 indicators. Peacetime or crisis. The system does not change — the signal does.The form stays the same. The numbers tell you when the ground moved.The form stays the same. The numbers tell you when the ground moved.
Three CSIs. Nine modules. Twenty-seven PIs. Designed for weekly field observation in normal conditions. When the river takes the bridge — the signal moves. The architecture was already watching.Six CSIs. Eighteen modules. Fifty-four PIs. Federation-level visibility across every community below. When the delivery chain collapses — the signal moves. The architecture was already watching.Nobody changes the form when the storm arrives. The field officer fills in the same numbers. The system reads the difference. The coordinator sees the name.Nobody changes the form when the storm arrives. Fifty-four observations. Same logic. The federation sees which name needs action.
The architecture principle, applied here:
Nobody redesigns the observation system when the crisis arrives.
The field officer who records passable roads every week in peacetime
records the same PI when the road is gone.
The number drops. The XmR catches it. The CPL — set by the community head before crisis season —
catches what was already failing before the storm hit.
Two different failure modes. Both named. Both require coordinator response.
The form does not change. The number changes.
You record what you see — same as every week.
When the road is blocked, the number goes down. The system reads it.
The floor was set before the storm. If the number was already below the floor before the event — that is the real story.
Deployment architecture — 3 CSIs · 9 Modules · 27 PIs · 3 CRIsThree areas. Nine teams. Twenty-seven things to observe.
STA
Stability — Physical infrastructure and resource readinessStability — Are the roads, buildings, and supplies holding?
Safety — Population protection and field hazard conditionsSafety — Is everyone accounted for and protected?
M4: Household Hazard Exposure · M5: Population Accountability · M6: Peace, Order & Field Actor ReachHouseholds at risk · Who is accounted for · Field officer coverage
CON
Continuity — Access, service delivery, and reporting chainContinuity — Can the community still reach its people?
M7: Access & Mobility · M8: Health & Social Service Delivery · M9: Records, Communication & ReportingRoutes open · Services delivered · Reports reaching the municipality
Tap any CSI → Module → PI → field formTap to read the signal
STA
StabilityStability
Physical infrastructure and resource readiness confirmedRoads, water, and supplies holding
▼
M1
Infrastructure IntegrityRoads and buildings
▼
STA-M1-P1
Local roads and paths confirmed passableRoads passable this week
90 %⚠ Slope
STA-M1-P2
Bridges and crossings confirmed intactBridges standing
12 bridges✓ Stable
STA-M1-P3
Structures with roof or wall damage reportedBuildings with damage
≤2 structures✓ Stable
M2
Water and SanitationWater and sanitation
▼
STA-M2-P1
Households with confirmed safe water accessHouseholds with clean water
342 households✓ Stable
STA-M2-P2
Functional sanitation facilities confirmedFacilities working
318 facilities✓ Stable
STA-M2-P3
Drainage blockages reported and unresolvedBlocked drains
≤3 drains✓ Stable
M3
Resource and Supply ReadinessSupplies and equipment
▼
STA-M3-P1
Emergency supply stock days availableDays of supplies left
14 days✓ Stable
STA-M3-P2
Evacuation items confirmed in storageKits ready
45 kits✓ Stable
STA-M3-P3
Field equipment confirmed operationalEquipment working
95 %✓ Stable
SAF
SafetySafety
Population protected and field hazard conditions monitoredEveryone accounted for and safe
▼
M4
Household Hazard ExposureHouseholds at risk
▼
SAF-M4-P1
Households in hazard zones confirmed visitedAt-risk households visited
68 households✓ Stable
SAF-M4-P2
Households with structural risk flaggedUnsafe buildings flagged
≤5 households✓ Stable
SAF-M4-P3
Early warning disseminations confirmed deliveredWarnings delivered
Data collection paths — choose what fits the environmentThree ways to send in the numbers
1
QR Scan — AutomatedScan the code
Field form carries a QR code. Field officer scans it. The PI loads in the Collector — pre-identified, ready to submit. One scan, one value, done. Works during and after an event.The form has a code. Scan it with your phone. The right field opens. Type the number. Send.
2
Paper — Photograph — Manual entryFill paper, type later
Field officer fills the paper form in the field. Takes a photograph. Values are typed into the Collector when connectivity returns. Paper remains as the source of truth. Critical when power and signal are down.Write on the form. Take a photo. When the signal comes back, type the numbers in. The paper stays as proof.
3
Full PWA — Direct digital entryAll digital
Field officer uses the Collector directly. Numeric counts, photos, geolocation, audio. Works offline — data queues and syncs when connected. Location coordinates logged automatically on each submission.No internet needed. Open the app. Enter everything. It saves and sends when the signal comes back.
Field observation formThe printed form
MetriqOne
Community Field Form — STAField Form
Scan to collectScan
Agent OperatorNameSta. Cruz
IDLGU-004
WeekWk9
PIWhat
CountNumber
ConfirmedChecked
Passable routesRoads open
2
✕NoNoYesYes
→
MetriqOne CollectorThe app
metriq.one/collect/06:43
MetriqOneONLINE
METRIQONE · COLLECTOR
▦▦▦ ▦▦▦ ▦▦▦
SCAN ASSIGNMENT QRSCAN THE CODE
Point camera at the QR code on the field form. PI loads pre-identified and ready to submit.Point your camera at the code on the form. Your field will open, ready to fill in.
DEVICE IDYOUR ID
4f2a91cc-b7e1‑4d83‑a902‑73cd5fe12b44
Share with coordinator on registration.Give this to your coordinator.
PI LOADEDREADY
Passable routes confirmedRoads confirmed open
MQ-D0010-P19-STA · LGU-004 · Wk 9
Enter countHow many routes?
⚠ Below CPL (6) — will be flagged⚠ Below the floor (6 routes)
numericoffline-readyCPL: 6
CPL set in the Kitchen · 6 routes / weekFloor set by coordinator · 6 routes
📄
Paper remains the source of truthFill paper, send later
Field officer fills the paper form in the field. Photographs it with scanning software on the phone — timestamped image and values both queue offline. When connectivity returns, both the scanned image and the entered values sync to the Collector. The paper copy is retained — signed, dated, immutable.Fill in the form. Photograph it with your phone — the scan and the numbers both wait for signal. When connectivity returns, everything sends. Keep the paper — it is your proof.
The photograph is the scan. One action creates the timestamped image record and prepares the value entry. Both travel together when signal returns. During a severe event, power and connectivity may be absent for days. The paper form survives. The evidence does not wait for infrastructure to recover.One photo does two things — it records the form and queues the data. No internet needed. Even if the signal is gone for days — the paper is still there and everything sends when it comes back.
Full input capability — all PI typesEverything digital
Works offline — data queues locally and syncs when connection returns. Geolocation captures field poouter settlementn automatically. Photo evidence attaches directly to the PI reading. The CPL is set per PI in the Kitchen, not on the form.No internet needed — the app saves everything and sends it when the signal comes back. You can attach a photo directly to your reading. The floor is set by the coordinator, not the worker.
Reading submitted → XmR processes → Step 2: SignalNumber sent → System reads it → Step 2
Signal Vantage — select levelChoose your view
Federation — 6 CSI Extended Stack · tap a CSI to read signalFederation view — tap a line to see the signal
Households confirmed accounted for — weekly countHouseholds confirmed located — weekly
StableOn track
CONContinuity
Services confirmed delivered to communities — weekly countServices reaching the communities — weekly
⚡ Signal⚡ Check this
CAPCapability
Field actors confirmed trained & on duty — weekly countTrained staff confirmed available — weekly
StableOn track
AORActor Orientation
Community reports submitted on time — weekly countReports arriving on time — weekly
⚠ CPL⚠ Not enough
PRFProcess Flow
Inter-community coordination actions confirmed — weeklyCoordination confirmed working — weekly
StableOn track
Municipality — XmR Wheeler + CPL · DemingMunicipality signal
PI readingsWeekly count
UCL / LCLNormal range
CPLThe floor
X̄ meanAverage
Outside limitsOutside range
⚡ Special Cause Signal — Wheeler XmR
CON — Continuity
Weeks 8 and 9 fall below the lower control limit calculated by Wheeler’s XmR method.
Services confirmed delivered to communities collapsed suddenly.
The storm event severed the delivery chain.
The coordinator is told weeks 8 and 9 need immediate response —
before a single damage report has been filed at the municipal office.
⚡ Something happened
CON — Continuity
The number of services reaching the communities dropped sharply in weeks 8 and 9.
Something broke the chain. The municipality needs to act this week.
⚠ CPL — Counterproductive Level · Deming
AOR — Actor Orientation
Statistically stable — every reading within Wheeler’s control limits.
The XmR chart alone would not flag this.
But 12 consecutive weeks below the CPL reveals a structural condition:
community reports are consistently not arriving on time.
The signal chain from field to municipality has been unreliable since before storm season.
Deming’s case. The CPL made the invisible visible.
⚠ Not enough — every week
AOR — Actor Orientation
Nothing suddenly changed. But every week for 12 weeks, the reports from communities were not arriving on time.
This started before the storm. The municipality has had 12 weeks of evidence to act on.
What the Federation sees across all 6 CSIs — right nowFederation view — all six areas
CON — Continuity — sudden collapse weeks 8–9. The storm event severed the service delivery chain. The XmR chart caught it before the damage report reached the mayor’s desk. — services stopped reaching the communities in weeks 8 and 9. The system caught it. Act now.
AOR — Actor Orientation — statistically stable. Nothing suddenly changed. But 12 consecutive weeks below CPL means the reporting chain from community to municipality has been structurally unreliable since before storm season began. The limits alone would never have caught it. — nothing suddenly changed. But every week for 12 weeks, the reports were not arriving. This started before the storm.
The coordinator does not see six colours. They see two names — and know exactly what each one means.The coordinator sees two problems. They know what to do with each one.
Communities — 3 CSI Basic Stack · tap a community to read signalYour communities — tap a name to see the signal
Daloy
Passable routes confirmed — weeklyRoads confirmed open — weekly
StableOn track
Haligi
Passable routes confirmed — weeklyRoads confirmed open — weekly
StableOn track
Sta. Cruz
Passable routes confirmed — weeklyRoads confirmed open — weekly
⚡ Signal⚡ Check this
Lunas
Passable routes confirmed — weeklyRoads confirmed open — weekly
Weeks 8 and 9 fall below the lower control limit
calculated by Wheeler’s XmR method. A sudden, special cause change
in the operational surface. The coordinator is told
Sta. Cruz — weeks 8 and 9 require immediate follow-up.
The river took a bridge. The signal found it before the damage report was filed.
⚡ Something happened
Sta. Cruz
The number of open roads dropped sharply in weeks 8 and 9.
Something changed. The system caught it.
The municipality needs to know this week.
Find out what happened in weeks 8 and 9.
⚠ CPL — Counterproductive Level · Deming
Lunas
Statistically stable — every reading within Wheeler’s control limits.
The XmR chart alone would not flag this.
But 12 consecutive weeks below the CPL — the manually declared
floor of 6 passable routes — reveals a structural condition.
Deming’s case: a stable process at a counterproductive level.
This community has been chronically under-connected since before the storm season began.
The CPL made the invisible visible — weeks before the event.
⚠ Not enough — every week
Lunas
The number never suddenly dropped. No big change.
But every single week for 12 weeks, the confirmed open routes were below the floor.
The floor is 6 routes. Lunas has been below it every week.
This started before the storm season.
Something in the situation needs to change — and the coordinator has had 12 weeks of evidence to act on.
What the Municipality Coordinator sees — right nowWhat the coordinator sees right now
⚠ Stable — CPL · 12 weeks⚠ Not enough — every week
Structural review · Access & connectivityThis started before the storm. What does Lunas need?
Sta. Cruz — sudden collapse. The bridge is gone or the road is blocked. The XmR chart shows it. A coordinator dispatch this week will find what happened. — something suddenly changed in weeks 8 and 9. The system caught it. Find out what happened before it gets worse.
Lunas — statistically stable. Nothing suddenly changed. But chronically below CPL for 12 consecutive weeks. This community was already under-connected before storm season. The limits alone would never have caught it. — nothing suddenly changed. But every week for 12 weeks, the number of open routes was not enough. The floor is 6. Lunas has been below it since before the storm.
The coordinator does not see a crisis dashboard. They see two names — and know exactly what each one means before the damage report is filed.The coordinator does not see colours. They see two names — and know what to do.
Every other framework stops at the CSI summary lineWhat other systems can and cannot do
You just tapped from CSI to module to PI to a field form signed by a named operator.
No other performance measurement framework on earth produces that chain.
Not Balanced Scorecard. Not OKRs. Not LogFrame. Not PuMP.You just followed the signal all the way to the field form. No other system does this.
FrameworkFramework
Fires before crisis?Warns early?
Names who needs support?Names who?
Prints field form?Prints form?
Uses NPL?Uses NPL?
Balanced Scorecard
No
No
No
No
OKRs
No
No
No
No
LogFrame
No
No
No
No
PuMP
No
No
No
No
MetriqOne
Yes — 3 layers
Yes — by name
Yes — from the field
Yes — Wheeler
All four fail Falsifiability Condition 4 by design — they use moving averages without Natural Process Limits. The signal cannot be confirmed or denied. MetriqOne applies Wheeler’s XmR method to every PI. Every signal is statistically defensible.The other four cannot prove when something is a real signal. MetriqOne can. Every time.
Your deployment. Your signals.
Every LGU deserves a Signal Vantage. Before the storm arrives.Your community. Your signals. Your floor. Set before the season starts.
Field — $9.99/yr · Organisation — $49/yr · Federation — $499/yr
Works offline. Paper-first. No training required.