StabilityProofOpen the calculator

Preparing your stability data

Paste or drop the table you already have. It does not need to be cleaned first: units, condition formats, <LOQ results and drifting RRTs are handled automatically, and every decision is listed in the data log.

Download the template (CSV)

The usual layout

One row per sample, one column per result:

BatchTime (days)ConditionRRT 0.45RRT 0.82Assay (%LC)
AInitialInitial<0.050.02100.2
A750°C/75%RH0.080.0499.9
A270°C/75%RH0.140.0799.4

The values above are made up to show the format.

One row per result (LIMS exports)

Most LIMS export one row per result instead. Paste that as it is; it is recognised and reshaped automatically:

BatchConditionTime pointTestAnalyteResultUnits
A50°C/75%RHDay 7Related substancesRRT 0.450.08% area
A50°C/75%RHDay 7Related substancesRRT 0.820.04% area
A50°C/75%RHDay 7AssayAssay99.9% LC
A50°C/75%RHDay 7Water (KF)Water2.1% w/w

Everything set aside is listed in the data log, so you can check nothing was missed.

Columns that are recognised

ColumnWhat works
TimeNumbers with the unit in the header: hours, days, weeks, months or years ("Time (weeks)", "Days"), or in the cell: "3M", "M3", "3 months", "Week 2", "T3". "Initial", "T0" and "0" mark the starting point.
ConditionOne column such as 50°C/75%RH, 50/75 or 50C 75% RH, or separate temperature and humidity columns. Kelvin and humidity as a fraction (0.75) are converted, tolerances (25 ± 2 °C) are ignored, and a range such as 2–8 °C is read as its midpoint, 5 °C.
DegradantsOne column per peak, headed by RRT or name ("RRT 0.82", "Imp B"). Footnote marks (0.21*) and comments in brackets (0.12 (OOS)) are ignored. Text that is not a result, such as "NR" or "see note", is read as no result and listed in the data log. Peaks within ±0.02 RRT that never appear in the same sample are treated as one degradant.
AssayOptional. Used to model assay loss from the initial value against the lower limit.
Total degradantsOptional. If missing, the total is the sum of the reported peaks, leaving out peaks seen only under harsh stress.
Statistics and partial totalsColumns such as "Assay RSD", "Total unspecified" and "Largest unknown" are left out, so they are never modelled as results.
One row per resultInstead of one column per peak: a peak name (or RRT) column and a result column, optionally with test name, batch and units. See above.

Workbooks laid out for people

Titles and product details above the table, a heading such as "Impurities (%)" over a second header row of peak names, units in a row of their own, and a condition written once and merged down its block of rows are all read. Cells formatted as percentages in Excel are read as shown (0.12%, not 0.0012). Blank cells filled from the row above are listed in the data log, and row numbers in the log match the rows in Excel.

Results below the limit

<LOQ, ND, <0.05, ND (<0.05), BLOQ and blank cells in samples where other peaks were reported are all accepted. By default they are treated as known to be below the limit (statistically censored), which avoids the bias of replacing them with zero or half the limit. You can choose either of those instead.

Study design that predicts well

The tool checks these for every degradant and says when the design limits what can be concluded.

Excel workbooks

.xlsx files are read in your browser. If the workbook has several sheets with data, you choose which one to use. Old .xls files need saving as .xlsx or CSV first, or you can copy the table and paste it.

Checking the prediction with real-time data

Include long-term or intermediate results (for example 25 °C/60 %RH at 3, 6 and 12 months) in the same table. On the settings page they are ticked under Real-time data, which leaves them out of the fit and uses them only to check the prediction. This happens automatically for conditions at 30 °C and below when three or more hotter temperatures are left to fit. Each result is compared with the 95% prediction interval for a single new measurement, which covers both the uncertainty in the fit and the scatter between measurements. The results page, the report and the Results JSON show which results fall within it. Expect about one result in twenty to fall outside by chance; several outside, or a trend, means the accelerated model does not describe long-term storage well. Untick a condition to fit it with the rest.

Adding later results

When new pulls come in (the 6- or 12-month real-time results, say), reopen the saved analysis and choose Add results on the results page. Paste the new rows with their header row, or drop a file. Columns are matched by heading, so they can be in a different order. A peak seen for the first time becomes a new column, read as below the reporting threshold in the earlier samples. Rows already in the table are skipped, so you can drop the whole updated table. Existing rows keep their numbers, so excluded points and locked models still apply. The data log and the report record when the results were added and from where. Save the analysis again afterwards.

Seeing the data used

Open Data used on the results page to see the table the models were fitted to: merged RRTs as one column, blanks filled in as below the reporting threshold, and the total and assay loss as modelled. Each result is coloured by its use: fitted, possible outlier, real-time check (within or outside the prediction), excluded by you, or in a response that was not modelled. The settings page shows every row of your table, with the rows held out for the real-time check highlighted. The data used can also be downloaded as CSV.

Saving and reopening an analysis

Save results › Analysis file downloads a .json file holding your data, column choices, settings, limits, locked models and excluded points. To carry on later, open the calculator and choose Open saved analysis, or drop the file on the first page. The file carries a fingerprint of the data, so a file whose data was edited is refused. It is not the same as the Results JSON below, which is for other software and can't be reopened.

Results as data (JSON)

Save results › Results JSON downloads every result in a structured file you can load into a database, a notebook or your own models. For each degradant, the total and the assay it holds:

The file also carries the settings, the data fingerprint, the engine version and the study details you entered (product, active ingredient, dosage form, packaging, batch). Shelf lives beyond 10 years are written as null with beyondHorizon: true. Field names stay the same within a schemaVersion, so files from different studies can be combined.