Task Priority vs Due Date

Priority and due date answer different questions. Priority asks how much this task matters relative to other tasks. The due date asks when it has to be finished. Teams collapse them into one word, "urgent," and then cannot tell a task that is important next month from a task that is due tomorrow and barely matters.

Keep the fields apart. Use both.

The four priority levels

A task priority is one of four values:

• Urgent
• High
• Normal
• Low

There is no fifth level, no numeric score, and no "critical" unless you rename nothing and simply use Urgent. Normal is the ordinary case. If everything is Urgent, nothing is.

Priority does not move a task across the board. Board columns are statuses. A high-priority task can sit in To do. A low-priority task can sit in In progress because someone started it.

What a due date is

The due date is the day the task is meant to be finished. The calendar view places a task on that day. A task with no due date does not appear on a calendar day. It shows with the undated work.

A due date is not a start date, and it is not a time estimate. Starting earlier is a start date. How long you think it will take is an estimate in minutes. Neither of those is priority.

The due date also does not send an email when it passes. Do not describe it as a reminder campaign. It is a field people can see.

Two tasks that should not share a label

Task A. "Rewrite the pricing page." Priority Urgent, because the commercial offer is wrong. Due date three weeks out, because legal has to read it and the page is not promised this week.

Task B. "Export the attendee list for tomorrow's briefing." Priority Low, because the list is a clerical step. Due date tomorrow, because the briefing is tomorrow.

If you mark both Urgent, you will work the export and postpone the pricing page, or you will ignore the export and miss the briefing. The fields exist so you can do the export tomorrow without pretending it is the most important work you own.

On a board, both might be In progress. The board will not tell you which is Urgent. You read the priority on the task. On a calendar, Task B sits on tomorrow and Task A sits on a later day. The calendar will not tell you that Task A matters more. You read the priority there too.

Which field should drive the day

Use this split:

Question	Read this
What must be finished on this date?	Due date, on the calendar
What is more important if I can only do one?	Priority
What stage is it in?	Status, on the board
What is blocked?	A Blocks link, on the Gantt

Kanban vs Gantt covers the view choice. Priority is not a view. It is a value on the task you can see while you use those views.

A practical order for a morning: look at what is due today and overdue, then among those, do Urgent before Low. Then look at Urgent work that is not due yet and decide whether to start it. That sequence uses both fields. Sorting the whole board by priority and ignoring dates will miss Task B. Sorting only by date will bury Task A until the week it is due, which may be too late to do it well.

How "urgent" gets ruined

Urgent is ruined in three ways:

1. It is used as a due date. "Urgent" with no day means "soon" to the writer and "whenever" to everyone else. Put the day in the due date.
2. It is used as a status. "Urgent" is not In progress. Move the status when work starts.
3. It is applied by default. If new tasks are created as Urgent, the field is decoration. Default to Normal. Raise the priority when the task actually outranks other Normal work.

Low is also a real choice. It tells a teammate they may finish this after higher work, even if a date exists. A low-priority task due tomorrow still needs a person to notice the date. Low does not mean "no date" and it does not mean "ignore."

What not to encode in priority

Do not store a client name, a team, or a billable flag in the priority. Those are tags or custom fields if you need them at all. A currency custom field is not a fee, and priority is not a fee either. Dayzen does not bill from tasks.

Do not expect priority to change the workload view. Workload counts tasks due per person on days in the current month. It does not weight a task heavier because it is Urgent.

A small team agreement

Write four lines where the team can see them:

• Urgent: do this before other work you own, even if the due date is later.
• High: do this soon, after Urgent items that are actually due.
• Normal: ordinary queue.
• Low: do this when higher work is under control, and still respect the due date.

Review the Urgent list once a week. If it has more items than the team can honestly put first, demote some. The field only works when it is scarce.

A week of both fields

Monday: six tasks are due this week. Two are Urgent, both with due dates on Thursday, because they affect a launch. One is Low and due Monday. Do the Low task on Monday. It is small, and the date is today. The Urgent work is not late yet. Starting it on Monday is reasonable if the Low task is finished first. Marking the Low task Urgent so you remember it would be the collapse this page is about. You already have the date.

Wednesday: a new request arrives with no date and the word urgent in the message. Put it in as Normal until someone names a day or explains what it outranks. If it outranks the Thursday launch work, set Urgent and say which Thursday task drops. Priority is a comparison with named work, not a volume setting on the request.

Friday: look at anything due today that is still Not started. That is a date problem, an owner problem, or a real slip. It is not fixed by raising priority on work that is already due. Change the date if the commitment moved, or do the task. Then look at Urgent items due next week and decide whether any should start. The calendar and the priority field each had a turn. Neither was asked to do the other's job.

If you cannot complete that Friday look because too many items are Urgent, the level has inflated. Demote anything that is not actually first. Leave the due dates alone while you do that, so you do not "fix" priority by moving days.

Conclusion

Task priority is Urgent, High, Normal, or Low. The due date is the day it is due. The board shows status. The calendar shows the due date. Use priority when two tasks compete for the same person, and use the date when the question is which day. Mixing them into a single "urgent" label is how important work and soon work get confused. The project tools are on /pms.