# Assess English Documentation for US Data Referrals

Canonical: https://refer.sourcex.si/guides/how-to-assess-whether-business-documentation-is-primarily-in-english
Last updated: 2026-11-04

SourceX primarily licenses data directly from companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) with operational documentation in English. Referral partners can assess this by checking key internal resources, communication patterns, and whether primary business operations are conducted in English, without needing to review sensitive data.

## Why English Documentation Matters for US Data Referrals

Many of the AI developer programs supported by SourceX have a strong preference for, or even require, proprietary operational documentation from referred businesses in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) to be primarily in English. This is because the AI models being trained or refined often operate in English, and ingesting non-English data requires additional processing and translation, which can increase costs and complexity for buyers. Successfully matching a referred company to a SourceX's current data needs often depends on this linguistic alignment.

As a referral partner, you don't need to deep-dive into a company's internal documents or ask for sensitive information. Your role is to make an informed, metadata-level assessment that can guide your referral and help SourceX prioritize evaluation of potential US data licensors.

## How to Assess English Documentation (Metadata-Level)

When considering a potential company for referral, you can make a quick, high-level assessment of their documentation's primary language through public information and general inquiries. Focus on indicators that suggest whether their *core internal operations* are conducted and recorded in English.

### 1. Company Origin and Primary Market

*   **companies based in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia:** Companies based in the USA are highly likely to have English as their primary documentation language.
*   **Global or multinational operations:** companies with a significant international presence, especially those serving English-speaking markets, often standardize their internal processes and documentation in English, even if they have offices in non-English speaking countries.

### 2. Website and Public Communication

*   **Primary website language:** Is their main website primarily in English? Do they offer an English version, and does it appear to be the most comprehensive? This suggests English is important for their external communication.
*   **Social media and press releases:** Are their official social media channels and public press releases predominantly in English? This indicates a public-facing English proficiency.

### 3. Hiring Practices and Employee Profiles

*   **Job postings:** Do their job descriptions often require English proficiency, especially for roles like project managers, engineers, or technical writers? This suggests English is used for internal communication and documentation.
*   **LinkedIn profiles:** While not definitive, looking at the professional profiles of key employees (e.g., project managers, operations leads) might indicate if they list English as a primary working language or highlight experience in English-speaking environments.

### 4. Software and Tools Used Internally

*   **Common platforms:** Many companies use standard enterprise software (e.g., Salesforce, Jira, SAP, Microsoft 365, Google Workspace) that are often configured and used in English for their teams. If the company operates globally, they may opt for English as the common language across these platforms.
*   *Illustrative:* A company in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia headquartered in Texas that primarily uses English for its internal Jira tickets and Confluence wiki across its global development teams is a strong indicator.

### 5. Direct, Non-Intrusive Inquiry

If you have a relationship with the decision-maker, you can ask general questions without requesting access to data:

*   "What language do you typically use for your internal standard operating procedures (SOPs) or internal knowledge base?"
*   "Is English commonly used for internal project documentation, especially for your international projects?"

Remember, your goal is to assess whether the bulk of their *proprietary operational documentation* (e.g., SOPs, internal knowledge bases, project histories) is in English, not just that they have an English-language website or some employees who speak English. This initial check helps ensure the company is a good fit for current buyer needs, as outlined in the [who qualifies criteria](/who-qualifies).

If you're unsure about a company's fit, even regarding language, it's always best to make the introduction. SourceX will perform a detailed review, and a company that doesn't fit one program's language requirement might fit another's in the future. You can also explore the [company fit checker](/tools/company-fit-checker) for a preliminary screen.

> Rewards are calculated as the greater of $50,000 plus 5% and 15% of the compensation SourceX actually pays the company you refer, with no cap. A lead, meeting or signed agreement alone does not trigger payment. See the [program terms](/terms).
