Early access

Every post covered. Every officer qualified.

Scheduling, GPS-verified time, and pay-versus-bill billing, built for guard companies.

Join the early-access listBook a demo

OfficerOps is in development. The list is how we schedule demos and share early-access pricing.

Scheduler preview with a week of posts, coverage gaps, and a credential warning. Sample sites only; personal names are hidden.
Product preview — sample data. Personal names are hidden.

Built for how a guard company actually runs

Armed or unarmed. One workspace from the post to the hours, instead of a stack of generic tools and spreadsheets.

  1. 01

    Qualified on every post

    OfficerOps keeps licence, credential, and firearms-qualification records with an expiry. The scheduler is built so an expired credential blocks the assignment.

    Early access — full enforcement on every shift is part of the first release.

  2. 02

    Time you can prove

    Geofenced GPS clock-in, breaks, and supervisor approval, so the timesheet is the record you can show a client.

    Early access.

  3. 03

    One flow, request to invoice

    A coverage request, the officers on it, approved hours, separate pay and bill rates, and the invoice stay connected.

    Early access.

  4. 04

    Training built in

    Qualification scores and requalification cycles live on the same officer record as the schedule.

    Part of the product in development.

  5. 05

    Clients see the coverage

    A client portal for coverage requests, staffing status, reports, and invoices.

    Early access.

From first shift to final invoice

  1. 01

    Request

    A client asks for coverage.

  2. 02

    Staff

    Assign an officer who still qualifies for that post.

  3. 03

    Clock in

    The officer clocks in inside the site geofence.

    Early access

  4. 04

    Approve

    A supervisor reviews the hours.

    Early access

  5. 05

    Invoice

    Pay and bill rates turn approved hours into an export and an invoice.

    Early access

When you run armed posts

Armed posts, when you run them

Most posts are unarmed. When a post is armed, the firearms qualification has to be current. OfficerOps keeps that qualification beside the schedule and is built to keep an officer with a lapsed qualification off the armed post.

See the product

The screens

Previews of the product in development. Sites such as Acme are sample data. Personal names are hidden.

GPS clock-in preview inside a site geofence for a sample client. No personal names.
Time clock — sample data.
Timesheet approval preview with overtime and geofence flags. Officer names are hidden. Sample sites only.
Timesheet approval — sample data. Names are hidden.
Pay versus bill preview with separate pay and bill rates for sample sites. Officer names are hidden.
Pay and bill — sample data. Not OfficerOps pricing.
Phone preview of open shifts, including a shift blocked because a firearms qualification expired. Sample data.
Open shifts — sample data. A lapsed qualification blocks the claim.

Pricing

Pricing is coming soon

Join the waitlist for early-access pricing. Rates are not published on this site.

Join the early-access list

Security

Isolated by company, from day one

OfficerOps is built multi-tenant, with per-company data isolation from day one. Each company's officers, sites, and hours stay in that company's workspace.

How the product is designed

Tell us the size of the company.

Name, company, work email, and a guard-count range. That is the whole form.

Join the early-access list