Another page changes the task you were closing
Before continuing, compare the new request with your definition of finished. Decide what you accept and what needs clarification. An earlier plan does not automatically include another page, its materials and its review.
This external exercise organises an everyday scope change. It describes neither automatic negotiation, version history nor shared project management in Nivora.
The leaflet that gained a second page
Fictional case: you were preparing one page with an association’s programme. Your definition was “reviewed programme and PDF ready to send”. Now someone asks for a second page with directions. The programme is ready, but you have no confirmed directions text.
You can keep this comparison on paper:
| Part | Status in this case |
|---|---|
| Original work | One-page programme prepared |
| New request | Add directions on a second page |
| Missing information | Who confirms directions and what they must include |
| Pending decision | Accept, narrow or clarify the request before committing to delivery |
Do not mark everything finished because page one is ready. Nor erase that work: it remains a prepared part. “Nothing is done” and “it is finished” would each lose different information.
Rewrite the finish only after deciding
For this fiction, assume you confirm and accept adding directions. A new definition could be “PDF with the programme and confirmed directions; both pages reviewed”. That is this case’s choice, not an acceptance you must always give.
A concrete first advance might be requesting the text and identifying who will validate it. Keep that dependency explicit while it is missing. Do not invent a route merely to close the file. When information arrives, recheck remaining work and whether the agreed deadline is still viable.
If the request is ambiguous, one possible question is “Which directions do you need and who can confirm them?” If you cannot take it on, your decision may differ; this guide replaces neither that conversation nor contractual advice. A scope change need not become a personal reproach for taking longer.
How this fits Nivora’s planned scope
Nivora is a local Android planner in preview. It orders pending work by deadline and supports defining completion, one optional checkpoint, a concrete first advance and voluntary reminders. It keeps up to three active priorities and leaves other tasks waiting; it imposes neither minute-based timers nor daily streaks.
Use these questions to prepare your description without attributing automatic change detection or third-party acceptance to the app. There is no public download or announced date. Consult Nivora’s presentation and primary reference. The leaflet comparison is invented and can be done on paper.

