# Global referral partner directory: coverage fields | SourceX

Canonical: https://refer.sourcex.si/guides/a-global-partner-directory-should-show-coverage-not-blanket-approval
Last updated: 2026-11-05

Give each listing coverage fields only: the countries where the partner works, as ISO country codes, the languages they work in, the sectors they know, and the date they last confirmed it. Keep eligibility out of listings entirely. Quote SourceX's geography sentence once, word for word, at the top of the directory, link the English-language guide, and never expand the sentence into a country list, a tick or a shaded map. A listing says where a partner can make introductions; SourceX alone decides which companies fit.

This is for the platform manager who runs a directory of people who introduce companies to SourceX: a fund's venture partners across regions, a network's members or an association's adviser finder. The listing-level evidence standard for claims such as activity and outcomes is in [a partner directory should not imply guaranteed results](/guides/a-partner-directory-should-not-imply-guaranteed-results). This page covers the geography fields, where a single green tick can turn a list of people into what reads as SourceX's verdict on a country.

## Coverage and eligibility are different fields

A directory answers "who can help me here?" Eligibility answers "will this company be considered?" Structured-data vocabularies already keep these apart. Schema.org describes areaServed as the property for the geographic area where a service is provided (paraphrase), and defines a separate property, eligibleRegion, as "The ISO 3166-1 (ISO 3166-1 alpha-2) or ISO 3166-2 code, the place, or the GeoShape for the geo-political region(s) for which the offer or delivery charge specification is valid."

A partner directory owns the first kind of field and none of the second. The partner's service, making an introduction, is available where they work. Whether a company in that place can license its records is a statement about SourceX's offer, and only SourceX can make it.

Two clauses in the Channel Partner Agreement make the line contractual as well as editorial. Section 7.1 says "Partner is not an agent of SourceX and may not commit SourceX to prices, licenses, payouts or other obligations." Section 4.5 says "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required." So a directory may not grant a country SourceX's approval, and it may not even call someone a SourceX partner without that written authorization.

## SourceX's sentence, shown once and never expanded

SourceX publishes one geography sentence, quoted here exactly:

Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Its English-language condition is explained in SourceX's [English-language guide](/guides/english-language-data-referral-eligibility). SourceX publishes no other country rule, and its who-qualifies page says criteria follow each program and can move.

Directories get this wrong in two predictable ways, and both come from trying to make the sentence machine-readable.

- **Expanding the groups.** The sentence names "the EU" and "Latin America" as groups, not code lists. Turning them into rows of ISO codes means the directory decides which countries belong, a rule SourceX has not published, and leaves the list stale whenever a group changes.
- **Ticking countries on the second list.** The English condition attaches to a company's data, not to a country. One country holds companies whose records meet it and companies whose records do not, so no country on that list can carry a tick.

The fix is to treat the sentence as a quotation, not as data: one header block, the exact words, a link to who-qualifies and the date the directory last read it.

## The coverage-versus-eligibility metadata standard

Every listing carries these seven fields and no others that touch geography. ISO 3166-1 supplies two-letter codes for country names and ISO permits free use of its country and ISO 639 language codes (paraphrase), which keeps entries consistent across regions and languages.

| Field | What it holds | Allowed values | Example (Illustrative) | Never |
|---|---|---|---|---|
| partner_works_in | Countries where the partner holds relationships and works | ISO 3166-1 alpha-2 codes, self-declared | MX, US | Region words such as "LatAm" or "APAC"; any color coding |
| partner_languages | Languages the partner works in | ISO 639 codes | es, en | Any statement about a company's record language |
| sectors_known | Industries the partner knows well | Free text, self-declared | freight, customs brokerage | "Sectors SourceX is buying" |
| program_status | The partner's standing with SourceX | "Registered partner", shown only with SourceX's written authorization and while the agreement is in force | Registered partner, authorized September 2026 | "Approved", "official", "preferred", "certified" |
| coverage_note | One fixed sentence on every listing | Identical text everywhere | "Shows where this partner works. It says nothing about which companies SourceX accepts." | Edited per listing |
| criteria_link | Link to who-qualifies and the date the directory read it | URL and date | /who-qualifies, read 27 October 2026 | A copied country list |
| last_verified | Date the partner last confirmed the listing | Date | 2026-10-27 | Undated listings |

**Banned outright:** fields named eligible_countries, approved_markets, supported_regions or SourceX coverage; per-country ticks or badges; map shading that follows SourceX's list; company names; counts of companies "ready" or "pre-qualified" in a country.

