DSAT · Phase 02 Design · Schema
Design timeline planner
Plan, schedule and track the Design phase as a project. Each row is an activity from the DSAT page, in the same order and with the same references and guides. Set your start date and target, adjust the durations and owners to suit your course, then update the status as the work progresses. The plan recalculates the dates, the critical path and your remaining time automatically.
44 activities · 10 steps
Top tip: start from the signed-off analysis. Design begins when the TrAD is signed off and the role is shared with Schema (Analysis steps 10.4 and 10.5). DTSM 3 para 2.1.1 says the TOs drafted in Element 1 are refined and developed in Design, not rewritten, so the golden thread from OPS task to TO and EO carries straight into your course. If you used the Analysis timeline, set the start date to its planned hand-off.
Top tip: work back from the Ready for Training Date. DTSM 2 paras 3.2.3 and 3.2.4 say the RFTD is agreed as a hard stop and stated in the TrAD produced at the end of Design. Set your hand-off target early enough to leave time for development and resourcing before the RFTD. Activities outlined in black are on the critical path, so any slip there moves your hand-off.
Top tip: LSpecs come last for a reason. DTSM 3 paras 7.2.1 and 7.2.2 say LSpecs bring together the outputs of the earlier design stages: the EOs and KLPs, the assessment, the methods and media, the time allocated and the resources. That is why Delivery Documentation (step 9) waits for Delivery Readiness (7) and Method and Media (8) in this plan.
Not startedIn progressCompleteBlocked or overdueApproval or sign-offCritical pathTodayPlanned hand-offHand-off target
Top tip: book SME time early. Design has five SME reviews (3.5, 4.3, 5.3, 9.3 and 10.3) and they are where design plans usually slip. Run them through the Schema SME Review guide so comments stay with the course, keeping the audit trail DTSM 2 para 2.3.7 asks for.
Top tip: the design review is a gate. Comparison (10.1) checks every objective from the analysis is covered, and Sign Off Design (10.5) follows your organisation's approvals process under JSP 822 3.32 Training Design Review. Set "Approval days" to your approving authority's real lead time. Development in Sphere shouldn't start until this gate is passed.
Top tip: durations are planning assumptions. Every activity starts at 0 working days. JSP 822 and the DTSMs don't set durations, so enter your own figures, and record schedule assumptions and risks on the course RAID register (DTSM 2 section 4.6, JSP 822 3.31), which you review at 2.5, 6.3 and 10.2.
Your plan is saved automatically in this browser only. Select Save plan to save your changes straight away. Use Load plan file to open a plan file shared by your team.