Put a defensible dollar figure on your Level 4 training result: monetize the outcome conservatively, subtract the fully-loaded cost, and express the ratio — with your assumptions and attribution limit stated in plain sight.
In short: Training ROI is the net financial benefit of a program divided by its fully-loaded cost, expressed as a percentage or ratio. In Sopact Sense you calculate it on the Level 4 result already sitting on each participant record: monetize the outcome conservatively, subtract program cost, isolate the share the training actually caused, and always show the ratio next to the assumptions behind it — a number without its assumptions is a guess, not ROI.
Training ROI is the last step of the Kirkpatrick chain, not the first. Before you touch a dollar figure, confirm the Level 4 business result is already captured in Sopact Sense — reduced attrition, higher productivity, fewer errors, faster ramp — and that it links back to the Level 3 behavior change that produced it. Sopact keeps Level 1 through Level 4 on the same persistent participant record, so the outcome you are about to monetize is traceable to the behavior evidence underneath it. If you cannot see the Level 3 behavior change, stop: you have a correlation, not a return.
The formula is net program benefit divided by fully-loaded program cost. Net benefit is the monetized outcome minus the program cost; dividing that by the cost gives a percentage, or you can express the raw ratio. A program that returns $150,000 in benefit against a $50,000 cost has a net benefit of $100,000, an ROI of 200%, and a benefit-cost ratio of 3:1. Fully-loaded cost means everything: design, facilitation, platform, participant time, and travel — not just the invoice from the vendor.
Convert the Level 4 outcome into money using the most defensible unit value you have, and round it down. Reduced attrition is valued at the replacement cost of the roles you kept; a productivity gain is valued at loaded salary times the percentage improvement; error reduction is valued at the cost of the errors avoided. When a value could reasonably fall in a range, use the bottom of the range. Conservative monetization is what makes a finance reviewer trust the number — over-claiming on the benefit side is the fastest way to have the whole figure dismissed.
Not all of the outcome is the training's doing, so estimate the share it actually caused before you report a return. The strongest method is a comparison group — trained participants versus a matched untrained cohort — and Sopact Sense can hold both cohorts on the same record structure for a clean side-by-side. Where a comparison group is not possible, use a participant or manager contribution estimate: ask what percentage of the improvement they attribute to the training, and multiply the monetized benefit by that percentage. State the attribution method and its limit every time.
Choose the framing to the audience. A benefit-cost ratio (3:1) or an ROI percentage (200%) is the right answer for a finance or executive reviewer who wants one comparable number. A payback story — "the program paid for itself in five months, then returned two dollars for every one spent" — lands better with program sponsors and participants who want the narrative. The underlying math is identical; only the presentation changes.
From the Level 4 results for [PROGRAM], estimate training ROI: monetize the outcome conservatively, subtract fully-loaded program cost, express the ratio, and state the two biggest assumptions and the attribution limit.
Expected output. A short ROI brief: the monetized benefit with its unit value, the fully-loaded cost, the net benefit, the ratio and percentage, the two largest assumptions, and one line naming the attribution limit. Input → output: the Level 4 outcome and cost inputs on the participant record go in; a defensible, assumption-labeled ROI figure comes out.
GRADE: green | ratio + assumptions + attribution stated | over-precise decimals; amber | ratio present | assumptions missing; red | headline ROI only | no Level 3 evidence, no attribution
A Green answer shows the ratio, its assumptions, and the attribution limit together. An Amber answer gives the ratio but hides the assumptions. A Red answer is a headline ROI with no behavior evidence and no attribution — do not ship it.
Be conservative on every input. When a value could fall in a range, take the bottom of it and round down. A modest ROI a finance reviewer believes beats a spectacular one they discount on sight.
Show your assumptions in the deliverable, not a footnote. Put the unit value, the attribution percentage, and the cost basis directly beside the number. ROI is only persuasive when the reader can see exactly how you got there and swap in their own inputs.
Never present ROI without the Level 3 behavior evidence. A return with no behavior change underneath it is a coincidence you monetized. Keep the Level 3 → Level 4 link visible on the participant record so the dollar figure always traces back to something people actually did.
Training ROI is the net financial return a training program produces, calculated as the monetized business outcome minus the fully-loaded program cost, divided by that cost, and expressed as a percentage or a benefit-cost ratio. It sits at Level 4 of the Kirkpatrick model, on top of the Level 3 behavior change that caused the result.
Monetize the Level 4 outcome conservatively, subtract the fully-loaded program cost to get net benefit, then divide net benefit by cost. Before reporting, isolate the training's share of the outcome with a comparison group or a participant/manager contribution estimate, and state your assumptions and attribution limit alongside the number.
A benefit-cost ratio at or above 2:1 (a 100%+ return) is generally considered strong, but the credible number matters more than the big one. A conservatively monetized, attribution-adjusted 150% that a finance reviewer accepts is worth more than an unqualified 400% they dismiss.
ChatGPT, Claude, and Gemini are fine for a quick test — but not for an answer you'll put in front of a funder or board. When it has to hold up, run it in Sopact Sense.
Try it in Sopact →
