Practical workshop guide
What works when load-shedding interrupts your workshop?
AutoAxxiz supports mobile inspection drafts and queued resource changes. It is not a complete offline replacement for the web workshop app. A working device, previously established account and a connection for server operations and customer messaging are still required.
What can be saved locally
The mobile workflow supports local DVI drafts and queued changes when connectivity is unavailable. Pending work is kept separate for each account on the device. Photo and video upload recovery is handled by the inspection workflow.
What still needs a connection
Signing in, retrieving uncached server records, sending WhatsApp messages, generating server PDFs, payment-provider callbacks and accounting sync require connectivity. Do not promise a customer that a message or approval reached the workshop until the server confirms it.
Recover in order
Reconnect using the same account, review the pending-work indicator and sync. If a change fails, dependent changes remain queued for retry. Check the resulting job and inspection on the server before treating the handover as complete.
Protect work on shared devices
Sign out when handing the device to another person. Another account cannot replay your pending changes. Do not clear queued changes or uninstall the app while unsynced work remains; those actions can remove local work.
Test your workshop’s actual conditions
During the pilot, capture an inspection, disconnect the network, save more findings, reconnect and compare the server result. Repeat with an app restart and a failed media upload. Full offline database sync and browser-cached operation remain planned capabilities.
Maintained by the AutoAxxiz product team at JVS Ethics Lab. Updated 14 October 2026.
Discuss your workshop pilot · Compare plans · Read setup questions