Instructions that stay current. Keep site instructions current.

Keep site procedures, attachments, and acknowledgments together so the next shift starts with the right context.

Attlock · Post Orders

Harbour Centre · Illustrative record

Post Orders

Open work

Owner

Assigned team

Site

Harbour Centre

Next

Publish the order

ContextThe current version is published for the site.
RecordRequires follow-up
Next actionOpen the responsible workflow

The binder is not the source of truth.

Follow a revised loading-bay instruction from publication to guard acknowledgment.

Harbour Centre · Illustrative record

Post Orders

Open work

Owner

Assigned team

Site

Harbour Centre

Next

Publish the order

ContextThe current version is published for the site.
RecordRequires follow-up
Next actionOpen the responsible workflow

Authored workflow illustration. Selection changes this example only; no dispatch, alert, tracking, patrol, or task is submitted.

Write for the shift. Keep post orders tied to their site, effective version, and supporting resources.

Explore the record
Site
Harbour Centre
Version
v4 · Loading bay procedure
Resources
Map · escalation contacts

Make changes visible. When instructions change, keep the acknowledgment and version context beside the active record.

Explore the record
Change
Updated loading-bay procedure
Audience
Assigned site guards
Review
Acknowledgment status

Post orders support communication and acknowledgment. Your company remains responsible for keeping procedures accurate and ensuring guards understand them.

More than a signature. Version-aware acknowledgments, an optional quiz, reminders, and review dates keep each order current.

Every new version asks again. When an order's content changes, the earlier version is kept and each guard is asked to acknowledge the new one.

Add a short quiz where it matters. When an order has one, acknowledgment is accepted only after the answers are correct. It supports review; it does not prove comprehension.

See who is still behind. Review who has not acknowledged the current version, then send one reminder to all of them.

Keep orders from going stale. Set a review date. Company admins are notified when an order passes it, and an admin can mark it reviewed.

Authored workflow illustration. No order is published, no reminder is sent, and no guard is notified.

From written to acknowledged. Three steps, one record per site.

  1. 01

    Write

    Compose rich text or upload a file for one active site, then add a category, review date, or quiz if the order needs them.

  2. 02

    Publish

    Publishing saves version 1 and notifies active field staff. Each later change to the content saves the earlier version with a change note.

  3. 03

    Acknowledge

    A guard acknowledges on mobile or web. The record keeps who, when, and which version, so the next change asks again.

Continue the workflow.

Move from this overview into the connected workflow where ownership, permissions, and review remain explicit.

Explore Tasks & Checklists

Questions about Post Orders.

What to know about getting started, supporting your team, and running your sites.

Talk to our team

Acknowledgment records the configured workflow state. It does not prove comprehension or replace supervisor follow-up.

Run your security team in one place.

Schedule shifts, track patrols, and share reports.