Request a technical briefing

Documents, and the questions we are asked most

Both documents are sent on request rather than posted, so you receive the current version and we can answer whatever it raises. Requesting one is not a commitment to anything.

Overview

Platform overview

What the platform does, the five stages, the programmes it covers, and what a first retrospective review produces. Written for a director or a deputy who needs to decide whether to convene a technical conversation.

Technical

Technical methodology note

Estimation design, validation protocol, and the explainability specification, at the level of detail your methodologists will want to argue with. Shared under agreement.

We use your details only to send the document and to respond to your request. We do not sell or share contact information. See the privacy policy for how contact details are handled.

Frequently asked questions

Does this replace our surveys?
No. Field collection remains the ground truth; the platform gives an independent second reading of it. Remove the survey and there is nothing left to reconstruct against — the method depends on the survey existing.
Does it replace our statisticians?
No. It produces flags and explanations for analyst review. Every decision stays with your staff and is logged. The platform has no authority to publish, alter, or override a figure.
Which surveys does it support?
Any repeating instrument that sits alongside administrative data — household, labour, health, agricultural, business, and price programmes among them. The method is not tied to a subject area.
Where is our data processed?
Within your own infrastructure, on-premises or in a sovereign cloud region inside your jurisdiction. No microdata leaves your jurisdiction, and there is no vendor-side copy.
How do we know the model is right?
You check it against data you already hold. That is why it reconstructs rather than predicts: run it against a closed, published round and you can measure how closely it reproduces figures you already know to be correct — before it informs anything.
Can our methodologists inspect it?
Yes. Model documentation, feature attribution and record-level explanations are deliverables, not extras. The point of the explanations is that your staff can disagree with the platform on substantive grounds.
What do we provide?
Existing microdata, any administrative registers you choose to include, and published macro indicators. Nothing needs to be collected specially, and no survey instrument is redesigned.
Insights

Notes on survey quality and model-based estimation will be published here. Nothing is listed yet — we would rather post nothing than post filler.

Still the wrong level of detail?

A technical briefing goes further than either document, and goes there against your own instruments.