Offline Walkaround Checks: How Autodue Works at the Depot, in a Basement Car Park, or on a Rural Route

Key Takeaways

• Autodue now completes the daily walkaround check fully offline (fixed 19 points for vans, 27 points for HGVs), along with defect reports, evidence photos, and the odometer reading at check completion.
• Anything captured offline is queued locally and syncs the moment your phone reconnects, on app open or resume, and on Android roughly every 15 minutes in the background.
• A persistent on-device proof page (latest walkaround with full pass and fail breakdown, MOT, Tax and Insurance dates, registration) is available offline for a roadside stop. The signed compliance PDF still loads from cache if you downloaded it while online.
• The honest limits: first login, first data load for a brand new vehicle, photo uploads, and live billing all still need a connection at some point. The daily check itself does not.
• DVSA explicitly accepts user-friendly digital devices for daily walkaround records (Guide to Maintaining Roadworthiness), and records must be kept for at least 15 months.

---

You know the spots. The underground car park before the first job. The multi-storey at the supermarket drop. The yard at the back of the depot where two bars becomes none the second you walk past the loading bay. The lane in the middle of nowhere on a rural route in Cumbria or Powys. Until now, that was the bit where the daily walkaround stalled, the photo refused to attach, and the driver stood with a thumb on the screen waiting for signal.

That is the gap a daily compliance app has to close. A walkaround is not optional. DVSA can ask to see the record at any roadside stop, and the operator licence audit trail depends on it being captured and kept for at least 15 months. If the app needs a connection to even start the check, it has stopped being a compliance tool and become a connectivity tool.

This is why Autodue is now offline-first for everything a driver does in the morning. You can start a walkaround on a basement car park with no bars, mark every pass and fail, photograph a defect, log the odometer, and finish. The phone catches up by itself when you walk back into signal. Below is exactly what works offline, what still needs a connection, and what shows on screen if a DVSA officer stops you in the middle.

Why a daily walkaround needs to work offline

A daily walkaround is the legally required first job of any commercial vehicle shift, and it almost always happens in the worst signal spot of the day. Depots are steel-clad sheds with concrete loading bays. Multi-storey car parks are concrete boxes. Rural starts are out of range of the nearest mast. A check that needs a connection at start-of-shift is the wrong tool for the job.

The check itself is not a small piece of work. Autodue uses the fixed 19-point check for vans and the fixed 27-point check for HGVs, matching the regulator's expected coverage so operators do not have to design a checklist from scratch. Every point has to be inspected and recorded, defects logged, photos taken where the defect needs evidence, and the odometer captured at completion. None of that can wait for a signal to come back. If the driver leaves the check half-finished and drives off, the operator has nothing to show at audit and nothing to show at a roadside stop.

The offline-first design removes that whole class of failure. The driver does the same check, in the same order, on the same screen, whether the phone is connected or not. The sync happens in the background, on the driver's behalf, and the audit trail is identical at the end.

What works offline in Autodue

Everything a driver does on a normal morning is now offline-capable: the walkaround itself, defect reports with photos, the odometer reading at check completion, the offline read of recent compliance data, the sync queue, and the persistent offline indicator. The phone catches up by itself when signal returns. The full list of actions that complete with zero bars:

• Daily walkaround check. Start and complete a fixed 19-point van check or 27-point HGV check, end to end, every item recorded, every pass and fail captured.
• Defect reports. Log a defect against a check item, add a description, and attach a photo. The defect saves immediately to the device. The photo uploads when you are back online.
• Odometer reading at check completion. The mileage at the end of the walkaround is captured offline and rides with the check when it syncs.
• Evidence photos. Captured and stored on-device offline. They upload automatically when the phone reconnects.
• View recent compliance data. Last-synced vehicle list, MOT, Tax and Insurance deadlines, defect history, and up to 28 days of check history are readable with no signal.
• Sync Queue. A dedicated screen shows exactly what is pending or failed, and lets you trigger a manual sync at any time.
• Offline indicator. A persistent, non-dismissible "You're offline. Changes will sync automatically." banner with a pending count taps through to the Sync Queue, so the driver always knows what state the app is in.

For an Autodue user, the practical effect is that the morning walkaround stops needing a plan. The check happens, the defect goes in, the photo goes in, and the phone handles the rest. You can read more about how the underlying walkaround flow itself is structured in our paper vs digital walkaround checks post, which lays out why a captured digital record beats a clipboard every time.

What still needs a connection (the honest limits)

Offline-first is not "works without internet, ever". The marketing copy that overclaims here is the marketing copy that breaks trust the first time a driver hits the edge. A short, honest list of what still needs a connection at some point:

