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.
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.
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.
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.
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.
| 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. |
| 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. |