Check which period the reminder concerns
“Send the documents” might mean September’s completed submission or a new request for October. Before treating it as a duplicate or reopening completed work, check the requested period, document and recipient. Similar wording does not establish that it is the same task.
In this fictional example, you sent September’s documents and retained confirmation. A reminder arrives requesting October’s documents. The earlier work remains complete: the new request has a different scope. You do not need to delete the previous confirmation to prepare the next submission.
Write two distinguishable commitments
On paper, you could write “September documents: sent” and “October documents: prepare and send the requested file.” Give the second task its own completion condition and a deadline grounded in the actual request. Do not automatically copy last month’s date; the example does not assume every request expires on the same day.
A first step might be checking which file belongs to October. If the reminder does not identify the period, asking for clarification is a different action from resending every document. Do not include personal or third-party information unnecessary to recognise the commitment.
If it is a duplicate, retain the evidence
Alternatively, the reminder might request exactly the same September submission. Check your confirmation and clarify what is missing before sending it again. A sending confirmation also does not by itself establish acceptance by the recipient; describe the evidence you actually have.
The reminder’s appearance does not resolve the difference between these cases. The requested period and deliverable do. That check lets you choose between preparing new work and clarifying a repeated request, while retaining a record of what you did.
What to expect from Nivora
The Nivora facts page describes tasks with a completion condition, deadline, optional checkpoint and first step; reminders are user-selected. That page does not document duplicate detection or automatic monthly task creation. This article proposes a manual distinction and does not attribute those features to the product.
Todoist explains recurring dates, and TickTick maintains its help centre. Consult each approach if you want automatic recurrence; do not presume identical handling of completed work. Nivora remains a local Android preview without a public download, price or release date. Start with two commitments on paper and consult the Nivora website for its current status.

