01
Plan
Set commander's intent, PIRs, NAIs, reporting triggers and desired outputs — then establish the site.
Output → Mission profile & collection plan
The Mission Loop
From collection to command, in one loop.
The friction is everything after collection. ReconOS removes it by carrying one mission record through every step — entered once, it flows to every product.
- Re-entryThe same observation, typed five times
Into separate, disconnected products.
- Missed reqsRequired fields and open PIRs slip
Under time pressure, the checklist breaks down.
- Lost trailConclusions cut off from their evidence
No fast path from a finding back to the image behind it.
- InconsistentEvery team's packet reads differently
No standard structure leadership can trust at a glance.
- Blind gapsWhat wasn't observed surfaces late
Collection gaps appear only after the commander asks.
The ReconOS Mission Loop
One guided loop.
One guided loop.
One mission record.
Information entered once flows to every product. As findings are validated, the PIR tracker, BORIS report, site assessment, and command summary update from the same data — and the assistant points to the next required action.
02
Collect
Upload imagery and log observations; each is tied to time, location, source, NAI and PIR.
Output → Organized collection + observation log
03
Identify
Run a guided exploitation pass. The operator confirms, corrects or rejects each finding.
Output → Validated, evidence-linked findings
04
Assess
Roll up PIR status, threat and risk, and the collection gaps that still remain.
Output → Site assessment + gap list
05
Report
Reports build from the record — no re-typing. Review the BORIS and command summary.
Output → Command-ready reports
06
Export
Package reports, imagery, the GRG and overlays into one mission package.
Output → Mission packet + TAK-compatible export
Underlying phases Mission › Site › Collection › Exploit › Validate › Report › Cmd Review › Export
Pilot & Demonstration
Put ReconOS in front of your operators.
Request a demonstration on a fictional training scenario — no sensitive data required.