Home / How it works

The project

What Guardlane is, and how it works.

Guardlane is a marketplace for security cover shifts. It has two parts: a web console for security companies and officers, and a mobile app officers carry on duty. Both work from the same records, so a shift booked on a phone shows up in the provider's console straight away.

Who's involved

Four parties, one shift.

A single shift can involve more people than it first appears. Guardlane gives each of them a defined role, so it's always clear who is responsible for what.

WhoWhat they do
Security officerKeeps their profile and licence details up to date, finds and accepts shifts, works them, and gets paid.
Shift providerA security company, contractor or staffing organisation that posts shifts and is responsible for the terms of the engagement.
Site operatorWhoever runs the physical site. Provides briefings and site instructions, and confirms attendance and handover.
Guardlane operationsReviews verification, handles disputes and safety reports, and keeps the marketplace fair.
The shift lifecycle

From posted to paid.

Every stage below writes to an append-only record. Events can be added to it, but not silently changed afterwards.

  1. A provider publishes a shift

    Site, start and end time, duties, required qualifications, pay and site instructions are entered as structured fields, with a live preview before it goes out.

  2. An officer finds and accepts it

    Officers search and filter by what matters to them. Accepting is a single step, and the system prevents the same shift being booked twice.

  3. The officer checks in on site

    Check-in starts a duty session. If the provider has set a site boundary, the officer's location is compared against it on the server, and the result is labelled plainly: inside, outside, not shared, or boundary not set.

  4. The shift is worked, and recorded

    Welfare checks, patrol checkpoint confirmations and required duty tasks are logged with timestamps. If the connection drops, the mobile app queues these actions and sends them once it reconnects, without creating duplicates.

  5. The provider watches it live

    An operations view shows active sessions, welfare status, patrol coverage and task completion, with an exceptions queue for anything missed.

  6. Check-out, ratings and payment

    Checking out closes the session and moves the payment into review. Both sides then rate each other, and payment status is visible to both throughout.

Ratings that mean something

Officers rate sites, too.

Feedback on Guardlane runs in both directions and is broken into specific dimensions. A raw star average hides too much, so each score is kept separate.

Officers rate the site onWhat it captures
Safety and conditionsWhether the post felt safe and had the welfare facilities it should.
Briefing and site instructionsHow accurate and useful the instructions, escalation path and induction were.
Shift accuracyWhether the time, duties, location, equipment and pay matched what was advertised.
Respect and conductHow the officer was treated by the client and site staff.
Payment reliabilityWhether pay was correct and arrived when promised.

Providers see officer reliability and attendance built from logged shift evidence. Safety and conduct concerns go through a private report, with its own severity levels, and never appear as a public rating.

Where the project stands

What's built, and what comes before launch.

We would rather be clear about this than oversell it. The core product works today. A number of things still have to be in place before Guardlane opens to the public.

Working now

  • Officer and provider accounts, with separate workspaces
  • Shift publishing, search, booking and double-booking protection
  • Mobile duty mode: check-in and check-out, welfare checks, patrol checkpoints, duty tasks
  • Offline queue that replays duty actions without duplicates
  • Live operations view with missed-check alerts
  • Two-way structured ratings and private safety reports
  • Payment timelines and exportable reports
  • Append-only record of operational events

Before public launch

  • Accredited licence and identity verification
  • Live payment processing and payouts to officers
  • Multi-factor authentication
  • Email delivery for account recovery and verification
  • Moderation and appeals tooling
  • Push notifications and timed supervisor escalation
  • Legal and privacy review of our policies
  • App Store and Google Play release
What Guardlane is not

A few clear limits.

Not an emergency service

Welfare checks and incident reports support your own procedures. They don't replace police, ambulance or site command structures. In an emergency, call 999.

Not a guarantee of work

Guardlane helps officers find shifts. It doesn't promise hours, income or employment.

Not a tracking tool

Location is used to confirm attendance at a site during a duty session, with a clear purpose and retention limits, not to follow officers off duty.

See it from your side.

Officers and providers use Guardlane very differently. Pick yours.