About
What we measure
Six things we track, the record that would prove each one, and what has actually been measured so far.
1/6
have a figure today
The programmes have not run yet. That is the whole reason the other 5 are empty, and it is worth more than a filled-in number would be.
It is easy for a student project to say it helped people and never check. So each of the six below is paired with the record that would prove it, and with whatever the current figure is.
Nothing here is a projection or a goal. A target we have not hit is not a measurement, so it does not appear on this page. A figure without the date it was collected does not appear either.
Every statistic on this site, with its source is the evidence layer for this page. The two are meant to be read together.
Measured today
0
corrections published
Does the work hold up
Review letters, revision logs, and the corrections log on this page.
Zero corrections is a measurement, not a blank. It will stop being zero, and when it does the number goes up on this page rather than quietly staying put.
Tell us if something here is wrong
What starts the rest
Each of the remaining 5 is waiting on one specific thing. Grouped by what that is, because two of them are waiting on the same workshop and five separate cards saying “not yet” would hide it.
The first full RemitBench run
unlocks 1 measure
Research quality
- How it is counted
- How many setups we tested, how many test runs finished, and whether someone else could rerun them.
- What proves it
- Public code repository, methods paper, version history, replication log.
The pilot workshop
unlocks 2 measures
Community reach
- How it is counted
- Workshops held, how many people came, how many languages, and where.
- What proves it
- Head counts and locations. No names, nothing sensitive.
Did people learn anything
- How it is counted
- Whether attendees could work out a full transfer cost and spot a scam afterwards when they could not before.
- What proves it
- Anonymous surveys before and after each session.
The first quarter with fellows on a team
unlocks 1 measure
Student leadership
- How it is counted
- Active fellows, finished deliverables, hours put in, and talks given.
- What proves it
- Quarterly delivery logs from each team.
One full quarter after the site goes live
unlocks 1 measure
Is anyone using the tools
- How it is counted
- Calculator sessions, guide downloads, and anyone citing the papers.
- What proves it
- Aggregate counts only. We do not track individual users.
Corrections
Every change made to a claim after it was published, with what it said before.
A lab that publishes and never corrects is not being careful, it is not checking. So corrections are counted on this page rather than quietly absorbed, and the count is treated as a credibility figure.
Nothing has been corrected yet
When a number, a claim or a source on this site turns out to be wrong, the change is recorded here: what it said before, what it says now, the date, who found it, and what prompted it. Nothing is edited away quietly.
If something here looks wrong, telling us is the most useful mail we get. Point at the page and say what is off.
Report something wrong on this siteThe annual brief
Once a year the lab intends to publish a Cross-Border Payment Access Brief. It will collect the RemitBench results, the questions that came up repeatedly at workshops, what the calculator turned up, and what we think should change.
It will also carry a section on what went wrong and what we could not work out, which is usually the more useful half and is the part most likely to be left out of a document like this.
It has not been published. There has been no first edition, and there is no date for one until there are results worth collecting.
When it exists, this section becomes a link to it.