A to Z
Everything here, listed alphabetically, because most people arrive with one specific question.
All 50 notes, A to Z
Listed alphabetically rather than grouped, because most people arrive with a specific question and know the word rather than the section. The section is shown against each entry, and each section has its own page below.
A
C
- Cameras in VehiclesThe boundary
- Choosing a SystemImplementation
- Collisions and IncidentsRunning it
- Consulting Before You DeployLegal
- Covert TrackingThe boundary
D
- Drivers Who Cross BordersLegal
- Dwell Time and Why It MisleadsThe boundary
G
- Gaps, Dead Zones and Missing DataTechnical
- GeofencesTechnical
- GlossaryReference
H
- Holding the Line on What It Is ForThe boundary
- How Accurate It Actually IsTechnical
- How Long to Keep ItLegal
- How These Deployments FailImplementation
- How to Decline a RequestThe boundary
I
- Introducing It Without Wrecking TrustImplementation
- The Impact AssessmentLegal
K
- Knowing Whether the Data Is Any GoodRunning it
L
- Lone Worker SafetyMethods
- The Least Data That Answers the QuestionFoundations
- The Legal Basis for Tracking StaffLegal
M
- Mileage and ExpensesMethods
P
- Proving You Turned UpMethods
Q
- The Question to Ask Before AnythingFoundations
R
- Requests to RefuseReference
- Route Planning and OptimisationMethods
S
- Securing the Location DataRunning it
- Small FleetsImplementation
- Speed, Braking and Driver ScoringThe boundary
- Subcontractors and Self-Employed DriversLegal
T
- Telling People What Is TrackedLegal
- The Thing You Are SpendingThe boundary
- Trackers, Plug-Ins and Phone AppsMethods
- Tracking a Vehicle or Tracking a PersonFoundations
- Tracking Outside Working HoursThe boundary
- Turning It OffRunning it
U
- Using It in an EmergencyRunning it
W
- What a Defensible Deployment Looks LikeReference
- What Location Data Cannot Tell YouReference
- What Location Data Is Actually ForFoundations
- What the Tracked Person Should SeeThe boundary
- What This Is Not ForReference
- When Someone Asks for Their Own DataLegal
- When the Vendor Adds a FeatureRunning it
- Where to StartImplementation
- Whether It Paid For ItselfRunning it
- Who Can Look, and WhenLegal
- Who Runs It AfterwardsRunning it
- Writing a Notice People Actually ReadLegal
Or read a section in order
Each section runs in a sequence that builds.
Foundations
Four operational purposes, and the distinction between following an asset and following a human being that decides everything else.
4 notes
Methods
Geofence events instead of continuous trails, position on alarm instead of continuous logging, totals instead of routes.
5 notes
What it can and cannot measure
The dot is the centre of a probability, not a position. A gap has seven possible causes and only one of them is deliberate.
3 notes
The legal position
Enforcement in this area has turned on the same question repeatedly: was the amount collected necessary for the purpose stated. The answers have been consistent.
10 notes
The boundary
Where deployments become unlawful without anyone intending it, usually because a default was left in place rather than a choice made.
9 notes
Putting it in
The order that produces a defensible design rather than a procurement, and the overnight test almost nobody runs.
5 notes
Running it
The project ends at go-live; the system generates work indefinitely, and in most deployments nobody was assigned to it.
8 notes
Reference
The questions these records cannot answer, the options that collect nothing at all, and the end state as a checklist.
6 notes