Gloss Tools Deadline back-planner 繁體中文

Work backward from a deadline to a reviewable plan

Use the longest dependency path to set the project anchor, then see how much each task can move.

You provide the holidays. This tool does not model team capacity or resource constraints.

✎ Editing

Calendar and tasks

A date in 2000–2099. Non-workday deadlines move earlier, with an explanation in the result.

Weekly workdays (select at least one)

Dates are not converted between timezones. Both start and finish dates count.

At most 366 unique dates, one per line or separated by commas. Holidays outside your workweek do not remove another day.

Tasks and predecessors

Use 1–260 workdays per task. Successors start on the next workday after predecessors finish. At most 500 dependencies per project.

Enter a deadline to enable calculation.

Plan results

No plan calculated yet

Enter a deadline and tasks to see a schedule here.

Slack is the number of workdays a task can move. ◆ Critical means zero slack. Every root task has the same early start at the project anchor. Parallel work is allowed; this tool does not allocate staff or guarantee on-time delivery.

How the plan works

Why is there no start-date field?

The tool finds the longest dependency path first, then counts back from the adjusted deadline to set the earliest start for every root task.

What happens when the deadline falls on a weekend or holiday?

It moves to the previous workday in your calendar. The result shows both the entered and adjusted dates.

Does the critical path guarantee a delay?

No. It marks tasks with zero slack under this model. It does not estimate staffing, risk, interruptions, or other resource limits.

Your data is processed in this page's memory, with no uploads or automatic saving. Editing, cancelling, clearing, or leaving removes results and download links. Downloaded files remain on your device; browser process memory cannot be guaranteed erased.