Size represents time; the decision also needs the commitment
Ora’s bubbles show the time you allocate to activities. A bigger bubble reserves a longer duration; it does not establish that the commitment is more important, more urgent or further along. Read the task’s name and context before choosing what to do, alongside looking at its size.
The sphere represents a twenty-four-hour day with a capacity limit. That view helps you see how much time you have allocated. Importance requires another question: what would happen if you left this until later? This guide does not claim Ora calculates that consequence for you.
Five minutes can resolve today’s binding commitment
Fictional example: you agreed to confirm before noon whether you will hand over an item this afternoon. You estimate five minutes to check the agreement and reply. You also want to organize a box of supplies, for which you have allocated sixty minutes, with no agreed deadline in this scenario.
The second activity has twelve times the estimated duration of the first: 60 ÷ 5 = 12. That does not make it twelve times as important. Looking only at the large bubble can hide a short confirmation with an actual deadline. These times are estimates for the example, not measured data or universal recommendations.
In this situation, check the agreement and handle the confirmation before its deadline. Then decide when organizing the box fits. The criterion follows from the fictional commitment, rather than an automatic priority rule or an observed app result.
Give the task context before placing it in the day
Ora documents an inbox, projects, labels, notes and checklists. Use a recognizable name and a note to retain what you need to confirm and by when. Avoid recording someone else’s details unless you need them for the decision.
Compare two invented descriptions: “Handover” and “Confirm this afternoon’s handover before noon.” The second retains the pending action. This does not mean Ora automatically interprets that sentence as an alert or calendar event.
When adding a task to the day, review the duration you actually want to reserve and your other commitments. Do not inflate its duration to make it look important: allocating forty minutes to an action you estimate at five changes time planning, not the agreement. If you need a buffer, decide how much and why.
A planned bubble does not establish completed work either
A sixty-minute allocation remains a plan. Ora supports recorded time through a timer or manual corrections; Pro adds planned-versus-recorded comparison. Neither replaces checking whether you sent the confirmation or finished organizing.
When reviewing the day, separate three questions: how much you allocated, how much time you recorded and what result exists. A sent reply can meet the example’s first commitment; a bubble on the screen does not establish that the reply was sent.
Try the decision with two tasks of your own
Find a short activity with a specific commitment and a longer one whose date you can choose. Read their context before comparing size. Review what you will reserve today and what can remain in the inbox.
The sphere and task organization are listed as available on the free plan. Consult the features and public demo to consider the workflow. This is a planning suggestion, not an interface test or a promise that a visual planner determines your priorities.