ms-participant-profile

To keep a participant profile in sync across programs, you maintain a portable profile file that enforces frontmatter requirements and tracks learner goals, identity, and progress. This unified profile travels with the learner across modules to ensure a coherent trajectory.

You preserve participant privacy in cross-program synthesis reports by applying privacy rules that replace third-party names with generic roles. This ensures external reports remain compliant while retaining the participant's unified learning trajectory.

You create an initial participant intake profile by initiating the intake process, selecting a storage location for the profile file, and answering the 10 measurement prompts. This starts the cross-program tracking journey and establishes the baseline profile.

The cross-program profile supports mid-course diagnostics and quick refreshes by utilizing versioned templates. It handles Initial Intake, Quick Refresh, Mid-Course Diagnostic, and Full Synthesis workflows to track participant evolution accurately.

The best way to maintain a unified learning trajectory across programs like 504 and 514-MIPT is using a single, portable profile file. This profile enforces frontmatter requirements and integrates with session-link and diagnostic workflows for continuity.

Your participant profile requires specific frontmatter for cross-program tracking to enforce continuity and accountability across programs. The frontmatter requirements ensure the profile integrates correctly with session-link and diagnostic workflows while maintaining privacy rules.