Shadow supports Analysis: the role, duties, tasks, OPS, objectives, FTS and the Training Needs Report. Schema supports Design: the course, curriculum blueprint, KLPs, lessons and LSpecs. Sphere supports Delivery: resources, lesson plans and assessments. Sift holds your source documents and answers questions from them. Scrutineer (Evaluation) and Streamline (catalogue oversight) are in development. The DSAT page shows every step and links to its guide.

No. Everything the applications generate is a draft. Objectives, KLPs, amplifications, resources and questions should be reviewed by your course designer and subject matter experts before use. Sign-offs such as the OPS, FTS, TrAD, design and assessments follow your organisation's approvals process.

The golden thread is the traceable link from the operational requirement to an OPS task, then to a Training Objective (TO), Enabling Objective (EO) and Key Learning Point (KLP). Shadow derives TOs and EOs from the tasks, Schema builds KLPs and lessons beneath each EO, and Sphere builds resources and assessments from those. Each item keeps its reference, so you can trace any lesson back to the task it trains.

No. The Operational Performance Statement (OPS) is the current name for the Role Performance Statement (RPS or Role PS). It is the same document, so read older references to RPS as OPS.

Objectives follow the task they come from. Task 1.1 gives TO 1.1, and its Enabling Objectives are EO 1.1a, EO 1.1b and so on. KLPs add a further number in Schema, for example 1.1.1a.1.

TCat 1 to 4 are formal training and go in the Training Performance Statement (TPS). TCat 5 is workplace training and goes in the Workplace Training Statement (WTS). TCat 6 means no training is provided, so the gap is recorded in the Residual Training Gap Statement (RTGS). TCat 1 is the highest level of training.

When the role is shared with Schema. The DSAT process does this after the Training Needs Report is complete and the TrAD is signed off, so course design starts from the approved analysis. See the Sharing a Role with Schema guide.

Enabling Objectives can be cognitive, practical or attitudinal, so the right verb depends on the knowledge, skill or attitude the task needs. Restricting EOs to practical verbs can push real assessed requirements down into KLPs and weaken the golden thread. Check instead that each EO states an assessable performance, conditions and standard at the right training category.

KLPs are generated for EOs that have none yet, and for a TO only when it has no EOs beneath it. The ACTIONS menu shows how many objectives are eligible. Amplifications and trainer notes stay unavailable until an objective has KLPs.

Yes. Open ACTIONS, then select Key learning points under GENERATE. Schema ticks every eligible EO and shows a bar with CLEAR SELECTION, CANCEL and GENERATE FOR. Untick or clear the ones you don't want, then generate. Once a run starts it can't be stopped, so work in batches you can review in one sitting.

Items carried over from Shadow show a grey Shadow chip with a padlock. They belong to the role's analysis, so change them at source in Shadow. Items raised in Schema belong to the course and can be edited there.

No. EXPORT RAID builds an Excel file in your browser from the course register and changes nothing in Schema. The file downloads with a name like 'date - CourseName-TPS-raidSchemaExport.xlsx'. Keep Schema as the master copy and export again whenever you need an up-to-date version.

Use the source documents chip on the Content page. It opens a picker where you can browse your Sift documents or choose a whole collection. Only the documents you tick are used. Selecting CANCEL closes the picker without changing anything.

For each objective it records how closely training needs to match the real task, scored 0 to 5 for physical, functional, environmental and tactical fidelity. The scores inform the training conditions and the choice of methods and media (DTSM 2 section 5.13). You can score one objective at a time, or tick several rows to give them the same scores.

Import the signed-off course from Schema. The TOs, EOs, KLPs and lessons come across with their references, so resources and assessments build on the approved design instead of being re-entered. See the Import Course from Schema guide.

Yes. Sphere downloads lesson plans, Learning Specifications and assessments for trainers to use. Download them after the resources have been through SME review, so trainers get the final versions.

Use Check Coverage before you sign off. It shows which objectives your assessment questions cover, so you can fill any gaps. Assessments are then signed off before they are downloaded.

Sift stores your source documents, such as doctrine, policy and role documents, and answers questions from them. Organise documents into collections so each project uses the right sources. Shadow and Schema draw on the documents you select from Sift.

Check that the document has been uploaded and that it is in the collection you are searching. If the document is a scan, the text may not have been read clearly. If you are sure the text is there, report it through Contact with the document name and the question you asked.

Invite them to your team. The Invite a new user guide covers this, and it is step 1.4 of the Analysis process on the DSAT page. Invite SMEs early, because SME reviews are where plans most often slip.

Use Contact and include the application, the page or task you were doing, what you expected, what happened instead and a screenshot if you can. Leave out personal or sensitive data. A clear example of the difference between what you expected and what you saw is the fastest way to a fix.

The Training page groups the guides by application and topic. Each guide uses current screenshots and steps through the task, with Top tips linking the action to DSAT, JSP 822 and the DTSMs. The DSAT page links each process step to its guide.

Yes. The Analysis, Design and Delivery phases on the DSAT page each have a timeline planner. Set your start and target dates, adjust durations and owners, and update progress. Plans save in your browser only, so use Save plan file to share one with your team.