Receive a delivery
Four live figures on the first page: deliveries this month, lots awaiting sign-off, expiring in 30 days, to order. Each opens its list. Read from the logs every time, changing nothing.
LotWarden reads any supplier's scanned docket, checks every lot against your acceptance register, and writes the receipt into the controlled workbooks you already keep. Runs only on the PCs you nominate, from local disk or an encrypted USB stick. No AI. Never online. Every action hash‑chained.
| Item | Material | Lot | Expiry | Qty | Read |
|---|---|---|---|---|---|
| APTT Reagent 10 × 5 mL | 10446744 | 21430 | 03/2027 | 4 | ok |
| Multi-analyte Calibrator | 10393254 | 92815A | 11/2026 | 2 | verify |
| ALT Reagent 4 × 20 mL | 11097512 | 4A0388 | 08/2027 | · | pen mark |
| Lipid Control Level 2 | 03456781 | 7L114 | 05/2027 | 6 | ok |
| Freight & handling | · | · | · | · | non-stock |
Many new document tools send each scan to a cloud server and an AI model to be read. Every service it passes through is one more company holding your data, and one more place it can leak. LotWarden reads the docket on the PC in front of you, with the network switched off.
No generative AI, no language models, nothing that learns from your dockets.
Only loopback is allowed. An empty block log after a full day is the proof.
No sign-in, no cloud copy, no vendor holding your data. Nothing to breach but the PC itself.
Running it from a USB stick? Lose the stick, lose nothing. On any PC you haven't nominated it refuses to run, and its data stays encrypted.
Pull the network cable. Nothing changes. LotWarden was built for a PC that has never seen the network, so there is no online mode to fall back to and nothing to switch off. Prove it in ten minutes.
Every reagent, calibrator and control enters the laboratory through the same bench, and every assessment traces back to what was written there.
A docket's lines are transcribed into the log by hand, often at the end of a shift. One transposed digit in a lot number is a finding waiting for the next assessment.
Whether a lot has passed pre-acceptance testing lives in a separate register. The check happens if someone remembers to open it before the box hits the shelf.
When a recall lands, the trail runs through three workbooks, a paper docket and whoever was on shift that day. Reconstructing it takes hours nobody has.
LotWarden puts the check at the door and the record in the log, in one pass. The docket is read, every lot is judged, the worklist is written and the receipt lands in your own workbook before the trolley leaves the bench.
One delivery from drop to audit chain, on the generic edition with the network guard on the whole time. Silent, captioned, no sign-up to watch.
Captioned, no soundPrefer a live one? Book a walkthrough.
Four steps, each previewed before anything is written. The order is the order of the job.
Drop the scanned delivery note. The built-in offline OCR reads item, material number, description, lot, expiry and quantity. Sideways scans are turned upright; a second pass on a colour-stripped copy rescues quantities under pen and highlighter.
Every incoming lot is checked against the pre-acceptance (PAT) register and given a verdict: accepted, awaiting sign-off, in progress, rejected or not on register. Shared lot codes are matched by product and flagged.
New, rejected or untested lots go onto a ready-made investigation worklist, worst first, each with the action required and blank columns for outcome and initials. Stock expired on arrival goes to the top with a quarantine action.
Confirmed lines go into the department's own workbooks through Excel, exactly as staff would enter them: the right sheet, the right columns, a coloured comment, a delivery-note stamp and duplicate protection. A backup is taken first.
Nothing is guessed. Only clean, confident reads are pre-filled; everything else is left blank for a person to count. Only an operator-confirmed quantity is ever written to stock, and a value under ink is shown as a best-effort guess, never as fact.
One banner, one side menu, and a section for each thing stores staff, scientists and quality managers actually do with a delivery. See every section in detail.
Four live figures on the first page: deliveries this month, lots awaiting sign-off, expiring in 30 days, to order. Each opens its list. Read from the logs every time, changing nothing.
Not tied to one supplier. One clean docket teaches a new supplier's letterhead and columns; confirm with your initials and their paperwork reads automatically from then on.
What to order, use first and take off the shelf, forecast from the logs' own dates in use. Expiry reminders for the team calendar. Advisory only: it orders nothing.
Record lots put into use, days later if need be. Each is signed and dated in the log through Excel, with a backup first and refusals listed by reason.
A USB barcode scanner puts a lot into use in one scan. GS1 barcodes read as they are; any other label is taught once from one scan.
Every lot the logs have ever shown and what happened to it: received, put into use, removed, and by whom. Trace a recall in seconds, across departments.
Weekly queue, second checks, supervisor report, log transfers and supplier evaluations. Every sign-off is dated, initialled, and kept where it cannot be edited.
A presentation and a workbook of every record behind it for a NATA (ISO 15189) assessment or an ISO 9001 audit, built in a minute, each item mapped to its clause.
A runtime network guard loads before anything else and wraps the socket layer. Only loopback is permitted. Every blocked attempt is logged, so an empty log after a full workload is positive evidence of no call-home behaviour.
Only 127.0.0.1 connections are allowed. Any outbound attempt is refused at socket level and written to network_audit.log with a timestamp. The banner shows the guard running.
OCR is the bundled Tesseract engine, running locally and deterministically. No analytics, update checks or crash reporting. Delivery data is never transmitted anywhere.
Every action carries the Windows username, timestamp, release and a SHA-256 chain value over the record before it. Edit, insert or delete a line and the page reports the chain broken.
Dropped workbooks stay pristine in original_logs; every write lands in a working copy with a timestamped backup first. Macros are never executed, so validation rules survive untouched.
All 31 state-changing routes check the request origin and refuse anything foreign with a 403. Downloads and writes are confined by resolved path. Errors are structured JSON, never stack traces.
Logs, register, lot history, sign-offs and answer keys are locked on the drive and unlocked only while the app works. A second lock under BitLocker; the audit trail stays readable for inspection.
The IT acceptance checklist ships with the product. Every claim on this page can be demonstrated on the machine in front of you. Tick them as you go.
ISO 15189:2022 §6.6 and §7.11 shape what is recorded at reception and how the software itself is validated. Assessment and audit packs are built from those records without changing them.
Date, lot, expiry, quantity, supplier and delivery-note number written to the receiving department's log on every receipt. The receiver's initials are required.
Every lot cross-checked against the PAT register at the door, with a generated investigation worklist. Elsewhere, each new lot is flagged and confirmed before it is written, then verified at the bench.
Intact and cold-chain condition recorded per delivery and written to the logs' Condition column. Failures are highlighted in red and audit-logged.
Stock expired on arrival is quarantine-actioned first on the worklist; short-dated stock is flagged amber; expired lots on the shelf are listed for removal.
A validation dossier issued per build: intended use, risk controls, change control and a release check re-run for every issue, including a fictional-data regression suite.
Reading on fictional and real dockets, column detection, writes into copies, duplicates, pre-acceptance, routing, confinement and both guards, re-run before every dossier.
Generated from the build record, the executable's SHA-256 and the release results. If they disagree, it marks itself DRAFT.
Choose the visit and the dates, enter your initials, and the presentation and workbook are built with each item mapped to its clause.
A single self-contained folder that runs from the PC's local disk or, if you prefer, an encrypted USB stick, on a PC that has never seen the network. Microsoft Excel is the only thing it asks of the host.
A digitally signed file names the machines approved to run, checked without any server. Machine identity is a one-way SHA-256 hash; nothing identifying is stored or transmitted. Renewal notice from 30 days out, then 30 days' grace, then read-only. A lapsed licence never locks the laboratory out of its own records. Evaluation codes cover three months from first use.
A 20-minute screen-share on a video call. We read a docket, check it, write it to a copy of a log and show you the audit chain. The app never opens a connection during the call; only the call does.
LotWarden was designed and proven at a working receiving bench and is now raising seed capital to reach accredited laboratories more widely. Read the investor page, or choose Investor in the form to request the brief.