Methodology
What this site is, and isn’t
The Best ELN is a structured overview of electronic lab notebook vendors, not a set of hands-on product reviews. No editor on this site has necessarily run every one of these systems in a live lab. Instead, each fiche is built from publicly available, citable sources: vendor documentation, compliance white papers, public records such as procurement documents and institutional reports, independent review platforms, and vendor pricing pages where they exist. That’s why fiches say “overview,” not “review,” and why the assessment section on each fiche uses a qualitative, sourced reading rather than a tested-and-scored rating.
Sourcing rules
- Every verifiable fact has a source. Each fiche lists its sources with a title, a URL, and the date it was checked.
- Claims are labeled by evidence level. For compliance specifically, each standard (21 CFR Part 11, EU Annex 11, ISO 27001, and so on) is marked Vendor-documented when a vendor publishes a specific, citable page mapping its product to that regulation, Vendor-stated when the vendor states support without that level of detail, Not mentioned when nothing was found, or Not supported when a standard is explicitly excluded. Vendor-documented means the vendor describes it; it does not mean we have tested it.
- No price is stated without a source. Where a vendor doesn’t publish pricing, we say so, and any third-party estimate is clearly labeled as an estimate, not a quote.
- Prices from public records. When a vendor publishes no price list, we do not quote amounts from third parties: not from contract award notices, procurement approvals or council minutes, not from university pages, not from user reviews. Such figures depend on scope, volume and negotiation, and are easily read out of context. The profile says that public documents give price benchmarks and links to them, so readers can consult them at the source. When a vendor does publish its prices, amounts from public records can appear next to them, with the buyer, the period and the scope. The same rule applies to every vendor, whether or not it is a paid partner.
- Nothing is invented. If a fact can’t be verified, the fiche says it was not found or stays in draft rather than guessing.
- No dashes standing in for real editorial judgment, no vendor superlatives repeated as fact. Every verdict names a trade-off.
- Review platform figures say where they come from. TrustRadius and SelectScience pages are read directly. G2 and Capterra do not allow automated collection, so their ratings are quoted only from a dated manual reading or from the vendor, and labelled with that origin. For each platform, a profile says how many reviews we read, over which period, and how many the platform marks as incentivized, that is, solicited by the vendor or by the platform.
- No competitor content. Comparison articles published by vendors about their rivals are never used as sources.
Evidence files and the publication threshold
Profiles are moving to a stricter format, one vendor at a time. Each new or re-verified profile is backed by an evidence file that records every fact with its source, the date it was checked, the exact passage it rests on, and who published that source: the vendor itself, an independent publisher (a public buyer, a university, a trade publication) or a review platform.
- Threshold. A profile is published only when at least three distinct independent publishers back it, and at least one of them is about the product rather than the company. A review platform counts only when it lists at least three reviews. Rarely, the editor publishes a profile, short or full, backed by two independent publishers when no third can be found; such a page says so in a note at the top, gives the reason, and is revised when a third independent publisher is found.
- Two levels. A short profile sets out documented facts and what independent sources report, without an editorial verdict. A full profile adds a verdict, a fit assessment and a statement of how much independent material backs it, and is written only when the independent evidence is strong enough to support them.
- Nothing filled in by default. When a fact is not published (a price, an implementation time, a compliance mapping), the profile says it is not published, rather than estimating it.
- Checked at build time. The site will not build if a profile states something its evidence file does not support, such as a compliance level, a deployment option or a price.
Profiles that predate this format show their sources at the bottom of the page and will be brought into it in successive batches.
Where research starts, and where it doesn’t end
Some fiches on this site cover vendors also profiled on labsoftwareguide.com, a sister publication I also run. Where that overlap exists, the labsoftwareguide.com article is a starting point for research, never a source to copy: every fact here is independently re-verified against primary sources, re-dated, and restructured into this site’s format (structured data plus a short verdict, not long-form prose).
What we don’t do
- We don’t generate a comparison page for every possible pair of vendors. A
/compare/<a>-vs-<b>/page only exists where it’s been separately researched and written. - We don’t publish an aggregate star rating. Schema.org review markup with a numeric rating implies a kind of consumer-review precision this site doesn’t have, so it’s left out entirely.
- We don’t accept payment for a listing, a better position in a table, or a specific verdict. A vendor that pays for a partnership is labelled “Paid partner” wherever it appears, and its profile follows the same rules as every other. See About for how the site is funded and Legal notice for the use of trademarks and logos.
Keeping fiches current
Every fiche carries a lastVerified date. A published fiche that hasn’t been re-checked in over 12 months fails our build automatically, which means the live site would keep showing the older, still-current version rather than let a stale fiche pass silently. When something material changes (a compliance claim, a pricing model, a deployment option), the fiche is re-verified and the date updated, not just edited in place.
Corrections
If you’re a vendor or a reader and something here is inaccurate or out of date, see Contact. Corrections are reviewed against primary sources before anything changes.