Working Offline and Sync Conflicts

Jobsites lose signal. schedule.construction keeps working: changes are saved on your device and sent when the connection comes back.

When you go offline

A banner says "Offline — edits are saved on this device and will sync when you reconnect. Dates and the critical path refresh after sync."

If you open a schedule offline, you'll see the last copy saved on your device, with "Showing a cached schedule from (time)".

What works offline

• Editing activity fields
• Adding, duplicating, splitting, reordering, and deleting activities
• Adding, editing, and deleting links
• Pasting rows
• Field progress updates

What needs a connection

• Importing a file
• Update progress (the data-date update)
• Capturing a baseline
• Recurring activities, resource leveling, and what-if scenarios
• Posting blocker notes

Syncing

"N change(s) queued offline" shows how many edits are waiting. They sync automatically when you reconnect, or tap Sync now. Dates and float update after the sync, because CPM runs on the server.

Resolving a conflict

If someone else changed the same thing while you were offline, sync pauses and shows Resolve conflict:

• A field was changed by both of you: compare Yours (offline) with Server and choose Keep mine or Keep theirs.
• The activity was deleted while you were offline: Restore as new task or Discard my changes.
• The change can't be applied: Discard this change, Discard all queued, or Reload from server.

Discarding can't be undone, so check with your team first if you're unsure whose change should win.

Don't clear your browser data with changes queued

Queued changes live in your browser's storage until they sync. Clearing site data, or using a private window, before syncing loses them.