Corrections Policy
We fact-check every claim in every article before it publishes. When we still get something wrong — and eventually, we will — here’s exactly how we handle it.
Our Commitment to Accuracy
Every statistic, price, feature claim, and quote in a TSL article is checked against a primary or otherwise verifiable source before publication. Tool reviews specifically follow the TSL Review Standard, which requires distinguishing what a vendor claims from what we’ve actually tested. Mistakes still happen — a price changes the day after we check it, a feature we tested behaves differently on a later visit, a source turns out to be wrong. This policy is how we handle that.
How We Handle Errors
| Type of issue | How we handle it |
|---|---|
| Factual error affecting a core claim, price, rating, or verdict | Corrected as soon as we’re aware of it, logged in the article’s Review History with a date and a description of what changed |
| Minor error (typo, formatting, a broken link) | Fixed directly, without a Review History entry |
| A tool’s pricing, features, or engine coverage changes after publication | Re-checked and updated on our normal review-refresh schedule, or sooner if flagged to us |
We don’t quietly rewrite a review’s conclusion to look like we always had it right. If a substantive fact or finding changes, the article’s Review History says so plainly, with a date — history is part of the record, not something we erase.
How to Report an Error
If you spot something wrong in one of our articles — a vendor, a reader, or anyone else — email us at hello@thesaaslibrary.com with the article URL and what you believe is incorrect, ideally with a source we can check it against. We read every message.
A Note for Vendors
If you’re the maker of a tool we’ve reviewed and believe something is inaccurate, the same process applies: email us with specifics and a source. Commercial relationships — including any affiliate arrangement disclosed on the article — never determine whether or how we correct a factual error.