A protected appointment can still be unprepared
If a meeting remains at 10:00 but its required document moves to 11:00, preserving the time does not resolve the plan. Before applying an Ora proposal, check the relationship between the protected appointment and work that must happen beforehand.
Protection answers “what must not move”. A dependency answers “what must come first”. Review both conditions in the preview; you define what prepared means. Ora can preview changes, protect commitments and respect dependencies; applying or undoing is a Pro feature.
A delay with a handoff that still matters
Invented example: you planned a task from 09:00 to 09:40 and a fixed meeting at 10:00. You arrive at 09:30. The whole task no longer fits before the meeting: it needs forty minutes and only thirty remain.
Now imagine you must deliver a document before that meeting. Moving all the work to 11:00 would miss that requirement. These are conditions in this example, not advice to change a deadline without agreement.
- Keep the meeting as a protected commitment.
- Check whether the earlier task depends on unfinished work or another task depends on it.
- Review which work is flexible and which scope or deadline change needs agreement outside Ora.
Read the proposal as a decision, not an order
In the preview, check the result against your real commitments. If a task changes time, check that it still serves its purpose: a document needed for the meeting is not resolved by scheduling it afterwards.
When there is insufficient space, decide what to remove, reduce with agreement or move to another time. Change the plan’s conditions before applying a proposal you cannot fulfil. We do not claim Ora understands a document’s meaning or negotiates with other people.
Distinguish three outcomes in this example: finish the document before 10:00 if it truly fits, agree a smaller useful document or change the commitment with the relevant person. Simply moving it to 11:00 does not preserve the preparation’s purpose. These are human decisions; we do not claim Ora negotiates or understands the document’s contents.
What to check before applying
Review the protected commitment’s time, available duration, dependencies and the destination of each moved task, in that order. If the result fits, a Pro account can apply the proposal. If it does not, keep the decision open and adjust the plan.
This guide uses commitments you prepared in Ora. It does not require Google Calendar or treat an external integration as validated. The public facts distinguish available capabilities from integrations still in validation.
Check the commitment, then the schedule
Before accepting, trace the relationship both ways: from the meeting, identify what must be ready; from the moved task, check which commitment it serves. This reveals an order that stopped being useful even when times no longer overlap.
Open Ora and review your next change against one concrete commitment. No productivity outcome or reminder delivery is guaranteed.