Deadline Backplanner

Build a calendar-day project backplan with editable task rows and finish-to-start dependencies.

On-device No sign-up Free to use

Calculate result controls

Showing an example. Edit to see your own.

?

Starts thirty calendar days from today. Work is complete at the start of this date. Calendar years 0001 to 9999; every calendar day is available.

?

One row per task: ID, name, whole calendar days, predecessor IDs. Separate columns with tabs and multiple predecessor IDs with commas. No header; up to 50 tasks and 3,650 days per task. Dependencies are finish-to-start.

Processed in your browser. Your inputs stay on this device.

Result

Showing an example.

A six-day chain must start on November 1 to finish before November 7, 2026.

Start by November 1, 2026 to finish before November 7, 2026: 6 calendar days.

https://usefreetools.net/deadline-backplanner · 20 November 2026

Was this helpful?

How to use Deadline Backplanner

  1. Enter the exclusive project finish date: all planned work must finish before this date begins.
  2. Use the task rows to enter a unique ID, task name and positive whole-day duration. List prerequisite task IDs, separated by commas when a task has more than one.
  3. If pasting task text, use tab-separated ID, name, days and optional predecessor IDs, with one task per line and no header.
  4. Calculate the backplan and review the latest starts, exclusive finishes, critical chain and slack. Check staffing, weekends and holidays separately.
  5. Download the schedule CSV if needed; its dates use ISO format.

Example: Deadline Backplanner

A six-day chain must start on November 1 to finish before November 7, 2026.

You add
Exclusive project finish date: 2026-11-07; Tasks and dependencies: A Plan 2 B Build 3 A C Review 1 B
You get
Start by November 1, 2026 to finish before November 7, 2026: 6 calendar days.

Options

Task durations
Durations are whole calendar days. They do not account for weekends, holidays, work hours or staffing.
Dependencies
Use the task IDs in the prerequisite column. Missing IDs and cycles are refused; parallel branches can overlap because resources are not scheduled.

Supported inputs and limits

  • From 1 to 50 tasks and 20,000 input characters.
  • Each tab-separated row contains an ID, name, positive whole calendar-day duration and prerequisite IDs.
  • IDs start with a letter and use up to 24 letters, digits, underscores or hyphens; names use 1 to 100 characters and durations 1 to 3,650 days.
  • Gregorian years 0001 through 9999.
  • Unknown or duplicate IDs, dependency cycles and date overflow are refused.
More details

Finish dates are exclusive and every day is available.

Weekends, holidays, working hours, reminders, staffing and resource conflicts are not modeled.

Business Day Calculator gives a separate weekday count and does not change this dependency schedule.

CSV keeps ISO dates.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

Latest dates need a resource review

The plan works backward from the entered deadline under its dependency rules. A valid dependency schedule can still assign two tasks to the same person on the same day. Check capacity and nonworking dates separately before treating the dates as commitments.

Questions about Deadline Backplanner

Is the finish date included as a working day?

No. It is the exclusive boundary. A one-day task finishing December 31 runs from December 30 to that boundary.

Can parallel tasks use the same person?

The mathematical graph allows parallel work. It does not check staffing or resource conflicts.

What is slack here?

It is the difference between the earliest and latest timing in this calendar-day dependency model, not spare staff or budget.

Page updated · Project managed by Tony Hines · Report a problem with Deadline Backplanner