Skip to main content

Info Tab

The incident's core record — split into Current details, the ICS/audit view, and a running History.

The Info tab holds the heart of the incident record. It is organized into three sub-tabs that you switch between using the buttons along the bottom of the screen. Each sub-tab shows a live form maintained on the server, so the information stays current as the incident develops. The active sub-tab is underlined and its label turns red.

Info tab

Overview​

Sub-tabPositionWhat it shows
CurrentFirst (opens here by default)The current state of the incident — the live, working record.
ICSSecondThe Incident Command System view and audit of the incident structure.
HistoryThirdThe log of changes and entries recorded against the incident.
ControlDescription
Sub-tab buttonsThree buttons along the bottom switch between Current, ICS, and History.
Active labelThe selected sub-tab's label turns red; the other two stay in the normal text color.
Active underlineA short line sits under the selected sub-tab only.
Unread badgeA number on a sub-tab counts unread items in that view. It is hidden when the count is zero.
Back buttonLeaves the incident. Any requests still loading are cancelled.
SwipeSwiping left or right moves between the three views, and the labels and underline follow.

Defaults and what is remembered​

BehaviorDetail
Default viewCurrent, the first sub-tab.
Remembered positionWhichever sub-tab you leave open is saved. Reopening the Info tab returns you to that same view, even after closing and reopening the app.
Inside Command ViewThe sub-tab bar shifts right so the command tools menu does not cover it. Everything else works the same.
AppearanceThe forms follow your light or dark appearance setting.
note

You can move between the three sub-tabs either by tapping the buttons or by swiping left and right — the underline and labels update to match.

Getting Here​

  1. Open an incident from the Incidents tab.
  2. Tap the Info tab.
  3. Use the bottom buttons to choose Current, ICS, or History.

Viewing the Current Record​

  1. Tap the Current button (the tab opens here by default).
  2. Review the live incident form. Fields and sections are defined by your agency's template, so what you see matches your agency's paperwork rather than a fixed layout.
  3. If you have edit permission, tap into a field to update it. Changes are saved to the incident record and pushed out to everyone else working the incident.
  4. Opening this view marks its new entries as read and clears that part of the badge.

Current sub-tab

tip

Because the form is defined on the server, an administrator can add a field mid-incident and it will appear here the next time the form loads — no app update needed.

Reviewing the ICS / Audit View​

  1. Tap the ICS button.
  2. Review the Incident Command System structure and the audit information recorded for the incident — who holds which position, and what has been recorded against the structure.
  3. Opening this view marks any new ICS entries as read.
note

This is the record-keeping view of the ICS structure. To actually build and rearrange the structure, use the command board in Command View.

Checking History​

  1. Tap the History button.
  2. Scroll the log of entries and changes recorded against the incident.
  3. Use this view to confirm what was changed, when, and by whom.

History sub-tab

tip

When two people disagree about what an incident said an hour ago, History settles it. It is the audit trail, not a summary — entries are added, never rewritten.

Loading and Empty States​

StateWhat you see
LoadingThe form area is blank for a moment while the template and its current values are fetched, then fills in.
Nothing recorded yetThe view shows the form's sections with no values in them. That is normal on a brand-new incident.
No historyThe History list is empty until the first change is recorded.
No connectionThe last loaded copy of the form stays on screen. Fields you cannot save are still visible, but your changes will not reach the server until you reconnect.

Permissions​

Your accessWhat you can do
View onlyRead all three sub-tabs. Fields are shown but cannot be changed.
EditChange values on the forms; your edits are recorded in History against your name.
AddCreate new entries where the template allows it.
caution

Edit access depends on your permissions for this incident tool. If fields are read-only, your account has view-only access and an administrator will need to change that. There is no in-app way to grant it to yourself.

How This Connects​

  • Where the data comes from. All three sub-tabs are forms defined on the server by your agency. The app asks for the template and its current values when you open the incident, and renders whatever comes back. That is why the Info tab looks different from agency to agency.
  • What updates it. Your edits, other responders' edits, and changes made from the web all land on the same record. Updates are pushed out live, so a field someone changes on another device appears here without you reloading.
  • What reads the same information. The incident header — number, name, type, and timer — comes from this same record, which is why it is identical on Comms, Maps, and Additional. The command board header in Command View shows the incident name, type, number, and address from the same place.
  • How unread counts work. Each sub-tab tracks its own unread items. Opening a sub-tab marks that view's items read, which is why the Info tab's overall badge sometimes only clears after you have visited all three. In Command View the Info tab badge is the combined total of all three sub-tabs.
  • Where the structure is built. ICS here is the record and audit. The live org chart you drag units around on is the command board — see Command View and Incident Side Menu.
  • Offline. The last loaded copy of each form stays readable. Edits you make are held on the device and are not visible to anyone else until you reconnect.
  • On reconnect. Held edits are sent and live updates resume. Reopen the Info tab and confirm your changes are present — if a colleague changed the same field while you were offline, the most recent save wins.

Troubleshooting​

If this happensWhat to do
Fields are visible but you cannot type in themYour account has view-only access to this incident. Ask an administrator for edit permission.
The form is blankIt is still loading, or you have no connection. Reconnect and reopen the tab.
A field you expect is missingYour agency's template controls the fields. Ask an administrator to add it — it will appear the next time the form loads.
An edit you made is goneCheck History to see whether someone else saved over it. If you made the edit offline, it may not have reached the server — make it again while connected.
The Info badge will not clearVisit all three sub-tabs. The badge is the total of Current, ICS, and History.
The tab keeps opening on HistoryThat is the sub-tab you last left open. Tap Current and it will be remembered instead.
History shows no entries at allNothing has been changed on the incident yet, or the record has not finished loading.
The sub-tab buttons are hidden behind the tools menuYou are in Command View; the bar shifts right to clear the menu. Scroll the view or close the popup panel to see it fully.

⬅️ Previous: Incident Overview | Next: Communications Tab ➡️