Product overview

One record, from the shiftto the client.

Bastrion is built around a single reporting chain. Field capture, supervisor review, correction, and client release are the same record at different stages, with every step attributed and retained.

Modules

What the platform contains.

  1. 01

    Shift reporting

    Officers work from a structured shift workspace. Entries are timestamped as they happen, required detail is enforced by the template assigned to the site, and the report is closed against a real shift window rather than written from memory the next day.

  2. 02

    Incident records

    Incidents are filed as their own record with severity, parties involved, actions taken, and a timeline. The incident stays linked to the shift it came from, so the surrounding context is never lost when the report is examined months later.

  3. 03

    Attachments and evidence

    Photos and supporting files attach to the entry they belong to, not to a loose folder. Each attachment carries the officer, the time, and the record it was filed against.

  4. 04

    Supervisor review

    Submitted reports enter a review queue ordered by exception, overdue status, and severity. Supervisors approve or return with a written reason, and the decision is attributed.

  5. 05

    Corrections

    A returned report goes back to the officer with the supervisor note attached and the original version preserved. Corrections are visible as a history, not as a silent rewrite.

  6. 06

    Client visibility

    Clients see approved reports, released incidents, and summaries for their own sites only. Internal review notes, correction history, and quality findings never cross into the portal.

  7. 07

    Compliance tracking

    Licences, permits, training, and onboarding stages are tracked per officer, with expiry reminders and a readiness view showing who can be deployed and who is blocked.

  8. 08

    Quality review

    Automated checks run in the background against your own rule set, flagging vague wording, timeline gaps, and missing detail for supervisors. There is no chatbot and no prompt box; officers only ever see a normal correction.

  9. 09

    Notifications and inbox

    Notifications carry the action that needs taking. The inbox keeps the permanent record of what was issued, to whom, and when, separated by role so client accounts never receive internal traffic.

  10. 10

    Billing and invoicing

    Plan, seat counts, and invoice history sit inside the platform. Invoices carry line items and status, and released invoices can be surfaced to the client account where that is part of the contract.

  11. 11

    Setup and deployment

    Company profile, sites, templates, team invitations, client portals, and compliance rules are configured as a deployment, with a readiness checklist that separates hard blockers from advisories before launch.

Workspaces

Three access contexts, one underlying record.

Access is shaped by responsibility. Nobody sees a version of the report that suits them.

Company workspace

Officers, supervisors, and administrators capture, review, and manage the operation, including compliance, deployment, billing, and audit history.

Client portal

Contracted clients read approved reports, released incidents, summaries, documents, and issued invoices for their own sites.

Platform console

Bastrion administrators oversee tenants, licensing, support, and platform-level audit activity without touching operational content casually.

Next step

See Bastrion running against your own operation.

We walk through your current shift and incident workflow, then show the same operation recorded, reviewed, and released inside Bastrion.