• First login and the first data load for a brand new vehicle need to be online once. The app has to have something cached before it can show it offline.
• Photo uploads complete only when the phone is back online. The check item or defect itself saves offline, and the image follows on reconnect.
• The official signed roadside PDF needs one prior online download to be cached. Without that prior download, the offline fallback is the native proof page covered in the next section, not the PDF.
• Billing changes, subscription updates, and brand-new fleet data added by an admin while the driver is offline need a connection on the driver's device before they show up.

In practice, this means once the driver has used the app online at least once on the phone they actually use, the daily work no longer depends on the signal at the kerb. The check, the defect, the photo, the mileage, the proof page, all work. What does not work is anything that genuinely needs the server to either show new data the driver has not seen before, or to confirm an upload has landed.

How the sync queue works

The sync queue is a list of pending and failed items, visible to the driver from the offline banner. It exists for two reasons: so the driver can see exactly what is waiting to go up, and so a stuck item never disappears silently. When the phone reconnects, items move out of the queue automatically as they upload.

Sync runs in four places: on reconnect, on app open, on app resume, and on Android roughly every 15 minutes in the background. iOS handles sync on open, resume and reconnect (Apple does not allow arbitrary background sync intervals on iOS for an app of this kind, so the trigger points are user-facing rather than time-based). In both cases, the user almost never has to think about it. If a manual push is needed (for example, the driver is parked in signal and wants to confirm everything has uploaded before walking away), the Sync Queue has a button.

A queued item that fails (server rejected, file too large, network dropped mid-upload) stays in the queue with its error state visible, and retries. It does not get silently dropped. This is deliberate: the compliance audit trail depends on the operator being able to see every item that was attempted, not just the ones that went through.

Roadside Mode offline: the proof a driver can show

If DVSA stops a driver at the kerbside, the legal expectation is that the most recent daily walkaround record can be produced. Autodue's offline Roadside Mode is designed to put that record on the screen even with no signal.

If the signed compliance PDF was downloaded while the phone was online (Roadside Mode pre-caches it for the current vehicle), it loads from cache and the driver hands the phone to the officer. If the PDF has not been cached for any reason, the fallback is a native on-device proof page that pulls everything from the last sync: registration, the latest walkaround check with the full pass and fail breakdown, MOT, Tax and Insurance dates, and the date the data was last synced. The officer sees a record. The driver does not stand at the kerb fumbling with a signal-less app.

For more on what officers actually look at during a roadside check, our DVSA roadside inspections guide covers the full checklist, the triggers for a stop, and the typical penalties.

Why DVSA accepts a digital walkaround record

DVSA's Guide to Maintaining Roadworthiness is explicit that operators should equip drivers with "suitable paper defect checklist or user-friendly digital devices to facilitate accurate reporting", and the same guide requires operators to keep safety inspection records, including driver defect reports, for at least 15 months for every vehicle, including vehicles that have been removed from an operator licence (gov.uk Guide to Maintaining Roadworthiness).

The shift to digital is not informal. DVSA has explicitly told operators in its blog that paper checklists and digital devices are both acceptable, with a clear preference for digital where it produces a better audit trail (Moving On: helping you carry out effective daily walkaround checks). A 2026 traffic commissioner regulatory decision went a step further and required an operator to switch to a digital reporting app for daily walkaround checks as a condition of keeping its licence, which is about as clear a steer as the regulator gives.

Two things in that regulatory picture matter for the offline question. First, the requirement is that the record exists, is accurate, and is retained for 15 months, not that the record was created online. A walkaround done offline and synced 20 minutes later is the same audit record as a walkaround done in full signal. Second, the photo evidence of a defect, the timestamp, and the GPS location are the parts of a digital record that DVSA cannot get from a paper sheet, and those still get captured offline; only the upload to the server waits for signal.

The combination of "captured offline at the vehicle, synced automatically on reconnect, retained at the server for the 15-month window" is what makes the audit trail hold up. The driver does not have to do anything different. The record is the record.

The bottom line

For a working van or HGV driver, the morning walkaround is the first compliance touchpoint of the day, and it usually happens in the worst signal spot the phone will see. Autodue's offline-first design means the check, the defect, the photo, the mileage and the roadside proof page all work with zero bars, and sync themselves the moment the phone reconnects. The only items that still need a connection are the ones that genuinely cannot work without the server: first login, first-time data loads, photo uploads, and live billing.

Update Autodue on the App Store or Google Play and offline support is on by default for every plan and every fleet size. There is no setting to toggle and no migration to run.

---

Do your daily checks anywhere, even with no signal. Everything syncs the moment you reconnect. See walkaround checks | See defect management | iPhone app | Android app

---

Sources: DVSA Guide to Maintaining Roadworthiness, commercial goods and passenger carrying vehicles · DVSA Moving On blog, helping you carry out effective daily walkaround checks · gov.uk: Carry out HGV daily walkaround checks · gov.uk: Roadside checks for HGV, van, bus or coach drivers, making sure your vehicle is roadworthy