Work offline and sync

May not be enabled

Mobile offline syncmay not be turned on for your workspace or plan. If you don't see it, contact your workspace admin.

Plant rooms, basements and remote sites are exactly where signal disappears and work still has to be recorded. The app keeps a copy of your work on the device, so you carry on, and everything you did syncs when you’re back in coverage.

Note

Offline working arrives with the Belrald Assets mobile app. The web app needs a connection — it tells you when you drop offline and blocks actions that can’t be queued. This guide describes how offline mode behaves once the app is available to you.

Before you lose signal

Open the app while you still have a connection and let it finish downloading. It keeps a local copy of the work you need on site: your work orders, the assets they cover, the procedures attached to them, and your meters.

Tip

Open the specific jobs you expect to do before you go in. Anything you’ve opened is definitely on the device.

What you can do with no signal

• View your assigned work orders and the assets they’re against.
• Update a work order — status, notes, time spent.
• Run a procedure and answer its steps.
• Record meter readings.
• Take photos and attach them to the job.

Reference data — labels, templates and workflow settings — comes down to the device read-only. You’ll see it offline, but it’s changed from the desktop, not from the field.

When you’re back in coverage

The app sends your queued changes first, then pulls down everything that has changed on the server since your last sync. Each queued change carries its own id, so a sync that retries after a dropped connection never records your work twice.

Caution

Keep the app open until the sync finishes. Photos upload separately from the records they belong to and are usually the slowest part.

How conflicts are settled

If someone changed the same record while you were offline, the app doesn’t silently pick a winner:

• Work orders and procedure runs merge field by field. Every field nobody else touched takes your value; a field that changed on the server while you were offline keeps the server’s value, and the clash is reported back to you rather than quietly resolved.
• Meter readings, time entries, parts used and comments are only ever added, never edited, so they can’t conflict.
• Assets are settled on the server. If the asset changed while you were offline, your edit is rejected and you’re shown the current version to redo it against. This is deliberate — asset records are shared, and quietly overwriting someone else’s change is worse than asking you to look again.