A start date answers when a task should enter your plan. A due date answers when the result must be finished. Treating them as the same date creates fake urgency.
The difference in one table
Both dates can belong to one task, but they serve different decisions. The start date helps you shape your workload. The due date protects a commitment whose timing is not entirely yours to choose.
| Question | Start date | Due date |
|---|---|---|
| Meaning | When the task should enter the active plan. | When the finished result is required. |
| What changes on that date | The work becomes current and available to begin. | The commitment reaches its deadline. |
| Useful for | Workload planning, lead time, and choosing a week. | External commitments, submissions, and fixed events. |
| Misuse risk | Starting too many tasks at once. | Turning preferences into false overdue work. |
Four examples
Submit passport renewal
If a trip creates a firm latest acceptable submission date, record that as the due date. Choose an earlier start date for gathering the photo, form, and supporting documents. The gap is useful: it acknowledges that preparation takes time without claiming every preparation day is a deadline.
Prepare Friday presentation
Friday's meeting creates the due date. Tuesday might be the start date because it gives you time to draft, ask for missing numbers, and revise. If the meeting moves, the deadline can move while your preferred start remains a separate planning choice.
Replace water filter
A maintenance target may tell you roughly when to act, but it does not always create a hard deadline. Put the task into an appropriate start week. Add a due date only if a real constraint makes completion by a particular day important; otherwise, the start date can carry the planning meaning on its own.
Explore a course recommendation
Curiosity is not automatically a commitment. Keep the recommendation in Backlog, or in a separate capture queue, until it supports a current goal. If you accept it, choose a future start week. It may never need a due date. The related guide to capturing ideas without committing to them can help with this decision.
Why fake deadlines make task lists harder to trust
When every intended work day is stored as a due date, a normal change of plan creates a page of “overdue” tasks. The signal stops distinguishing a missed commitment from an estimate that changed. That is overdue inflation: the label is technically triggered, but it no longer tells you which item has a real consequence today.
The practical cost is extra review. You must open each overdue item, remember what its date was meant to represent, and decide whether anything is actually late. Keeping start and due meanings separate makes the list easier to interpret. Overdue can then mean “the required finish date passed,” while an unfinished start-date task simply needs a new planning decision.
A weekly workflow for both dates
- Capture the work. Write a clear outcome before deciding where it belongs.
- Choose a start week. Consider lead time, dependencies, and the other work already in that week.
- Add a due date only for an external deadline. Record the date another person, event, or real consequence requires the finished result.
- Review unfinished work. Keep, reschedule, return to Backlog, or remove it. Change the due date only when the underlying commitment changes.
This workflow fits naturally inside a weekly plan. For a broader way to choose a realistic scope, see how to plan a week without blocking every hour .
What if your task app only has one date?
Pick one meaning and use it consistently. You can treat the field as a do date—the day or week when you intend to act—or as a deadline—the last acceptable completion date. Neither convention is universally correct. Consistency is what lets you scan the list without interpreting the same field differently on every task.
Keep the other meaning in a label or note. For example, if the app's date always means deadline, add “Begin Tuesday” to the task note. If it always means do date, write “Must submit by Friday” in a visible label. Use separate calendar events for appointments, because attending at a fixed time is a different kind of constraint from completing a task by a date.
How Getsbetter uses both dates
In Getsbetter, start dates place tasks into Backlog or weekly views while due dates remain independent deadlines. A task planned for the current week appears in Current Week; work placed into the near future appears in Upcoming; work with a more distant start remains in scheduled Backlog until its week approaches. An item without a start date can stay in unscheduled Backlog.
Because the due date is separate, a Friday obligation can remain due Friday even if you decide to begin on Tuesday. If unfinished work needs a different week, you can revise the start date without pretending the external commitment changed. That preserves both pieces of information: when you plan to engage and when the result is truly required.