Choose the tools your team needs.

What is included in Core?

These features are available in Core. Wellbeing, team chat and staff offers are optional modules, licensed separately. Your service’s setup and your role determine what you can see and manage.

• Turnout and call-out alerts

  Send an alert to a person or a location’s team. People can respond and give an estimated arrival time. Test alerts let you practise the workflow.

  Critical notifications depend on the device and its permissions. On-call filtering follows the member’s notification preference.

• Wellbeing and support (optional)

  Record how you’re feeling in a wellbeing journal, look back at your recent entries and find your service’s support contacts. Choose a journal sharing option or ask the wellbeing team to contact you.

  Team check-ins and follow-up records help those responsible for support. We’ll walk through who can see what during setup.

• News and briefings

  Publish service news, send targeted messages and request acknowledgements. Read and acknowledgement records help you follow up a briefing.

• Team chat (optional)

  People at the same location can chat, with replies and reactions.

• Documents, calendars and events

  Keep policies and procedures in a categorised document library. View your duty and on-call entries in a personal calendar, and add personal or shared location events for the intended audience.

• Training and qualifications

  See assigned practical training, e-learning due dates and enrolled courses with venue and time details. Qualification records show what is current, expiring or expired. Skills adds the full competency framework and evidence review workflows.

• Availability and vehicle status

  Record basic on-call availability and see vehicle staffing and availability information. Rota adds the detailed shared planner, repeating duty patterns and approval workflows.

• Incident awareness

  View a read-only incident feed for your locations when a control-room connection is configured. Agree the source and information supplied during setup. Command adds incident coordination and command support records.

• Ask HQ

  Send a question to the relevant service category and follow its replies in My Requests. Keep the question and the response together, so you can refer back to them.

• Mobile access and widgets

  Sign in to the iOS or Android team app with an email code, then unlock using supported device biometrics or a device passcode. Home-screen widgets show duty, vehicle status, training and message counts from the last update.

  Previously loaded duty entries, training information and support contacts can be read offline. Sending replies and receiving updates need a connection. Read about app access.

• Staff offers (optional)

  Find the discounts and benefits your service shares with its people in the offers section.

Planning, requests and records

• Duty patterns and planner views

  Set repeating duty patterns and review the plan by day or week. See bookings and cover counts together, rather than checking each person’s diary.

• Availability and cover requests

  People record when they can work and respond to cover requests. Personal calendar feeds help them see upcoming duties alongside their other commitments.

• Leave, swaps and overtime

  Submit leave requests, propose shift swaps and record overtime claims. Managers have an approvals inbox for the teams they are responsible for.

• Balances and payroll exports

  Track leave and time-off-in-lieu balances using your service’s policies. Export approved overtime and worked hours to CSV, with the format agreed for your payroll process.

• Staffing and coverage

  Review staffing requirements and try coverage scenarios before changing the plan. A configured Skills connection brings competency information into staffing decisions.

• Records of changes

  Audit records show who made a recorded change, when it happened and the old and new values. Managers can review those records when a booking needs explaining.

From evidence to a reviewed record

• Your competency framework

  Define requirements and capability programmes around your service’s framework. Assignment rules help apply requirements to the people who need them.

• Evidence and attachments

  Keep an evidence journal with notes and supporting files linked to requirements. Members and reviewers can refer back to the material behind a competency record.

• Verification and quality assurance

  A person cannot verify their own evidence. Where quality-assurance countersign is required, a separate reviewer checks it after verification; neither the author nor the original verifier can countersign.

• Team competency views

  See which requirements are current, expiring or lapsed, and which reviews are waiting. Training teams can use this view to plan the next review or training activity.

• Courses and bookings

  Publish scheduled and recurring courses. Learners request a place and managers approve it, with a waitlist for full courses and requests to change dates. Before each date, readiness shows numbers, instructors and booked resources.

• Attendance and assessments

  Mark attendance to complete linked e-learning and add evidence for practical requirements. Assess practical skills against a rubric with per-criterion scores and a fixed report once the assessment is complete.

• E-learning, quizzes and your LMS

  Add a knowledge check to an e-learning requirement, with several question types and a pass mark. Completions can also come from your existing learning system through the integration API; hosting learning content is a separate arrangement.

• Compliance matrix and certificates

  See your team’s requirements in one matrix and download it as CSV. Learners and managers can download a PDF certificate for a programme once every requirement in it is complete and in date.

• Competency and duty planning

  A configured connection shares competency information with Rota. Agree the requirements and mappings used for staffing, so planners understand what the information means.

Your hierarchy, checks and records

• Configurable hierarchy

  Define the asset types and names your team uses at each level. Nest assets to the depth each branch needs, whether you’re managing a fleet, an estate or equipment stores. Follow the hierarchy to see what belongs where.

• Search and tagged items

  Find a record by searching or using a configured QR or barcode tag. Check the record against the item in front of you before recording a result.

• Check routines

  Set recurring check routines and record results against individual items. Keep pass or fail results and notes with the equipment record.

• Defects and follow-up

  Record a defect with a photo, notes and severity, then review open and resolved records. Failed check results can create a linked defect record. A critical defect alerts the handhelds at that location straight away.

• Readiness

  Readiness is worked out for each vehicle or other top-level asset, and a fault on kit marked as critical takes it off the run. The readiness overview lists every location, worst first.

• Works without a signal

  The handheld keeps a copy of its location’s assets, routines and open defects. Checks and defect reports made offline are sent when the connection returns, in the order they happened.

• Documents and check history

  Attach manuals and certificates to any asset and open them on the handheld. See each routine’s recent checks and whether random spot checks were done in time.

• Administration and field use

  Administrators manage equipment details and routines; field users find records and complete checks. Agree your hierarchy, permissions and device setup before rollout.

The incident support record

• Incident information

  Receive incident details through a configured integration or create an incident manually. Agree which information your control-room source supplies and how updates are handled.

• Sectors and responsibilities

  Organise sectors and objectives, and record the people responsible for them. The hierarchy helps command support teams follow the incident structure.

• Attendance and device positions

  Track resource attendance alongside available device positions. Location information depends on device reporting; check its freshness when using it to support decisions.

• Tasks, requests and timeline

  Assign tasks, follow their status and record resource requests. Timeline entries keep updates together for the people supporting the incident.

• Command, handover and decisions

  Show who is in command and record an accepted handover. Keep a decision log of what was decided, why and by whom, with every earlier version kept.

• What needs attention now

  Each incident opens with a panel of what needs someone: overdue breathing apparatus wearers, unacknowledged hazards, uncontrolled high risks, a pending handover and appliances whose position has gone stale.

• Appliance tablets

  The Android tablet app shows the incidents an appliance is attending, takes hazard acknowledgements, runs breathing apparatus entry control and gives route guidance. Opened incidents stay readable without a signal; changes need a connection. Route guidance does not replace your satnav or MDT.

• Risks, relief and attachments

  Keep the risk log, photos and documents with the incident. Record vehicle-for-vehicle relief as arranged, arrived, accepted and released steps.

• The full incident record

  Print or save as PDF the complete record: command and handovers, decisions with every version, objectives, the risk log, attendance, breathing apparatus entry control, tasks, the timeline, photos and documents, and the full change history. The same record can be downloaded as a data file for retention.