Subsidy Seesaw
Employer and trainee blame each other for one stuck claim; the seesaw shows who.
The job
Joins what employers and trainees say about each wage-support, training or stipend claim, finds where the money is stuck and why, and tells the one party who can unblock it. Warns them before the next cycle, and closes claims only when both confirm payment.
The moment
In October, 412 employers say their wage subsidy is stuck and 1,900 trainees say their stipend is late. The app shows they are two ends of the same 1,640 claims under 380 employers.
All are waiting on the employer's monthly attendance confirmation, which the portal showed as submitted even though it had failed validation. The stuck money totals $6.8 million.
The director approves one plain message to the 380 employers and a ticket to fix the portal's status text. Five days later 1,420 claims have paid, and on 1,100 both sides have confirmed the money arrived.
In November, 290 employers get a warning before the cycle, and only 31 claims get 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 each cycle, money that never got stuck thanks to early warnings (compared with similar unwarned claims), and the share of claims closed with both sides confirming payment.
Built for
- Finance
- Compliance, complaints & legal
