Pharma & Bioanalytical
Every calibration curve, verified before it reaches a study report.
Built for bioanalytical CROs and pharma QC laboratories. WLTR shows every candidate model side by side, objectively identifies the best fit, and gives your team documented evidence that the regression and weighting you report are the right fit for your data.
Why labs switch to WLTR
Review every curve in a run at once, not one analyte at a time.
Chromatography data systems were built to acquire and process data, not to judge a calibration. WLTR does that job objectively, for every analyte, in one view.
- Your CDS shows one analyte at a time, on one small screen.
- Curves are checked by hand, analyte by analyte, often in a spreadsheet.
- The model is chosen by whoever processed the batch, often a junior analyst.
- QA directors sign off without an objective basis for the curve that was chosen.
- Every analyte and every candidate model on one screen, in the Calibration Intelligence dashboard, with multi-analyte visibility.
- Every curve is checked automatically, including back-calculated accuracy at the LLOQ.
- The best fit is determined objectively: same data, same answer, every time.
- QA directors review exceptions only, with one unified calculation behind every calibration.
Hours back every batch
Review by exception instead of one analyte at a time.
Peace of mind for QA
An objective, documented basis for every curve that is signed off.
Accurate data for sponsors
Results built on the best-fit calibration, not on habit.
More capacity, more revenue
Faster review frees analysts and QA to take on more work.
What is at stake
When bioanalytical data cannot be trusted, the studies are thrown out.
Since 2016, FDA has notified sponsors that certain studies conducted at five contract research organizations are unacceptable because of data integrity concerns. Sponsors were asked to repeat the affected studies at another site, and affected approved generics were rated BX, no longer recommended as automatically substitutable.
- 2016Semler ResearchStudies unacceptable
- 2021Synchron Research and Panexcell Clinical LabStudies unacceptable
- 2024Synapse LabsStudies unacceptable
- 2025Raptim ResearchIn vitro studies unacceptable
Source: FDA, Notifications on Data Integrity. Analysis: FDA data integrity actions against bioanalytical CROs.
The real problems
Six data integrity failures auditors find in bioanalytical labs.
None of them require bad intent. They happen when calibration decisions are made by hand, one analyte at a time, under deadline. Select a problem to see how WLTR closes it.
Processing until it passes
A failing curve is reprocessed, reintegrated or refit until it meets acceptance, and only the passing version is kept. Auditors call it testing into compliance.
Every candidate model, scored in one pass
WLTR evaluates every candidate model against the same acceptance criteria at once and keeps the full evaluation. There is no curve to shop for and no failed attempt to hide.
Standards excluded without a reason
A low standard is dropped to rescue a curve, with no documented justification. ICH M10 expects every exclusion to have a documented, justified cause.
Every exclusion is logged
Each exclusion is recorded with the user who made it and the reason given, and it travels with the record into QA approval.
The model changes after the data is in
The regression model or weighting set during validation is switched after results are seen, because the new one passes.
Methods frozen once results exist
Method configurations are frozen once results exist, so the model cannot quietly change and historical results never shift.
Spreadsheets and retyped numbers
Calibration data is copied into Excel for checks and calculations, outside any audit trail, where one transcription error can change a result.
Raw exports, hashed at upload
WLTR reads the raw instrument export directly and records a SHA-256 hash of the original file. Nothing is retyped.
Actions nobody can attribute
Shared logins and generic accounts make it impossible to say who processed, changed or approved a calibration.
Named users and separated roles
Named users, role-based access and role-separated sign-off mean every action and every approval belongs to a named person.
Audit trails nobody reviews
The data system keeps an audit trail, but reviewing it line by line for every run is impractical, so it is rarely done.
Review by exception
WLTR surfaces the exceptions QA needs to see and attaches a complete trail from export to approval to every record.
What WLTR adds to your data
Your CDS calculates a curve. WLTR shows whether it is the right one.
A passing r² does not prove a model is correct across a wide dynamic range. WLTR independently evaluates your calibration standards, ranks how well each established model describes the concentration response, and documents the result for every run and analyte.
Regression and weighting, justified with evidence
ICH M10 expects the regression model, weighting scheme, and transformation to be determined during validation and governed by written procedures. WLTR evaluates the candidate calibration models side by side, so your choice is supported by data rather than habit.
See the bias a strong r² can hide
WLTR checks every calibration level, including back-calculated accuracy at every level. Bias at the LLOQ and ULOQ surfaces before it reaches a concentration-time profile or a study report.
Consistency across runs, instruments, and analytes
Trend calibration performance across batches, instruments, and sites. Spot drift and recurring failures early, before they turn into rejected runs, reassays, or ISR investigations. Multi-analyte oversight
A record built for sponsors and auditors
Every evaluation is documented and reproducible, giving QA, study directors, and sponsors a clear answer when they ask why a model and weighting were used. Audit defensibility
See it for yourself
Same eight standards. Three models. Three different answers.
Switch the regression model and watch what happens to back-calculated accuracy. The unweighted linear fit posts an r² above 0.998 and still fails at the low end. This is the gap WLTR is built to close.
Inside WLTR
From raw export to a defensible record.
Step 01
Export from your CDS, upload the run.
Drop in the calibration export from your chromatography data system. WLTR parses the run, maps analytes, and confirms the instrument and method context. Nothing in your validated acquisition or processing changes.

