Connect assessments, participant feedback and later skill use across cohorts. See who needs support and give program leaders, sponsors and funders evidence they can review.
“I ran the whole client setup on my own this week. Two months ago I would not have tried.”Exit response · AR-118
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.
Each stage adds evidence to the participant record. Consistent identifiers and configured relationships keep the journey connected; teams review missing or mismatched records.
Begin with an application and supporting evidence. Staff review missing information and suitability before an offer; participant acceptance precedes enrollment and the baseline assessment. Keep these decisions distinct on the continuing participant record.
Compare the midpoint with the baseline for participants who have both assessments. When confidence and knowledge differ, review the participant’s feedback before choosing support. Missing evidence stays visible.
Connect the exit assessment to the same participant and comparable baseline questions. Report observed change alongside coaching notes and support history; a before-and-after difference alone does not establish what caused it.
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.
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.
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.
01Week oneEach response opens a participant record that lasts the whole journey.
02Week five
03Day ninetyIllustrative human moments · not customer imagery
Use the selected participant records, collection stages and reporting definitions together. Check source coverage and exceptions before relying on the answer.
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.
Synthetic example: Alex completed eight training modules and has a credential assessment scheduled. Employment follow-up has not yet been collected. Completion, certification and employment are separate results.
“You completed 8 of 8 modules. Your credential assessment is scheduled; a result is not yet recorded. Suggested next step: review the assessment requirements with your coach.” Keep the summary brief and distinguish suggestions from commitments.
Record the module evidence, assessment date and source, missing employment follow-up and any agreed coaching actions. Do not count a scheduled assessment as a credential or missing employment data as unemployment.
Start the pilot with an application, review, offer and acceptance before enrollment. Verify the participant relationship and report access in the working configuration.
Sopact brings collection and analysis together to prepare a report for review. Staff verify calculations and interpretations, decide who needs support, and approve the information shared with participants or funders.
Explore how applications, staff review, acceptance, enrollment and follow-up could connect. Bring a cohort, a reporting question and the evidence your team needs to review.
Explore the training evaluation software guide, pre/post survey method and worked report examples. See how the King Center uses program feedback and watch Training Program Data: From Application to Job Placement.
