# Range status URL: /investigate/range-status Start a shift from one screen. Range status shows a strip of six figures, every vehicle's link state, and one list at a time, from the sorties flown today and yesterday to everything waiting on a named approver. **Range status** is the console's home view: `/app` opens it, and **Operations**, **Range status** in the sidebar returns to it. Its subtitle names the range and the date, then states its job: "What flew, what is on the net, and what is waiting on a person." Everything on the board is read from runs, collectors, incidents, alert firings and exports already in your deployment. It adds no data of its own. Each row opens the run, vehicle, incident, event or export behind it. ## Before you start [#before-you-start] * Nothing needs setting up: the board reads what your deployment already holds. What a row opens follows your role, as [Roles and permissions](/security/roles) sets out. * The board is most useful once collectors report and sorties close out. See [Install and enroll the collector](/collect/collector/install) and [Alerts](/integrate/alerts). ## Read the board [#read-the-board] Six figures run across the top. The values below are from the example dataset. | Figure | Example | What it counts | | ---------------------- | --------------------------------------- | ---------------------------------------------------------------------------------------------- | | **Range** | Harrow PG, `13R FP` | The active site and its MGRS 100 km square | | **Sorties today** | 1, with 4 sorties yesterday | Runs that started today, UTC. Bench runs are left out. | | **Collectors linked** | 13 / 15, with 16 vehicles on the roster | Collectors online against collectors enrolled | | **Open incidents** | 5, with 2 in review | Incidents that are not closed | | **Rule firings, 24 h** | 4, from 1 run | Alert rule firings in the last 24 hours, and the runs they came from | | **Awaiting approval** | 2, oldest 17 h ago | Exports and report reviews waiting on a named person. With none, it reads **Nothing waiting**. | **Sorties today**, **Open incidents**, **Rule firings, 24 h** and **Awaiting approval** are also buttons. Each one opens its list in the panel below the fleet, and the figure whose list is showing is underlined. The two header buttons open **Runs** and **Import files**. **Fleet** shows one tile per vehicle, in two groups, one under the other: **T4 tracked UGV** and **Q4 recon quad**, each with its count. The subtitle explains the source: "Link state is the companion collector’s. Last contact is its last upload." Each tile shows the vehicle ID, its MAVLink system ID (such as **SYS 22**), a drawing of the platform, the link state and **Last contact**. A vehicle with no collector shows **Last run** instead, with the run ID and date. A short note flags what needs a look: **Clock not synchronized**, the megabytes spooling, an offline note or a count of dropped samples. | Link state | Meaning | | ---------------- | ----------------------------------------------------------------------------------- | | **Linked** | "Collector online, uploading after each segment." | | **Buffering** | "No uplink. The collector spools on the vehicle and uploads when the link returns." | | **Offline** | "The collector has not reported." | | **No collector** | "No collector is enrolled on this vehicle. Its runs are imported by hand." | The legend counts each state; the example reads **Linked** 13, **Buffering** 1, **Offline** 1 and **No collector** 1. Last-contact times age on the page as you watch. Each group shows 12 tiles a page, with the page controls under it. Select a tile to open the vehicle. Below the fleet, one panel holds four lists, one tab each, with the count beside each tab: **Sorties**, **Open incidents**, **Rule firings** and **Approvals**. The right of the tab row gives the list's subtitle and a link to the full page: **All runs**, **All incidents**, **All firings** or **All exports**. The address keeps the tab, so a link to `/app/range?tab=approvals` opens on **Approvals**. Each list shows 6 rows a page, and the controls under it give the range, such as **1 to 5 of 5**, and the pages. **Sorties** lists today's and yesterday's runs under a heading per day, newest first. Its subtitle reads **1 today, 4 yesterday** in the example. The columns are **Start, UTC**, **Sortie** (label, run ID, vehicle and any incidents), **Length, m:s**, **Sources** and **Import**. A day with no runs reads **No sorties.** Select a row to open the run, or **All runs** for the full list. See [Check a run](/investigate/runs). **Open incidents**, subtitled **By the evidence level of each finding**, sorts every incident that is not closed by the evidence level of its finding: observed, correlated, hypothesis, then unknown. A count per level and a bar show the mix at a glance. | Level | Example incidents | | ------------------------------- | ---------------------------------------------------------- | | | INC-0141, jamming reported along the north fence | | | INC-0142, INC-0143 and INC-0137 | | | INC-0139, where the companion clock was never synchronized | The columns are **Evidence level**, **Incident** (title and ID), **Vehicle**, **Status** and **Updated**. With nothing open, the list reads **No open incidents**. [Evidence levels](/concepts/evidence-levels) explains the four levels. **Rule firings** lists what the alert rules caught in the last 24 hours. The columns are **Event, UTC**, **Rule**, **What held**, **Vehicle** and **Severity**. In the example, INC-0143 produced four firings on UGV-02: | Event, UTC | Rule | Severity | | ------------ | -------------------- | -------- | | 15:41:00.912 | R1 Vibration | Warning | | 15:41:02.604 | R5 Device disconnect | High | | 15:41:03.713 | R2 Telemetry gap | High | | 15:41:14.293 | R3 Failsafe entered | High | **What held** states the condition in words, such as "No HEARTBEAT from system 22 for 31.0 s while armed, longer than COM\_DL\_LOSS\_T, so High." A row opens the event it fired on. With nothing to show, the list reads **Nothing fired in the last 24 hours** and "Alert rules run when a sortie closes out." See [Alerts](/integrate/alerts). **Approvals**, subtitled **2 items waiting on a named person** in the example, lists two kinds of item, newest first: * **Report review.** A report sent for review names who asked, the reviewer and when. In the example, INC-0142's finding waits on its reviewer. * **An export to release.** The row reads the export ID and **Release of** the incident **to** its destination, such as **EXP-0034 Release of INC-0143 to removable media**. It shows the class, the approvals it has against the number it needs (such as **1 / 2**), who has approved and who it waits on. In the example, EXP-0034 is at L2, one of two approvals in, held by automation A2. Select an item to open the report or the export. With nothing waiting, the list reads **Nothing waiting**. See [Write and review a report](/investigate/write-a-report) and [Export formats and evidence bundles](/integrate/exports). ## The range readout [#the-range-readout] The top bar of every screen repeats the range in brief: **Range**, the site's short name and its MGRS 100 km square, then **DTG**, the date-time group in Zulu time. The example reads `260945Z SEP 26`, 26 Sep 2026 at 09:45 UTC. Hover over it for the full date-time group and the active range. ## Next [#next] * [Work an incident](/investigate/incidents) from the first finding to the report. * [Vehicle parts and their logs](/platforms/vehicle-parts) explains what each vehicle's logs can and cannot show. * [A tour of the console](/get-started/console-tour) covers the rest of the frame.