ora.
A fictional person reviews unmarked cards beside a clock on a kitchen table.
AI-generated image; illustrative scene.

Your day is running late: change the plan without erasing the work

Keep the past first; then decide what still fits

When a task overruns by 30 minutes, do not erase those minutes to make the plan look tidy again. Preserve the time actually worked, identify the next commitment you cannot move and decide which remaining work fits before it. Everything else needs another slot or a change of scope.

Ora records actual time using a timer or manual corrections. Pro replanning adds a proposal you can review, apply or undo while preserving recorded time. This guide explains a manual decision around that feature; it does not promise to finish everything or turn an estimate into a met deadline.

A concrete delay, without inventing another hour

Fictional example: it is 16:00 and you have a fixed commitment at 17:00. A review planned for 45 minutes took 75: a difference of 30. You still need 40 minutes to finish a document, 25 to answer messages and want to reserve 10 to prepare for the commitment.

There are 60 minutes between 16:00 and 17:00. The three activities need 75: you are short by 15. Moving their bubbles does not create those minutes. You could finish the document in 40 minutes and prepare for the commitment in 10, leaving a 10-minute buffer while messages need another slot.

These numbers are an arithmetic example, not a customer outcome or a universal recommendation. If the document depends on an outstanding reply, check that dependency before choosing it.

Record what happened before moving unfinished work

Stop the timer when the actual task ends, or correct its minutes if you log manually. Check that the 75 minutes correspond to the work you intend to record. Keep the original 45-minute estimate distinct: the difference may help you reconsider a future estimate.

Do not mark unfinished work complete or log time you did not work to balance the picture. Your record describes the past; your plan describes what you still choose to do. Planned-versus-actual comparison is a Pro feature.

Review the proposal, not just the new start time

When preparing a delay or new-appointment replanning proposal in Ora Pro, protect commitments and review the relevant dependencies. Before applying it, check the complete result:

  • The 17:00 commitment remains where it needs to be.
  • Previously recorded work is preserved.
  • The document has enough space and its dependencies allow it to start.
  • Messages deliberately move to another slot and are not counted twice.
  • Preparation time and your chosen buffer still fit.

Check the scope and availability of Ora replanning

When it does not fit, change a decision outside the picture

You can reduce the document scope where appropriate, move messages to a real slot or renegotiate a delivery with the relevant person. These are your decisions; this guide does not claim Ora contacts anyone or chooses which commitment to miss.

A sphere represents 24 hours and its limit prevents overbooking, but fitting within a day does not establish that the work fits before 17:00. For a specific commitment, check the available interval too. A valid daily total does not, by itself, resolve a scheduling conflict.

Other ways to approach replanning

Sunsama documents shifting task working sessions after conflicts or early completion. Motion explains using duration, priorities, deadlines and availability to move tasks and flag work that cannot fit. These are established approaches; this guide has not measured which produces better results.

The contribution here is checking recorded history and a specific available interval before accepting a revised plan. You can use that review on paper or in your existing tool. Sources checked on October 22, 2026.

Sunsama: auto-rescheduling documentation

Motion: auto-scheduling behavior and limits

Explore the workflow before relying on it for an important day

Ora’s public demo works without registration and keeps changes in that browser tab. Explore the visual plan there and use the feature page to distinguish Free, Pro and pending acceptance. This guide does not promise the demo enables every Pro feature.

This example does not require a connected calendar or automatic reminders. Provider connections and actual reminder delivery have separate validation states. Check their current status before depending on them.

Explore the public Ora demo

Review current features, plans and limits

Try the Ora demoFeatures and availabilityMore guides