Public remittance data for stories that need evidence

What we publish publicly

A public source pack is an aggregate research packet, not a raw feed. When a corridor clears the public gate, the packet can include the corridor, origin, destination, amount band, collection window, observation count, category count, freshness label, and approved aggregate exhibits such as a receipt-gap estimate, spread index, or payout-method bucket. It also includes a claim registry so a reader can see which claims are approved, which evidence supports each claim, and which statements were intentionally withheld.

Public source-pack rules are strict: provider names stay out of public source packs. Raw quote records, exact collection timestamps, collection URLs, internal identifiers, and provider-specific fingerprints stay private. The public CSV should be easy for a journalist to cite without exposing the data that belongs in governed institutional feeds. That is the center of the business model: public research earns trust and backlinks; private governed feeds preserve the more detailed value for institutional review and paid use.

The public page is also expected to be honest about uncertainty. A full source-pack article needs at least 30 eligible observations, at least three provider categories, and a largest observed category share at or below 60 percent. A smaller packet can still teach us where to look next, but it should be described as directional or watchlist-only. That language is not hedging for its own sake. It tells a journalist that a signal exists, while keeping us from making a market-wide claim when the sample is not ready for that weight.

The public source-pack URL pattern is intentionally simple. The source-pack index lives at /press , while publishable story packets can appear under a story-specific press path when their manifests clear the frontend publication gate. If a packet is draft-only, suppressed, or missing a publishable manifest, it should not appear as a public detail route, in SEO inventory, or in JSON-LD as if it were ready.

The article types

The drafter treats story lanes as article types. New Economy Desk proposals use the same writing criteria: a finished article body of at least 1,500 words, official source references, approved source-linked claims, public-safe source-pack links, a named editor, corrections routing, and language that matches the strength of the data. This is a proposal gate, not a retroactive word-count promise for every historical article. The current Economy Desk lanes are receipt gap, hidden FX spread, corridor watchlist, quote drift, payout friction, policy or news hook, benchmark gap, regional pattern, operator or institutional view, and journalist source pack.

The receipt-gap lane is the default because it can be sourced directly from a fresh aggregate dispersion artifact when the corridor is publishable. Other lanes are real, but they often need enrichment. A hidden-spread story needs an approved spread exhibit. A quote-drift story needs a drift metric. A payout-friction story needs payout-method buckets. A policy-hook story needs a primary policy or news source. A regional-pattern story needs enough corridors to avoid turning one route into a continent-wide claim. A journalist source-pack story needs a citable packet, not just a promising lead.

This is why the system can look conservative even when the datasets are large. We may have many internal observations, but public journalism depends on the subset that is current, rights-safe, comparable, and broad enough to carry a claim. Economy Desk should use outside public data where it adds context. It can cite the World Bank, the Consumer Financial Protection Bureau, central-bank releases, migration data, or primary policy documents, then add Remit-Scout's aggregate lens. It should not manufacture certainty from a corridor just because a story slot exists.

How outside sources fit

Official datasets give the article a public baseline. The World Bank Remittance Prices Worldwide project tracks remittance prices and is used in global cost-monitoring work. The World Bank also describes the database as a source of quarterly analyses used by researchers and economists. The World Bank DataBank corridor dataset gives reporters a public place to inspect corridor-level indicators. In the United States, the Consumer Financial Protection Bureau money-transfer resources explain consumer rights and disclosure expectations for international transfers, and Regulation E defines covered remittance transfers in official rule text.

Economy Desk should use those sources as context, not camouflage. If a World Bank series says global remittance costs remain high, that does not automatically prove a Remit-Scout corridor finding. If a regulator explains disclosure duties, that does not automatically prove that a specific route is misleading. The article must keep the layers separate: official context tells readers why the subject matters; Remit-Scout's aggregate packet tells readers what our observed data can and cannot add today.

This is also how backlinks should be earned. A journalist should be able to link to a source pack because it answers a real reporting question: what was measured, over what window, with how many observations, under which public-safety rules, and with which claims approved for reuse? The best language is precise and modest: "Remit-Scout Economy Desk found," "the public aggregate snapshot suggests," "this is a directional signal," and "the source pack does not identify providers." That language gives the article authority without overstating the dataset.

How the workflow should run

The nightly workflow starts with radar and dispersion evidence. It looks for corridors or regions where current observations are strong enough to support public writing. It then builds a sanitized draft input: no public provider names, no raw quote records, no unsafe identifiers, and no fields that would expose private collection mechanics. The readiness layer classifies each candidate as publishable, directional, watchlist-only, suppressed, or degraded.

If a candidate is publishable, the drafter can generate the article, source pack, claim registry, methodology, and related metadata. That is the "wake up with a usable article" path. The output should already contain the editor, source links, article body, word count, public-safe claims, corrections route, and calls to action. The editorial review is still real, but the human should be reviewing a finished packet, not stitching together a blank page.

If no candidate is publishable, the system should not force a corridor article. It should write a readiness memo that explains what failed: too few eligible observations, not enough categories, missing dominance evidence, stale data, degraded collection, or a rights policy that suppresses the row. That memo is useful for the editor and for engineering. It says where to fix coverage, which enrichment is missing, and which story lane could become public once the data clears. The memo is not a substitute for a source-pack-backed corridor article.

Editorial standards

Every public Economy Desk piece needs the same trust signals. It needs a named desk and editor, a publication or update date, visible source links, an explanation of the method, a clear boundary between public aggregates and private feeds, and a path for corrections. The article should avoid anonymous authority. It should say who prepared the piece, what dataset was used, what was withheld, and where a reader can ask for clarification.

It also needs a useful reader path. Consumer readers should be able to compare today, because a data story about costs is more useful when the reader can check the current market. Journalists should be able to read more source-pack policy and contact the desk for a source note. Operators and NGOs should understand that the public packet is aggregate, while governed private feeds can support deeper diligence. That is why the primary calls to action on this page are Read more , Compare today , and Contact us .

Corrections are part of the product, not an afterthought. If a public claim is wrong, stale, unclear, or missing context, readers can use the corrections policy or press contact route. A correction should identify the affected claim, the source-pack URL, the change made, and the reason for the change. If a correction changes the meaning of an aggregate finding, the article should say so directly.

Who should use it

Journalists can use Economy Desk when they need a remittance story with a method, not just a quote. The strongest targets are reporters who already cover immigrant communities, consumer finance, development economics, fintech infrastructure, payments, banking access, or cross-border policy. The pitch should be short: one finding, why it matters to that beat, the source-pack link, and an offer to verify the method.

NGOs can use the public packets as a lead generator for consumer-friction research. Fintech operators can use them to understand where consumer experience gaps may be visible from the outside. Executive readers can use them to frame a market question before requesting governed data. Consumers can use the comparison path to check live options, while understanding that a public research article is not personal financial advice and not a guarantee that a quote shown elsewhere remains available.

The gap this page is meant to close is practical. If today's data does not clear the publication gate, Remit-Scout still needs a credible public explanation of how the desk works, why some stories wait, and how source packs can be cited once they are ready. That gives journalists a stable reference now and gives the drafter a stricter target later: not just a long article, but a long article with evidence, public-safe source files, official context, and reviewable editorial standards.