Checks · local product-use draft
Local draft or server receipt? Read the difference.
Understand what Fleet has saved locally, what the server has committed and what a safe retry preserves.
Prepared 13 November 2026 from the implemented local workflow. Local product-use draft; independent operational and legal review remains open.
Confirm the asset and actor
Start from the currently assigned asset and applicable versioned template. A current authorised session is required to send or recover a receipt; an old assignment or another person’s session does not inherit the pending operation.
A saved local record is still local
The local queue can preserve explicit answers and synthetic photo blobs while offline. Pending, uploading, conflict and received describe different states. Do not treat a local save or successful network request alone as a server-confirmed check.
Use the committed receipt
A confirmed receipt identifies the canonical check, original operation, actor and server time. After response loss, retry the original frozen request. The server checks the payload and current scope before returning that same receipt.
Keep the urgent route separate
Use the operator’s configured urgent reporting procedure for immediate concerns. The local prototype does not send real alerts or prove a manager has received an offline observation. Operational templates, encrypted storage/privacy and physical-device acceptance remain open.
Product context and sources
This guide describes the current local Fleet feature and its visible record/permission boundaries. It does not define a legal retention period, statutory check schedule or competent release policy.
Open the related feature explanation