PUBLIC DATA // HUMANITARIAN USE
ISSACHAR / Field Collection
FIELDOPS
Where the network ends.

A reporting app for field staff, monitors and investigators working where there is no signal. Record what you see on your phone. It sends itself to your team the moment you are back in range.

Works Without Signal  //  No App Store Needed  //  Every Report Pinned to a Location
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 report sits on his phone. No spinner. No error. It is simply waiting.

“The places where the truth on the ground matters most are the places where the signal drops. FieldOps does not need a signal. It does not need the internet. It just needs someone to be there.”

Seventy kilometers south, Aisha is walking the edge of a camp for displaced families 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 jump in numbers, 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 marks one report as urgent. Her tablet now reads seven reports waiting to send.

Pastor Daniel finishes his second report — 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 reports, eleven photos, two voice notes. They begin to send in the order they were recorded. 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 reports 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 two reports were recorded 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. Two reports, one event. We have it confirmed.

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 Problem WHY REPORTS GET LOST
The places where the truth on the ground matters most are the places where there is no signal, online forms fail, and a dropped connection means a lost report.

Field workers in dangerous areas — aid workers in camps for displaced families, ministry coordinators driving rural roads in Plateau and Benue, local monitors recording what happened after an attack — often have patchy signal at best, and none at all at worst.

Paper notes survive the trip but rarely reach the people who need them. Online forms need a signal that often isn't there. Ordinary survey apps weren't built for photos pinned to a place, a location you can rely on, or a clear record of who captured it, where and when — the things a reviewer needs before they can trust what they're looking at.

FieldOps was built to close the gap between what happened and the report that reaches your team.

What It Is IN PLAIN TERMS

FieldOps is how reports from the field reach the rest of ISSACHAR. It installs from your phone or tablet's web browser — no app store needed. You record what you see, pinned to where you are. It holds the report safely until you have signal, then sends it to your team's Command Dashboard on its own.

NO SIGNAL NEEDED
Built for Dead Zones
Everything works without a connection. Reports are saved on the phone itself and stay safe through airplane mode, dead zones and restarts. The app never assumes you have signal.
PINNED TO A PLACE
Exact Location, Automatically
The phone's GPS fills in the location for you, along with how precise it is. You can add a place name too. Your team sees exactly where a report came from, not just what it says.
SENDS ITSELF
Sent the Moment Signal Returns
As soon as the phone reconnects, waiting reports and their photos, videos and voice notes are sent securely to your team. Nobody has to remember to press upload.
What’s in a Report AN EXAMPLE
FOPS-2026-04812 Submitted
Security Severity: High
Burnt compound — Tse-Akenyi, north of Naka
GPS 7.5126° N, 8.7341° E Precise to ± 4.2 m Location Tse-Akenyi, Gwer West LGA, Benue Recorded 2026‑04‑28 · 06:42 WAT (offline) Sent 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 recorded as a voice 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 photos · 1 voice note attached
Type · 7 choices
What kind of report this is
Incident, observation, infrastructure, humanitarian, environmental, security, or other. Helps your team sort reports and decide who should look at each one.
Urgency · 5 levels
How quickly someone should act
Critical, high, medium, low, or info. The field worker sets it on the spot, and a reviewer can adjust it later. Critical reports rise to the top of the list.
Location · filled in automatically
Where it actually happened
The GPS position from the phone, and how precise it was. An optional place name adds the local detail a map pin can't.
Photos · video · voice notes
Evidence, captured on the spot
Up to five photos (10 MB each), five videos and ten voice notes. They stay on the phone with the report until it sends. Only the person who sent them and your reviewers can see them.
Title · description · notes
The story, in your words
A short title, a written description, and room for any extra detail the situation calls for — witness names, who told you, or links to related incidents.
From the Field to Your Team HOW IT WORKS
STEP 01
Record
In the field · no signal needed
Open FieldOps on a phone or tablet. Choose the type and urgency. The location fills in by itself. Add a title, a description, photos, video or a voice note on the spot.
STEP 02
Hold
Saved on the phone
The report is kept safely on the phone. It survives the phone being switched off, airplane mode, and whole days without signal — nothing is lost and nothing expires.
STEP 03
Send
As soon as there’s signal
The phone reconnects and sends the report and its attachments securely, on its own. It lands with your reviewers and its status changes to Submitted.
STEP 04
Review
Command Dashboard · Overwatch Map
A reviewer reads the report and marks its status. It shows up as a pin on the Overwatch map, right next to live reports of violence, fires and other events. Any report can be downloaded as a printable PDF with maps and photos.
What you see on the ground becomes part of the bigger picture — all inside ISSACHAR.
Who Uses It IN THE FIELD
Humanitarian Field Staff
Camp monitors, shelter assessors and protection officers recording conditions, changes in numbers, and incidents where displaced families are on the move 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 keeping track of armed groups, checkpoints and damage to roads, power and water. FieldOps lets them send a dated, located record without having to call it in or stay online while they work.
Investigators
Independent investigators and partner researchers building case files on specific incidents. Every report keeps a clear record of who captured it, where and when, from the phone all the way to the reviewer.
Report Types QUICK GUIDE
Type · 7 choices
Type Use For
Incident Something that happened — attacks, raids, accidents, arrests.
Observation Things you noticed — people moving, sightings, who is around.
Infrastructure Roads, bridges, towers, power, water — status and damage.
Humanitarian Camps, shelter, food, medical care — needs and conditions.
Environmental Fires, flooding, deforestation, mining scars, contamination.
Security Armed groups, checkpoints, defenses, the scene after an attack.
Other Anything that does not fit cleanly above — describe in full.
Urgency · 5 levels
Level Meaning
Critical Happening now — active danger, people hurt or killed.
High Recent harm; likely to get worse if nobody acts.
Medium A real concern that needs follow-up.
Low Worth knowing, but not urgent.
Info Background only — no action needed.
Access Required
FieldOps is available to ISSACHAR teams on request. Sign in, or request access to set up your team’s phones.
Access granted person by person · 633 Innovations · GEOINT Division
“Be diligent to know the state of your flocks, and pay attention to your herds.”
Proverbs 27:23
PUBLIC DATA // HUMANITARIAN USE