UniQorn Safety — Part 7: Offline work and reports
Public demonstration | Interface captured 18 October 2026

Prepare before leaving coverage
Chapter seven explains offline preparation and reporting. Safety Field holds prepared work on a device. The live browser shown here has no prepared workspace, so this chapter combines actual help screens with a labelled process illustration; it is not a new disconnected-phone test. A connection indicator or cached page does not prove that an inspection is prepared or synchronised.

Use the same installed app
On an iPhone, open the field page in Safari and use Share, then Add to Home Screen. On Android, use Install app or Add to Home screen where available. Launch the Safety Field icon online and open online inspections from that app. Browser and installed-app storage can be separate. A new icon does not transfer drafts or photographs from another browser context.

Prepare and verify the draft
While online in that same app, open the assigned draft and save online changes first. Create or unlock the offline workspace with the operator's private offline passphrase, which is separate from the login password. Use Prepare this draft on device, then Open prepared field inspection. Verify the correct record, answers, actual evidence, cached-page status and authorisation expiry before leaving coverage.

Save on device is local only
After preparation has been verified, use the same field app when disconnected. Unlock the prepared work, enter the inspection answers and save on the device. Check the local saved status or revision. Saved on device means the work is local only. Completed on device means sign-off is queued locally, not that the server has accepted official completion. A failed check still requires immediate local stop-use action.

Reconnect, sync and check receipt
Reconnect, open online inspections in the same app, unlock the workspace and use Sync saved device work. Verify the server receipt and the accepted answers and evidence. If completion was queued locally, confirm server completion too. Resolve conflicting answers through the review workflow before retrying. Do not clear storage, uninstall the app or create a duplicate inspection to fix an uncertain synchronisation.

Find signed reports
For completed records, open Inspection reports and audit history. Search by equipment or checklist and use the failure filters. The search covers loaded reports, so load older records when needed. Drafts and work awaiting synchronisation remain in inspections, not completed reports. Choose Open signed report and confirm the correct equipment, checklist version, sign-off identity and time.

Review and export
The signed report preserves the equipment and checklist recorded at sign-off, together with answers and protected evidence. Use Print slash save inspection PDF, then Save as PDF in the browser's print dialog. The report explains that later audit decisions stay in the audit workspace. Review Current status and linked audit separately, because a historical passing report is not a current release decision.

Ready for a supervised pilot
You have now seen the workflow from equipment setup to signed reports and linked decisions. Before your operational pilot, confirm the actual assets, approved checklists and frequencies, nominated inspectors and release authority, devices and fallback arrangements. Verify scanning and offline synchronisation on the chosen phones. Keep training records separate from pilot acceptance. This series is platform training, not evidence that those operational approvals are complete.