Calibration reminders that actually fire
Escalating alerts at 30 days, 14 days, 7 days and on the due day, then weekly until someone acts. Every send is logged, and you can send yourself a test alert before you have to trust it.
The short version
A recall system has one job: no instrument slips past its due date unseen. Gaugelog runs recall as an escalation ladder, with email digests at 30, 14 and 7 days before due and on the due day itself, then weekly for as long as an instrument sits overdue. Sends are grouped into one digest per recipient, never one email per instrument, and every delivery is written to a log with recipient, time and status, so the claim that a warning went out is checkable, not folklore. There is also a test button, because a recall system you have never seen fire is a rumor. Details checked 11 July 2026.
How the recall workflow runs
Recall is the part of calibration management that must work unattended. Here is the machinery, step by step.
Escalation before the due date
Alerts fire at 30, 14 and 7 days before due and on the due day itself. The thresholds are configurable per account; those are the defaults. Four chances before a gauge can fall overdue, each one closer and harder to ignore.
Escalation after the due date
An overdue instrument does not fall silent. It moves to the top of the digest and repeats weekly by default, daily or monthly if you choose, until a calibration is logged. Retired and lost instruments are the only ones that never fire.
One digest, not an inbox flood
Everything due lands in one email per recipient, grouped into overdue, due today and upcoming. Recipients are set per account and per instrument, and an instrument's assignee is included automatically. An alert system people mute has already failed; the digest is built to be read.
The delivery log
Every send is recorded: recipient, subject, time, delivery status and which instruments were in the digest. Failed sends are logged too, with their status. When someone asks whether the warning went out before the miss, you answer from the log.
The test button
Settings has a button that emails you a real digest immediately: everything currently due or overdue, or an explicit all-clear if nothing is. Press it on day one. A recall system you have never seen fire is not yet a system.
Why a ladder, not a single reminder
One reminder is a coin toss: it lands during vacation, gets buried, and the next anyone hears of the gauge is the audit. A ladder fails differently. Four alerts before the due date and a weekly drumbeat after it mean that missing a calibration takes sustained inattention, not one bad week.
If it was sent, you can prove it was sent
Reminder systems usually fail silently: the address was wrong, the job stopped running, and nobody noticed for a quarter. Gaugelog writes every send to the delivery log, including the failures, and the log sits in Settings where anyone can read it. Silence has to explain itself.
Batching that never skips
If you set a weekly digest cadence, thresholds that cross mid-week fold into the next send day. Nothing is dropped for arriving at the wrong time; it is batched. The rule: every instrument that crossed a threshold appears in the next digest, every time.
What Gaugelog doesn’t do
- Email only. There is no SMS or phone push, and we will not pretend a notification channel exists before it does.
- Alerts get people to act; they cannot act for anyone. If nobody owns the due list, no cadence fixes that.
- Under roughly 150 instruments, a well-kept spreadsheet plus calendar discipline can work; the free calibration log template is the honest place to start.
What your auditor sees
Overdue gauges are the first thing an auditor checks. When they ask, you answer with documents, not promises. Both samples below are generated by Gaugelog from fictional data.
Weighing it against another tool?
Shops shopping for recall usually arrive from GAGEtrak. The comparison covers licensing, platform and fees, dated and sourced, and says where GAGEtrak wins.
Gaugelog vs GAGEtrakQuestions, straight answers
What is a calibration recall system?
The machinery that calls instruments back for calibration before they fall overdue: due dates per instrument, escalating alerts as the date approaches, repetition while overdue, and a record of what was sent. Recall here means calling gauges in for service; it is unrelated to a product recall.
What are the alert thresholds?
By default, 30, 14 and 7 days before the due date and the due day itself, then weekly while overdue. Both sides are configurable per account: the pre-due steps, the digest cadence (daily, weekly or monthly) and the overdue repetition.
Who receives the alerts?
Account-level recipients you configure, plus optional extra recipients per instrument, plus the instrument's assignee. Each person gets one digest covering everything relevant to them, grouped into overdue, due today and upcoming.
How do I know the alerts actually work?
Press the test button in Settings. It emails you a real digest immediately, marked as a test in the subject and in the delivery log, with an explicit all-clear if nothing is due. Do it before you trust the system, not after.
What happens if a send fails?
The failure is written to the delivery log with its status rather than vanishing. The log keeps recipient, subject, time and which instruments were covered, newest first, in Settings.
Weighing your options before the audit?
Gaugelog is in development and launches in 2026. Until then you can generate a clean calibration certificate PDF with our free tool, no account needed, and compare the plans on the pricing page.