The course row that turns green when the funding adds up

By Konstantinos Karamatzianis · Co-Founder, Dabster Labs · Client engagement, anonymised at the client’s preference

The situation

A Cyprus training provider runs courses that only make financial sense once enough participants qualify for a national training-subsidy scheme. The rule is exact: a programme is viable only with at least six subsidised participants, and at least four of those must be employed or self-employed rather than unemployed. Operators were working this out by hand, course by course, from the pipeline, and getting it wrong. Part of the reason was the data itself: the government feed only flagged one kind of subsidy, so the numbers on screen told half the story.

What we built

A funding-eligibility view inside the course pipeline. For each course it splits the approved participants into three subsidy buckets, and it turns the whole row green the moment the programme clears the threshold: at least six funded, at least four of them employed. The buckets reconcile exactly with the approved participant count, so operators trust the number instead of re-checking it. It also closes the data trap that was quietly under-counting funded people.

What changed

• Viability is now a glance, not a calculation: a green row means the course clears the funding bar, with no manual counting.
• The three subsidy buckets add up to the approved count exactly, so the figure is one people act on rather than second-guess.
• Unemployed participants, who are funded under a separate scheme, are no longer left out: they count toward the six, but not toward the mandatory four.
• The funding rule lives in one place and is applied the same way every time, instead of being re-derived by hand for each course.

How it works

The view reads the approved list for each course and sorts every participant into one of three buckets. It then applies the funding rule, six funded of whom four are employed, and flips the row and its status indicator green when both conditions are met. The fix for the data trap sits underneath: the government feed’s subsidised flag only records the employer subsidy, so unemployed participants showed up as unsubsidised even though they are funded through a different scheme. The view now counts them toward the six-person total while correctly keeping them out of the four-employed requirement.

Where it stands

Live in the daily course pipeline. It was shaped through several rounds of operator feedback, so the column labels match the language the team already uses and the totals line up with what they see everywhere else. The result is a single, honest read on whether a course pays for itself, available the moment operators open the pipeline.

Have a process where the right answer is hiding in the data your team already has? Talk to us about it.

Related service: Workflow Automation