Subsidy Seesaw
Employer and trainee blame each other for one stuck claim; the seesaw shows who.
The job
For every wage-support, on-the-job-training and stipend claim, join what the employer says with what the trainee says about the same claim, find where the money is actually stuck and exactly what is missing, tell the one party who can unblock it in plain words, warn key-holders before the next cycle, and close the claim only when both sides confirm the money arrived.
The moment
October: 412 employers say their subsidy is stuck and 1,900 trainees say their stipend is late. The seesaw shows they are two ends of the same 1,640 claims under 380 employers, all waiting on the host employer's monthly attendance confirmation, which the portal marked submitted even though it had failed validation. $6.8M sits in coins on the employer end. The director approves one plain message to the 380 employers and a ticket to fix the status text. Five days later 1,420 claims have paid, 1,100 seesaws have levelled as both sides said paid, and the counter reads $6.8M fell off the seesaw this week. In November's Eve Check, 290 employers got the warning before the cycle, and only 31 claims stuck.
What it does
- Message the side holding the key in plain language
- Propose one bot answer for each side
- Open a digital-team ticket for a misleading portal status
- Ask both sides 'did it arrive?'
- Warn key-holders before the next cycle
- Refer an integrity case to compliance
- Log the fix's price
What you see
A split-screen seesaw per claim and cluster (employer left, trainee right) tipping towards whoever holds the blocker, with coins piling on that end and dropping to both hands on confirmation.
What it moves
Money released per cycle, money never stuck (Eve Check vs matched unwarned claims), and share of claims closed with both sides confirming paid.
Built for
- Finance
- Compliance, complaints & legal
