Compare the change, not just the copy time
When you have a remote version, your local plan and a recovered copy, inspect what each preserves before replacing anything. The newest copy might contain your revised duration while missing a note added in another version.
Ora provides an optional per-account local copy, off by default. It stores plans as plain text in IndexedDB, supports recovering unsent changes and compares remote, local and recovered versions before explicit conflict resolution. This guide proposes a manual check; it does not promise automatic merging.
A worked example with two different changes
Invented example: the server plan contains “Pack suitcase”, 30 minutes and the note “bring adapter”. While offline you change the duration on your laptop to 40 minutes. Another version adds “bring charger” and keeps 30 minutes.
Before choosing, write down what you want to retain: 40 minutes if that remains your estimate, and both notes if still relevant. Do not add 30 and 40: they are alternative estimates for the same moment. Seeing the laptop change after reopening does not establish that it was sent.
Review briefly before confirming
Check that you are in the intended account and sphere. Read the name, duration, notes and steps that differ between versions. Decide what to recover and review the outcome before continuing to plan.
Keep three questions separate: what can I see now, which change do I want to retain, and which remote version has been confirmed? A paper note can help while you inspect the choices your session offers; these are not screen names or a tested click sequence.
The local copy has limits
Browser quota or eviction can prevent persistence. Reconnection needs an open page: there is no delivery in the background with the app closed. Logging out clears local copies after confirmation of unsent changes. Do not make logging out or clearing storage your first response to a discrepancy.
This feature does not guarantee retaining every change or replace a reviewed planning backup. Mobile acceptance remains pending. This example concerns personal plans; shared-space drafts remain in memory rather than using this cache.
Check the scope before using your own data
Explore the planner in the no-registration demo; edits remain in that tab. Consult the public capability reference for saved plans and recovery limits. The demo does not certify account durability.