**Display rules.** Label the country filter "Partner works in", never "Eligible in" or "Available in". Show country chips in one neutral color. Put the quoted sentence above the results, not in a footer. Remove the program_status line the day a partner's agreement lapses: the terms say it runs for one year and renews only with fresh acceptance and signatures.

**Method note.** The standard applies SourceX's who-qualifies page, the program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and the sample Channel Partner Agreement, read on 2026-10-27, with schema.org's property definitions and ISO 3166 as naming conventions. It governs what a listing may say about geography. It does not assess any partner's quality, any company's fit or any country's prospects.

## Three listings, before and after (Illustrative)

Illustrative. Invented partners; no listing describes a real person or firm.

| Listing as first drafted | What it implies | Listing under the standard | Still unknown |
|---|---|---|---|
| "Mexico City. Covers Mexico and LatAm. SourceX-eligible markets", beside a green tick | SourceX has approved Mexico and every country in the region | Works in: MX, US · Languages: es, en · Sectors: freight, customs brokerage | Whether any company this partner knows fits a current program |
| "Frankfurt. EU-wide coverage, all countries approved" | The partner can reach every EU company, and SourceX approved them all | Works in: DE, AT, NL · Languages: de, en · Sectors: industrial distribution | Whether the partner holds written authorization to be named as a SourceX partner |
| "Singapore. Asia-Pacific, SourceX covered" | SourceX covers a region its sentence does not name as a whole | Works in: SG, IN, AE · Languages: en, hi · Sectors: customer operations | Each company's record language, which only that company can state |

Notice what the corrected listings gave up: nothing a company owner needs. They still say where to find someone who knows freight in Mexico. What they dropped was a promise only SourceX can make. For a SaaS company listing the program itself, rather than people, the equivalent checklist is in [a partner marketplace listing for an introduction-only program](/guides/a-partner-marketplace-listing-for-an-introduction-only-program).

## Who answers the questions a directory raises

- **Whether a partner may advertise referral work where they practice:** that partner's own adviser or professional body.
- **Whether a listing may name SourceX:** SourceX, in writing, under section 4.5.
- **Whether a company in a listed country fits:** SourceX, in review. The directory never pre-screens.
- **Whether a company's records may cross borders:** the company's own advisers.

Give no legal view on any of these, even in a help-desk reply. The directory's job is to route the question and note where it went.

## Keeping the directory honest: one dated line per listing

Review every listing at least every six months and whenever SourceX's who-qualifies page changes. Each review ends with one dated line:

1. **Kept:** "2026-10-27: partner confirmed MX, US; no change."
2. **Corrected:** the field changed and the reason.
3. **Paused:** the partner asked to stop receiving enquiries; listing hidden, data kept.
4. **Removed:** agreement ended, authorization withdrawn or partner left; the date and which of these.

When SourceX changes its sentence, update the header the same day, with the new read date, before touching any listing. Listings never carry their own copy of the sentence, which is why one update fixes all of them.

## Where a coverage directory can still mislead

- **Maps persuade.** Even neutral shading suggests availability. A table of partners by country is harder to misread than a colored map.
- **Coverage is self-declared.** A partner who lists five countries may know one well. The last_verified date and a short sectors field limit the damage; they do not remove it.
- **Search reads as endorsement.** A reader who filters by India and sees ten partners may infer SourceX favors India. The coverage note on every result row is the countermeasure.
- **Criteria change.** SourceX's page says its criteria follow each program and can move. A header read in October is a dated quotation, not a standing rule.
- **Translation drift.** A localized directory can turn "works in" into "approved for" in another language. Check translated labels against the English ones before publishing.

A measurable check: once a quarter, open ten random listings and count fields that would fail the standard. The target is zero, and the trend matters more than any single count.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Partners who appear in your directory still introduce companies one at a time: each should [register](/register), check every company against [who qualifies](/who-qualifies) on the day and work from the current [program terms](/terms). The full set of geography checks before an ask is in [why geography is only one part of qualification](/guides/why-geography-is-only-one-part-of-referral-qualification), and more guides are in the [guides library](/guides).

Running a partner directory is referral work; evaluating SourceX as an investment is a separate decision, and readers considering it can request materials through the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://schema.org/areaServed
- https://schema.org/eligibleRegion
- https://www.iso.org/iso-3166-country-codes.html
- https://sourcex.si/investors
