UNCLASSIFIED // FOR OFFICIAL USE ONLY
ISSACHAR / Field Collection
FIELDOPS
Where the network ends.

A handheld collection tool for investigators, monitors, and field staff operating beyond the reach of signal. Capture ground truth on-device. Sync to ISSACHAR when you come back into range.

Progressive Web App  //  Offline-First  //  GPS-Tagged Submissions
Scenario 09:14 LOCAL · PLATEAU STATE
Two Phones, Seventy Kilometers Apart, One Picture

A pastor walks through a village that burned overnight. A camp monitor counts new arrivals at a shelter site she has watched for six months. Neither of them has signal. Both of them are recording.

Pastor Daniel reaches the edge of the village just after sunrise. The smoke is still going. He has been here before — baptisms, a funeral, a clinic day — and he knows the elders by name. There is no signal out here, there has not been signal out here for two years, and the nearest mast is forty kilometers behind him. He opens FieldOps on his phone anyway.

He taps New Submission. The GPS fills in on its own — nine meters of accuracy, good enough. He picks the category, picks the severity, writes three sentences about the chapel roof and the two families he has already spoken to. He photographs the burned doorway, the school wall, and the well. Each photo is tagged with where it was taken and when. He saves it. The submission sits on the device. No spinner. No error. It is simply waiting.

“The places where ground truth matters most are the places where the browser fails. FieldOps does not need the browser. It does not need the cloud. It just needs the operator to be there.”

Seventy kilometers south, Aisha is walking the perimeter of an IDP camp she has been monitoring since the spring. She is a humanitarian field monitor. Yesterday the camp population was fifteen hundred and forty. This morning, by her own count at the gate, there are nearly seventeen hundred people inside. The arrivals came in through the night. They came from the north.

She opens FieldOps on her tablet. The signal at the camp is two bars and unreliable; the tablet has been offline for most of the morning. It does not matter. She logs the population delta, photographs the new shelters along the west wall, marks the water point at the corner where the queue is longest, and notes the three families she interviewed — where they came from, how long they walked, what they left behind. She tags one submission as urgent. The queue on her tablet now reads seven submissions pending sync.

Pastor Daniel finishes his second submission — this one about the pastor in the next village over, who has gone missing — gets back into the truck, and starts driving. Forty minutes later, on the road south, his phone catches a bar of signal. FieldOps wakes up on its own. Three submissions, eleven photos, two GPS tracks. They begin to upload in the order they were captured. By the time he reaches the junction, the status on each one has flipped from Queued to Submitted.

Aisha's tablet finds the camp Wi-Fi an hour later. Her seven submissions go up in a burst. The urgent one lands first.

In a city two thousand kilometers away, an analyst named Ezra opens the Command Dashboard at the start of his shift. Two new red points have appeared on Overwatch overnight, sitting beside the existing layers of incident data, fire detections, and refugee sites. One is a burned village in the north. One is a sudden population spike at a camp to the south. The submission timestamps are forty-eight minutes apart. The line between them, drawn on the globe, points exactly the direction the arrivals came from. Ezra picks up the phone to the regional lead. We have a corroborated event.

This is what FieldOps is built to do: turn the gap between an incident and a report into a tagged record that survives the walk home. The pastor's phone and the monitor's tablet do not know about each other. The analyst's dashboard knows about both.
The Operational Reality PROBLEM SET
The places where ground truth matters most are the places where browsers fail, cloud forms time out, and a dropped signal means a lost report.

Field workers in contested terrain — humanitarian responders in IDP camps, ministry coordinators driving rural routes in Plateau and Benue, security monitors documenting attack aftermath — operate in environments where connectivity is intermittent at best and adversarial at worst.

Pen-and-paper survives the trip but never makes it back to the analyst. Web forms require a signal that often isn't there. Generic survey apps weren't built for tagged photos, GPS accuracy that matters, or the chain of custody an analyst needs to trust what they're looking at.

FieldOps was built for the gap between the incident and the report.

What It Is PLATFORM ROLE

FieldOps is the collection edge of the ISSACHAR platform — an offline-first Progressive Web App that installs to a phone or tablet, records GPS-tagged submissions on-device, and queues them for automatic sync to the Command Dashboard the moment connectivity returns.

