Back from a Seville conference, I find my quercetin standard has been out of its stability window for two months. Reagent traceability, that black hole of academic labs.
I got back from Seville on a Sunday evening, suitcase full of printed handouts and my head still in the SEFIG conference sessions on triterpene saponins. Monday morning, 8:15 AM, I pushed open the door of my lab at Mohammed V University with the firm intention of resuming the measurement series I had left hanging ten days earlier on the saponin extract of Centaurium erythraea. Six calibration points to complete, a vanillin-sulfuric acid colorimetric assay to quantify total saponins as oleanolic acid equivalent, and a quercetin standard for the coupled antioxidant controls.
The aliquot that caught me
I opened my bench notebook to March 14th, the last entry before the conference. I reread my notes, pulled out my plates, set up the glassware under the fume hood. When I went to fetch the quercetin aliquot from the fridge, it jumped at me. The Sigma vial reference Q4951, opened on November 12th according to the yellowed post-it stuck on its side. The opening date was barely legible, written in a fine-tip marker that had bled after sitting too close to a sink. But you could still make out the "12/11" and the initials of an intern who had left the lab back in February.
The Sigma COA for this reference gives a stability window of two months after opening for stock solutions in DMSO, stored at -20°C, protected from light. We were on March 24th. Four months and twelve days since opening. More than double the window.
I set the aliquot down on the bench and stood there a good minute doing nothing. I mentally walked back through the last six measurement sessions. All of them used this vial as reference standard for the antioxidant calibration curve. Six points compromised. Not wrong in the sense that the numerical result doesn't exist, but wrong in the sense that I could no longer defend them in front of a reviewer paying any kind of attention.
Nadia confirms
Nadia, the lab technician, arrived at 9. She saw my face. I showed her the vial and the post-it. She sighed, went to get her own log, an A4 binder she has kept for eight years, where she theoretically records every opening of a sensitive reagent. She flipped to November. No trace of this particular opening. The intern had pulled the vial out of the fridge, opened it, slapped on the post-it, and walked away without writing anything in Nadia's binder.
"It happens twice a month," Nadia told me. "Interns don't know they're supposed to go through the binder. And even PhD students forget sometimes." She showed me three other vials in the same fridge with similar post-its. A gallic acid opened in January, nothing on paper anywhere else. A Trolox opened in February. A BHT whose post-it had fallen off.
I redid the series within the week, with a fresh quercetin vial Nadia pulled from central stock. Three days of work to redo. Not catastrophic, but three days nonetheless, plus the shame of having nearly submitted a manuscript with a calibration curve that did not hold.
The field that didn't exist in my app
That same evening, I opened my laptop and edited the protocol schema of PhytoNote. The version 0.8 I was using in March let you enter a lot number, but not an opening date. It was a gap I had downplayed because in my own sessions I noted openings in my notebook. Except that in the real life of a lab, several people touch the same vial, and one researcher's notebook does not follow the vial into the fridge.
I added three things to the protocol YAML. A mandatory opening_date field tied to the lot number, triggered on first use of a reagent in a series. A configurable stability_window_days field at protocol level, with a default value inherited from the COA when available. An automatic age calculation on each entry, comparing today's date against the opening date and blocking validation if the window is exceeded. The app then offers only one action: scan a new vial.
I pushed version 0.9 three weeks later, after testing it on my own series all through April. The field is soft by default on non-sensitive reagents, hard on reference standards. Configurable at the project level, not hardcoded.
Nadia migrates the whole fridge
I showed Nadia the new version in May. She spent two hours with me scanning, one by one, the 47 sensitive vials in her fridge, re-sticking clean post-its when the opening date was recoverable, and throwing out three vials nobody remembered. Since then, she manages every standard in the lab through PhytoNote. No more A4 binder. No more post-its. When a PhD student opens a new vial, they scan the barcode, the app asks for the opening date, and Nadia gets a notification in her dashboard.
She told me last week she had gained roughly three hours a week on that one task. Three hours, on a technician's salary at public university rates in Morocco, doesn't translate into dirhams you can pocket. It translates into three hours she can spend on something else. This week, she spent those three hours training a new intern on the Folin-Ciocalteu assay without running between two benches.
The black hole
This story made me realize something I had been seeing since the start of my PhD without wanting to see it. Reagent traceability is a black hole in most phytochemistry labs I have visited, whether on internship, at conferences, or during collaborations. We have expensive LIMS for hospitals and pharma. We have well-documented ISO protocols on paper. But on the actual bench of an academic lab in the Maghreb, or in Spain, or sometimes in France, traceability hangs on a post-it stuck to a vial and on the memory of an intern who left in February.
I do not know how many published papers rest on standards past their stability window. Nobody knows. And the community does not raise the question because the answer would be uncomfortable.
PhytoNote version 1.0 shipped in September 2025 with full standards management; the v1.0.1 released recently adds COA OCR so the vial opening date gets scanned automatically. I had in fact spotted this provenance gap earlier that year when a J. Ethnopharm. reviewer asked for my Trolox lots — that episode is told in the reviewer and post-it story. The product page is here. What about you — which fields are still missing from your bench notebook to make it hold up under audit?