Training & programs

Every participant, from enrollment to proof.

Track skills and confidence from baseline to follow-up, see who needs support before graduation, and answer funders with evidence that continues after the program ends.

Book a custom demoSee a participant journey
Illustrative workflow · synthetic sample data
Baseline
Midpoint
Exit
Follow-up
Journey record · AR-118Current
AR
Participant AR-118Digital skills · Cohort 6
Exit assessed
Skill assessment
41%78%+37
Confidence
2.14.2+2.1
Midpoint flag, resolved: practice confidence lagged at week 5. Added paired practice sessions before exit.

“I ran the whole client setup on my own this week. Two months ago I would not have tried.”Exit response · AR-118

Open sources
Explore solutions
Case ManagementApplications & GrantsGrantee & PortfolioTraining & Programs
The operating gap

Your funders ask what changed. Your data ends at graduation.

The baseline survey lives in one spreadsheet. The exit survey lives in another. The follow-up never quite happens. When the funder report is due, someone rebuilds the whole story by hand — and the participants who needed support mid-program were only visible in hindsight.

The journey was happening. The record wasn't.
W1
Baseline collectedIntake form, skills assessment, confidence score — filed in the intake spreadsheet.
W5
Struggles startA facilitator notices, mentions it in a meeting. It is not attached to the participant's record.
W10
Exit surveyNew form, new file. Matching rows to baseline means manual name-matching.
+90
Follow-up… lostDid the skills stick? Did they get the job? The answer exists — nobody can produce it.
One connected journey record

Follow the same participant through every stage.

Each stage adds evidence to the same record. Nothing is re-matched, re-keyed, or rebuilt.

1 · Baseline
2 · Midpoint
3 · Exit
4 · Follow-up

Start with a real starting point.

Enrollment captures the skills assessment, confidence score, and goals in one step — one record per participant from day one, ready to compare against later without any file matching.

Nontechnical staff run the whole intake
AR-118 · Baseline · Week 1Recorded
Skill assessment41%Cohort median 44%
Confidence2.1 / 5Self-reported
“I want to stop guessing my way through the software my job depends on.”Intake response · AR-118

See who needs support while it still matters.

The midpoint check compares against baseline automatically. When practice confidence lags behind knowledge, the record is flagged — during the program, not in the post-mortem.

The flag is a prompt for the team, not an automated action
AR-118 · Midpoint · Week 5Flagged
Skill assessment63%+22 vs baseline
Confidence2.8 / 5Lagging skills growth
Support flag: knowledge is growing faster than applied confidence. Pattern matches two other participants in cohort 6.
Facilitator adds paired practice sessions

Graduate with a delta, not a certificate.

Exit assessment lands in the same record, so the change from baseline is computed — not reconstructed. The midpoint intervention and its result stay part of the story.

Every delta traces to the participant's own responses
AR-118 · Exit · Week 10Assessed
Skill assessment78%+37 vs baseline
Confidence4.2 / 5+2.1 vs baseline
“I ran the whole client setup on my own this week. Two months ago I would not have tried.”Exit response · AR-118

Keep the evidence alive after graduation.

A short follow-up at 90 days attaches to the same record. Now the funder question — did it last? — has an answer that names its source instead of an anecdote.

This is the evidence most programs never capture
AR-118 · Follow-up · Day 90Responded
Using skills weeklyYesSelf-reported at day 90
EmploymentEmployedRole uses trained skills
“I got the coordinator role. The spreadsheet system we built in week 8 is what I showed in the interview.”Follow-up response · AR-118
From one journey to the cohort

See the whole cohort move.

Every participant journey rolls into one progression view. The team sees who is ahead, who is stalling, and where the pattern is — while there is still time to change the outcome.

Sopact flags the pattern. The training team decides who gets support and how.
Cohort 6 · Digital skills · Week 5 of 10Current
AR-112On track
AR-114Ahead
AR-118FlagSupport
AR-121On track
AR-127FlagSupport
AR-130On track
Confidence progression vs. cohort plan · 2 participants flagged for paired practice
Review flagged
The program behind the record

The record follows real people.

A journey record is only useful because the journey is real: a first assessment in week one, a hard practice session in week five, a job that sticks in month three.

Instructor guiding a training cohort taking a baseline skills survey at laptops01Week one
What Sopact captures here

The baseline lands clean, in the session.

Baseline capture · Cohort 6Collecting
Assessments22/25
Confidence2.1
Goals set21

Each response opens a participant record that lasts the whole journey.

What the team sees

The midpoint flag reaches the facilitator in time.

Support flag · Week 52 participants
Pattern: applied confidence lagging knowledge growth in AR-118 and AR-127. Both cite the same module.
“I understand it in class, then I blank at the machine.”AR-127
Paired practice added before week 7
Facilitator coaching a trainee one-on-one during a hands-on practice session02Week five
Recent training graduate working confidently in a modern workplace03Day ninety
What travels to the funder

The follow-up proves it lasted.

90-day follow-up · Cohort 6Source-linked
18 of 23 graduates report weekly use of trained skills. Employment outcomes trace to individual follow-up responses.
“The spreadsheet system we built in week 8 is what I showed in the interview.”AR-118
Included in the Q3 funder report

Illustrative human moments · not customer imagery

Questions the team can answer

Ask about any participant, any stage, any cohort.

Because every stage lives on the same record, the answer is a query — not a reconstruction project.

Mid-programWho needs support before graduation?##INLINE1##Open flagged records
Program designWhich module is confidence stalling on?##INLINE3##Compare stages
Cohort qualityIs this cohort's delta weaker than the last one?##INLINE5##Compare cohorts
OutcomesDid the skills persist after the program?##INLINE7##Trace follow-ups
Q3 program reportSource-linked

Cohort 6 outcomes, baseline to day 90.

CohortProgramFunder
Avg skill delta+34 pts
Skills in use at day 9018 / 23
Every figure expands to the participant records behind it23 journeys
Open the journeys
Funder reporting without the rebuild

The report is the journeys, rolled up.

When every participant record already holds its baseline, exit, and follow-up, the funder report stops being a quarterly reconstruction. Roll cohorts into program and funder views — and let any number be opened back to the people behind it.

Funders get an answer that names its evidence, not a summary that asks for trust.
Keep humans in control

Sopact keeps the record. Your team runs the program.

Sopact connects the stages, computes the deltas, flags the patterns, and prepares the report. Deciding who gets support, what changes next cohort, and what goes to the funder stays with the people who run the work.

1
Sopact connects and computesBaseline to follow-up, one record per participant.
2
Sopact flags the patternLagging confidence, stalled modules, missing follow-ups.
3
Your team decidesSupport plans, program changes, and what the funder sees.
Start with one cohort

Bring the cohort that starts next.

We will show how enrollment, midpoint, exit, and follow-up could run as one connected journey for your program — with the funder report built in from day one.

Book a custom demo
Illustrative workflow · synthetic sample data · your team keeps the final decision
Book a custom demo