# Update content and decide on replay Adding learners, changing deadlines and updating content are different operations. Identify the change before accidentally requiring a replay just to add people. The journey is active. Document why it is changing and whether previous qualification still meets the requirement. This is a training-owner decision, not an automatic system judgment. A typo correction may retain qualification; a changed handling policy may justify reassessment. These are examples of decisions, not automatic classifications. ## Choose an action for your objective | Your objective | Choose / do this | Important effect | | --- | --- | --- | | Add the next cohort | Update identities/audience | Newly eligible people get their requirement; existing learners do not replay just because of the addition. | | Change 30 days to 14 | Journey settings → Completion days | Existing requirements retain their deadline; later eligible learners use 14 days. | | Revise content but accept prior qualification | Publish and retain qualification | Retained qualification is not a new-version score. | | Require reassessment | Publish and require replay | The current scope requires all stages in the version again; history remains. | ## For audience or deadline changes, edit settings To add learners, adjust audience tags in Journey settings or ask an administrator to give new members the qualifying identity. Audience changes take effect on save. A changed completion window applies to later eligibility, not existing obligations. Adding learners does not require existing learners to replay. When an identity condition is removed, learners who no longer qualify and have not started have their assignment withdrawn; learners who have started retain their requirement. Narrowing the audience therefore does not stop everyone's existing training. **What you should see**The audience/deadline changes without an unintended replay publication. When the result is different This field does not retroactively change an existing deadline. Confirm the appropriate handling with your administrator. ## Edit content changes before reviewing a new version Edit stages, ordering, replacements or passing rules in the existing journey and save. After a Doc2Sim update, select the intended content/version in the journey instead of assuming the binding updates automatically. Then open Publish new version. Saving edits and publishing a learner-facing version are different. Routine corrections do not require another journey. **What you should see**The preview identifies changes and provides the full stage scope and affected learners. When the result is different If expected changes are absent, verify saved edits and content versions before reopening the preview. ## Explicitly retain qualification or require the version again Retain qualification when previous evidence remains acceptable. Otherwise require replay and inspect the preview carefully: the current replay scope is ALL stages in that version, not only the edited stage. Review affected learners before publishing. Replay starts the new requirement from zero while preserving history; an existing learner's new deadline runs from publication. Without replay, applicable qualification and the existing requirement's deadline are retained, so publication does not automatically extend the deadline. Retained qualification does not create new-version scores for someone who has not played it. **What you should see**Check the version, qualified count and replay requirement in Behavior analytics. One completion rate does not prove everyone played the new version. When the result is different Recheck after publication failure or a changed preview. An attempt started before the update remains evidence for the old version, not the new replay requirement. You can identify the published content version, affected learners and replay decision, without treating retained history as new-version scores.