Task Deadline Change Impact Planner

How to use Task Deadline Change Impact Planner

A duration change can delay downstream tasks or be absorbed by release times and alternate predecessors. Compare two explicit assumptions against each task’s own deadline before changing the real plan.

1. Declare baseline/scenario durations, release offsets, individual deadlines and finish-to-start dependencies.
2. Compare earliest finish changes, own-deadline slack and newly late tasks under unlimited parallel resources.
3. Check real worker/calendar constraints and approve any schedule change outside this planning artifact.

Good to know

• Minute zero is a user-defined origin; all values are exact minute offsets. This is change-impact analysis, distinct from CPM latest times/total float or a job-shop resource schedule.
• Positive own-deadline slack does not prove a feasible real calendar. Changed ancestors show potential provenance, not a causal allocation of delay minutes.
• Each input field is limited to 8,000 UTF-16 characters and each exact-header CSV to 100 data rows. Quoted commas/newlines and doubled quotes are supported. Unsupported controls and unpaired surrogates are refused. Decimal magnitudes are at most 999,999,999 with a smallest nonzero magnitude of 0.000000001; exponents are refused and whole counts are checked exactly. Rational results show at most 18 fractional digits and an ellipsis when more remain.
• Editable Markdown and long-form CSV both retain all summary metrics, context, detailed findings, entered source rows and scope limitations. CSV columns are Record type,Section,Source row,Field,Value; spreadsheet-looking text is apostrophe-prefixed. These are review artifacts, not proof of source truth or a completed real-world task.
• Runs deterministically in this browser. No AI, API, vendor connection, upload, outreach, calendar change, payment, storage or background monitoring. Use authorized pseudonymous records; inspect exports before sharing.