CRC ToolboxGuides

100% client-side & Zero-PHI:Data stays in your local browser storage. Client-side processing by design — avoids server-side PHI ingestion. No login required.

GuidesFor CRCs & CRAs

Why Kit Lots Expire Faster Than Expected — and How Sites Miss It

Apr 8, 2026GuideKit Expiration TrackerAdministrative reference · Zero-PHI examples only

kit expirationFIFOdestruction logCRA exportZero-PHI

How clinic closets lose track of approaching kit expirations, why the mango window matters, and how Kit Expiration Tracker keeps FIFO urgency visible without a shared spreadsheet.

The problem on the clinic floor

Kits do not expire on a schedule that matches your clinic calendar. A lot can sit quietly on the middle shelf for weeks, then land inside the 30–60 day window while everyone is buried in visit days. By the time someone notices, you are either pulling usable units out of rotation, writing a deviation note, or explaining to a CRA why the destruction log looks like it was rebuilt the night before.

Most sites still track this in a shared spreadsheet. That works until a typo lands in a lot number, two people edit different copies, or the “weekly review” slide becomes every other month. The failure mode is rarely malice — it is attention. Closet scans start with whatever is eye-level, not whatever expires soonest.

Utilization makes it worse. A lot that looked fine at 40 days can burn down faster than the calendar suggests if weekly use jumped after a protocol amendment or a cohort opened. Spreadsheets rarely show “days of supply left” next to the date, so the date alone feels calmer than the shelf really is.

Monitoring visits expose the gap. A CRA asks for current inventory by lot and expiration; the coordinator walks the closet with a clipboard and discovers a box that should have been quarantined two weeks ago. The scramble to reconcile physical stock against a stale sheet is exactly the kind of morning nobody plans for — and it is almost always preventable with a current urgency view.

Temp excursions and damaged seals add another layer. A lot may still show a future expiration on the label but is no longer usable. If the inventory tool does not reflect disposition status alongside the date, FIFO pulls can accidentally include stock that should sit in quarantine until the sponsor confirms destruction or replacement.

Practice context

Sponsors and monitors expect sites to know which lots are usable, quarantined, used, or destroyed — and to show that without inventing the story mid-visit. ICH E6-oriented site practice treats investigational product and supply accountability as an ongoing control, not a binder exercise before monitoring.

Expiration-driven waste and out-of-window kit use show up as protocol deviations or NTF language. The regulatory question is often simple: did the site have a current inventory view, or were they reconstructing from boxes and memory? A Zero-PHI lot list — kit labels, lots, quantities, expirations, utilization — is enough to answer that without subject identifiers.

Site SOPs typically define how often inventory is verified, who signs off, and how destruction is documented. The tool does not replace those procedures — it gives the team a FIFO-first board that matches what monitors ask for: earliest expiration among usable stock, clear counts, and an export trail that was not assembled under pressure.

Client-side storage fits the compliance boundary here. Kit logistics labels are not PHI when kept free of subject allocation. Keeping the board on the clinic workstation avoids putting lot lists in a shared cloud sheet with unclear access controls.

How to use Kit Expiration Tracker for this

Use Kit Expiration Tracker as the closet’s urgency board, not as another archive nobody opens. Treat the built-in bands the same way you would a color-coded shelf tag: past due and ≤7 days get touched first, mango window gets scheduled for use or destruction review, and OK lots stay in FIFO order behind them.

  1. Open Kit Expiration Tracker and paste a sponsor/CRO manifest, import a CSV, or add lots by hand (kit/supply name, lot/kit ID, qty, expiration, optional protocol and visit type). Leave subject IDs out — logistics labels only.
  2. Sort or scan by the built-in urgency bands: past due, ≤7 days, ≤30 days, the 30–60 day mango window, then OK. Start the physical closet walk with past due and ≤7d first — match what you see on the shelf to what the board shows before pulling for visits.
  3. When a unit is dispensed or destroyed, use Use 1 (or the destruction/export flows) so the row updates immediately — no confirmation theater that causes people to skip logging. If a lot drops to zero, the row should reflect that before end of day.
  4. Optional: set PAR (min stock) by kit name if low stock, not just expiration, is your reorder trigger. PAR alerts sit beside expiration urgency so reorder conversations happen before a visit type runs dry.
  5. Before a CRA visit, export the audit-ready destruction CSV and/or Export Session Backup (.json) so another clinic PC can pick up the same Zero-PHI workspace. Print or save the export with a date stamp so the binder matches what the screen showed during the walk.

The point is not a prettier spreadsheet. It is a FIFO-first view that makes the next expiring lot harder to ignore than the next email reminder. When the board and the closet agree before monitoring week, expiration stops being a surprise and becomes a scheduled decision.

Open Kit Expiration Tracker

All guidesFAQZero-PHI architecture

Administrative reference only. Browser-local tools — not a medical device, CDSS, or Part 11 system. Verify outputs against protocol SOPs and primary site records. Zero-PHI local mode: do not enter names, MRNs, DOBs, or subject IDs. Study / kit / lab / deviation / IP accountability / equipment / regulatory / visit drafts use this workstation's localStorage until you clear them. On shared clinic PCs, clear all local site data when finished.