Step 02
Every analyte, every model, side by side.
WLTR fits each analyte against the candidate calibration models and plots back-calculated accuracy by level, so curvature and low-end bias are visible at a glance.

Step 03
A ranked, documented recommendation.
All 15 acceptance criteria roll up into a ranked model comparison with a clear recommendation and the evidence behind it, ready for data review.

Step 04
See the whole lab, not one run.
Trend calibration performance across runs, instruments, and analytes, and spot recurring failures before they become reassays or ISR investigations.

WLTR complements your validated workflow. It does not replace your CDS, your LIMS, or your method validation. The WLTR methodology is patented (US 12,038,448 B2).
Where calibration risk hides
The calibration problems bioanalytical labs live with.
Weighting set once, never revisited
A 1/x² weighting chosen at validation may not suit a new matrix, a new instrument, or a method transferred from another site.
Wide dynamic ranges
Over three or four orders of magnitude, the correlation coefficient is dominated by the high standards while accuracy at the low end erodes.
Calibrators excluded to pass
Dropping standards within the 75% rule can keep a run acceptable, but a recurring pattern of exclusions usually points to a model problem.
Response nonlinearity
Ion suppression, matrix effects, and detector saturation bend LC-MS/MS response curves in ways a linear fit does not capture.
ISR and reassay investigations
When incurred sample reanalysis fails or reassays pile up, calibration fit is one of the first places investigators look.
Method transfer between sites
The same validated method can behave differently in a receiving laboratory. Comparable calibration evidence makes transfer defensible.
How it works
Three steps. No change to your validated method.
-
Export
Export calibration data from your chromatography data system for the runs you want verified.
-
Evaluate
WLTR fits your standards against the candidate calibration models, scores each one, and ranks model performance.
-
Review and document
Analysts, data reviewers, and QA receive a clear verification result per run and analyte, ready for data review, study files, and audits.
Regulatory alignment
Built around the expectations you already work to.
| Framework | What it expects | How WLTR supports it |
|---|---|---|
| ICH M10, Bioanalytical Method Validation and Study Sample Analysis (FDA guidance, November 2022) | At least six calibration levels including the LLOQ and ULOQ. Back-calculated concentrations within ±15% of nominal, ±20% at the LLOQ, for at least 75% of standards. Regression model and weighting determined during validation under written procedures. | Side-by-side model comparison and back-calculated accuracy review that support your model and weighting justification. |
| 21 CFR Part 58, Good Laboratory Practice | Nonclinical study data that is complete, accurate, and reconstructable. | A reproducible calibration evaluation that can be filed with the run and the study record. |
| 21 CFR 211.160 and 211.194, GMP laboratory controls and records | Scientifically sound standards and test procedures, with complete records of calculations and test data. | Independent verification evidence for second-person data review and batch record review. |
| 21 CFR Part 11 and ALCOA+ data integrity principles | Electronic records that are attributable, accurate, complete, and consistent. | An independent check of results produced by your CDS, without altering source data. |
Who it is for
Built for the people who sign off on the data.
- Bioanalytical laboratory directors
- Study directors and principal investigators
- QA managers and QAU auditors
- Method development and validation scientists
- LC-MS/MS analysts
- Data reviewers
- Sponsor quality oversight
Founding pilot · Standard operating procedure
How a founding pilot runs in a bioanalytical lab.
Written the way your own SOPs are: who owns each step, when it happens and how you know it is done. It is the same procedure we follow with every founding lab.
When you finish, you will haveEvery calibration in scope verified beside your current review and approved in WLTR by your QA lead, a look back at what a second check would have flagged in your recent runs, and a co-authored outcome study built from your own numbers.
- 01
Apply and confirm fit.
Your labAbout five minutes
Tell us your LC-MS/MS instruments, data system, calibration workload, the programs you work to, such as GLP and ICH M10, and who signs off. We accept or decline in writing.
Done whenYou have a written decision and, if accepted, a kickoff date within fourteen days.
- 02
Scope the pilot together.
WLTRYour labWithin five business days of acceptance · 60 minutes
A working session with your QA lead and an analyst lead. We run a representative export from your data system through WLTR together, agree the methods in scope and write down what the pilot must show, measured from your own figures.
Done whenThe success criteria are written and agreed by your QA lead.
- 03
Share data under NDA.
Your labBefore kickoff
Raw calibration exports go to one NDA data location that WLTR names. Nothing by email or chat, and nothing retyped, so the record starts clean.
Done whenThe first data set is in the NDA location.
- 04
Configure to your validated method.
WLTRKickoff to go-live
We set up your instruments, methods, acceptance criteria and roles with you, to your validated method and SOPs, including ICH M10 limits where they apply. Each gate, from method inventory through validation, acceptance and training, is a record your QA lead signs before the next one starts.
Done whenEvery gate record is signed and your first real run has been processed in WLTR.
- 05
Look back at recent runs.
WLTRYour labRight after go-live
Where your data system can export them, the last six to twelve months of calibrations for the methods in scope run through WLTR. You see what a second check would have flagged and the review time it represents. It stays under NDA, is never framed as a finding against your lab, and your QA lead decides what to do with it.
Done whenYour QA lead has reviewed the first evidence pack.
- 06
Run beside your current review.
Your labGo-live to the outcome study · thirty minutes with us every two weeks
Your analysts keep reviewing as they do today, and every calibration in scope also runs through WLTR. Your QA lead approves in WLTR with a named signature, and your current process stays the official record until you decide otherwise. A midpoint review decides whether to keep, fix or expand the scope.
Done whenEvery calibration in scope has a WLTR record and a QA approval.
- 07
Write the outcome study and decide.
WLTRYour labEnd of the run
We draft the outcome study from your pilot’s own numbers and review it with your team. The decision is yours, with no obligation to convert, and founding pricing is locked if you do. Nothing is published without your permission, anonymized if you prefer.
Done whenThe co-authored study is complete and your decision is recorded.
Never
- Ask you to change your validated method, your data system or a reported result.
- Take data by email or chat, or retype a value.
- Call a result compliant or guaranteed. We state what WLTR checked and what your QA lead approved.
- Publish anything without your written permission.
Done when
- Every calibration in scope has a WLTR record and a QA approval.
- Your QA lead has reviewed the look-back and the outcome study.
- Your decision is recorded, with founding pricing locked if you convert.
Read the founding pilot program →Limited to five laboratories · No obligation to convert
Questions
Frequently asked questions
Does WLTR replace our CDS or LIMS?
No. Your chromatography data system keeps running as it does today, and your LIMS continues to manage samples and reporting. WLTR is a verification layer that evaluates the calibration data your CDS already produces.
Do we need to change or revalidate our bioanalytical methods to use WLTR?
WLTR works from calibration data you export after a run. It does not change acquisition, integration, or processing in your validated method. How WLTR results are referenced in your SOPs is decided by your quality system.
Which techniques does WLTR support?
WLTR is built for quantitative methods that report against a calibration curve, including LC-MS/MS, HPLC, and UPLC assays used in bioanalysis, pharmacokinetic and toxicokinetic studies, and QC release testing.
How does WLTR help a CRO during sponsor audits and regulatory inspections?
WLTR gives your team a documented, reproducible evaluation of each calibration curve, including how the reported model compares with alternatives and how accurately each standard back-calculates. That record supports the questions sponsors and auditors ask about model selection and weighting.
How do we get started?
Apply to the WLTR Pilot Program or request a demo. We will walk through your workflow and show how WLTR evaluates calibration data from your own runs.
Pilot program
See what WLTR finds in your calibration data.
Bring a recent run. We will show you how your reported curve compares with the best-fit model, analyte by analyte.
References: ICH M10 Bioanalytical Method Validation and Study Sample Analysis (FDA) · 21 CFR Part 58 · 21 CFR Part 211