At a glance
A due date records when something must be finished; a scheduled date reserves when you intend to work on it. Give substantial work a place before its deadline. If you move a work session, keep the original commitment visible and check whether the remaining time, inputs, and review steps still make the deadline feasible.
A due date is the agreed finish point. A scheduled date is when you intend to do the work that gets you there. Keep those meanings separate: moving a work session changes your plan, but it does not change the deadline someone else is relying on.
What is the difference?
| Question | Due date | Scheduled date |
|---|---|---|
| What does it describe? | When the agreed result must be ready | When you plan to work on a task |
| Who may depend on it? | A client, collaborator, event, or another task | You and anyone sharing the work session |
| When can it move? | When the relevant commitment is renegotiated or its conditions change | When another usable work slot exists without breaking a commitment |
| Example | Send the approved deck Friday at noon | Draft slides Tuesday from 9 to 11 a.m. |
Different tools use different labels. For example, Todoist’s deadline documentation explicitly distinguishes its work dates from fixed completion deadlines. Check the meaning of the field in the tool you use rather than assuming that every date picker records the same thing.
Some dates describe both a commitment and a reserved time: a client call is an appointment you have agreed to attend. Other work may have a target you choose yourself rather than a fixed outside deadline. Label that honestly instead of making every task look equally urgent.
Which tasks need a place in the calendar?
Schedule work when it needs protected time, when another person must attend, or when a prerequisite makes the timing important. You can leave a small flexible task on a list, but do not leave a substantial deliverable with only a finish date and no plan for doing it.
- Record the commitment. Name the result, recipient, finish date, and any relevant time zone.
- Break it into actions. Separate preparation, production, review, and delivery when each needs its own time or input.
- Estimate the work. Use the information available and make uncertainty visible. A task that may take two to five hours needs a different plan from a reliable 20-minute action.
- Place usable sessions before the finish. Leave space for required feedback and the final handoff, not just production.
- Check other commitments. Use the freelance capacity calculation to see whether the work fits alongside what you have already accepted.
Worked example: a deck due Friday at noon
Imagine a consultant has agreed to deliver a short presentation deck on Friday at noon. They expect six hours of their own work and need the client’s feedback before the final revision. This is an illustrative plan; the estimates and turnaround are not universal recommendations.
| Action | Planned session | Duration |
|---|---|---|
| Check the brief and outline the story | Monday, 10–11 a.m. | 1 hour |
| Draft the slides | Tuesday, 9–11 a.m. | 2 hours |
| Review and send the draft | Wednesday, 10–11 a.m. | 1 hour |
| Apply consolidated feedback | Thursday, 2–3:30 p.m. | 1.5 hours |
| Check the export and deliver | Friday, 10–10:30 a.m. | 0.5 hours |
The sessions total six hours. The plan also assumes feedback arrives by Thursday morning. Record that dependency with the client; it is not part of the consultant’s six work hours, but it affects whether Thursday’s session can proceed.
If Tuesday becomes unavailable, a Wednesday 8–10 a.m. slot could preserve this example’s draft-review session only if that slot is actually free and two hours remains a credible estimate. Dragging the work into Wednesday is not enough; check the dependencies and the rest of that day.
What should happen when a work session moves?
Keep the deadline visible and reassess the remaining plan. Ask whether there is enough usable time, whether the required inputs will arrive, and whether anyone else needs to adjust. If the plan no longer fits, discuss a revised deadline or scope before continuing on an assumption.
Do not repeatedly move a task to tomorrow until its deadline disappears into routine rescheduling. A missed work session is information: the estimate, availability, priority, or dependency may need to change. The guide to setting better deadlines covers the commitment itself; this guide keeps that commitment distinct from the working plan.
Use the distinction in ProjectBook
Use the daily planner to choose a task’s scheduled day or time and set its duration. For a project with an agreed finish, record the project end date and describe the commitment clearly in the project overview.
For a task-specific cutoff, keep a plain note such as “Delivery deadline: Friday noon, client’s time zone” in the task description. ProjectBook’s current task scheduling controls do not provide a separate dedicated deadline field. Rescheduling the task therefore needs a manual check against that recorded commitment; this guide does not promise an automatic deadline warning.
Build the week around those sessions with the time-blocking template. A short review of the next deadlines and unfinished sessions is more useful than filling every calendar gap. Find related planning habits in the Productivity guides.
From ideas to a clearer week