What the Calibration Due-Date Calculator does
This builds a calibration register from a list of instruments: last calibration date, interval in months, and the due date that follows. It sorts by urgency, flags what is overdue and what falls inside your due-soon window, and exports the register as CSV or as a calendar file so the recall dates land in a diary rather than in somebody's memory.
The date arithmetic is done properly. An instrument calibrated on 31 January with a one-month interval is due on 28 February, not on a date that does not exist, and the calculation uses calendar dates rather than timestamps so no time zone can move a due date by a day.
Everything runs in your browser. The register stays in the tab.
How to use it
- Enter one instrument per line: identifier, description, last calibration date as YYYY-MM-DD, interval in whole months, and optionally the owner and location.
- Set the date the register is being run as - normally today, but back-dating it is how you answer 'what was overdue when this batch was made?'.
- Set the due-soon window. Thirty days is the usual default; make it longer if your calibration house has a long lead time or if instruments have to be shipped.
- Read the overdue list first, then the next-due item. Book the slot before the due date rather than on it.
- Export the CSV for the quality system, or download the .ics file and import it into a calendar to get the recall dates in front of the right people.
Reading the results
The due date is the last calibration plus the interval, which is the common convention. Some quality systems push it to the end of that month instead, so check yours before treating a date as authoritative.
Days remaining is negative when the instrument is overdue, and the register sorts by that number so the worst case is at the top.
An overdue instrument is not just a scheduling problem. Every measurement it has taken since the due date is unverified, which is why a quality system asks what those readings were used for before the instrument simply goes back into service.
The following due date column shows where the next interval would land, which is useful when deciding whether to pull a calibration forward so several instruments travel together.
Worked example: a workshop register run on 20 September 2026
A Fluke 87V was last calibrated on 31 January 2026 with a 12-month interval, so it is due 31 January 2027 - comfortably in date. Change that interval to one month and the due date becomes 28 February 2026, because 31 February does not exist; on 20 September it would be 204 days overdue.
A test pressure gauge calibrated on 1 October 2025 with a 12-month interval is due on 1 October 2026: 11 days away, inside a 30-day window, so it is flagged due soon.
A torque wrench calibrated on 15 April 2026 with a six-month interval is due on 15 October 2026 - 25 days away, also inside the window.
An insulation tester calibrated on 1 March 2026 with a 12-month interval is due 1 March 2027 and is not flagged at all.
The register therefore shows two instruments to book this month and nothing overdue. The gauge and the wrench are due within a fortnight of each other, so sending them together is one collection rather than two.
Formulas and scoring rules
- Due date
due = last calibration + interval monthsMonth arithmetic clamps to the end of the month: 31 January plus one month is 28 February, or 29 February in a leap year.- Days remaining
days = due date - the date the register is runNegative means overdue. Calendar dates are compared as whole days, so time zones cannot shift the answer.- Status
overdue if days < 0; due-soon if days <= warning window; otherwise in date- Following due date
next = due date + interval monthsWhere the next interval lands if the instrument is calibrated exactly on its due date.
Where calibration intervals come from
A twelve-month interval is a convention, not a requirement. ISO/IEC 17025 expects the interval to be justified and reviewed, and the justification comes from the instrument's own history: if a meter has come back in tolerance five years running, the interval is probably too short, and if it drifts out every time, it is too long or the instrument is worn.
The factors that shorten an interval are the ones people skip: how hard the instrument is used, whether it goes in a van, what happens if it is wrong, and whether it has been dropped. A torque wrench living in a toolstore and a torque wrench living on a truck deserve different intervals even if they are the same model.
When an instrument comes back out of tolerance, the interval is not the only thing to change. The question the quality system asks is what was measured with it since the last calibration, and whether any of that needs revisiting.
The recall problem
Most calibration failures are not technical. An instrument goes out for calibration and nobody notices it is back; a van kit is never on site when the collection happens; a spare meter in a drawer has been out of calibration for three years because it is not on any list.
Two practical defences. Put the due date on the instrument itself, so anybody picking it up can see it, and keep the register complete rather than convenient - including the instruments that are rarely used, because those are exactly the ones that drift out unnoticed. The calendar export here exists so the recall date sits somewhere that nags, rather than in a spreadsheet nobody opens.
Limitations: what the result does not prove
- It calculates dates from the interval you give it. It has no view on whether that interval is appropriate, which is an ISO/IEC 17025 question about the instrument's history, use and consequence of error.
- Some quality systems set the due date to the end of the due month, or run intervals from the certificate date rather than the measurement date. Check which convention yours uses before treating a date here as authoritative.
- It does not know whether an instrument passed. An in-date instrument that failed its last check is still in date on this register and still unusable.
- It is a planning aid, not a calibration record. The record is the certificate, with its traceability, uncertainty and as-found condition.
Privacy: where your data goes
Everything you paste, type or drop is processed in this browser tab. It is not uploaded, logged, stored or sent to analytics. Session recording and tag-manager scripts are switched off on this page.
Standards and sources
- ISO/IEC 17025 - Requirements for testing and calibration laboratories - checked 19 Sep 2026
- NIST Technical Note 1297 - Guidelines for evaluating and expressing measurement uncertainty
- RFC 5545 - Internet Calendaring and Scheduling Core Object Specification (iCalendar)
Frequently asked questions
How do I calculate a calibration due date?
Add the interval to the last calibration date. The only subtlety is month-end: 31 January plus one month is 28 February, and plus three months is 30 April, because the day of month clamps to the length of the target month. This page handles that rather than producing an impossible date.
How often should instruments be calibrated?
Twelve months is the common default, but the interval should be justified from the instrument's history, how hard it is used and what a wrong reading would cost. ISO/IEC 17025 expects intervals to be reviewed rather than inherited, and a meter that is always in tolerance is a candidate for a longer one.
What happens if an instrument is used after its due date?
Every measurement taken since the due date is unverified. Quality systems normally require an impact assessment: what was measured, what decisions were based on it, and whether any of that work needs revisiting. It is not simply a matter of sending the instrument off late.
Should the due date be the anniversary or the end of that month?
Either, as long as you are consistent and it is written down. The anniversary is what this page calculates. End-of-month is popular because it makes scheduling easier, at the cost of a few extra days of interval each cycle.
Do I need to calibrate every instrument?
Only those whose readings affect a decision - product acceptance, safety, a certificate. Instruments used purely for indication are often designated as such and checked rather than calibrated. The important part is that the designation is deliberate and recorded, not that an instrument quietly fell off the list.
What is the difference between calibration and verification?
Calibration measures the instrument against a traceable standard and reports the deviation, with an uncertainty. Verification checks that the deviation is within a stated tolerance and produces a pass or fail. A calibration certificate can therefore be perfectly useful even when the instrument is out of tolerance, because it tells you by how much.
Can I import these dates into a calendar?
Yes. The .ics download creates one all-day event per instrument on its due date, which any calendar application will import. The file is generated in your browser and is not sent anywhere.
How do I decide whether to extend an interval?
Look at the as-found condition over several cycles. If the instrument has been well inside tolerance every time and the consequence of a wrong reading is low, extending is defensible and should be recorded with that reasoning. If it has ever come back out of tolerance, shortening it is the usual response.
Last reviewed by the A2Z.Tools team against the sources listed above.
