A red date does not tell you what to do
On Friday, Anna opens her list and sees “Get the landing page design approved” with yesterday's deadline. The design is not approved: the editor has not even received the first screen. The quickest action is to change the date to today. But that does not answer the main question: when will Anna send the material, and how much time will the editor need? The story and task are illustrative; below is the real interface with fictional data.
Reviewing overdue tasks does not start with the calendar. First decide what to do about the commitment, then change its date. Otherwise, tomorrow will bring the same list with a new red number.
- Cosmetic rescheduling
Put every task on tomorrow's list. The list looks fresher, but the workload and agreements stay the same.
- A meaningful review
Understand what is still needed, who was promised a result and which next step is possible. Reschedule only after deciding.
In GTD, David Allen specifically describes renegotiating commitments when circumstances change. This is guidance for reviewing, not a requirement to complete everything that has accumulated. The process below is our editorial practice for a specific list; it does not diagnose the causes of postponement or promise to remove them in one evening.
Gather the facts first; do not start doing everything
Open the list and choose one overdue entry. Check whether the result is still needed, who is waiting for it and what has already happened outside the app. An email may have been sent yesterday, with the checkmark forgotten. Or a meeting was cancelled, but preparing for it still appears as a commitment. These cases need different decisions.
Do not turn a review into an unplanned work marathon. If you need a quick look at correspondence to check the status, do that. If you discover a large piece of work, first decide where it will fit. Otherwise, you will only review the first item and the rest of the list will remain unclear.
Every backlog item needs a decision
- Already completed
Check the result and mark it complete. Do not repeat the work just to get a checkmark.
- No longer needed
Remove it from the active plan. If you made an external promise, communicate the cancellation first.
- Needed, but not now
Choose a realistic day or leave it without an invented deadline until the next review.
- Needed, and the deadline was missed
Clarify the consequences and revised scope. Contact the person waiting before changing the promise.
Anna chooses the last option. The landing page is still needed, the editor is waiting for the material and final approval today is already uncertain. So the task is to restore the agreement, not press a reschedule button. This can feel less comfortable than changing a date, but it is where a new realistic plan begins.
What to write to the person waiting
Instead of “Sorry, I won't make it; I'll try to hurry,” Anna writes: “The first screen has not been sent yet, and yesterday's approval deadline was missed. I can send it today by 15:00. I suggest moving final approval to Monday. Would that work, or does the launch require another part sooner?” This is an example message, not a universal formula.
The message gives a fact, the next action and a proposal. A new deadline becomes an agreement after a reply, not after editing a date in Sinqly. If the consequences are serious, choose an appropriate communication channel and discuss them directly.
Until the reply arrives, you can separately plan what depends on you: “Send the first screen to the editor.” “Get the design approved” remains a result with an external dependency. Do not promise to finish someone else's part of the process just because you want to clear an overdue task.
Save the next step in the card, rather than an excuse
Open the task and refine its description: what material to send, to whom and what counts as a response. Our screenshot explicitly states that the first screen and the editor's decision are needed: accept it or list specific revisions. That note is more useful than a long account of why the deadline was missed.
Once the new deadline is agreed, update it. Choose the day for your own work separately. If a general item has become two independent actions, create them separately: send the material and check for a reply. Do not attribute automatic approval or editor notifications to the app—you maintain the agreement in this scenario.
After the review, find a recurring cause
If the same task moves for the third time, examine how it is defined. Perhaps it is an entire project behind a short title, essential inputs are missing or the deadline was invented without checking the calendar. Changing the date will fix none of these causes. Make the step smaller, request what is missing or honestly withdraw the commitment.
- The result is clear
No entry leaves you guessing what it means all over again.
- The next step is named
You can see what to do yourself and what you are waiting for from someone else.
- Deadlines are agreed
Dates reflect decisions rather than attempts to clear the screen.
At the next review, return to pending responses that have stalled as well as red dates. This can help you notice a problem before another missed deadline. Reviewing a few important backlog items is enough to start; clearing the list quickly matters less than keeping the remaining promises truthful.
More questions to clarify
Does every old task need a new date?
No. First check whether the task is needed and has a real deadline. A deferred idea without a commitment does not have to become tomorrow's overdue task.
Can I review one overdue task a day?
Yes, if there are no urgent consequences or external promises requiring an immediate conversation. Choose the order by consequences, not just the age of the entry.
Was this helpful?
Rate the article and tell us what was missing. Your feedback goes to the Sinqly team and will not be published on the site.
Sources and notes
- David Allen: Renegotiate Your Commitments—on reviewing commitments, 2020
- The suggested process reflects editorial practice; it does not promise identical results for everyone.



