Formulate

The schedule and the record — not the lab, and not a shelf-life prediction.

Tamats schedules a cosmetic stability study — conditions like accelerated, ambient, cold, freeze/thaw cycling and light exposure, each with its own timepoint checkpoints — and generates the concrete due dates for every reading up front. Each observation logs pH, viscosity and appearance against that timepoint, and is judged pass, fail or drift against the spec bounds you set, with drift computed from the trend across observed points rather than a single reading. Tamats does not run the testing itself: a lab or your own bench places the samples and takes the measurements, and there is no shelf-life prediction model behind any of it — the tool is the schedule and the record, not the chamber.

A stability study is mostly a bookkeeping problem wearing a chemistry problem's clothes: which sample sits in which chamber, when the next reading is due, whether last week's pH is trending toward the spec's edge before it actually breaches. The measuring itself has to happen on a real bench or in a real lab. What Tamats replaces is the spreadsheet that tracks all of it, and what it adds is a verdict computed from the readings rather than eyeballed.

What you do with it

A protocol, scheduled up front

Pick storage conditions and their checkpoint weeks and the whole schedule generates as concrete due dates in one pass — no manually maintained calendar of when each sample is next due.

Measured readings, logged per timepoint

Each due timepoint takes an observation — pH, viscosity, appearance — recorded against that exact scheduled point, so the study's history is the readings themselves, not a summary of them.

A computed verdict, not an eyeballed one

Each observation is judged pass, fail or drift against the spec bounds you configured; drift is an early-warning read on a value trending toward a bound before it actually crosses it, not itself a failure.

Overdue and next-due, always current

The study's status — what's overdue, what's next, how many readings are in versus scheduled — derives from the persisted timepoints and the current date, so a study never silently goes quiet.

What it computes over

• —The protocol's own storage conditions and checkpoint weeks, as configured
• —Measured pH, viscosity and appearance readings entered against each timepoint
• —The spec bounds you set for the study
• —The study's persisted timepoint schedule and due dates

Where it stops

• Tamats does not run the study. A lab or your own bench places the samples in the actual conditions and takes the actual measurements — this is the schedule and the record over that work, not a replacement for it.
• There is no shelf-life or expiry prediction model. A pass/fail/drift verdict describes one observed reading against your spec, not a forecast of when the product will fail.
• Drift detection needs several observed points in a series to call a trend honestly — with too few, it reports no drift rather than guessing from too little data.

Questions

Does Tamats run stability testing for me?

No — it schedules the protocol (which conditions, which weeks, when each reading is due) and holds the record of what was measured. A lab or your own bench places the samples and takes the actual pH, viscosity and appearance readings; Tamats never touches the physical product.

What does a 'drift' verdict mean?

An early warning: a reading is inside the spec bound but trending toward it across the observed points, computed as a simple slope over the series. It is not a failure — a fail verdict means a reading is already outside the bound; drift means it's heading there.

Can Tamats predict my product's shelf life?

No. There is no shelf-life or expiry prediction model in the product — the study tracks what was actually observed against the spec you set, and any conclusion about shelf life is yours, or your lab's, to draw from that record.