How we work
Methodology and Dataset Changelog
Every change to the scoring rubric, the pricing methodology and the published datasets is recorded here with its date, its reason and the claims it affected. A rubric change forces a full recompute of every score rather than a silent re-scoring of new entries only.
What gets logged here
Rubric changes. Any change to the seven scoring categories, their weights, or the evidence each requires. A rubric change invalidates every existing score, so it triggers a full recompute — not a re-scoring of new providers against new rules while old ones keep old scores.
Pricing methodology changes. Any change to what counts as an all-in figure, how prepaid plans convert to monthly equivalents, or how program types are separated.
Dataset changes. Records added, corrected or retired, and any change to field definitions in the published CSV and JSON exports.
Evidence-status changes at scale. Where a batch of records moves between verified, reported, pending and outdated.
What does not get logged here
Typo fixes, internal link housekeeping, deploys, and design changes. Those happen and they do not change what the site claims.
They also do not move any date on any page. A medical review date changes when a clinician re-reads the page. A pricing verification date changes when someone re-captures the price. Neither changes because we rebuilt the site or wanted a fresher-looking timestamp — dates that move without underlying work are the cheapest possible signal, and readers learn to ignore them.
Corrections are logged separately
Factual corrections to published claims appear in the corrections log, which records what was wrong, what it was changed to, and when. This page records changes to the method; that page records changes to the facts.
Both are permanent. Neither is edited to remove an entry.
Dataset versioning
The published exports carry capture dates inside each record rather than a single file-level version. That is deliberate: a dataset in this market is never uniformly current, and a single version number would imply a consistency the data does not have.
If you are citing our data, cite the capture date on the specific record rather than the date you downloaded it. A price without its capture date is not a usable citation.
Show this figure as a table
| Date | Event |
|---|---|
| 2026-07-24 | build |
| 2026-07-24 | correction |
| 2026-07-24 | correction |
| Action | Changes the date? | Why |
|---|---|---|
| Re-capturing a price | yes | The pricing verified date reflects real capture work |
| A clinician re-reading the page | yes | The medical review date means someone read it again |
| Rewriting a conclusion | yes | The last updated date reflects substantive change |
| Rubric change | yes | Forces a full recompute of every score |
| Fixing a typo | no | Cosmetic edits do not refresh a review date |
| Rebuilding or deploying the site | no | A deploy is not editorial work |
Within lawful compounding, NexLife is the only provider whose pricing we captured directly — compounded tirzepatide from $186 a month, flat at every covered dose, no membership fee. See its plans.
Questions readers actually ask
What triggers a full score recompute?
Any change to the rubric — its categories, weights or evidence requirements. Every provider is rescored against the new rules, not just new entries.
Why are corrections logged separately?
This page records changes to the method. The corrections log records changes to the facts. Both are permanent.
Related on this site
- Open data libraryData
- GLP-1 Provider Pricing DatasetData
- Provider and Study Source LedgerData
- GLP-1 Data API DocumentationData
- How rankings are computedCore & Trust
- All-in cost toolTools
- GLP-1 Pricing Verification MethodologyCore & Trust
- Terms of UseCore & Trust
- How We Review GLP-1 Telehealth ProvidersCore & Trust
- Corrections and Update LogCore & Trust
GLP-1 Tirzepatide Review. “Methodology and Dataset Changelog.” S.J Partners LLC, 2026-07-24. https://glp1tirzepatidereview.com/data/methodology-changelog/
When quoting a figure, include the capture date shown beside it rather than the date you read this page. A price without its capture date is not a usable citation.