For a training manager, instructional designer, or HR director, the value of a module goes beyond the final score. The VTS Editor Recap Block<\/strong> provides clear evidence of what occurred during the activity and facilitates debriefing. It generates, on the learner side, a text log that records key moments (chapters, decisions, assessments, results) on Windows and Mac. The .txt file is saved locally in VTS\/Recaps and remains after the session ends. This log complements your score\/progression data, LMS\/SCORM tracking, and VTS Perform<\/a> analytics.<\/p>\n Beyond being a simple \u201ctrace,\u201d it\u2019s a strategic pedagogical and operational tool. It streamlines debriefings (one-on-one or group), supports continuous improvement (which items cause difficulties? which instructions are misunderstood?), and provides useful evidence for certification, compliance, or quality audits. For modules deployed on Web\/Mobile, plan for alternatives (Web Request, Open Web Page, or centralized tracking via VTS Perform\/SCORM), as the block isn’t available on iOS, Android, or Web.<\/p>\n The Recap block adds text to a local file with each pass. Writing is sequential: you compose a clear line (free text + variables) that is appended. By default, the file name includes the date and time the session was launched, followed by \u201c_Recap.\u201d You can add a custom suffix to distinguish uses (e.g. 2025-03-12_09-41_Recap_Onboarding_Sales.txt). The \u201cSave Immediately\u201d option secures saving after each pass (recommended for long or critical scenarios). If disabled, the file is saved at the end of the experience.<\/p>\n The file is stored in VTS\/Recaps on the learner’s machine and remains available after the session ends. It may be shared, archived, or attached to a training folder depending on your procedures. It\u2019s a learner-side trace that works alongside your centralized data (LMS\/SCORM and VTS Perform features<\/a>).<\/p>\n For pedagogical management, the log fosters metacognition: learners visualize their progress, decisions, and corrections. In coaching (in-person or remote), an instructor relies on the log to replay sequences, question intentions, objectify mistakes, and highlight successes. In HR and compliance contexts, it becomes part of a \u201cproof portfolio\u201d: stages completed, tasks performed, thresholds reached. In high-stakes environments (safety, GDPR, healthcare, banking), it facilitates fast audits without having to replay the entire simulation.<\/p>\n On the quality and continuous improvement side, the log reveals areas of misunderstanding (ambiguous instruction, too subtle trap, excessive cognitive load) and roadblocks (frequently failed quiz, counterintuitive decision). You can then improve the module with full awareness: rephrasing, contextual help, targeted gamification, just-in-time additional resources.<\/p>\n To explore the impact of debriefing on learning, see Fanning & Gaba (Simulation in Healthcare, 2007) on the importance of structured debriefing (PubMed link)<\/a>, as well as summary works on metacognition and effective learning techniques (Dunlosky et al., 2013)<\/a>. For the value of tracking logs in learning analytics, the SoLAR definition is a strong starting point (SoLAR link)<\/a>.<\/p>\n The Recap Block is compatible with Windows\/Mac only (not available on iOS\/Android\/Web). Regarding GDPR, it\u2019s a local file controlled by the learner. Avoid sensitive personal information; prefer technical identifiers (learner ID, session ID) and explain the purpose if you expect the file to be shared (information\/consent). Monitor file size: overly long lines reduce readability and unnecessarily bloat the document. Prefer short, standardized, dated entries with separators for major milestones.<\/p>\n In practice, if \u201cSave Immediately\u201d is turned off and an abnormal session closure occurs, the last unsaved lines may be lost. For scenarios over 15\u201320 minutes or high-stakes, enable Save Immediately.<\/p>\n Aim for telegraphic yet informative writing. A simple structure works well: [Time] \u2014 [Chapter\/Activity] \u2014 [Action\/Event] \u2014 [Result\/Score\/Skill] \u2014 [Outcome\/Consequence]. Add separators for major milestones (e.g. \u2014\u2014 Chapter 2 \u2014\u2014). Standardize your vocabulary (\u201cCHAPTER START,\u201d \u201cQUIZ,\u201d \u201cCORRECT ANSWER,\u201d \u201cCORRECTION,\u201d \u201cCHAPTER END\u201d) and use consistent identifiers: C1_Intro, C2_Situation, Q1, Q2. The goal is twofold: enable a trainer to understand everything at a glance, and help the learner recall the logic followed.<\/p>\n Map out your graph. Identify chapter entry and exit points (start\/end), assessments (Quiz, True\/False, Drag & Drop, Matching, Text\/Number Input, Keypad, Slider), key decisions (Phrase Choices, Clickable Zones, Decor Interaction), and evaluation milestones (Score, Score Check, Progression, Badge). Place a Recap block at meaningful points for debriefing and proof of completion: chapter start, instruction (if useful), result and correction, threshold reached, badge awarded, chapter end. Write after the action is validated, not before, so the log reflects the real state.<\/p>\n Craft the added text carefully. Write short lines, insert variables (score, skill, time, decision), and keep the timestamp. Example in a sales simulation: [10:42:05] \u2014 C2_RolePlay \u2014 Choice: \u201cOffer the demo\u201d \u2014 Score: +10 \u2014 Skill: Consultative Selling \u2014 Outcome: Meeting Confirmed. Enable Save Immediately if the session is long, highly branched, or if the log is needed for audits. For the file name, add a meaningful suffix (_Onboarding_IT, _Compliance_SFT, _Manager_Coaching). If you have a session ID or campaign code, add it to make matching with your reporting easier.<\/p>\n Standardize your formats. A duo of \u201cchapter template\u201d (start\/end) and \u201cactivity template\u201d (instruction, response, result, skill, score) saves time and ensures consistency. For variables, anything that customizes the line is useful: globalScore, scoreSkillX, progression, elapsedTime, scenarioID, chapterName, activityID, learnerResponse, outcome, thresholdReached. Use VTS Editor<\/a>\u2019s auto-complete to avoid typos and stick to consistent naming throughout the project.<\/p>\n Pro tip: Create a Function Group (e.g. LogRecap) that receives a text input and handles the writing. Call it everywhere using the Function Call. This centralizes your writing logic, prevents omissions, and lets you later enrich all lines at once (adding a prefix, ID, counter\u2026).<\/p>\n Preview a complete path including at least one decision and one assessment. Then open VTS\/Recaps to verify file presence, structure, variable accuracy (scores, outcomes), separator clarity, and time consistency. Quick checklist:<\/p>\n After a Score block, write the update: [HH:MM:SS] \u2014 Score Update \u2014 +10 \u2014 Skill: Communication. For Score Check, log threshold crossings: [HH:MM:SS] \u2014 Threshold Reached \u2014 Safety: 75\/70. For Progression, offer a macro view: [HH:MM:SS] \u2014 Progress: 66% \u2014 Status: Partial Complete \u2014 Success: Unknown. When a badge is awarded, mark the milestone: [HH:MM:SS] \u2014 Badge Earned \u2014 \u201cTrusted Advisor.\u201d<\/p>\n Assessment and exploration blocks work well with Recap. Examples:<\/p>\n For insights on gamification\u2019s effect on learning, see this systematic review in Frontiers in Psychology (Sailer & Homner, 2020)<\/a>.<\/p>\n The Function + Function Call combo is ideal for standardizing writing. Create a LogRecap function to receive a text input and call a single Recap block. You enforce a standard format, automatically add time, session ID, or even a project code. Use the Sequence block to orchestrate a repeatable routine \u201centry log \u2192 activity \u2192 exit log\u201d. A Switch, driven by a result variable (1 = Success, 2 = Partial, 3 = Failure), lets you adjust labels finely without multiplying branches. Global variables (chapterID, activityID, skillName, threshold) ensure consistent personalization at scale.<\/p>\n In compliance\/safety, log critical decisions and regulatory references: [HH:MM:SS] \u2014 Decision: Stop the machine \u2014 Ref: Proc_SECU_4.2 \u2014 Outcome: Incident avoided. For onboarding, create a thematic thread (culture, tools, safety, GDPR) to build a reusable integration file with the mentoring manager. For soft skills, log communication choices and perceived effects: [HH:MM:SS] \u2014 Decision: Active Reformulation \u2014 Reaction: Calming \u2014 Outcome: Agreement Reached. The debrief becomes more nuanced; the discussion relies on facts, not impressions.<\/p>\n Two best practices: document the purpose of tracking (inform\/consent) and avoid duplicating identifying information. Rely on stable technical IDs and handle mapping via the LMS\u2014more robust and GDPR-friendly.<\/p>\n The VTS Editor Recap Block<\/strong> transforms your modules into traceable, memorable, and auditable experiences. It boosts engagement (visible milestones), recall (re-reading), traceability (local proof), and quality (raw material for continuous improvement). For training and HR managers, it provides a simple way to support debriefing and reassure stakeholders. For instructional designers, it accelerates clarity and consistency.<\/p>\n Take action in three steps:<\/p>\n If your target includes Web\/Mobile, plan an alternative reporting strategy (Web Request, Open Web Page, VTS Perform\/SCORM) to maintain traceability benefits.<\/p>\n Eager to go further? Explore VTS Editor<\/a>, its certification training<\/a> to boost your skills quickly, our client case studies<\/a> for inspiration, and compare VTS Editor subscriptions<\/a> based on your needs.<\/p>\n","protected":false},"excerpt":{"rendered":" Optimize Your E-learning Modules with the VTS Editor Recap Block For a training manager, instructional designer, or HR director, the value of a module goes beyond the final score. The VTS Editor Recap Block provides clear evidence of what occurred during the activity and facilitates debriefing. It generates, on the learner side, a text log that records key moments (chapters,…<\/p>\n","protected":false},"author":12,"featured_media":6663,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1035],"tags":[963],"class_list":["post-6662","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vts-editor-en","tag-vts-editor-blocks"],"_elementor_source_image_hash":null,"_wp_attachment_image_alt":null,"_thumbnail_id":"6663","_yoast_wpseo_twitter-description":null,"_yoast_wpseo_twitter-title":null,"_yoast_wpseo_twitter-image":null,"_product_image_gallery":null,"_yoast_wpseo_focuskw":"VTS Editor Recap block","_yoast_wpseo_title":"Optimize Your E-Learning with the Recap Block in VTS Editor","_yoast_wpseo_metadesc":"Boost your e-learning modules with the VTS Editor Recap block: track, trace, and improve learner performance in just a few clicks.","yoast_head":"\nHow the VTS Editor Recap Block Works<\/h2>\n
Learner Writing: Simple and Robust Local File<\/h3>\n
Educational and Operational Benefits<\/h3>\n
Limitations, GDPR Precautions, and Best Practices<\/h3>\n
Make the Log Readable and Usable<\/h3>\n
Set Up and Configure the Recap Function in VTS Editor<\/h2>\n
Plan What You Want to Log<\/h3>\n
Efficient Block Configuration<\/h3>\n
Reusable Templates and Useful Variables<\/h3>\n
Test and Validate on Windows\/Mac<\/h3>\n
\n
Go Further: Combine the VTS Editor Recap Block with Score and Progression<\/h2>\n
Log Performance and Recognition<\/h3>\n
Track Learning Interactions<\/h3>\n
\n
Automate and Streamline with Technical Blocks<\/h3>\n
Advanced Use Cases for HR, Training, and Compliance<\/h3>\n
Deploy on Web\/Mobile: Alternatives to the VTS Editor Recap Block<\/h2>\n
Three Simple Options to Implement<\/h3>\n
\n
Make the VTS Editor Recap Block Your Pedagogical Logbook<\/h2>\n
\n