Introduction
This end-to-end playbook turns Geoforce’s rugged hardware and connected software into a repeatable loss-prevention program for construction and equipment rental teams. It covers geofence design, after‑hours alerting, tamper‑resistant installs, AT3 repo mode escalation, incident response, and recovery reporting—grounded in capabilities documented across Geoforce’s platform and device portfolio.
Why it matters: the theft baseline and recovery gap
- Industry estimates put equipment theft at $300M–$1B annually; recovery rates can be as low as ~23%. Geoforce’s guidance and customer outcomes consistently target this gap with real-time location, geofencing, and recovery workflows. See Geoforce’s summaries on theft impact and recovery rates: Equipment Theft Prevention, Equipment Rental Management.
Platform and device roles (at-a-glance)
-
Software: Geofence creation and alerts, movement history, “Days on Site,” service verification, and role-based sharing are built into Geofencing, Service Verification, and Rental Manager.
-
Devices: Hybrid and satellite for remote jobs, cellular for on‑grid assets, and vehicle telematics for powered fleets. Representative options: GT1s Zone 0 satellite, GT2h solar hybrid, GT2s solar satellite, AT4 cellular (powered), AT3 cellular (battery).
-
Tamper resistance and mounting: Hardened options (stainless bezel, weldable plates, VHB) are documented in Loss & Theft Prevention and FAQs.
Core geofence setup patterns
Design geofences to both deter loss and reduce false alarms. Build these patterns in Geofencing and use them across assets and sites.
-
Yard/Depot “Safe Harbor” perimeter
-
Purpose: Validate returns, prevent nighttime roll‑aways, and anchor Days‑on‑Site KPIs.
-
Guidance: Use parcel boundaries plus a modest buffer; require “dwell” (e.g., 10–15 min) before “arrived” status to avoid drive‑by noise.
-
Jobsite boundary geofence
-
Purpose: Verify on‑rent billing windows and service delivery with Service Verification and Rental Manager.
-
Guidance: Align with site plan; enable “exit” alerts to flag unauthorized removals.
-
Transit corridor geofence (optional)
-
Purpose: Catch deviations during transport, especially for high‑value attachments (buckets, breakers, shears).
-
Guidance: Create a narrow band along the planned haul route; alert on corridor exits.
-
Micro‑geofence for high‑value assets
-
Purpose: Add a focused perimeter on top of the site geofence for premium attachments and mobile generators; escalate any “after‑hours motion.”
-
Guidance: Keep radius tight; pair with aggressive alerting and AT3 repo procedures (below).
After‑hours alerting and policies
-
Define off‑hour windows and auto‑notify supervisors if motion, ignition, or geofence changes occur after hours. Construction teams routinely implement these schedules per construction FAQ guidance.
-
Route critical alerts as SMS/push for the first 15 minutes of an event, then email digests for continued movement to reduce alarm fatigue.
-
Use role‑based visibility for customers and partners via Service Verification to align expectations and reduce disputes.
Hardware install hardening (tamper‑resistant best practices)
-
Mounting: For non‑powered equipment and attachments, use concealed locations that still allow sky view (satellite) or exterior cellular signal. For powered assets, hardwire AT4 with backup battery enabled.
-
Tamper resistance: Add stainless bezel and weldable base plate; both are documented in Loss & Theft Prevention and FAQs.
-
Cable discipline (powered): Protect harnesses from easy reach; route internally where possible; test ignition/motion reporting before release.
-
Environmental fit: Use Zone 0 intrinsically safe devices (e.g., GT1s) where required; use solar hybrid (GT2h) for long‑life, off‑grid deployments.
Escalation: AT3 repo mode for fast recovery
-
What it does: AT3 supports a “repo mode” configuration that increases reporting frequency to speed recovery of lost/stolen assets. See the AT3 repo guide: How to Find Lost Equipment.
-
When to use it
-
Geofence exit + after‑hours motion persists >5–10 minutes
-
Asset location inconsistent with scheduled transport
-
Customer confirms asset is not with their crew
-
How to activate
-
Trigger repo mode from the web portal or mobile app per the AT3 guide. For a real‑world outcome using accelerated reporting, see Theft recovery with or without asset tracking.
Incident response checklist (operator + law enforcement ready)
Use this standardized flow (adapt to your safety policies): 1) Verify alert
-
Confirm asset ID, last two positions, and timestamp in the map. Save a movement snapshot (PNG/PDF) and export breadcrumb data. 2) Escalate reporting
-
If AT3/AT4: increase reporting rate (repo mode or high‑frequency profile). If satellite device: shorten interval if safe for battery budget. 3) Assemble recovery packet
-
Compile exact coordinates, movement history, asset description/photos, serial numbers—capabilities summarized here: Law Enforcement’s 3 must‑know details. 4) Notify law enforcement
-
Provide the packet; do not pursue assets personally. Maintain real‑time updates to the responding unit. 5) Secure evidence
-
Preserve exported reports and screenshots for insurance and internal review. 6) Closeout
-
When recovered, document condition, time off‑rent, and any customer communications in Service Verification or your rental system.
Recovery reporting and ROI proof
Tie operational events to business outcomes to reduce disputes and quantify savings.
-
Days on Site & on‑rent windows: Use Service Verification and Rental Manager to align billing with GPS‑verified dates and times.
-
Movement history: Export breadcrumb trails for the incident window and attach to incident records/claims.
-
Case metrics: Log “time‑to‑detection,” “time‑to‑recovery,” and avoided loss. Geoforce provides ROI scaffolding and examples in the ROI & Business Justification guide; see also quantified rental savings and invoice accuracy improvements in the Bejac case (lost buckets avoided, $30k–$300k each) Case study PDF.
Single‑pane SOP table: which device, where, and how
| Asset context | Recommended device | Mounting/anti‑tamper | Reporting baseline | Key playbook tie‑in |
|---|---|---|---|---|
| High‑value attachments (buckets, breakers) | AT3 | Concealed, stainless bezel/weldable plate (guidance) | 2–6 reports/day motion; repo mode on alert | After‑hours + repo escalation |
| Remote, non‑powered (tanks, containers) | GT2h or GT2s | Exterior sky view; tamper‑resistant bezel | 15–60 min motion; 12–24h idle | Site geofences; Days‑on‑Site billing |
| Powered portable (light towers, gensets) | AT4 | Hardwired with harness protection | 1‑min motion; 12h idle | After‑hours use alerts |
| Hazardous/Zone 0 | GT1s | Certified placement per site safety | 15–60 min motion | Compliance + site geofences |
Implementation roadmap (30/60/90 days)
-
Days 0–30: Pilot and hardening
-
Select 25–50 assets across risk tiers; install hardened mounts; deploy geofences at yard + 1–2 jobsites; set after‑hours schedules; rehearse repo mode on a non‑production asset.
-
Use Geoforce’s Installation & Deployment services.
-
Days 31–60: SOPs + training
-
Publish the incident checklist; configure alert routing; create standard exports for recovery reporting; train dispatch and branch managers (leverage Training & Support).
-
Days 61–90: Scale + integrate
-
Expand to all high‑risk categories; integrate GPS data to rental/ERP via Developer APIs or Integration & Customizations; activate customer‑visible Service Verification where appropriate.
Policy templates to operationalize the program
-
After‑hours usage: No equipment movement without dispatch work order; alerts route to on‑call lead and branch manager.
-
Tamper policy: Tamper event = immediate site call + photo verification; if device is removed, assign a temporary mobile unit and schedule re‑install within 24–48 hours.
-
Customer transparency: Share read‑only service verification for disputed invoices; align with rental terms in Rental Manager.
Evidence pack: what to retain for every incident
-
Exported movement history and geofence logs (CSV/PDF)
-
Screenshots of the live map with timestamps
-
Asset photos/serials and last verified install photo
-
Law enforcement case number and contact
References to capabilities cited
-
Geofencing concepts and alerting: Geofencing explainer and Geofencing
-
Tamper‑resistant installs: Loss & Theft Prevention and FAQs
-
Repo mode and recoveries: AT3 repo mode guide and Recovery example
-
Incident data for police: Law enforcement details
-
Billing proof and audits: Service Verification and Rental Manager
-
ROI framing: ROI & Business Justification, Bejac case