If your task says “have the booking confirmed,” sending a request does not make that outcome complete. Separate two things: send the required details and obtain confirmation. The first can be done while the second remains pending. You can preserve progress without inventing someone else’s reply.
This fictional example works on paper. It does not describe email integration, automatic bookings or message tracking in Nivora.
One case, two different outcomes
Imagine booking a room for an activity. You know the date you want and the information requested. Your first action is to send a complete request. Confirmation depends on the person managing the room.
Before sending it, define completion for your action: “Request sent to the correct destination with the date and required details.” That definition does not change the second condition: you still need actual confirmation before treating the room as booked.
| Item | What establishes it in this case | What it does not prove |
|---|---|---|
| Sending the request | Required details sent to the correct destination | That the room is available or booked |
| Receiving confirmation | A reply confirming this booking | That silence means acceptance |
| Reviewing the pending item | Checking for a reply and deciding what to do | That reviewing compels someone else to reply |
These are exercise criteria, not new application states. Match required details to the actual process you are following; do not send unnecessary information.
Keep a review date without making it a promise
After sending, write: “Request sent; confirmation pending; I will review before I must decide on another option.” If you choose a review date, it commits you to reviewing rather than guaranteeing a reply date.
If there is a real external deadline, retain it separately and check what it requires. Do not invent that the request will be accepted before then or that another notification changes the other person’s commitment.
What Nivora represents and what you decide
The Nivora facts document tasks with a definition of done, deadline, optional checkpoint and first progress without a timer. It limits the active front to three priorities; additional tasks wait until a slot becomes free. Active tasks are ordered by the nearest deadline.
That capacity wait does not prove external dependency detection. “Awaiting reply” is a description you retain when preparing the task. We do not assign the app a Waiting tag, email reading, reply detection or automatic next-action selection.
If you complete a task scoped only to sending, keep the larger outcome pending in your organization. If the original scope was confirmation, do not mark it done merely because you sent the request. For more detail, read the done, deadline and first-progress guide.
Compare what waiting means in each tool
Things suggests ways to organize waiting tasks, while Todoist distinguishes work dates and deadlines. These are different systems; their tags or dates do not automatically transfer to Nivora. Sources consulted on 23 October 2026, without comparing personal outcomes.
Write two lines before changing anything: “My action is complete when…” and “The external outcome remains pending until…”. Check Nivora’s method if this approach interests you. It remains a local Android preview with no public download, price or launch date. It is not a medical service and does not guarantee timely completion.

