Make a dated handoff from a small dependency list
Dependency day plan turns whole-day task estimates and finish-to-start links into an earliest-date review. Add a requested start date, supply any known closure dates, and build a schedule that skips Saturdays, Sundays and those closures. Save the task dates and assumptions as a readable HTML handoff and a structured JSON review.
This is a limited planning model for a small prepared task list. It does not reserve people, send invitations, update a project system or promise that the work can be staffed. Independent tasks may receive the same dates. Check available people and other commitments before using the output as a plan.
Enter the task CSV
Use this exact header: id,title,days,after. Add one to sixty data records. Each ID starts with an ASCII letter and contains at most twenty letters, digits, underscores or hyphens. IDs are case sensitive and unique. Task titles can contain up to 160 single-line characters; quote CSV fields containing commas or quotation marks. Titles remain text, including leading zeros or strings that look like formulas.
Days means one through 260 whole working days of elapsed task duration under this model. It is not a person's hours of effort and does not change when more people are assigned. Zero-duration milestones, fractional days and automatic effort conversion are not supported. Use a dedicated scheduling system if those distinctions are required.
The after field contains predecessor IDs separated by a vertical bar, such as Draft|Artwork. Leave it empty for a task with no predecessor. A task waits for every predecessor. Dependencies can point to later rows, so the source file need not already be sorted. Unknown IDs, repeated IDs, self-dependencies and cycles are refused rather than silently ignored.
Calendar rules are explicit
Dates must be valid YYYY-MM-DD dates from 2000 through 2099. The working week is Monday through Friday. List up to fifty closure dates, one per line, without blank lines or duplicates. These are dates supplied by you, not a public-holiday service. The same calendar applies to every task.
If the requested start falls on a weekend or a closure, the first permitted working day moves forward. A one-day task starts and finishes on the same working date. A two-day task uses that date and the next permitted working date. Its displayed finish is inclusive: the last working day occupied by the task.
A successor starts on a working day strictly after all predecessor finish dates. This whole-day interpretation is deliberately explicit; it does not model a handoff partway through the same day. There are no start-to-start, finish-to-finish or start-to-finish links, lags, deadlines, constraints or resource-specific calendars.
A fictional example
Prepare source material starts on Friday October30,2026 and needs two working days. With Monday November2 entered as a closure, its second working day is Tuesday November3. Review copy then occupies Wednesday November4. Prepare artwork also starts Wednesday and finishes Thursday November5. Final review waits for both and starts Friday November6. Arrange delivery has no predecessor and can be dated Friday October30 under the dependency-only model.
The overlap between copy review and artwork is intentional: this tool does not know whether the same person must perform both. The example closure is only an input illustrating the rule, not a statement that November2 is an official holiday. Changing or removing it changes the resulting dates.
Review before committing
The result table retains the original task order and displays IDs, durations, predecessors and dates. An independent task appears where it was entered even if its date is earlier than nearby rows. The JSON also includes the dependency-processing order and source record positions, so the derived dates can be traced without reordering your source list.
All scheduled dates must remain within approximately five calendar years of the requested start and within year2099. Excessive chains are refused with a message. This protects a small interactive review from becoming a multi-decade projection. Duration estimates and closure completeness remain your responsibility.
The HTML handoff includes the requested start, adjusted first day, every task, supplied closures and model limitations. It contains no script or remote assets. The JSON stores dates as date-only strings and durations as whole numbers. A schema 1 JSON review saved by this app can restore its source title, start date, closure dates and task list using Resume above. Saved result dates, calendar descriptions and other derived metadata are ignored. Build again to recompute under the current documented rules. Restore accepts UTF-8 JSON up to 256 KiB and validates the complete source before replacing input fields. Invalid files leave your input fields intact and clear the previous result. Editing, Clear or loading an example cancels a pending restore. Keep a downloaded copy before closing the page; nothing is automatically saved. This is not a calendar subscription, Microsoft Project import or guaranteed interchange format for other tools.
Local and temporary
Inputs and results stay in temporary page memory. This app adds no account, browser storage, analytics or network submission for the task data. Editing an input clears the previous result; Clear and reload remove the in-page plan. Downloaded copies remain on your device and may contain project information, so inspect them before sharing.
No timezone conversion is performed. These are calendar-day labels, not meeting timestamps. Full project-management tools support broader scheduling, resources and progress tracking. Use those when the scope of the work needs them.