Methodology
This page describes how Clinical Research Data Management Guide researches, sources, verifies, and maintains information. Structured product data is still being assembled, so much of this page describes the standards that content will be held to as it is published — stated now so readers can hold us to them.
Sources, in order of preference
For factual claims about products, we prefer, in order:
- Primary vendor documentation — official product documentation, published specifications, release notes, and vendor statements, identified as such.
- Public documentation — publicly accessible materials such as knowledge bases, published contracts, validation documentation, and procurement records.
- Government and standards-body sources — regulatory guidance (FDA, EMA, OHRP), funding-agency requirements, and standards from bodies such as ICH, CDISC, and relevant professional societies.
- Reputable third-party sources — established publications, peer-reviewed literature, and researchers, cited by name.
Sourcing is claim-level, not page-level: individual facts carry source labels (vendor documentation, public source, third-party source) so readers can see where each piece of information came from.
Fact versus analysis
A vendor's claim about its own product is reported as a vendor claim. Our own assessment is labelled as Clinical Research Data Management Guide analysis. The two are never blended into a single unattributed statement.
Verification and review dates
Software changes constantly, which means information about it decays. Structured facts carry "last verified" or "last reviewed" dates so readers can judge freshness for themselves. An old verification date is a signal to double-check, and we treat it the same way. Where products are listed rather than assessed, ordering is alphabetical or by verification date — never by preference.
Pricing
Pricing appears only when the vendor publishes it or it can be supported by another documented source, and it carries the date it was verified. We do not estimate, extrapolate, or invent pricing. When reliable pricing is not available — common in this market — we say "Pricing not publicly disclosed" rather than guessing.
Capability assessments and comparisons
Capability assessments and product comparisons are built on a shared, published taxonomy of 53 capabilities applied uniformly to every product — including QuesGen, which is developed by our publisher. Comparison criteria are published before conclusions are drawn from them, and comparisons state what was and was not evaluated. Category labels describe what a product is designed to do; they are descriptive, never a ranking.
Uncertain information
When information cannot be verified to our standard, we either omit it or publish it clearly marked as unverified — never silently presented as fact. Absence of a capability claim is not evidence a capability is missing, and our content will avoid implying otherwise.
Corrections and vendor feedback
Errors get corrected, not quietly buried. When we correct a substantive error, the correction is applied promptly and materially affected content is annotated. Vendors and readers can report inaccuracies via the Contact page; vendor-submitted corrections and updates are welcome and are verified against documentation before publication, just like anything else.
What we don't do
We do not sell placement, rankings, scores, or editorial conclusions. Vendors cannot pay for inclusion, ranking, or favorable coverage — not competitors, and not QuesGen. And this publication provides educational information, not legal, regulatory, statistical, or compliance advice; decisions about specific studies belong with qualified professionals who know their context.
Note: See also the Editorial Policy for the principles governing what we publish, and the Disclosure page for who publishes this site.