MyBoatDeskBoat records
All guides

Offline

Work offline and synchronize safely

Supported workflows update locally and submit named mutations when a connection becomes available.

Before you begin

  • A device that has signed in previously
  • Enough local space for records and file bytes
  1. 1

    Synchronize before leaving

    Open the boat on a good connection before an extended offline period so the local projection is current.

  2. 2

    Capture work offline

    Save supported records normally. Pending mutations remain in the local queue.

  3. 3

    Keep file bytes local

    Files stay on device until an authorized upload succeeds. Do not remove the local copy first.

  4. 4

    Resolve visible conflicts

    Permanent validation or version conflicts remain visible and are never silently overwritten.

Check the result

Local changes appear immediately and later become either accepted records or clearly explained permanent conflicts. Review “Work offline and synchronize safely” once from another crew member’s perspective: labels, status and the next action should make sense without a verbal explanation.

If something goes wrong

If work remains queued, keep the app available, verify connection and account access, and do not create a duplicate entry.

Keep data safe and traceable

For “Work offline and synchronize safely”, capture only information required for the task. Passwords, access tokens and complete payment details never belong in notes or screenshots. Every change should remain connected to the correct boat, a responsible person and a visible status. If two devices produce different versions, resolve the conflict deliberately; an earlier accepted record must not disappear without explanation.

After the first real use

After the first use, review the workflow against “Synchronize before leaving”, “Capture work offline”, “Keep file bytes local”, “Resolve visible conflicts”. Add missing labels, sources or follow-up work in context. A short review at season change, after a crew change or when signing in on a new device is then enough. The guide remains useful without maintaining the same task in parallel private lists.