OFFLINE-FIRST
Designed for No Signal
Full capture workflow runs locally. Submissions are written to on-device storage and persist through airplane mode, dead zones, and reboots. The app does not assume a connection exists.
GPS-TAGGED
Coordinates & Accuracy
Every submission carries latitude, longitude, and reported accuracy from the device's GNSS receiver, plus an optional human-readable location name. Analysts see where the report came from, not just what it says.
AUTO-SYNC
Pushes When Signal Returns
Queued submissions and photos transfer to the ISSACHAR backend over a token-authenticated channel as soon as the device reconnects. The operator does not need to remember to upload.
Anatomy of a Submission DATA MODEL
FOPS-2026-04812 Submitted
Security Severity: High
Burnt compound — Tse-Akenyi, north of Naka
Coords 7.5126° N, 8.7341° E Accuracy ± 4.2 m Location Tse-Akenyi, Gwer West LGA, Benue Captured 2026‑04‑28 · 06:42 WAT (offline) Synced 2026‑04‑28 · 14:17 WAT
Two compounds burned overnight. No fatalities reported on-site at time of walk-through. Residents displaced to relatives in Naka. Spent cartridges collected from the access path; samples in photo 3. Witness account attached as metadata note.
01 Wide view of burned compound
02 Surrounding compound structures
03 Spent cartridges collected from access path
04 Access path to compound
05 Wider area context
5 / 5 photos attached · max 10 MB each
Category · 7 values
What kind of report this is
Incident, observation, infrastructure, humanitarian, environmental, security, or other. Drives routing to the correct analyst queue and which overlay it appears on in Overwatch.
Severity · 5 levels
How urgent the analyst should treat it
Critical, high, medium, low, or info. Set by the operator on-device, re-assessed at review. Critical submissions surface at the top of the analyst queue.
Location · lat / lon / accuracy
Where it actually happened
Device-reported coordinates with the GNSS accuracy figure preserved. Optional location name supplies human context the coordinates can't.
Photos · up to 5
Visual evidence, on-device
Up to five photographs at 10 MB each. Stored locally with the submission and uploaded on sync. Photos remain accessible only to the submitter and the assigned reviewer.
Title · description · metadata
The narrative
A short title, an open-form description, and a free-form metadata object for whatever the situation demands — witness names, source attribution, related incident IDs.
Field to Command, Closed END-TO-END
STEP 01
Capture
In-field · offline
Operator opens FieldOps on phone or tablet. Selects category and severity. GPS auto-fills. Title, description, and photos are added on the spot.
STEP 02
Queue
On-device storage
Submission is written locally. Captures persist through power cycles, mode switches, and full days off-network without loss or expiration.
STEP 03
Sync
First available signal
Device reconnects. Token-authenticated upload to the ISSACHAR backend. Submission and photos arrive in the analyst queue, status flips to Submitted.
STEP 04
Review
Command Dashboard · Overwatch
Analyst reviews the submission, marks status, and surfaces it as a georeferenced point on Overwatch alongside ACLED events, FIRMS hotspots, and other live feeds.
Ground truth in, fused picture out — the loop closes inside ISSACHAR.
Who Carries It OPERATOR PROFILES
Humanitarian Field Staff
IDP camp monitors, shelter assessors, and protection officers documenting site conditions, population shifts, and incidents in displacement corridors across the Middle Belt and Lake Chad Basin.
Ministry Coordinators
Pastoral teams and ministry leads driving rural routes in Plateau, Benue, Kaduna, and Nasarawa — logging attack aftermath, displaced congregations, and church and clinic damage as they encounter it.
Security Monitors
Local observers tracking armed-group activity, checkpoint behavior, and infrastructure damage. FieldOps gives them a way to push a tagged, time-stamped record without exposing themselves on the wire.
Investigators
Independent investigators and partner-org researchers building case files on specific incidents. Submissions retain chain of custody from the device to the analyst review record.
Submission Taxonomy FIELD MANUAL
Category · 7 values
Category Use For
Incident Discrete events — attacks, raids, accidents, arrests.
Observation Conditions noted in passing — movements, sightings, presence.
Infrastructure Roads, bridges, towers, power, water — status and damage.
Humanitarian IDP sites, shelter, food, medical — needs and conditions.
Environmental Fires, flooding, deforestation, mining scars, contamination.
Security Armed presence, checkpoints, fortifications, post-attack scenes.
Other Anything that does not fit cleanly above — describe in full.
Severity · 5 levels
Level Meaning
Critical Active threat, casualties, ongoing incident.
High Recent harm, escalation likely without action.
Medium Material concern, requires follow-up.
Low Notable but non-urgent.
Info Background, context, no action implied.
Access Required
FieldOps is issued to ISSACHAR operators by request. Sign in or request access to provision a device.
Access granted per operator · 633 Innovations · GEOINT Division
“Be diligent to know the state of your flocks, and pay attention to your herds.”
Proverbs 27:23
UNCLASSIFIED // FOR OFFICIAL USE ONLY