Calibration fundamentals · Recordkeeping

Your spreadsheet is not a calibration system.

A spreadsheet is a sensible place to start an instrument register. It is inexpensive, familiar, and easy to sort. But a list that says what is due is not the same as a process that gets the work done and proves what happened afterward. Here are five ways the gap shows up, and how to tell whether your team needs more than a workbook.

1. A highlighted cell is not a reminder

A red due date only helps someone who opens the right workbook at the right time. Suppose a gage comes due next Tuesday and the scheduler is off that week. If nobody owns the reminder, the gage may still be in use on Wednesday. Adding an email rule helps, but the team still needs an owner, a backup, and a process for failures or holidays.

Test this without opening the sheet. Can the person responsible see what is due, acknowledge the work, and tell quality if the gage cannot be calibrated in time? A date calculation should support that handoff, not stand in for it.

2. Edit history is not necessarily an audit trail

Some shared spreadsheets have version history. That can be enough to undo a mistaken edit, but it may not be enough to attribute a change, preserve original results, and retrieve evidence after a workbook is copied, renamed, or archived. In a controlled process, an auditor or reviewer may need to understand what changed, who changed it, and how a correction was approved.

Pick one changed due date from last quarter. Can someone who did not make the edit show the old value, the new value, and the authorization for it? If the only explanation is a message in someone’s inbox, make that evidence part of the controlled record.

3. Tolerance formulas can fail quietly

A spreadsheet can calculate deviation correctly, but it does not automatically know which formula, unit, range, or decision rule applies. A copied formula may point to the tolerance from the preceding instrument. Rounding a displayed value before deciding conformity can change an outcome near a limit. A green cell with the wrong setup is more misleading than an obvious blank.

Test exactly at the boundary and just outside it, in both directions. Add a missing tolerance and a row in the wrong units. If the workbook still shows a pass, correct the logic and its review process before it informs an acceptance decision.

4. Two copies can tell opposite stories

A technician downloads the workbook for bench work. A colleague updates the shared version after a gage returns from service. The technician emails the local file back, and now two reasonable-looking copies disagree about whether the gage is due. A filename with a date is not enough to decide which update wins, particularly across shifts or sites.

Define one authoritative register and a method for late updates. Record when someone must verify against the source instead of relying on a printout. A spreadsheet can work for a tightly controlled team, but the overhead grows when each handoff depends on a person reconciling copies.

5. The auditor samples a record, not your spreadsheet layout

There is no universal auditor reaction to seeing a spreadsheet. The question is whether your records and controls meet the requirements that apply. If an assessor samples one accepted part, the team may need to show which instrument was used, its status on that date, and the supporting calibration evidence. A current due date in a neat register does not answer the historical question.

Run a dry run with one ordinary instrument and one exception. Ask someone new to the process to retrieve the evidence. Time the search and note anything they can only explain by memory. Those gaps tell you which controls to improve.

When to switch, and what to switch first

Keep a spreadsheet if it has a clear owner, protected formulas, reliable backups, and a small enough register that people can maintain the controls. Consider moving when missed recalls repeat, several people change records across sites, or retrieving approvals and certificates has become a recurring problem. Set a measurable goal, such as finding the correct asset and due date on any shift.

Start with one equipment group rather than a complete replacement. CaliberOS provides a searchable browser register and a hash-chained log for asset changes. It does not currently replace calibration event records, validated tolerance decisions, or certificate issuance. Keep your approved process for those functions while comparing the day-to-day lookup and schedule work.

FAQ

Frequently asked questions

Can a spreadsheet ever be acceptable for calibration records?

Yes, depending on the requirements and controls. A spreadsheet is not automatically unacceptable, and specialized software is not automatically compliant.

What is the first sign I need a dedicated system?

Start with recurring problems you can measure: missed recalls, duplicate updates, unclear approvals, or slow retrieval of a sample record.

Can I use the free due-date calculator with my spreadsheet?

Yes, as a local check for a group on a calendar-month schedule. It does not read or update your spreadsheet or replace an approved due date.

Does CaliberOS replace tolerance calculations today?

No. Use your approved methods and controls for measurement, uncertainty, and conformity decisions. The current register supports instrument lookup and scheduling records.

Try a register beyond the spreadsheet.

Join the free beta waitlist and start with a small, familiar group of instruments.

Join the waitlist