Overview
Every pre-start you complete is recorded permanently against the machine — the same history a supervisor or an auditor reviews later, and the same record that powers the machine's public digital logbook. This article covers reading that history in the app, confirming a check landed, and what an invalidation means for you.
Confirming a check landed
Open the machine — scan its GoTag, or find it on the Equipment tab — and tap Logbook. Your most recent check appears at or near the top of today's entries, with its result badge.
If you submitted offline, the check shows on your phone immediately and reaches the server on the next sync — the Profile screen's sync card shows anything still pending. A queued check is not a lost check; see Working Offline.
Reading an entry
Open a logbook entry for the full record of that inspection: the result, when and where it was performed, every item response, photos, any defects raised, and the spotter confirmation where one applied. What you see is exactly what a reviewer sees — there is one record, not an operator version and an office version.
If a check gets invalidated
A supervisor can review a check after the fact and invalidate it — most often when the check was flagged automatically (a spotter that couldn't be verified, unusual timing) and the review decided it shouldn't stand.
Note
Invalidation isn't an accusation, and it doesn't erase anything. Your original submission stays in the record exactly as you made it — it's tagged Invalidated, meaning it no longer counts as a valid pass. This is the platform's second-set-of-eyes review, not a penalty; nothing in the audit trail is ever rewritten.
When it happens to one of your checks:
- The check's badge in the logbook changes to Invalidated.
- You get a "Pre-Start Check Invalidated" notification — it's delivered as a priority notification, so it's hard to miss.
- The machine needs a fresh, passing pre-start before it's cleared again. If you're mid-shift on it, that means stopping and re-inspecting.
Checks also expire on their own — a passing check past its validity window is marked accordingly, which is the normal daily rhythm rather than anything unusual.
Your history across machines
Your own inspections are attributed to you on every machine you've touched — there is no separate "my checks" ledger to maintain. If you work across organisations (a contractor licensed by two companies), each organisation's records stay within that organisation, all under your one phone identity.
Edge cases
- A check that stays "pending sync" for days just hasn't had coverage since — it uploads on the next sync, with its original performed-at time intact. The record keeps both timestamps: when you did the inspection and when it reached the server.
- A flagged check (spotter unverified, time skew) still counts and still unlocks — flagging queues it for review rather than blocking you. It only stops counting if a reviewer invalidates it.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Your check isn't in the logbook | Still queued offline | Check the Profile sync card; it lands on the next sync |
| A check shows Invalidated | A supervisor reviewed and rejected it | Run a fresh pre-start before operating; ask your supervisor if the reason isn't clear |
| A check shows a "flagged" marker | Automatic flag awaiting review | Nothing to do — it counts unless a reviewer says otherwise |
| The public logbook shows an older result | The latest check hasn't synced yet | It updates when your phone syncs |