DSUR timeline back-planner
Enter a data lock point (DLP). The planner fills in the calendar date of every milestone in the 60-day model from Writing the DSUR (Chapter 3, 3.2; Appendix C.1). Day 0 is the data lock point; only the day-60 limit comes from ICH E2F (§2.2). Adjust the other days to the size of your program, but keep scope, templates and output shells settled before the data lock point.
Inputs
Day 0. The submission deadline is 60 calendar days later.
Dates listed here are flagged like weekends.
Back-planned timeline
| Include | Milestone | Day | Date | Weekend or holiday | Owner | What must be ready |
|---|
The regional requirements row is an addition to the Chapter 3 model (Appendix C.1); it moves the discovery of regional needs to where they cost least. Untick a row to leave it out of the printout and the CSV.
Checks
Planning notes (Appendix C.2)
- Work back from the earliest deadline. When the 60th day falls on a weekend or public holiday, submit before it, not after. Where a region's deadline is earlier than day 60, rebuild the calendar backward from that deadline (set the day numbers accordingly).
- Protect the key messages review. It is the milestone most often dropped under pressure, and dropping it costs the most (Chapter 17).
- Set the late-breaking cut-off at the start of the consolidated review, and name its owner (Chapter 8).
- Keep ten days between sign-off and the deadline for publishing, regional packaging and problems.