Where the console fits
The console is the middle of a chain that starts on an officer’s phone and ends with a report in a client’s hands. Your work sits at stage two and stage four.
- 01
On site
The officer works the nine steps, offline if there is no signal. Photos are annotated on the device before they upload.
- 02
In the console
A reviewer reads it in one standard format and either approves it or sends it back with notes.
- 03
On the day
Approved recces feed straight into Live Ops. The team appears on the map and incidents are logged as they happen.
- 04
Afterwards
Scrub back through the job, review it with the team, and hand the client a report drawn from the record.
Roles & access
Three people look at Recce Net from three directions, and the console is where two of them work:
Records what is actually there — recces, photos, site conditions.
Runs the job — live map, assigning work, incidents.
Keeps an eye on it all — God's Eye, review, audit, analytics.
Every action is gated by role. The four built-in roles:
| Role | What they can do |
|---|---|
| Super Admin | Everything: users, roles, recces, media, analytics, settings |
| Operations Manager | Approve/reject recces, manage officers & verification, view all, export |
| Reviewer | View recces and approve or reject them |
| Read-only Auditor | View-only across recces, media, analytics and logs |
Custom roles can be defined with a granular permission grid.
Reviewing recces
The Recces list gives you venue, client, job date, AI risk level, status, escalation flag, media count and officer — with filters, search, bulk CSV export, and inline risk override.
Recce detail
A tabbed layout: Overview (job, team, AI risk score with factor breakdown), Location (map, access points, evacuation, what3words), Plan (vehicle line-up, routes), Risks, Media (signed-URL gallery grouped by step), Vehicles, AI insights, and Review with the Approve / Reject buttons. Rejection requires a reason; both actions write to the review history and the activity log.
Export a print-ready PDF of the entire recce plus all AI output for client delivery.
Live Ops
The Ops list is grouped by status (Active / Preparing / Completed). Each event opens a real-time console: incident feed streamed from officers in the field, a weather block, handover history, and — once an officer triggers it — an AI post-event review and client-report summary.
Incidents originate from the officer's app and surface here in real time.
Officers & verification
Create officer accounts, edit contact and role inline, and work the verification queue: open each submitted document, confirm the OCR name matches, then Approve or Reject with a reason. Suspend or activate officers and change roles as needed.
Insights & audit
- Analytics — a 30-day snapshot: risk distribution, creation trend, high-risk sites, top officers by volume.
- AI Usage — the last 500 AI calls with tokens, USD cost, latency and status; aggregate spend and failure rate; CSV export.
- Activity Logs — a full audit trail of approvals, verifications and overrides, filterable and exportable.
AI artefacts in the console
Every AI generation from the field app surfaces here for review:
| Artefact | Where it appears |
|---|---|
| Risk Score | Recce Overview — score, level, factors, recommendations (overridable) |
| Area Brief | AI insights — area context and focus checklist |
| Area risk overview | AI insights — crime, protest, construction, incidents |
| Venue Changes | AI insights — diff vs the last recce of this venue |
| Weather Impact | AI insights + Ops — event-day forecast and risk |
| Contingency Plan | AI insights — plans for each risk you flag |
| Photo Analyses | Media — what the AI spotted in each photo, plus notes |
| Post-event review & client report | Live jobs — post-event summary and client deliverable |
Support
Email support@reccenet.com with the recce ID or officer ID. Audit any administrative action via Activity Logs first — most “what happened?” questions are answered there.