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. You review at stage two, run the day’s orders and movements at stage three, and hand over the report at 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
Daily orders go out and every officer acknowledges them. Scheduled movements call STANDBY to the day’s roster, and every call is logged.
- 04
Afterwards
Hand the client a report drawn from the record, as a PDF or a PowerPoint brief, and read the day back in the daily log.
- Officer submitsFrom the field app
- You reviewApprove or send back
- The day runsOrders, movements, STANDBY
- You reportClient PDF and slides
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 day — daily orders, movements and STANDBY, assigning work.
Keeps an eye on it all — review, the daily log, 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.
Every recce arrives in the same format, so review is a read rather than a hunt.
The quality score
Each recce carries a score with a breakdown of where it came from. The officer sees the same score before submitting, which is the point — most thin sections get fixed on site rather than in review.
The officer sees this before submitting, so thin sections get fixed on site.
Export a print-ready PDF of the entire recce plus all AI output for client delivery.
Illustrative diagrams, not screenshots of the app. Book a demo to see the real thing.
Orders, movements & the daily log
Daily Orders are written and published from the console. They land on every officer's phone, each officer acknowledges them in the field app, and every acknowledgement is recorded against the orders.
Scheduled movements and STANDBY
Plan the day's movements ahead of time. When one is due, STANDBY goes to everyone on the day's roster; each acknowledgement is time-stamped, and a stand-down closes the call on every phone. Movement plans — each leg by road, air, rail, sea or on foot, with the return journey — are kept as workspace documents.
- Orders published
The day’s orders go out from the console, and each officer acknowledges them in the app.
- 2STANDBY
When a scheduled movement is due, one call reaches everyone on the day’s roster.
- 3Acknowledged
Each acknowledgement is time-stamped as it happens, not typed in afterwards.
- 4On the record
Orders, calls, acknowledgements and the stand-down go into the daily log, emailed after midnight.
The daily log and end-of-day reports
Shortly after midnight in your workspace's time zone, the day's log — orders, STANDBY calls, acknowledgements and stand-downs — is emailed to every owner, admin and supervisor as a branded PDF. End-of-day reports are set up in the console: choose who writes the report and who receives it, and it is filed from the field app.
- 09:00Orders publishedFour officers on the roster
- 09:12Orders acknowledged4 of 4
- 17:45STANDBY calledResidence to venue
- 17:47STANDBY acknowledged4 of 4
- 18:04ArrivedGrosvenor Ballroom
Illustrative diagrams, not screenshots of the app. Book a demo to see the real thing.
Reports and exports
Hand the client a report drawn from the record rather than retyped from notes — the full recce as a branded PDF, or the same brief as PowerPoint slides for a meeting.
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.
A seat is a person who can use Pack features. Reclaim one and give it to someone else.
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.
- 09:14Recce approvedJ. Morrow · Grosvenor Ballroom
- 09:02Seat reassignedS. Bell → T. Kaur
- 08:47Report exportedPDF · client copy
- 08:31Signed inStep-up verification passed
Illustrative diagrams, not screenshots of the app. Book a demo to see the real thing.
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 — 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 |
Drawn from ongoing area updates, and always dated so you know how fresh it is.
Support
Email help@reccenet.com with the recce ID or officer ID. Audit any administrative action via Activity Logs first — most “what happened?” questions are answered there.