The planner starts with the final step and moves backward through the list. A step that needs one day may use its end date; the previous step must finish the day before. This keeps the steps consecutive without inventing hidden gaps.
Weekends and holidays count. Dates are moved as local calendar dates instead of dividing milliseconds, so daylight-saving changes do not shift the result by a day. If a process only runs on business days, include that waiting time in its duration.
The planner keeps one ordered plan and does not ask you to check off work. It highlights the step you should have reached today, while the timeline remains a calculation you can adjust whenever the deadline or duration changes.
Common questions and answers about this topic.
Yes. The final step may use the completion date itself. A one-day final step can therefore start and finish on the deadline.
No. Version one uses calendar days. If an office, delivery or approval pauses on non-working days, include those waiting days in that step's duration.
The result highlights the step you should have reached today and shows how far its latest start is behind you. It does not claim the work is complete; adjust the deadline or durations to test a workable plan.
Not in this version. Steps form one consecutive sequence in the order shown. Projects with parallel work or dependency graphs need a project-management tool rather than this quick calculation.
No. It calculates dates for one ordered plan and keeps the current inputs for your next visit. There are no completion checkboxes, assignments, reminders or collaboration features.