Step 1: check whether the evidence is comparable
Two numbers can look comparable while representing different evidence. GCI labels results as baseline, hybrid or measured and publishes a data period. A dated baseline estimate should not be described as current-month measurement data.
Start by checking period, mode, sample size and confidence. If those fields differ materially, state the difference in the comparison instead of treating rank alone as precise.
The GCI evidence modes
| Mode | Meaning | Responsible use |
|---|---|---|
| Baseline | Dated reference values without enough current community evidence | Broad orientation with an explicit period and lower confidence |
| Hybrid | Baseline combined with validated community observations below the measured threshold | Directional update with visible sample size |
| Measured | Validated observations meeting the published sample threshold | Stronger period-specific comparison, still not a venue guarantee |
Step 2: choose components for the decision
A traveler who mostly reads and streams may value download and availability. A remote worker on calls should give more attention to upload, latency and stability. A media team may need sustained upload that a composite rank cannot fully describe.
Use the Traveler Score to build a shortlist, then open the country pages and compare components. If two countries are close in score, differences in evidence quality or one critical component may matter more than the ordinal rank.
Step 3: respect geographic scale
Country-level evidence blends very different locations, carriers and access conditions. It cannot prove that one neighborhood, hotel or rural route will perform like the aggregate. Small territories and disputed geometries also require explicit mapping rules.
GCI leaves areas without defensible data as “No published data” or “Special area” rather than silently assigning another jurisdiction’s score. The data coverage policy documents this boundary.
Step 4: avoid false precision and weak trend claims
- Round scores when a decimal would imply more certainty than the samples support.
- Do not describe a one-rank difference as meaningful without component and confidence context.
- Do not compare two months as a trend if one is copied baseline or uses a changed methodology.
- Name the index: Mobile Traveler is not the same as fixed-broadband household quality.
- Keep the source URL and retrieval date when publishing an analysis.
A defensible comparison sentence
A useful statement names the measure and limitation: “In the GCI Mobile Traveler Index, Country A has a higher published score than Country B for the stated data period; both values are baseline estimates, so the comparison is directional rather than a current venue-level measurement.”
For a measured or hybrid result, add sample size and period. For journalism or research, use the citation guidance on the Press page and retain the exported evidence fields.
When an API integration needs guardrails
An integration should not drop `data_period`, `mode`, `sample_size`, `confidence` or `availability`. Cache behavior should also preserve the version so an old response is not relabelled as current.
The proposed Connectivity API & Data Pro adds keys, higher limits and change monitoring while retaining those interpretation fields. Commercial access will not create exclusive scores or remove attribution requirements from the standard tiers.