ora.
A fictional adult plans a house move beside boxes and a closed laptop.
AI-generated image; illustrative scene.

One move, several days: split the project instead of filling one Ora sphere

Group the project; reserve only each day’s work

A moving project can hold several tasks without putting them all in today’s sphere. Ora’s inbox, projects and labels organize pending work; a sphere shows the time allocated to a day. Grouping work and reserving capacity are separate decisions.

Before placing the project in a daily plan, separate actions whose completion you can recognize. A single bubble called “move house” may not answer the question you need: which part will I do today, and which part on another day?

Two hours spread out, rather than one impossible block

Fictional example: estimate 45 minutes to review the boxes you need on Monday, 30 to confirm transport on Tuesday and 45 to prepare an essentials box on Wednesday. That is 120 planned minutes across three days. These are not recorded actuals or a promise of how long moving takes.

Keep related tasks in the project and decide which date and space belongs to each action. A two-hour total does not establish that you have two hours available today, or that you can perform work dependent on an outstanding confirmation.

Inspect the day receiving each task

For each action, check that day’s commitments, rest and other allocated time. Ora documents a 24-hour limit per sphere; creating another project does not increase that capacity.

  • Choose one concrete action and its estimate, rather than copying the whole project into the day.
  • Check what must be decided first, such as transport before a dependent delivery.
  • If it does not fit, choose another date or review the scope you intend to complete.
  • Record what actually happened if you want a later comparison; an estimate is not an actual record by default.

The project does not schedule the tasks for you

This guide proposes manual organization using published features. It does not claim that Ora automatically finds moving dates, turns a list into a week or confirms external services. Replanning has a separate review flow; Pro can apply or undo proposals while preserving recorded time.

If a confirmation call takes longer, review dependent actions before moving everything out of habit. Keep the work that happened and change pending work without declaring the project finished.

Try a small project

The public facts list the inbox, projects, labels, notes and checklists as available free features. Planned-versus-actual comparisons and other tools have their own plan conditions. You do not need a calendar connection or an integration awaiting validation to understand this example.

Review the features and try the demo with fictional information. Begin with three related actions and ask of each: what will I finish, how much time will I reserve, and on which real day does it fit?

Ora features and current status

Open the Ora demo

Public capability facts

Try the Ora demoFeatures and availabilityMore guides