Hypothesis
A placement still employed after ninety days is the programme's result; a match shown is only its activity.

Operator foundations, CSR teams and employment agencies
A verified employer lists a vacancy. Two hundred programme members with a matching skill have consented to be matched, in three languages.
Read the journey; a working session shows it running.
Seen by the customer · USSD
From the record, not a run: what would reach them, on USSD, App, SMS.
What happened
A verified employer lists a vacancy, and two hundred programme members with a matching skill have consented to be matched.
A verified employer lists a vacancy. Two hundred programme members with a matching skill have consented to be matched, in three languages.
What it reads
Checks before anything is sent
Consent, eligibility, legal basis, minimum group size and bias and exclusion checks pass.
Every option considered, including doing nothing
Doing nothing is one of the outcomes, and it is recorded with its reason. The options are the record's own; a run decides between them.
The shape of the record, with no values. A reference appears only after a run is saved.
Hypothesis
A placement still employed after ninety days is the programme's result; a match shown is only its activity.
Modelled
The mechanism that could produce the result, stated; the figure is measured in the pilot.
Observed
Measured in a pilot’s validate stage, on your systems, against a comparison agreed first.
Geographic/time phased rollout; process baseline; independent privacy and bias review; publish limitations; never infer causal impact without design
Measured on: Response time; queue reduction; service completion; coverage; false alert; excluded population; resource efficiency; public outcome metric
The result wanted.
Faster, more accessible and better-targeted public service; improved resilience and resource allocation
The mechanism that could produce it.
Authorise purpose → prepare/aggregate → analyse → apply thresholds → agency review → act → log → publish impact and bias checks where appropriate
The records kept to show it.
Purpose approval; data agreement; aggregation test; model/logic version; agency decision; action log; impact/bias review; public reporting
The cost, and the ways it can go wrong.
Costs: Fixed project + annual managed service; government framework contract; outcome milestone only where measurement and authority are agreed
If it fails: Withhold unsafe output; escalate to agency privacy/command authority; fall back to official data/process; never expose raw subscriber records
The measure that shows it helped.
Geographic/time phased rollout; process baseline; independent privacy and bias review; publish limitations; never infer causal impact without design
Measured on: Response time; queue reduction; service completion; coverage; false alert; excluded population; resource efficiency; public outcome metric
Measured in the pilot's validate stage, on your systems, with the comparison agreed first. Every line above is the record's own design intent.
The business side
| Step | What the customer experiences | What the operator does |
|---|---|---|
| The momentThe moment that started it. | A verified employer lists a vacancy, and two hundred programme members with a matching skill have consented to be matched. | Reads the vacancy and its requirements, skills, location and availability the applicant shared, consent, eligibility and accessibility rules, bias and exclusion review of the match. |
| The decisionThe decision to be made. | The customer's screen is unchanged. | Matches skills, location and availability to the vacancy within the programme's eligibility and accessibility rules, in the applicant's language. |
| The safeguardsThe conditions that stop it. | Still unchanged: the action waits until every check has passed. | Consent, eligibility, legal basis, minimum group size and bias and exclusion checks pass. |
| The actionThe action that reaches the customer. | Show the match to the applicant first; the employer sees a profile only with the applicant's consent, and the agency records the placement. Reaches them on USSD, App, SMS. | Recommends. The system that holds the right confirms, charges or provisions. |
| When it goes wrongThe failure, and the recovery. | The match favours applicants in the city because the location signal is finer there, and rural members with the skill are never shown the vacancy. | The bias and exclusion review catches the skew before the vacancy closes, the location weighting is corrected, and the impact review reports the correction publicly. |
| The resultThe change it made. | What changed for them is what is counted; nothing else is claimed. | Placements made and still employed after ninety days, against matches shown. |
| The proofThe proof anyone can check. | Can be answered for, later, from the record. | Vacancy, consent, match reasons, applicant's decision, employer's decision, placement record and employment outcome. |
Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.
What goes wrong
The match favours applicants in the city because the location signal is finer there, and rural members with the skill are never shown the vacancy.
What happens then
The bias and exclusion review catches the skew before the vacancy closes, the location weighting is corrected, and the impact review reports the correction publicly.
Job, skills and vacancy matching, training recommendation and a local-language application assistant run as a measured programme with clear eligibility, accessibility, employer and agency responsibility and employment-outcome tracking.
the public-service data rules the programme runs under
the local-language assistant a job seeker uses
Available to see today
Read the journey; a working session shows it running.