Resume the same task when the deliverable is still the same
If you worked for twenty minutes, took a break and returned for another fifteen minutes on the same task, you recorded thirty-five minutes of work towards that deliverable. A break does not require a complete copy of the task. Before adding another task, check whether the result you want has actually changed.
Ora separates estimated time from recorded work. Its public reference documents free focus sessions, breaks and manual actual-time corrections; plan-versus-actual comparison and reports belong to Pro. This is an editorial example, not a session tested in an account.
One folder, two periods of work
Imagine a fictional task: reviewing a folder of documents. In the first session, you review the opening pages for twenty minutes. You stop and leave a note about where to continue. Later, you spend fifteen minutes on the next pages. If both records belong to that task and that day, the example adds up to 20 + 15 = 35 minutes.
Do not automatically turn the second session into another Review folder task with the full original estimate. First identify what you have done and what remains. A second copy could represent another deliverable; it needs a reason beyond having taken a break.
- Check the task identity before resuming.
- Leave a specific interruption note, such as continue from the appendices.
- Check that records reflect actual work and do not accidentally include a break.
- Decide whether the deliverable remains unfinished even though a session ended.
Thirty-five minutes do not establish what remains
If the initial estimate was one hour, subtracting thirty-five leaves twenty-five minutes arithmetically. That does not prove the remaining work can be completed in twenty-five minutes. An unexpected document may have appeared, or the opening section may have been easier. Review the remaining work before reserving another slot.
Do not change the record to sixty minutes just to match the estimate. Work already done and a future forecast answer different questions. If you forgot to stop the timer, check and correct the record using information you actually have rather than inventing precision.
When two deliverables really are different
Reviewing a folder and then writing a report can be different outcomes. Keep them as separate tasks if that describes your work. Stopping for water and returning to the same review does not create another outcome by itself. This guide does not attribute automatic record merging, task splitting or guaranteed remaining-time calculations to Ora.
In Pro reports, also check the period and filters before interpreting a total. Do not mix this example’s thirty-five minutes with another sphere or another day without checking the context.
Choose the next session around what remains
Ora provides web planning with a finite-capacity sphere; it does not guarantee an accurate estimate or complete the work when focus ends. Its public reference keeps reminders and the Android companion under pending acceptance; neither is needed for this decision.
Check the current features and write one sentence describing the unfinished result before resuming. Here it is review the appendices and check the folder is complete. Then reserve a slot you can justify. Two sessions can contribute to one task without becoming two completed tasks.