LMS reflections can look like learning when they are really just module completion. Here is how to read a reflection for real learning depth — surface, applied, or transfer — and grade it in one pass with Sopact Sense.
In short: An LMS reflection can look like learning when it is really just module completion. Point the Sopact Sense Assistant at the reflection, tag what was demonstrated to your competency set, rate the depth as surface, applied, or transfer, and flag any misconception. You get a graded read that tells you whether real learning happened — and the one edit that turns a weak reflection into evidence.
Tell the Assistant which dataset it is working over and load your Decision Brief first, so every grade ties back to the decision, audience, outcomes, indicators, and evidence standard you already set.
You are the Sopact Sense Assistant working over the DEMO-09 · Mentorship & LMS dataset (clean data + persistent contact IDs). Load my Decision Brief (decision, audience, outcomes, indicators, evidence standard) first, then wait for my task.
From the LMS reflection, identify demonstrated learning, tag to [COMPETENCY_SET], rate depth (surface/applied/transfer), flag misconceptions. Grade green/amber/red.
The prompt carries five elements. Dataset: the reflection the Assistant reads. Competencies: the competency set you tag demonstrated learning to. Depth: rate each as surface, applied, or transfer. Flag misconceptions: surface any wrong belief stated as fact. Grade: a green / amber / red call on every element.
Run on the Mentorship & LMS dataset (DEMO-09) already loaded in Sopact Sense.
GRADE: green | Transfer | learning · amber | Surface | module · red | Misconception | uncorrected
The Assistant reads the reflection and grades it. Green is transfer-depth learning — the learner applied the idea to a new situation. Amber is a surface module: the reflection repeats content without applying it. Red is a misconception stated as fact, which has to be corrected before it counts as evidence.
Take the lowest-graded element and fix it with something the program could realistically measure.
Take the surface-module element above and fix it: add one prompt asking the learner to apply the idea to their own situation. Show the before → after grade and the single edit that moves it to green.
Create a 'missing & incomplete' report from this analysis in Sopact branding. List every element graded amber or red, what is missing, and the one input that fixes each. Lead with the decision this report informs.
Create a shareable link for this report & open it in a new tab.
Tag for transfer, not completion. A finished module is an input, not evidence. Make the depth rating — surface, applied, transfer — the thing you report, and completion becomes context rather than the headline.
Always flag misconceptions separately. A confident, well-written reflection can still be wrong. Keep the misconception flag as its own red call so a correction is scheduled, not buried.
Give it your real competency set. Generic tags produce generic grades. Paste the competencies your program actually teaches so the Assistant maps demonstrated learning to language your team already uses.
Run it the same way every cohort. Consistency is what makes the grades comparable over time.
Re-run this prompt unchanged each cohort so a surface-to-transfer shift shows up as a trend, not a one-off read.
Read each reflection for demonstrated learning, tag it to your competency set, and rate the depth as surface, applied, or transfer rather than counting completion. Flag any misconception as its own item. The Sopact Sense Assistant does this in one pass and grades every element green, amber, or red so you can see which reflections are real evidence.
Surface depth means the learner repeats the module content; transfer depth means they apply the idea to a new, often personal situation. Transfer is the strongest evidence of learning, which is why it grades green while a surface reflection grades amber.
Flag it as red and route it to a mentor follow-up. The fix is to capture the correction at the next check-in so the misconception is resolved rather than recorded as learning.
Open Sopact Sense, paste your program description, and put it to work.
Try in Sopact
