Friday is the deadline. When will you do the work?
Julia promised to send a client a proposal on Friday. On Monday, she added “Prepare proposal” to Friday's list and relaxed. On Thursday, she discovered that she first needed prices from a colleague, then a calculation, then a review. The entry was accurate, but it never said when the work itself would happen. This is a teaching example; names, dates and times are illustrative.
A task raises two different questions. The planned day is when I intend to work on it. The deadline is when the result must be ready. One date can answer both questions, but that should be a deliberate decision rather than a default.
- Plan: Tuesday
Prepare the calculation. This is a commitment to yourself about the work; you can reconsider it based on your workload.
- Deadline: Friday
Send the proposal to the client. This is a commitment to someone else; changing it requires agreement.
Other planners also separate the start and finish: Asana, for example, describes separate start dates and due dates. This is a useful model, but in Sinqly we use a planned day for an individual action. It does not mean the service has automatically reserved time in your calendar.
Work backward from the deadline to the first action
Start with a result someone can receive: “Reviewed proposal sent.” Now ask what must happen before that. Julia writes down three prerequisites: get the initial prices, prepare the calculation and check the figures. You do not need a separate task for every button click. You need steps separated by a decision, a wait or a result of their own.
- Mon → get the data
Request the prices and ask when your colleague can reply. Without a reply, the calculation is not ready to start.
- Tue–Wed → prepare and check
Prepare the calculation on Tuesday and check the figures on Wednesday. These are chosen work days, not new promises to the client.
- Thu → buffer, Fri → send
Thursday is reserved for clarifications. Friday is for sending the proposal, not doing all the preparation at once.
This buffer is neither a standard nor a magic percentage. Julia left a specific window because the figures may come back with questions. If approval usually takes several days, one Thursday is not enough: request the data earlier or discuss a different deadline. A plan should reflect dependencies rather than hide them behind tidy dates.
In Sinqly: give the action a day and the commitment a deadline
In the example task list, the calculation is planned for October 13, the review for October 14 and sending for October 16. Sending also has a separate October 16 deadline. When applying this approach, the goal is to distinguish work from commitments in your own list, not to copy our dates.
Open the relevant task's date and set its planned day. Do not give every preparation step the client's deadline just to get a red marker. Otherwise, the list will once again stop showing what needs to happen in advance.
If an intermediate step has its own real commitment—for example, you agreed to send the calculation to a colleague on Tuesday—it has a deadline of its own. Keep it. The distinction comes from the agreement, not the size or importance of the task.
Wednesday did not work out: what should move?
Suppose the data arrived late and you could not check the figures on Wednesday. First, assess the remaining work and the time available on Thursday. If the review fits and sending is still realistic, change the review's planned day. The Friday deadline for sending does not have to move with it.
Sometimes an honest option is to send an agreed first part on Friday and the rest later. But the recipient must confirm that this result works for them. For Julia, “unchecked figures instead of a proposal” does not fulfill the agreement: it is a different result with a different risk.
When there is no external deadline
Sorting materials, reading an article or trying a new approach may have no deadline. That does not make them unimportant. Choose a work day if you are ready to make time for them. If you are not ready yet, leave the task without an invented urgent deadline and return to it when reviewing the list.
- You have promised someone a result
Keep the real deadline. Separately choose when you will do the preparation.
- You only have an intention
Set a planned day. Do not create an overdue task just to make it feel serious.
A self-imposed deadline can sometimes help as a personal technique. Remember that it is your constraint, not an obligation to someone else. Do not mix it up with a report submission or payment date: when everything looks equally urgent, the list stops helping you choose.
A check before closing your planner
Look at your next task with a deadline and ask one question: does the list show when I will start the work? If it only shows the final day, add an earlier preparation step.
Then check three things: whether there is enough available time, whether you depend on other people and who needs to hear about a change. Julia needs a reply from her colleague, a window for reviewing the figures and a clear deadline for the client. A neat calendar cannot replace any of those agreements.
More questions to clarify
Can the planned day and deadline be the same date?
Yes, if the action can actually be completed that day and needs no earlier preparation. That may be fine for a quick send; for an entire project, it is a reason to check the prerequisites.
Will Sinqly automatically reschedule related actions?
Not in this example. We show a manual change to an individual task. After rescheduling, you check the other steps and agreements yourself.
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
- Asana: the distinction between start and due dates (2017); not a source of information about Sinqly
- The suggested process reflects editorial practice; it does not promise identical results for everyone.



