# Axiospec > Axiospec is cloud calibration management software from CaliTech LLC for manufacturers and calibration labs working under ISO 9001, ISO/IEC 17025, AS9100, ISO 13485, IATF 16949, and related quality standards. It tracks instruments and gages, records as-found/as-left calibrations with automatic pass/fail, issues certificates, and keeps a tamper-evident hash-chained audit trail. There is a genuinely usable free plan (50 instruments, unlimited users, full platform) and every new workspace runs at full capacity for its first 45 days. Everything linked below is free to read or use with no signup and no email gate. Key facts: flat published pricing (Free, then $59, $129, $229 per month); unlimited users on every plan; no per-gigabyte storage fees; native iOS and Android apps with offline capture and QR scanning on every plan including free; self-serve CSV/Excel import that reads GAGEtrak and GAGEpack exports; built-in AIAG MSA studies (Gage R&R, bias, linearity, attribute agreement) and per-instrument uncertainty budgets. The free plan is permanent, not a trial. It covers 50 instruments with unlimited users and the full platform, including the mobile apps, certificates, and the audit trail. No credit card is required to start and nothing expires at the end of the 45-day full-capacity window; the workspace simply settles onto the free plan if it is under 50 instruments. This file is the full text of every Axiospec guide, concatenated. It is the companion to /llms.txt, which is the link index. Everything below is published at the URL shown under each title. --- ## Switching to Axiospec from Spreadsheets or Legacy Calibration Software https://axiospec.com/guides/switching-to-axiospec Last updated: 2026-08-17 What actually moves when you switch: your instrument registry and calibration history come over by import or free white-glove migration, your auditor sees tamper-evident records from day one, and the price is one flat number per workspace. This guide walks the whole path, including how you leave if you ever want to. Most shops that come to Axiospec are not starting from zero. They are leaving a spreadsheet that got too big, or a desktop package like GAGEtrak or GAGEpack that the one person who understood it no longer maintains. Switching calibration systems feels risky because the records are audit-critical. This guide answers the four questions a quality manager actually has: how the data comes over, what the auditor will see, what it costs, and how you get your data back out if you ever leave. ### What switching actually involves The whole move is three steps. First, your instrument list and calibration history come in from CSV or Excel, or from a GAGEtrak or GAGEpack export. Second, you verify the imported registry against your current list, with due dates and statuses computed for every instrument. Third, you cut over: new calibrations get logged in Axiospec and the old system goes read-only. For a typical registry of a few hundred instruments the import takes an afternoon, not a project plan. There is no installation, no server, and nothing for IT to maintain. 1. Export your current list (CSV or Excel from a spreadsheet, or the export from GAGEtrak or GAGEpack). 2. Import it. Columns are mapped for you, imperfect data comes in with warnings instead of failures, and history lands as real ledger entries. 3. Verify the registry and due dates against your old system, then start logging new calibrations in Axiospec. Tip: If you would rather hand it over, the team migrates your data for free. Send the export, get back a populated workspace to review. ### Your history comes over as real records Imported calibration history is not a flat attachment. Each historical calibration becomes a ledger entry on the instrument, so reverse traceability, due-date computation, and the audit trail work across your old data as well as your new entries. That matters at audit time. An assessor who asks for the last three calibrations on a gauge gets them in one place, even if two of the three happened before you switched. See also: How the import works, step by step (https://axiospec.com/guides/importing-your-registry) See also: Migrating calibration data: the full guide (https://axiospec.com/guides/how-to-migrate-calibration-data) ### What your auditor sees Every calibration in Axiospec is written to a tamper-evident, hash-chained ledger with timestamps, attribution, and bound e-signatures. As-found and as-left readings post an automatic out-of-tolerance check. When an instrument is found out of tolerance, you can trace a drifted reference standard to every calibration it stood behind to assess validity. For the audit itself, you export a complete audit pack for one instrument or your whole registry from the Audit Center, and certificates carry the fields your chosen standard requires. Axiospec documents your calibration program and keeps it audit-ready. It does not certify or guarantee compliance. That determination stays with your auditor and your own processes, which is exactly how an assessor expects the tooling to behave. See also: How Axiospec maps to each standard (https://axiospec.com/standards) ### What it costs, in one sentence One flat price per workspace. Unlimited users on every plan, no per-seat charges, and no separate annual maintenance fee. Under 50 active assets the platform is free, permanently. Past that, plans start at $59 per month, and you can see every number on the pricing page. That is the whole quote, suitable for the one-line email to whoever approves spending. See also: See the full pricing table (https://axiospec.com/pricing) ### How you leave, if you ever want to Your data is yours. Every plan, including free, exports your full instrument registry and calibration history to CSV at any time, with no export gate and no retention hostage-taking. If Axiospec ever stops being the right fit, you take your records and go. We put this in writing because it is the question a careful quality manager should ask about any cloud system, and the answer should never be vague. ### Try it with your own registry The live demo shows a working lab with no signup. When you are ready to evaluate seriously, create a free account: every new workspace runs on Professional for its first 45 days with no credit card, so you can import your full registry and run it side by side with your current system. Under 50 active assets, the free plan simply keeps going after that. See also: Open the live demo (https://axiospec.com/demo) See also: Create a free account and import your registry (https://axiospec.com/signup) --- ## ISO 17025 Accreditation vs Certification Explained https://axiospec.com/guides/iso-17025-accreditation-vs-certification Last updated: 2026-09-06 ISO/IEC 17025 is accredited by bodies like A2LA and UKAS, not certified like ISO 9001. This guide explains the difference, what accreditation actually involves, the surveillance cycle that keeps it honest, and what a 17025 traceable calibration certificate really tells you as a buyer. You will often see a lab or a calibration certificate described as ISO 17025 certified. It is a small wording slip, but it points at a real distinction that matters when you are choosing a calibration supplier or preparing for your own audit. ISO/IEC 17025 is not something you get certified to. It is something a laboratory gets accredited for, by a recognized accreditation body such as A2LA or UKAS. This guide explains what that difference actually means, what accreditation involves, how the surveillance cycle keeps it honest, and what a 17025 traceable certificate really tells you as a buyer. ### Is ISO/IEC 17025 a certification? No, it is accreditation The short answer is that ISO/IEC 17025 is not a certification. There is no ISO 17025 certificate in the way there is an ISO 9001 certificate. A calibration or testing laboratory is accredited to ISO/IEC 17025 by an accreditation body, and that accreditation is issued for a specific, defined scope of tests or measurements. So when a supplier says it is 17025 certified, read that as loose shorthand for accredited, and then check the accreditation for yourself. The wording matters because certification and accreditation are different processes, run by different bodies, and they prove different things. The rest of this guide walks through that difference and what to do with it. Tip: If a vendor cannot show you an accreditation certificate with a scope and a named accreditation body, treat 17025 certified as a marketing phrase, not a verified fact. ### Accreditation and certification are not the same thing Certification is a third-party attestation that your management system meets the requirements of a standard. A certification body, sometimes called a registrar, audits your system and issues a certificate. ISO 9001 is the classic example. The certificate says your quality management system conforms to the standard. It does not, on its own, say your measurements are technically correct. Accreditation goes a step further. An accreditation body formally recognizes that a laboratory is technically competent to carry out specific tests or calibrations, to a stated measurement uncertainty, using validated methods and traceable equipment. Accreditation to ISO/IEC 17025 is about proven technical competence for a defined scope, not just a conforming system on paper. - Certification confirms a management system conforms to a standard. Accreditation confirms technical competence for specific measurements. - Certification is issued by a certification body. Accreditation is granted by an accreditation body such as A2LA, ANAB, or UKAS. - An ISO 9001 certificate applies to your organization. An ISO 17025 accreditation applies to a defined scope of tests or calibrations, each with a stated uncertainty. - Certification bodies are themselves usually accredited to run their schemes, so accreditation sits one level up the chain of trust. ### How ISO 17025 differs from ISO 9001 certification ISO 9001 is a management system standard. It applies to almost any organization and can be certified because it is about how you run and control your processes. A calibration program can absolutely live inside a 9001 system, which is why many manufacturers hold ISO 9001 certification and run calibration as one of its controls. ISO/IEC 17025 is narrower and deeper. It combines management requirements that overlap with 9001 and a set of technical competence requirements that 9001 does not have: personnel competence, equipment and metrological traceability, method validation, measurement uncertainty, and specific reporting rules for calibration and test results. Because those technical requirements have to be assessed by people who understand the measurements, 17025 is verified through accreditation rather than certification. In short, a 9001 certificate tells a customer your system is controlled. A 17025 accreditation tells a customer that a named laboratory is competent to make a specific measurement and report it with a defensible uncertainty. See also: Calibration for ISO/IEC 17025 (https://axiospec.com/standards/iso-17025) See also: Calibration for ISO 9001 (https://axiospec.com/standards/iso-9001) See also: Calibration for ISO 10012 (https://axiospec.com/standards/iso-10012) ### What ISO 17025 accreditation requirements cover People often search for ISO 17025 certification requirements. The requirements are real, but the correct term is accreditation requirements, and they fall into two groups. The first group is about impartiality and the management system: organizational structure, impartiality and confidentiality, document and record control, handling of complaints and nonconforming work, and internal audits and management review. Much of this overlaps with ISO 9001. The second group is the technical heart of the standard, and it is what accreditation actually verifies: - Competent personnel, with defined qualification, training, and authorization for each method they perform. - Equipment that is calibrated and maintained, with metrological traceability to the SI units, usually through a national metrology institute such as NIST or NPL. - Validated or verified methods, so the laboratory can show its procedures actually work for their intended use. - A documented estimate of measurement uncertainty for every calibration or test in scope. - A stated decision rule when the lab reports conformity to a specification, so pass and fail statements account for uncertainty. - Suitable and controlled environmental conditions wherever they affect results. - Clear reporting rules, so certificates carry the results, the uncertainty, and the traceability a reader needs. Tip: The measurement uncertainty and decision rule requirements are where a lot of buyers get surprised. A certificate that states pass or fail with no uncertainty and no decision rule is not meeting the spirit of 17025. See also: Metrological traceability explained (https://axiospec.com/guides/metrological-traceability-explained) See also: Measurement uncertainty budget calculator (https://axiospec.com/tools/measurement-uncertainty-budget-calculator) See also: Guard-band and TUR calculator (https://axiospec.com/tools/guard-band-calculator) ### How the accreditation process works Accreditation is earned, not bought, and the process is designed to test competence directly rather than take a lab's word for it. The exact steps vary a little between accreditation bodies, but the shape is consistent. 1. The laboratory implements ISO/IEC 17025 across the methods it wants in scope, and defines that scope precisely, down to the measurement ranges and best uncertainties. 2. It applies to an accreditation body that operates under ISO/IEC 17011, such as A2LA, ANAB, or UKAS. 3. Assessors review the laboratory's documented system against the standard. 4. Technical assessors, who are experts in the relevant measurements, carry out an on-site assessment and witness the lab actually performing calibrations or tests. 5. The lab demonstrates competence through records, traceability, uncertainty budgets, and usually participation in proficiency testing or interlaboratory comparisons. 6. Any findings are corrected, the accreditation body reviews the evidence, and accreditation is granted for the defined scope, with a scope document and a certificate. See also: ISO calibration requirements explained (https://axiospec.com/guides/iso-calibration-requirements) ### Surveillance and reassessment: accreditation is not one and done A common misunderstanding is that accreditation is a one-time achievement. It is not. Accreditation is maintained through an ongoing cycle of oversight, and it can be reduced, suspended, or withdrawn if a lab slips. Because most recognized accreditation bodies are signatories to the ILAC Mutual Recognition Arrangement, a valid accreditation is also recognized internationally, which is what lets an accredited certificate travel across borders and supply chains. - Surveillance assessments happen periodically, typically at intervals of about 12 to 24 months, to confirm the lab still operates as assessed. - A full reassessment covering the whole scope happens on a longer cycle, often around every two to four years depending on the accreditation body. - Ongoing proficiency testing and interlaboratory comparisons give objective evidence that results stay accurate over time. - Changes to methods, key staff, or location are expected to be reported and may trigger an extra assessment. - If problems are not fixed, the accreditation body can suspend or withdraw part or all of the scope. Tip: When you rely on a supplier's accreditation, note the certificate's validity dates and scope, and re-check them periodically. Scopes change, and an expired or narrowed scope is easy to miss. ### What 17025 traceable means when you are the buyer For most buyers, the practical question is not whether to become an accredited lab, but whether the calibration you are paying for is genuinely backed by accreditation. When a certificate or a service is described as 17025 traceable or 17025 accredited, here is what to verify. The last point below catches people out. An accredited lab can still issue non-accredited calibrations, so an accreditation logo on the letterhead does not mean the specific measurement was accredited. Read the certificate, not the logo. - The laboratory holds a current ISO/IEC 17025 accreditation from a recognized body, with an accreditation number you can look up. - The specific measurement you need is on the lab's scope of accreditation, since accreditation is per scope and a lab can be accredited for one measurement but not another. - The certificate shows the measurement results with an associated measurement uncertainty, not just a pass stamp. - If it states conformity to a tolerance, it names the decision rule used. - Metrological traceability is stated, ideally back to the SI through a national metrology institute. - The accreditation body mark or the ILAC MRA mark appears on the certificate for accredited work, and any calibration done outside the accredited scope is clearly marked as such. See also: What a calibration certificate must show (https://axiospec.com/guides/calibration-certificate-requirements) See also: Metrological traceability explained (https://axiospec.com/guides/metrological-traceability-explained) See also: Guard-band and TUR calculator (https://axiospec.com/tools/guard-band-calculator) ### You likely need accredited calibration, not your own accreditation Here is the distinction that saves the most confusion. Most manufacturers and quality teams do not need to become ISO/IEC 17025 accredited laboratories. What they need is calibration they can trust, sourced from labs that are accredited, so their own traceability holds up. Your internal calibration program usually lives under ISO 9001, AS9100, ISO 13485, or IATF 16949, and it draws its traceability from accredited calibration suppliers. That means your job is less about accreditation and more about control: keeping a clean instrument register, storing each accredited certificate against the right instrument, tracking metrological traceability, holding your due dates, and being able to reverse-trace from a drifted instrument to the work it touched. That is where calibration management software helps. Axiospec is built for exactly that program. It keeps your instrument register and status in one place, stores calibration certificates against each asset, records as-found and as-left readings with an automatic out-of-tolerance check, holds due dates on a Due Calendar, and writes every change to a tamper-evident, hash-chained ledger so your history stays traceable and audit-ready. It supports calibration workflows behind ISO/IEC 17025, ISO 9001, AS9100, ISO 13485, IATF 16949, Nadcap, and more. One honest limit. Axiospec is a documentation and workflow tool. It helps you keep clean, traceable records and export an audit pack in one click, but it does not accredit you, certify you, or guarantee an outcome. Accreditation is granted by an accreditation body, and certification by a certification body, based on your own scope, processes, and assessment. Tip: You can load your own instruments and certificates and see the workflow before you commit. The live demo needs no signup and no credit card, and the free trial needs no credit card. See also: See a live demo, no signup and no credit card (https://axiospec.com/demo) See also: Start a free trial, no credit card (https://axiospec.com/signup?plan=trial) See also: Or compare plans, including a free option (https://axiospec.com/pricing) ### Common questions Q: Is ISO/IEC 17025 a certification or an accreditation? A: Accreditation. ISO 9001 is certified by a registrar against a management system. ISO/IEC 17025 is accredited by an accreditation body, which assesses technical competence for specific measurements as well as the management system. That is why a 17025 laboratory has a scope of accreditation listing the exact quantities, ranges, and uncertainties it is competent for, and an ISO 9001 company has a certificate covering its processes. Q: Which bodies accredit calibration laboratories in the United States? A: A2LA, ANAB, NVLAP, PJLA and IAS all accredit calibration laboratories in the US, and each publishes a searchable public directory of the laboratories it accredits along with their scopes. They are not the whole list. NAC, a United States body, is also an ILAC Mutual Recognition Arrangement signatory for the accreditation of calibration and testing laboratories. A laboratory accredited by any ILAC signatory holds accreditation recognized internationally through that arrangement, so a certificate from one is not more valid than a certificate from another. Q: What is a scope of accreditation and why does it matter? A: A scope of accreditation lists the specific measurement quantities, ranges, and calibration and measurement capabilities a laboratory has been assessed as competent for. It matters because accreditation is not blanket. The same accredited laboratory can perform work outside its scope, and that work is not accredited. Before you approve a supplier, check that the exact parameter and range you need appears on the published scope with a stated capability, rather than relying on the accreditation logo alone. Q: Does using an accredited lab make my company ISO/IEC 17025 accredited? A: No. Buying calibration from an accredited laboratory gives your measurements traceability and gives you certificates that hold up at audit. It says nothing about your own accreditation status. Accreditation covers your own laboratory's competence, methods, personnel, and quality system, assessed by an accreditation body against your own scope. --- ## Calibration vs Verification: What Is the Difference? https://axiospec.com/guides/calibration-vs-verification Last updated: 2026-09-06 Calibration and verification are two different jobs. Calibration measures an instrument against a reference and quantifies the error and uncertainty. Verification confirms the instrument meets a specified tolerance and is fit for use. This guide explains each, how they connect through as-found and as-left readings, when to use which, and how a calibration management system records both. Calibration and verification get used as if they mean the same thing, but they answer different questions, produce different records, and some standards ask for one where a full calibration is not required. Calibration measures how far off an instrument is and states the uncertainty of that measurement. Verification takes a result and decides one thing: is the instrument good enough for the job, yes or no. This guide defines each in plain terms, shows how they connect through as-found and as-left readings, explains when to reach for which, and covers how a calibration management system captures both in one traceable record. ### The short answer: two different jobs Calibration and verification blur together because you usually do both in the same visit. But they are separate operations. Calibration is a measurement: you compare an instrument to a better reference and record how far off it reads, with the uncertainty of that comparison. Verification is a judgment: you take a result and decide whether the instrument meets the requirement you actually need. One quantifies, the other judges. Keeping them straight matters, because a calibration on its own does not pass or fail anything, and a verification is only as meaningful as the calibration and the tolerance behind it. - Calibration: compare the instrument to a traceable reference, quantify the error, and state the measurement uncertainty. It does not, by itself, declare the instrument good or bad. - Verification: confirm the instrument meets a specified requirement, usually your working tolerance, and decide fit or not fit for the intended use. - In practice: calibration produces the numbers, and verification uses those numbers to make a pass or fail decision. ### What calibration is In metrology, calibration is the operation that, under stated conditions, establishes the relation between the values an instrument indicates and the corresponding values realized by reference standards, together with the associated measurement uncertainties. In plain terms, you measure your instrument against something better and record how far off it reads and how sure you are of that result. The point that surprises people is that a calibration, by itself, does not tell you pass or fail. It gives you the error at each test point and the uncertainty. The decision comes afterward. A calibration certificate can report only as-found values with no statement of conformity at all, leaving the pass or fail entirely to you. Calibration is also where traceability is established. The reference you compare against must itself be traceable to a national or international standard through an unbroken, documented chain, and each step in that chain adds a little uncertainty. Without that chain, the numbers on the certificate are just numbers. - Compares the instrument to a traceable reference standard under stated conditions. - Quantifies the error at each test point, meaning how far the reading sits from the true value. - Reports the measurement uncertainty, so you know how sharp the result is. - Produces objective evidence, but does not on its own declare the instrument in or out of tolerance. See also: Metrological traceability, explained (https://axiospec.com/guides/metrological-traceability-explained) See also: Calibration certificate requirements: what a certificate must contain (https://axiospec.com/guides/calibration-certificate-requirements) ### What verification is (verification in metrology) Verification in metrology is the provision of objective evidence that an instrument meets specified requirements. The quality vocabulary frames it as confirmation, through evidence, that specified requirements have been fulfilled. In practice you take the calibration result, compare it to the tolerance you actually need, and decide whether the instrument is fit for the job. The requirement is the whole point. Verification is always against a stated requirement, whether that is your working tolerance, a product spec, or a legal limit. The same instrument, on the exact same calibration data, can pass verification for a loose tolerance and fail for a tighter one. That is why verification is a decision and not a measurement. Many quality systems call this metrological confirmation, the set of operations that ensure measuring equipment conforms to the requirements for its intended use. ISO 10012 builds a measurement management system around exactly this idea. One nuance worth keeping straight: verification confirms an instrument meets a specified requirement, while validation is the broader confirmation that it is fit for a specific intended use. For everyday calibration work, verification against tolerance is the one you will meet most. - Confirms the instrument meets a specified requirement, usually your working tolerance. - Produces a yes or no: fit for the intended use, or not. - Depends on the requirement, so the same data can pass one tolerance and fail a tighter one. - Often recorded as a calibration result of pass or fail, or as a quicker in-service check between calibrations. See also: ISO 10012 measurement management systems (https://axiospec.com/standards/iso-10012) See also: Calibration for ISO 9001 (https://axiospec.com/standards/iso-9001) ### Calibration vs verification, side by side Here is the difference between calibration and verification laid out point by point. The clean way to remember it: calibration is a measurement, and verification is a judgment made against a requirement. - Question answered. Calibration: how far off is it, and how sure are we? Verification: is it good enough for what we need? - Output. Calibration: measured errors and uncertainties, which are numbers. Verification: a pass or fail decision, fit or not fit. - Needs a tolerance? Calibration: no, it stands on its own. Verification: yes, always against a stated requirement. - Traceability. Calibration: establishes it. Verification: relies on the calibration behind it. - When it happens. Calibration: at set intervals, usually by a lab or a qualified technician. Verification: at calibration time, and often as faster checks in between. - Adjustment. Calibration may be followed by adjustment. Verification never adjusts, it only confirms. Tip: A calibration certificate that includes a statement of conformity, a pass or fail against a spec, has already done a verification for you. One that reports only as-found values has left the verification decision in your hands. ### How they connect: as-found and as-left As-found and as-left readings are where calibration and verification meet in a single event. When an instrument arrives, the as-found reading is measured, which is calibration, and comparing that reading to your tolerance is a verification of the instrument's incoming state. After any adjustment, the as-left reading is measured and compared again, verifying that the instrument leaves within tolerance and fit to return to service. An out-of-tolerance as-found is a failed incoming verification, and it is your signal to ask what measurements or product the drifted instrument touched since its last good calibration. That reverse-traceability question is one you cannot answer without the as-found number, which is why standards expect you to evaluate the validity of previous results when an instrument is found unfit. The pass or fail in a verification is not always a bare comparison to the limits. Because every calibration result carries uncertainty, a documented decision rule decides how much of that uncertainty to absorb before you call something in tolerance. A guard band narrows the acceptance limits by a portion of the uncertainty to reduce the risk of a false accept, which is calling an instrument good when it might not be. - As-found reading: the calibration measurement on arrival. Comparing it to tolerance verifies the incoming state. - As-left reading: the measurement after any adjustment. Comparing it to tolerance verifies the instrument leaves fit for use. - An out-of-tolerance as-found is a failed verification, and your prompt to review the past measurements that instrument affected. - The pass or fail applies a decision rule, and a guard band narrows the acceptance limits to control false-accept risk. See also: Guard-band and TUR calculator (https://axiospec.com/tools/guard-band-calculator) See also: As-found, as-left, and the decision rule (https://axiospec.com/guides/calibration-certificate-requirements) ### When to use each Both belong in a healthy program, and they are not interchangeable. Reach for a full calibration when you need traceable, quantified errors. Reach for a verification check when you need a quick, defensible answer about whether an instrument is fit right now. The limit to hold onto is that a verification check does not replace calibration. An in-service check against a known artifact tells you the instrument still reads right today, but it does not establish or renew traceability, and it does not reset your calibration interval. Interim checks are early warning, not a substitute for the scheduled work. - Calibrate when you need traceable, quantified errors: at set intervals, after a repair, drop, or overload, or when a standard or customer requires it. - Verify when you need a fast fit-for-use answer: before a critical measurement, at receiving inspection against a spec, or as an in-service check between calibrations. - Use interim verification checks to catch drift early, so a failure at the next calibration does not blindside you. - Remember the boundary: a verification check confirms the instrument still reads right today, but it does not establish or renew traceability, and the calibration interval still applies. Tip: Interim checks do not extend an interval on their own, but a documented history of stable checks is exactly the evidence that supports lengthening an interval when the data justifies it. See also: How to set calibration intervals (https://axiospec.com/guides/how-to-set-calibration-intervals) See also: Calibration interval calculator (https://axiospec.com/tools/calibration-interval-calculator) ### How a calibration management system records both Day to day, the difference between calibration and verification comes down to record-keeping. You want the measurement and the decision captured in the same event, so the numbers and the yes or no stay together and stay traceable. That is how a calibration management system earns its place. In Axiospec, logging a calibration captures the nominal value, the tolerance, and the as-found and as-left readings, and the pass or fail decision is made automatically against the tolerance. A reading outside nominal plus or minus tolerance sets the result to Fail and quarantines the instrument, setting its status to Quarantined, so the calibration measurement and the verification decision live in one record. You also capture the reference standard used for traceability, and per-instrument Metrology Insights surface the test uncertainty ratio and false-accept risk behind the decision. Every event writes to a tamper-evident, hash-chained ledger with timestamps and optional maker and checker approval, where the server refuses to let the person who logged a calibration approve it, so the history cannot be quietly altered. You can generate a PDF certificate in one click, status and the next-due date update on their own, and the Due Calendar shows what needs attention. If a reference or an instrument is later found out of tolerance, you can reverse-trace to the measurements it stood behind. One honest boundary: Axiospec documents and organizes the calibration and the verification decision, but it does not certify you or guarantee an audit outcome. Conformance is determined by your registrar, accreditation body, or customer. The tool's job is to make the record complete, traceable, and easy to produce. You can try the whole flow on your own data by creating a free account, which runs on Professional for its first 45 days with no credit card, or explore the live demo with no signup. See also: See it in a live demo, no signup and no credit card (https://axiospec.com/demo) See also: How to log a calibration in Axiospec (https://axiospec.com/guides/logging-a-calibration) See also: Compare plans, including a free option (https://axiospec.com/pricing) ### Common questions Q: What is the difference between calibration and verification? A: Calibration measures an instrument against a reference and quantifies the error and its uncertainty. It tells you how far off the instrument is and how confident you are in that number. Verification confirms the instrument meets a specified tolerance and is fit for use, which is a pass or fail judgment against a requirement. Calibration produces the measurement, verification applies the requirement to it. Many calibrations do both in one visit, which is why the terms get blurred. Q: Does calibration always include adjustment? A: No. Calibration is a measurement activity, not a repair activity. An instrument can be calibrated, found within tolerance, and returned with no adjustment at all, and that is the normal outcome for a stable instrument. Adjustment happens when the as-found reading is out of tolerance or drifting far enough that you want to recenter it. When no adjustment is made, the as-found and as-left readings are the same. Q: Which one do quality standards require? A: They require both, though they rarely use the words this cleanly. Standards ask that measuring equipment is calibrated or verified at defined intervals against traceable standards, that it is identified so its status is known, and that you act when it is found not to conform. In practice that means a traceable measurement, a documented judgment against a tolerance, and a record of both. --- ## As-Found vs As-Left: What the Readings Mean https://axiospec.com/guides/as-found-as-left-readings Last updated: 2026-09-06 A plain explainer of as-found and as-left calibration readings: what each state means, why recording both matters for reverse traceability and impact analysis, how they drive pass, fail, and out-of-tolerance handling, and what auditors look for. As-found and as-left are the two calibration readings that bracket the work. As-found is the reading an instrument gives when it arrives for calibration, before any adjustment; it is your evidence of how the instrument was actually measuring during the interval that just ended. As-left is the reading taken after any adjustment is finished, at the moment the instrument is returned to service; it is your evidence that the instrument is fit to keep using. So the as-found and as-left data answers two plain questions: was our recent measurement work sound, and is this instrument safe to put back to work. Together they tell you whether the instrument was in tolerance while it was in use, and whether it is fit to return. They look like a formality, but they carry most of the weight in an audit and almost all of the weight when something goes wrong. This guide explains what each reading means, why you need both, how they drive the pass or fail decision and out-of-tolerance handling, and what an assessor actually checks. It is written to help you understand the topic first, whatever tool you use to record it. ### As found and as left, defined As-found is the state of the instrument as it was received, before anyone adjusts, repairs, or resets it. It captures how the instrument was actually reading after a full interval in service. If the gauge had drifted on the shop floor, the as-found reading is where that drift shows up. As-left is the state of the instrument after the calibration work is complete, including any adjustment or repair. It is the condition the instrument is returned to service in, and it becomes the baseline for the next interval. When no adjustment is made, as-found and as-left are the same value, and that is a perfectly normal result. The two readings differ only when the technician actually changed something. The point of recording both is to make that difference visible, or to prove there was none. - As-found: how the instrument was reading before any adjustment. Evidence about the interval that just ended. - As-left: how the instrument reads after the work is done. The starting point for the interval about to begin. - No adjustment made: as-found equals as-left, recorded honestly rather than left blank. ### Why record both, not just a pass A single pass or fail throws away the most useful information in the record. The as-found reading is the only evidence you have about whether the instrument was giving good measurements during the months it was in use. The as-left reading is the only evidence that it is fit to go back out. Collapse both into one word and you lose the ability to answer the two questions that matter most at audit time and after a problem: was our past work sound, and is this instrument safe to keep using. Recording both also lets you see drift. The gap between the previous as-left and the current as-found is how far the instrument moved over one interval. That number is what turns a fixed calibration schedule into an interval you can actually defend, because you are adjusting based on how the instrument behaves rather than a date on a sticker. See also: How to set calibration intervals (https://axiospec.com/guides/how-to-set-calibration-intervals) See also: Drift-rate interval calculator (https://axiospec.com/tools/drift-rate-interval-calculator) ### As found is your reverse-traceability trigger The as-found reading is where impact analysis begins. If an instrument comes back out of tolerance, every measurement it made since its last good calibration is now in question. You cannot assume the parts it checked were good, because the tool doing the checking was wrong. This is the moment reverse traceability earns its keep: you work backward from the drifted instrument to every part, batch, job, or product it touched during that interval, then decide what to contain, rework, re-inspect, or notify a customer about. This is also why as-found must be captured before any adjustment. If a technician resets the instrument first and only then records a reading, the out-of-tolerance condition disappears, and with it the trigger for the whole impact process. Adjusting before recording as-found is not a shortcut. It hides the one fact that protects your product and your customers. Tip: Record as-found before touching the adjustment. Once you reset the instrument, the evidence that it had drifted is gone for good. See also: Metrological traceability explained (https://axiospec.com/guides/metrological-traceability-explained) See also: See reverse traceability in the live demo, no signup and no credit card (https://axiospec.com/demo) ### As left is proof the instrument is fit to return Where as-found looks backward, as-left looks forward. It is your evidence that the instrument leaving calibration is inside tolerance and safe to put back into service. If a technician adjusted the instrument to correct drift, the as-left reading proves the adjustment worked and left the instrument within limits, ideally near the center of its tolerance so it has room to drift before the next due date. As-left is also the new baseline. When the instrument comes back next time, its next as-found reading is compared against this as-left to measure the drift over the coming interval. A clean, well-centered as-left today makes next year's interval decision easier and gives the instrument the most working margin in between. ### How the two readings drive pass, fail, and out-of-tolerance The pass or fail decision is normally made on the as-found readings, because that is what tells you whether the instrument was still good while it was in use. Compare each as-found reading against the tolerance for that point. If it is inside the limit, the instrument passed for the interval just ended. If it is outside, you have an as-found out-of-tolerance condition and the nonconformance process starts. Where the reading sits close to the tolerance limit, a decision rule comes into play. Guard banding and the test uncertainty ratio determine how much of your own measurement uncertainty you subtract from the limit before you call a pass, so that a borderline result does not become a false accept. The as-left reading is then checked the same way to confirm the instrument is back inside tolerance before it returns to service. So the two readings do two different jobs. As-found decides whether past work is trustworthy and whether an impact assessment is needed. As-left decides whether the instrument is cleared to keep working. A record should show both, along with the tolerance and the decision rule used, so the pass or fail is reproducible rather than a matter of judgment. - As-found inside tolerance: the instrument held up over the interval. No impact analysis needed. - As-found out of tolerance: past measurements are suspect. Open the nonconformance and reverse-trace affected work. - As-left inside tolerance: the instrument is cleared to return to service. - Borderline readings: apply your guard band and TUR so a near-limit result is not falsely accepted. See also: Guard-band and TUR calculator (https://axiospec.com/tools/guard-band-calculator) See also: Conformance and false-accept calculator (https://axiospec.com/tools/conformance-probability-calculator) ### As found and as left with temperature compensation Dimensional measurements are referenced to 20 degrees Celsius (68 degrees Fahrenheit), the standard reference temperature. A reading taken on a warm shop floor includes thermal expansion of both the instrument and the standard, so for tight-tolerance dimensional work the raw number and the number at 20 degrees are not the same thing. For as found and as left records this means two disciplines. First, record the ambient temperature at the time of the readings. Second, state clearly whether the recorded values are as read or corrected to the reference temperature, and apply the same convention to both readings. A corrected as-found compared against an uncorrected as-left is a drift analysis built on sand. How much this matters depends on what you measure. The correction is roughly the length times the material's expansion coefficient times the temperature offset, so for a 25 mm micrometer check a couple of degrees off reference moves the answer by fractions of a micrometer: real for gauge blocks and long length standards, usually below the resolution of shop-floor calipers. If you do not correct, the temperature effect belongs in your uncertainty budget instead; it never just disappears. Here is the flip made concrete. Say you are verifying a 100 mm steel gauge with a tolerance of plus or minus 2 micrometers, and the shop floor is sitting at 24 degrees Celsius, 4 degrees above the 20 degree reference. Steel expands about 11.5 micrometers per meter for every degree, so across 100 mm and 4 degrees the part has grown by roughly 100 times 0.0115 times 4, about 4.6 micrometers. The raw as-found reading is 100.0038 mm, which is plus 3.8 micrometers from nominal and outside the plus or minus 2 micrometer limit: on the raw number, it fails. Correct that reading back to 20 degrees by subtracting the 4.6 micrometers of thermal growth and you get 99.9992 mm, minus 0.8 micrometers from nominal and comfortably inside tolerance: on the corrected number, it passes. Same instrument, same part, opposite call, and the only thing that changed was whether the temperature term was accounted for. That is exactly why the record has to state the ambient temperature and whether each value is as read or corrected, and why the same convention has to carry through to the as-left reading so the drift comparison stays honest. Axiospec records the ambient temperature with each calibration event, so the conditions behind every as-found and as-left value stay on the record the auditor reads. See also: Put the temperature term in your uncertainty budget (https://axiospec.com/tools/measurement-uncertainty-budget-calculator) ### Multi-point calibrations: 5-point, 10-point, and as found/as left A single reading pair verifies one point on the instrument's range. Many procedures instead check 5 or 10 points across the span, sometimes rising and falling to expose hysteresis, and pressure gauges, indicators, and scales are the classic cases. In a multi-point calibration, as found and as left are recorded per point: each nominal value gets its own before and after reading against its own tolerance. The pass rule follows from that: the instrument passes as found only if every point is inside tolerance, and one bad point makes the whole as-found a fail even when the other nine are perfect. The per-point record is also where linearity problems show themselves, since an instrument can be dead-on at zero and mid-span while drifting at full scale. Keep the record honest at whatever granularity your procedure uses: if the procedure says 10 points, a certificate showing one summarized reading pair does not evidence the procedure. Record each point's as found, apply the same points as left after any adjustment, and keep the run in the calibration record. See also: How decision rules apply pass and fail at each point (https://axiospec.com/guides/iso-17025-decision-rules-and-calibration-intervals) ### What as found and as left data means on a calibration report On a calibration report or certificate, as found and as left usually appear as two result tables, or as paired columns in one table. Each row is a test point: the nominal value applied, the reading the instrument gave, the tolerance limits, and a pass or fail flag. The as-found table is the instrument's condition on arrival, before anyone touched it. The as-left table is its condition when the work was finished. Reading them is a two-step check. First look at the as-found column: if every point is inside the tolerance limits, the instrument was still measuring correctly through the whole period since its last calibration, and every measurement it made in that period stands. If any as-found point is outside the limits, the report is telling you the instrument was reading wrong for some unknown part of that period, and the measurements it made need an impact review, regardless of what the as-left column says. Some reports collapse the two: a line like "as left same as as found" or a single results table marked no adjustment made means the instrument passed as received and nothing was changed. That is a normal, healthy outcome. What a report should never do is show only as-left data for an instrument that was adjusted, because that hides the condition that matters most: what it was reading before the fix. See also: Axiospec records as found and as left with an automatic out-of-tolerance check and writes the certificate for you. Free for up to 50 instruments (https://axiospec.com/signup) ### What auditors look for Assessors against ISO/IEC 17025, ISO 9001, AS9100, and similar standards do not just want to see a pass. They want evidence that your as-found and as-left process is honest and complete, because that is what protects the product. Expect them to probe how you handle an out-of-tolerance instrument, not just a clean one. - Both readings present on the record, not a lone pass or fail with the numbers missing. - As-found captured before adjustment, so a drifted instrument cannot be quietly reset first. - A documented out-of-tolerance procedure, including impact assessment and, where needed, customer notification, when an as-found fails. - Reverse traceability from the failed instrument to the work it affected during the interval. - The tolerance, units, and decision rule recorded alongside the readings, so the call is reproducible. - Traceability of the reference standards used to take the readings. - Who performed the calibration and who reviewed it, ideally with a second-person check where your standard expects one. - Records that cannot be edited after signing without the change being logged and attributable to a person. See also: Calibration for ISO/IEC 17025 (https://axiospec.com/standards/iso-17025) See also: Calibration for ISO 9001 (https://axiospec.com/standards/iso-9001) See also: What belongs on a calibration certificate (https://axiospec.com/guides/calibration-certificate-requirements) ### Common mistakes to avoid - Adjusting the instrument before recording as-found, which erases the drift and skips the impact process. - Leaving as-left blank when no adjustment was made, instead of recording that as-found equals as-left. - Recording only a pass or fail, so you keep no evidence of how far the instrument had drifted. - Treating an as-found out-of-tolerance as a paperwork event rather than a trigger to reverse-trace affected work. - Storing readings without the matching tolerance and decision rule, so the pass or fail cannot be reproduced later. - Keeping records where a past reading can be changed with no history and no name attached to the change. ### How Axiospec captures as found and as left Axiospec is a documentation and workflow tool. It does not make you compliant or decide an audit outcome, and it never claims to. Conformance is determined by your registrar, notified body, accreditation body, or customer. What the software does is make the right record the easy record. When you log a calibration, you enter as-found and as-left readings and Axiospec checks the as-left reading against your tolerance and sets the result to Fail if it lands outside the band. An as-found out-of-tolerance result flags the instrument and lets you reverse-trace from a drifted reference standard to every calibration it stood behind, and record the impact on the record itself, so impact analysis starts from evidence rather than memory. Records land in a tamper-evident, hash-chained ledger, so a signed reading cannot be quietly edited, and optional maker and checker approval, where the server refuses to let the person who logged a calibration approve it covers the second review some standards expect. You can generate a PDF certificate in one click, log calibrations at the bench or on the floor with QR scanning and voice capture, and print the instrument labels themselves from the web app, and use Metrology Insights per instrument to turn the drift between as-left and the next as-found into a defensible interval. The free plan is the full platform capped at 50 active assets with unlimited users, so read access on the floor costs nothing. Every new workspace runs on Professional for its first 45 days with no credit card, and the live demo needs no signup at all, so you can load a real instrument and see the as-found and as-left flow with your own numbers before you decide anything. See also: Start a free trial, no credit card (https://axiospec.com/signup?plan=trial) See also: See a live demo, no signup and no credit card (https://axiospec.com/demo) See also: Or compare plans, including a free option (https://axiospec.com/pricing) ### Common questions Q: What do as-found and as-left mean on a calibration certificate? A: As-found is the reading the instrument gave when it arrived for calibration, before anyone adjusted it. It is your evidence of how the instrument was actually measuring during the interval that just ended. As-left is the reading after any adjustment is complete, at the moment the instrument goes back into service. It is your evidence that the instrument is fit to keep using. On a certificate the two usually appear as two result tables, or as paired columns, with one row per test point showing the nominal value applied, the reading, the tolerance limits, and a pass or fail flag. Q: Why record both as-found and as-left instead of just a pass or fail? A: A single pass or fail throws away the most useful information in the record. The as-found reading is the only evidence you have about whether the instrument was giving good measurements during the months it was in use. The as-left reading is the only evidence it is fit to go back out. Recording both also lets you measure drift, because the gap between the previous as-left and the current as-found is how far the instrument moved over one interval. That number is what turns a fixed schedule into an interval you can defend. Q: What happens if an as-found reading is out of tolerance? A: An as-found out-of-tolerance result means every measurement that instrument made since its last good calibration is now in question, because the tool doing the checking was wrong. That triggers reverse traceability and impact analysis. You work backward from the drifted instrument to every part, batch, job, or product it touched during the interval, then decide what to contain, rework, re-inspect, or notify a customer about. This is why as-found must be captured before any adjustment. Resetting the instrument first erases the out-of-tolerance condition and skips the whole impact process. Q: Should as-found and as-left be the same value if nothing was adjusted? A: Yes. When no adjustment is made, as-found and as-left are the same value, and that is a perfectly normal result. The two readings differ only when the technician actually changed something. Leaving as-left blank is a common mistake. Record that as-found equals as-left so the record shows the instrument was checked and needed no work, rather than looking incomplete. Q: How do as-found and as-left work on a multi-point calibration? A: In a multi-point calibration, as-found and as-left are recorded per point. Each nominal value gets its own before and after reading against its own tolerance. The pass rule follows from that: the instrument passes as-found only if every point is inside tolerance, so one bad point makes the whole as-found a fail even when the other nine are perfect. The per-point record is also where linearity problems show up, since an instrument can be dead-on at zero and mid-span while drifting at full scale. Q: Do as-found and as-left readings need temperature compensation? A: For tight-tolerance dimensional work, yes. Dimensional measurements are referenced to 20 degrees Celsius (68 degrees Fahrenheit), so a reading taken on a warm shop floor includes thermal expansion of both the instrument and the standard. That means two disciplines for the record. Record the ambient temperature at the time of the readings, and state clearly whether the values are as read or corrected to the reference temperature, applying the same convention to both. A corrected as-found compared against an uncorrected as-left is a drift analysis built on sand. How much it matters depends on what you measure, since the correction is roughly the length times the material expansion coefficient times the temperature difference. Q: What is the difference between as-found and as-left in one sentence? A: As-found is the reading before any adjustment, showing how the instrument was measuring during the interval that just ended, and as-left is the reading after the work is done, showing the condition it goes back into service in. If nothing was adjusted, the two are the same value. Q: What do auditors look for in as-found and as-left records? A: Assessors want evidence that the process is honest and complete, not just a pass. They look for both readings present on the record rather than a lone pass or fail with the numbers missing, as-found captured before adjustment, a documented out-of-tolerance procedure including impact assessment and customer notification where needed, reverse traceability from a failed instrument to the work it affected, the tolerance and units and decision rule recorded alongside the readings, and records where a past reading cannot be changed without a history and a name attached. --- ## Gage R&R and measurement systems analysis (MSA), explained https://axiospec.com/guides/gage-rr-and-msa-explained Last updated: 2026-09-06 What measurement systems analysis is, the difference between Gage R&R, bias and linearity, and attribute agreement studies, what %GRR and NDC thresholds mean, when to run each study, and how MSA relates to calibration. Gage R&R measures how much of your recorded variation comes from the measurement system itself, split into repeatability (same operator, same gage) and reproducibility (between operators). It is the core study of measurement systems analysis, usually shortened to MSA, which is how you separate the two and decide whether you can trust the numbers. This guide explains the families of MSA studies in plain terms, how Gage R&R differs from bias and linearity, what the %GRR and NDC thresholds mean, when to run which study, and how the whole thing relates to calibration. ### What measurement systems analysis is The measurement system is not just the gage. It is the gage, the person using it, the method, the fixture, and the environment, all working together to produce a reading. Measurement systems analysis is a set of studies that tell you how much of the variation you see comes from the parts themselves, and how much is noise added by that system. This matters because you make decisions from measurements. You accept or reject parts, adjust a process, or judge whether an instrument still reads true. If a large share of your measured variation is coming from the measurement system rather than the parts, those decisions rest on noise. MSA gives you a defensible, numeric answer to a simple question: can you trust the numbers this system produces? MSA is most strongly associated with the automotive quality world, where the AIAG Measurement Systems Analysis reference manual defines the standard methods and IATF 16949 control plans routinely call for it. But the ideas apply anywhere you measure to make a decision. See also: Run a Gage R&R now with the free calculator (https://axiospec.com/tools/gage-rr-calculator) ### The three families of MSA studies People often say MSA when they mean Gage R&R, but Gage R&R is only one part of the picture. MSA is a family of studies, and each one answers a different question. Knowing which is which is the difference between running the right study and wasting a morning on the wrong one. The three families below cover almost everything you will need. - Gage R&R (repeatability and reproducibility) measures precision. It tells you how much variation the measurement system adds when different people measure the same parts more than once. It says nothing about whether the readings are correct, only whether they are consistent. - Bias and linearity, together with stability, measure accuracy. They compare the system's readings to a known reference value. Bias is the offset at one point, linearity is how that offset changes across the range, and stability is how it drifts over time. - Attribute agreement analysis covers judgements that are not numbers: pass or fail, go or no-go, accept or reject, or a visual grade. It measures whether appraisers agree with each other, with themselves, and with the correct answer. Tip: A system can be precise but wrong, or accurate on average but too noisy to trust. That is exactly why Gage R&R and bias and linearity are separate studies. You usually need both. See also: Calibration for IATF 16949 (https://axiospec.com/standards/iatf-16949) ### Gage R&R: repeatability and reproducibility explained Gage R&R is the workhorse of MSA. The two Rs are repeatability and reproducibility, and they capture two different sources of measurement variation. Repeatability is the variation you get when one person measures the same part, with the same gage, several times. It is sometimes called equipment variation, because it reflects the gage and the measurement itself. If a caliper gives you three different readings on the same block, that spread is repeatability. Reproducibility is the variation you get when different people measure the same parts. It is sometimes called appraiser variation, because it reflects differences in how people use the gage, seat the part, or read the scale. If two inspectors consistently disagree on the same parts, that gap is reproducibility. A typical study combines both into a single measure of measurement system variation, usually written as GRR. The study design below is the common one, and keeping to it is what makes the result trustworthy. - Choose about 10 parts that represent the real range of process variation, not 10 good parts. - Use 2 to 3 appraisers who normally do the measurement. - Have each appraiser measure each part 2 to 3 times, in random order, blind to their earlier readings. - Keep the gage, method, and conditions the same as real production use. See also: Gage R&R calculator (https://axiospec.com/tools/gage-rr-calculator) See also: Free Gage R&R template (Excel, AIAG 3 x 10 x 3) (https://axiospec.com/tools/gage-rr-template) ### Reading Gage R&R results: %GRR and NDC The raw GRR number is not meaningful on its own. You compare it to something: either the total variation you observed in the study, or your tolerance. Expressed as a percentage, that is %GRR. Which base you use matters. Percent of study variation tells you how the system performs against your actual process spread. Percent of tolerance tells you how it performs against the spec you have to hold. They can give different answers, so always state which one you used. The widely used AIAG guidelines for %GRR are easy to remember, but treat them as guidelines, not law. The right threshold depends on what the measurement is for and what a wrong decision costs. - Under 10 percent: the measurement system is generally considered acceptable. - 10 to 30 percent: may be acceptable depending on the importance of the application, the cost of the gage, and the cost of getting the decision wrong. - Over 30 percent: the system is generally considered unacceptable and needs work before you rely on it. - NDC (number of distinct categories): how many distinct groups the system can reliably tell apart across your process range. A value of 5 or more is the usual target. Below that, the system struggles to resolve real differences between parts. Tip: A common trap is running the study on 10 nearly identical good parts. If the parts barely differ, the measurement system looks bad no matter how good it is. Pick parts that span the real range. See also: Gage R&R calculator, with %GRR and NDC (https://axiospec.com/tools/gage-rr-calculator) See also: Process capability (Cp and Cpk) calculator (https://axiospec.com/tools/process-capability-calculator) ### Bias and linearity: the accuracy side of MSA Gage R&R tells you whether a system is consistent. It cannot tell you whether it is correct. A gage can repeat the same wrong number all day. That is what the accuracy studies are for, and they all compare your readings to a known reference value, usually a master or reference standard with a calibrated, traceable value. Bias is the difference between the average of your measurements and the reference value at one point. It is a systematic offset. If a reference block is known to be 25.000 mm and your gage averages 25.014 mm, the bias is 0.014 mm. Bias is the same kind of error calibration deals with, which is why the two are closely linked. Linearity asks whether that bias stays the same across the measurement range or changes. A gage might read almost perfectly near the low end and drift high near the top of its range. You measure linearity by checking bias at several reference values across the range and seeing whether it trends. Stability, sometimes grouped with these, is how bias behaves over time. You measure the same reference repeatedly over days or weeks and watch for drift, often on a control chart. Stability is closely related to how you set calibration intervals. See also: Bias and linearity calculator (https://axiospec.com/tools/bias-linearity-calculator) See also: How to set calibration intervals (https://axiospec.com/guides/how-to-set-calibration-intervals) ### Attribute agreement analysis Not every measurement is a number. A lot of real inspection is a judgement: pass or fail, go or no-go, accept or reject, or a visual grade like scratch or no scratch. You cannot run a numeric Gage R&R on a decision, so these judgements need their own study, usually called attribute agreement analysis or attribute Gage R&R. The study works by having appraisers judge a set of parts whose correct answer is already known, more than once, without seeing their earlier calls. From that you learn three things: whether each appraiser agrees with themselves, whether appraisers agree with each other, and, most important, whether they agree with the known correct answer. Agreement is often summarised with a kappa statistic, which measures agreement beyond what you would expect from chance alone. Higher is better. You also look at practical error rates. A missed bad part is usually the costliest error, so watch the miss rate closely. - Within-appraiser agreement: does each person make the same call on the same part every time? - Between-appraiser agreement: do different people make the same call on the same part? - Agreement with the standard: do the calls match the known correct answer? - Miss rate and false alarm rate: how often bad parts pass, and how often good parts are wrongly rejected. See also: Run an attribute agreement study in the free calculator (https://axiospec.com/tools/attribute-gage-rr-calculator) ### When to run which study You do not run every study every time. Match the study to the question in front of you and to what your quality plan or customer requires. In automotive work, MSA is typically part of new part approval and is called out on the control plan, but the same logic applies anywhere you measure to decide. - New gage or a new measurement process going into service: run Gage R&R, and check bias and linearity against a reference. - The measurement is a pass or fail or visual judgement: run attribute agreement analysis instead of a numeric Gage R&R. - After a gage is repaired, moved, or its method changes: re-run Gage R&R to confirm nothing shifted. - You suspect one operator's results differ from another's: the reproducibility part of a Gage R&R will show it. - Readings seem consistent but possibly off: that is a bias and linearity question, not a Gage R&R one. - On a schedule set by your control plan or customer: run whatever the plan specifies, on the stated interval. Tip: Do the accuracy work first. If a gage is not calibrated and its bias is unknown, a clean Gage R&R still only proves the system is consistently producing an unknown offset. See also: Calibration requirements by ISO standard (https://axiospec.com/guides/iso-calibration-requirements) ### How MSA relates to calibration, and where Axiospec fits Calibration and MSA are often confused, because both are about trusting measurements, but they answer different questions and you need both. Calibration compares one instrument to a traceable reference standard to establish, and if needed correct, its accuracy. It is the gage against a known truth. MSA evaluates the whole measurement system as it is actually used, including the people, the method, and the parts, and it is mostly about variation in real conditions. The two overlap at accuracy. The bias and linearity side of MSA measures the same kind of error that calibration corrects, which is why a valid MSA depends on a properly calibrated reference in the first place. Calibration is a prerequisite, not a replacement. A calibrated gage can still fail Gage R&R because of operator or method variation, and a gage with a great Gage R&R can still read a consistent but wrong offset if it was never calibrated. Calibration decision rules such as the test uncertainty ratio and guard banding sit alongside all of this, governing how you accept or reject the instrument itself. Axiospec is a calibration management tool, and it includes an AIAG Gage R&R study and per-instrument uncertainty budgets, so the measurement analysis lives next to the calibration record for the same asset rather than in a separate spreadsheet. When you run a study, the data stays attached to the instrument, alongside its as-found and as-left readings, its certificates, and its due dates. Axiospec organizes and surfaces this evidence and does the AIAG math, but it does not decide conformance. Whether a system is acceptable, and whether your program meets a standard, is a judgement for your quality team, customer, or assessor. The free tools below run the core Gage R&R and bias and linearity math in your browser with nothing to install. If you want the studies stored on the asset, Axiospec's free plan is the full platform capped at 50 active assets, with unlimited users, and every new workspace starts with 45 days on Professional, 1,500 active instruments, no credit card. See also: Guard-band and TUR calculator (https://axiospec.com/tools/guard-band-calculator) See also: Metrological traceability, explained (https://axiospec.com/guides/metrological-traceability-explained) See also: See a live demo, no signup and no credit card (https://axiospec.com/demo) See also: Start a free trial (https://axiospec.com/signup?plan=trial) See also: Or compare plans, including a free option (https://axiospec.com/pricing) ### Common questions Q: What is the difference between calibration and Gage R&R? A: Calibration compares an instrument against a reference and tells you whether the instrument is accurate. Gage R&R asks a different question: how much of the variation you see in your measurements comes from the measurement system itself rather than from the parts. A perfectly calibrated instrument can still fail Gage R&R if operators use it inconsistently or the gauge lacks resolution for the tolerance. You need both, and they are not substitutes. Q: What is an acceptable %GRR? A: The common AIAG guidance is that under 10 percent is acceptable, 10 to 30 percent is conditionally acceptable depending on the application, the cost of the gauge, and the cost of repair, and over 30 percent is unacceptable and the measurement system needs work. Judge %GRR against the tolerance or the study variation according to which your customer or procedure specifies, because the two give different numbers for the same data. Q: What is NDC and what number should it be? A: NDC is the number of distinct categories, an estimate of how many separate groups your measurement system can reliably tell apart within the part variation. AIAG guidance is that NDC should be 5 or more. An NDC below 5 means the measurement system cannot resolve the process well enough to be used for process control, even if the %GRR looks borderline acceptable. Q: When do I run a variable versus an attribute study? A: Run a variable Gage R&R when the measurement produces a number, such as a dimension read from a caliper or a torque value. Run an attribute agreement analysis when the measurement produces a category, such as pass or fail or a visual grade. Attribute studies report agreement and effectiveness along with kappa rather than %GRR, because there is no continuous variation to partition. Q: What is bias and linearity, and how is it different from Gage R&R? A: Bias is the difference between the average of your measurements and a reference value, so it tells you whether the measurement system reads consistently high or low. Linearity is how that bias changes across the operating range, so a gauge can be accurate at mid-span and biased at the extremes. Gage R&R measures spread, that is repeatability and reproducibility, while bias and linearity measure position against a reference. A complete MSA looks at both. --- ## How to Choose Calibration Management Software: A Buyer's Guide https://axiospec.com/guides/choosing-calibration-management-software Last updated: 2026-07-19 A vendor-neutral buyer's guide to choosing calibration management software: the capabilities that matter, the questions to ask any vendor, how pricing really works, how to migrate your data without losing history, and where standards fit. Calibration management software promises to replace the spreadsheet, the sticky notes, and the scramble before an audit. But the market is crowded, and two tools that look identical on a feature grid can behave very differently once your real instruments and history are inside. This guide walks you through the capabilities that actually matter, the questions that separate a serious vendor from a polished demo, how pricing usually works, how to move your data without losing your traceability, and where each tool sits against your standard. It is written to help you choose well, whichever tool you land on. ### Start with the job, not the feature grid Before you compare products, get clear on the job you are hiring the software to do. Most buyers do not need the longest feature list. They need a small set of things done reliably, every day, and defensibly at audit time. If a tool covers the jobs below cleanly, it is a real contender. If it dazzles on a demo but stumbles on one of these, keep looking. - Keep one trusted register of every instrument and its current status. - Tell you what is due, due soon, and overdue before it bites. - Capture each calibration with as-found and as-left readings and an automatic out-of-tolerance check against tolerance. - Produce records an auditor or customer accepts without a follow-up email. - Let you reverse-trace from a drifted instrument to every part, batch, or job it touched. ### Must-have capabilities Use this as a checklist. Score each tool honestly against it before you look at price. Anything missing here tends to become a manual workaround later, and manual workarounds are exactly what you are trying to leave behind. - A complete asset register with live status for every instrument (in tolerance, due, overdue, or quarantined). - A due view that separates due, due soon, and overdue, so nothing slips. - As-found and as-left readings with an automatic out-of-tolerance check against your tolerance. - PDF certificates you can generate in one click and hand to an auditor or customer. - A tamper-evident ledger, ideally hash-chained, so past records cannot be quietly edited. - Reverse traceability, so one out-of-tolerance instrument leads you to all the work it affected. - Maker and checker approval if your standard expects a second review. The server refuses to let the person who logged a calibration approve it, and with electronic signatures on, the approver's sign-off is bound to the record. - Multi-site rollup if you run more than one facility. - Mobile capture on the floor: QR-code scanning and voice logging, with instrument labels printed from the web app. - Interval math you can defend, based on how the instrument actually performs, not just a fixed date. - Test uncertainty ratio and guard-band handling behind your pass and fail decisions. - Import and export you control, so your data is never trapped in someone else's system. See also: Calibration interval calculator (https://axiospec.com/tools/calibration-interval-calculator) See also: Guard-band and TUR calculator (https://axiospec.com/tools/guard-band-calculator) ### Questions to ask any vendor A good vendor answers these plainly and can show you, not just tell you. Vague answers are themselves an answer. - Who owns the data, and how do I export all of it, including history, if I ever leave? - Can a record be edited after it is signed, and if so, is every change logged and attributable to a person? - How do you handle as-found versus as-left, and does a fail update the instrument status automatically? - Can I reverse-trace from a single instrument to everything it measured? - When I import, does my calibration history come across as real events, or only the last-calibrated date? - Is there a genuine free tier or trial I can load with my own data, with no credit card? - What is included at my price, and what is gated to a higher tier, such as the API, extra sites, or users? - Do you charge per user, per instrument, or per facility? - What is your uptime, backup, and hosting story, and where does my data physically live? - Can you show the exact workflow my standard requires, live, rather than describing it? ### How to compare tools without getting sold The fastest way to a bad decision is to compare demos. Vendor demo data is always clean, complete, and flattering. Your data is not. Compare tools against your own reality instead. 1. Write down your standard, your instrument count, your number of sites, and who needs access. 2. Shortlist three tools that clearly cover your must-haves, not the three with the longest feature lists. 3. Load each one with a real slice of your own data, not the vendor's sample set. 4. Run one full cycle end to end: import, log a calibration, fail one on purpose, then generate the certificate. 5. Try to break it. Attempt to edit a past record and see whether the tool stops you or logs the change and who made it. 6. Put the generated certificate in front of whoever owns your audits and ask if they would accept it as-is. 7. Compare total cost at your real user and instrument count, not the headline price on the pricing page. See also: Compare the main calibration management tools side by side (https://axiospec.com/compare/best-calibration-management-software) ### Red flags to watch for - Records that can be edited after the fact with no history and no attribution. - No way to export your full data, or export locked behind a higher-priced tier. - Per-seat pricing that effectively charges you for giving the floor read-only access. - A demo that only ever runs on the vendor's clean sample data. - Fuzzy answers on hosting, backups, and who owns your records. - Any claim that the software makes you compliant, certified, or audit-proof. No tool can do that. - Import that brings over current status but silently drops your calibration history. - Fixed intervals with no way to adjust based on how an instrument actually behaves over time. ### How pricing usually works Calibration tools price on a few common models, and the model matters as much as the number. Map each quote to your real usage before you compare. Per user or per seat is predictable, but it quietly punishes you for giving technicians and auditors read access, so cost climbs as your team grows. Per instrument or per active asset scales with the size of your register. Per facility or per site is a flat charge per location, which suits multi-plant operations. Many tools use a flat platform fee with certain features gated to higher tiers. The single most useful pricing signal is whether you can test with real data before you pay. A genuine free tier or a free trial lets you prove the tool on your own instruments and history, so you are buying evidence, not a sales pitch. For example, Axiospec's free plan is the full platform capped at 50 active assets with unlimited users, so read access on the floor costs nothing, and its paid Professional tier and above add capabilities like the REST API. Every new workspace starts with 45 days on Professional, 1,500 active instruments with no credit card, and the live demo needs no signup and no credit card. Tip: Load real data before you decide. A price that looks great on 10 sample assets can look very different on your full register and your full team. See also: Compare plans, including a free option (https://axiospec.com/pricing) See also: See a live demo, no signup and no credit card (https://axiospec.com/demo) ### Migrating your existing data Migration is where most calibration projects stall, and it is worth planning before you sign anything. There are two walls to get over. The first is your current register, the list of instruments and their status. The second, and the one tools quietly skip, is your calibration history. If only the last-calibrated date comes across, your traceability starts from zero on day one. Good vendors offer both self-serve import from common formats, such as CSV, Excel, and legacy tools like GAGEpack and GAGEtrak, and hands-on white-glove migration for the complex cases. Axiospec, for instance, supports self-serve import from those sources plus free white-glove migration by its team, and it brings history over as real calibration events rather than a single date field. 1. Export your current register from wherever it lives today, whether a spreadsheet or another system. 2. Clean obvious duplicates and standardize your units and date formats before you import anything. 3. Import current status first, then confirm the instrument counts match your source exactly. 4. Bring over calibration history as real events, not just a last-calibrated date, so traceability survives the move. 5. Spot-check a handful of instruments against your original records to catch silent field drops. 6. Keep the old system read-only for one full cycle as a safety net before you retire it. See also: How to import your existing registry (https://axiospec.com/guides/importing-your-registry) ### Where standards fit Software supports the workflow, but the standard defines the requirement, and different standards emphasize different things. ISO/IEC 17025 leans hard on measurement traceability and uncertainty. ISO 9001 frames it as control of monitoring and measuring resources. AS9100 adds aerospace expectations, ISO 13485 covers medical devices, and IATF 16949 and Nadcap bring their own automotive and special-process demands. Choose a tool that maps cleanly to the clauses you are actually assessed against, and confirm it during your trial rather than trusting a checkbox on a comparison page. The right tool makes producing that evidence routine instead of a scramble. See also: Calibration for ISO/IEC 17025 (https://axiospec.com/standards/iso-17025) See also: Calibration for ISO 9001 (https://axiospec.com/standards/iso-9001) See also: Calibration for AS9100 (https://axiospec.com/standards/as9100) See also: Calibration for ISO 13485 (https://axiospec.com/standards/iso-13485) See also: ISO calibration requirements explained (https://axiospec.com/guides/iso-calibration-requirements) ### What software can and cannot do for compliance Be clear-eyed about the boundary here, because it protects you at audit time. Good software can produce clean, traceable, audit-ready records, keep a tamper-evident ledger of every change, show live status for every instrument, let you reverse-trace from a drifted gauge, hold your schedule, and standardize your certificates. That is real, and it removes most of the pain. What software cannot do is make you compliant, certify you, or guarantee an audit outcome. Conformance is determined by your registrar, notified body, accreditation body, or customer, based on your own processes, your scope, and your assessor. The tool makes the evidence clean and findable. The discipline behind it is still yours. Choose the software that makes doing the right thing the easy path, then do the work. --- ## Get your workspace set up https://axiospec.com/guides/getting-started Last updated: 2026-06-30 Walk through first-run setup: name your workspace, add your first instruments, understand calibration status, and invite your team. This guide walks you through your first session in Axiospec, from naming your workspace to seeing your first instruments on the dashboard. By the end you will have a working registry and a team ready to log calibrations. ### What a workspace is Your workspace is the home for your whole quality program. It holds your instrument registry, your calibration records, your team, and your sites (each physical facility). Everything you do in Axiospec lives inside one workspace, and the people you invite all share it. A workspace name is shown across the app and printed on calibration certificates and audit exports, so use the name you want auditors to see. Inside the workspace, a site is a physical facility, and the labs, benches, and rooms within it are locations. A new account starts with one default site that you can rename, and you can add more later under Settings, Sites. Tip: Nothing here is permanent. Every setting you choose during setup can be changed later from Settings, so it is fine to move quickly and refine as you go. ### Run the first-run Onboarding wizard The first time you sign in as an admin, Axiospec opens the Onboarding wizard at /manager/onboarding. It has three steps, and you can use Skip to Dashboard at any time if you would rather explore first. 1. Step 1, Workspace Foundation: enter your company or workspace name, name your primary site (your first facility), and set your standard date format and workspace timezone. These control how timestamps appear on calibration records and certificates. 2. Set your compliance strictness. Turn on "Require approval for calibration events" if every calibration should be reviewed and approved (maker-checker) before it is committed, and keep "Require electronic signatures" on so users re-authenticate when approving high-risk calibrations. 3. Optionally upload a company logo. It appears in your workspace sidebar and on your certificates. Select Continue. 4. Step 2, Build Your Team: invite a Technician to perform calibrations and a Manager to approve them, with a first and last name for anyone you invite. This step is optional, so you can choose Skip for now and invite people later. 5. Step 3, Bring Your Data: choose how to add your first instruments, then finish. You land on the Compliance Overview dashboard at /manager/dashboard. Tip: Names are required for anyone you invite because their name appears on the calibration records they perform or approve. Keep first and last names accurate from the start. ### Add your first asset, or import in bulk An asset in Axiospec is a calibrated instrument or gauge that you track, such as a digital multimeter, torque wrench, or caliper. You can add one at a time to try things out, or import your full registry at once. On the last onboarding step you can add a single asset inline (instrument name, asset tag, optional last calibration date, and a calibration interval) or open the import tool. After onboarding, both paths live on the dashboard. - Add one asset: on the Instrument Registry section of the dashboard, select Add Asset. Fill in the asset tag, instrument name, manufacturer, model number, and serial number, set the calibration interval, and optionally pick a location and a last calibration date, then select Create Asset. - Import many at once: select Bulk Import to map and upload your existing tool list from CSV or Excel, including legacy exports such as GAGEpack or GAGEtrak. The import tool maps your columns and validates fields inline. - Set the calibration interval (for example, 12 months) so Axiospec can schedule the next due date automatically. - Provide the last calibration date if you know it, and the compliance status and next due date are set from it. Leave it blank and the instrument shows as not yet calibrated until its first calibration is logged. Tip: Just testing? Add a single asset first to see how the workflow feels. When you are ready for real data, import your full registry, or send it to us and we will load it for you free on any plan, usually within a couple of business days. ### Understand calibration status and intervals The calibration interval is how often an instrument must be recalibrated. Axiospec uses the interval plus the last calibration date to compute each asset's next due date, and the dashboard rolls those into a status you can scan at a glance. Your dashboard leads with clickable status counts that summarize your registry and double as filters. Selecting a count filters the Instrument Registry below it, so you can jump straight to what needs attention. When you want to plan ahead, the Due Calendar gives you a calendar view of what is due, due soon, and overdue across the whole program, so you can schedule work before anything lapses. - In Tolerance: the instrument is within its calibration tolerance and on schedule. - Due Soon: the next calibration date is approaching (within the 30-day window). Plan the work before it lapses. - Overdue: the instrument is past its calibration due date or in a failed state and needs attention now. - Out of Service (quarantined): the instrument has been pulled from use and should not be relied on until it is calibrated and returned to service. - Checked Out: the instrument is signed out to a person through the tool crib, so you can see who has what at a glance and check it back in with one click. - When a calibration is logged, the result is recorded as Pass, Fail, Limited, or Adjusted, which is what drives the status above. Tip: Use the status filter, the clickable counts, or the Due Calendar on the dashboard to surface every Due Soon and Overdue instrument, then work that list down. ### Invite your team If you skipped the team step during onboarding, you can invite teammates anytime from Settings, Team at /manager/settings/team. Inviting people lets technicians log calibrations and managers review and approve them, with each person's name attributed to the records they touch. Roles shape what each person can do: technicians perform calibrations, managers approve them, and read-only auditors can review records without changing anything. Pricing is per workspace with unlimited users at every tier, so add everyone who needs access. 1. Go to Settings, Team. 2. Add each teammate's email, first name, and last name, and assign a role (technician, manager, or auditor). 3. Send the invitations. Invited users receive an email to set up their own login and join your workspace. ### How your records are protected Calibration records are written to a tamper-evident, hash-chained ledger with timestamps and electronic signatures, and changes that matter run through a maker-checker approval flow. That means the history of any instrument stays traceable and audit-ready. Axiospec is a documentation and workflow tool. It helps you keep clean, traceable records and export an audit pack in one click, but it does not certify or guarantee an audit outcome. Whether you pass depends on your own processes, your scope, and your assessor. ### Next steps With your workspace set up and your first instruments in the registry, you are ready to load the rest of your data and start capturing calibrations. - Bringing data from another system? See "Import your registry" to map and validate a CSV, Excel, or legacy export. - Ready to record work? See "Log a calibration" to capture a reading, attach a photo, and e-sign a record. --- ## Import your asset registry https://axiospec.com/guides/importing-your-registry Last updated: 2026-07-27 Bring your existing equipment list into Axiospec with the Bulk Import tool, from preparing a CSV through mapping, preview, and fixing rows. You can bring your whole equipment list into Axiospec in one pass using the Bulk Import tool, which reads a CSV or Excel file, maps your columns to Axiospec fields, and checks every row of a CSV or TSV before you commit, and validates Excel rows on the server as they import. If you would rather not touch your data at all, our team can do the migration for you at no cost. ### Before you start: prepare your file Bulk Import reads CSV, TSV, and Excel files (.csv, .tsv, .xlsx). Export your current registry from your spreadsheet or your existing calibration system, and make sure the first row is a header row that names each column. The importer reads those headers to suggest a mapping, so clear names like Asset Tag, Description, or Serial Number save you work later. You do not need to rename or reorder anything to match Axiospec exactly. You map columns in the next step, and common names (for example Gage ID, Control Number, Description, or Mfr) are detected automatically. If you would rather start from a known-good layout, open Bulk Import and use Download CSV Template to get a file with the right headers already in place. - Asset Tag (required): your unique identifier for each instrument, such as CAL-001 or a gage ID - Instrument Name (required): a short description of the instrument, such as Torque Wrench #12 - Manufacturer, Model Number, and Serial Number: optional but recommended, since serial number helps tell apart identical instruments of the same model - Location and Site: optional; Site places each asset location under that site, and a blank Site uses your default site - Calibration Interval: a combined value like 12 Months or 6 Weeks (you can also map separate value and unit columns), plus an optional Last Cal Date Tip: Asset Tag and Instrument Name are the only required columns. Everything else can be filled in later, so do not let missing manufacturer or serial data hold up your import. ### Open Bulk Import and upload your file Bulk Import lives in the Asset Ledger. From the manager app, go to the Asset Ledger and open Bulk Import, then upload your prepared file. 1. Open the Asset Ledger at /manager/asset-ledger. 2. Launch Bulk Import. Optionally expand the Formatting Guide or use Download CSV Template first. 3. Drag your file onto the upload area, or click to browse and select it. 4. Wait while Axiospec reads your column headers. If it cannot find a header row, add one to your file and upload again. Tip: If your spreadsheet was exported in a non-US format, the importer auto-detects the delimiter (comma, semicolon, tab, or pipe), so a European Excel export will not collapse into one giant column. ### Map your columns to Axiospec fields After upload, you land on the mapping step. Each Axiospec field is shown as a navy tag on the left, and for each one you pick the matching column from your file on the right. Axiospec pre-fills the obvious matches for you, so often you only need to confirm or adjust a few. Required fields are marked with an asterisk. You must map Asset Tag and Instrument Name before you can continue. For any column you do not want to bring in, leave the selection on Do not import. Use Show Advanced System Fields when your interval is split across two columns (a number and a unit), or to map Department and Procedure. Anything else worth keeping, such as purchase date, vendor, or lab ID, can come in through the Custom attributes section, where you choose a file column on the left and name the attribute it becomes on the right. - Core fields: Asset Tag, Instrument Name, Manufacturer, Model Number, Serial Number, Location, Site, Calibration Interval, Last Cal Date - Advanced System Fields: separate Interval Value and Interval Unit columns, Department, and Procedure - Custom attributes: any extra columns you want to carry over, each saved as a named custom field on the asset Tip: When the interval is in one column, map it to Calibration Interval (for example 90 days). When it is two columns, switch to the advanced fields and map Interval Value and Interval Unit separately. ### Preview and run the import Select Confirm Mapping to build a preview. Axiospec shows the first rows as they will be saved, using Axiospec field names rather than your original headers, so you can confirm the data landed in the right places before anything is written. Any previewed row missing a required value (Asset Tag or Instrument Name) is flagged as Missing and highlighted. You can go Back to Mapping to fix the mapping, fix those values in your source file and re-upload, or continue and handle them at the validation step. When the preview looks right, choose Execute Import. Axiospec validates every row, and the import only commits when the rows pass. Imported instruments appear in your Asset Ledger, ready for you to schedule calibrations and start logging work. Tip: An imported instrument with no calibration history shows as Not calibrated yet until its first calibration is logged. Once you log calibrations, status moves to Compliant, Due Soon, or Overdue based on its interval. ### Fix validation errors and import the rest If some rows fail validation, Axiospec lists each one with its row number, asset tag, and a plain-language description of the problem, often with a hint on how to fix it. Nothing partial is silently saved; you stay in control of what gets committed. You have a few ways to resolve errors. Use Edit Mapping if a whole column was mapped wrong, or Upload New File after correcting your source. For a quick path forward when only a handful of rows are bad, Skip Errors and Import Valid Assets brings in the good rows and leaves the flagged ones behind (this works for CSV and TSV files). For larger registries, Download error report exports every flagged row as a CSV with the problem and the suggested fix, so you can correct your source file offline and re-import in one clean pass. - Edit Mapping: re-point a column that was mapped to the wrong field - Skip Errors and Import Valid Assets: load the rows that pass and set aside the rest (CSV/TSV) - Download error report: get a CSV of every failed row, the problem, and how to fix it - Retry Import or Upload New File: re-run after you have corrected the issues ### Add assets one at a time You do not have to import in bulk. To add a single instrument, go to the Asset Ledger and create a new asset at /manager/asset-ledger/new, or use the Add New Instrument dialog. Enter the asset tag, instrument name, manufacturer, model number, and serial number, optionally set the location and calibration interval, and add a last calibration date if you know it. This is handy when you receive a new instrument, when you want to try the workflow with one record before importing everything, or when you are filling in details after a bulk import. Tip: You can also decide here whether an asset requires supervisor approval for its calibrations. If left unchecked, qualified technicians can auto-approve, which keeps routine work moving while higher-stakes assets still route through the maker-checker approval flow. ### Free white-glove migration If your data is unusual or complex, or you are coming off another calibration system, you do not have to wrangle it yourself. Our team will handle the full migration for free, including moving you off another tool. This is especially useful for complex database exports from systems like GAGEpack, GAGEtrak, or a legacy ERP. Choose Send us your files and we do the rest. Our team maps and loads it for you, usually within a couple of business days. You can keep using the self-serve Bulk Import tool in the meantime, and switch to white-glove help at any point if a file gives you trouble. Whichever path you choose, your records land in the same place: a tamper-evident, hash-chained ledger that timestamps and e-signs calibration entries, so the history you build stays traceable and audit-ready. Tip: Not sure whether to import yourself or hand it over? Try Bulk Import with a small sample export first. If the mapping and preview look right, finish the full file yourself. If not, choose Send us your files and we do the rest. --- ## Log a calibration https://axiospec.com/guides/logging-a-calibration Last updated: 2026-06-30 Record a calibration result, readings, reference standard, and certificate, then e-sign so the status and next-due date update automatically. Logging a calibration is the core daily task in Axiospec. This guide walks you through finding the instrument, recording the result and readings, attaching the certificate, e-signing, and letting the status and next-due date update on their own. ### Find the instrument Every calibration is logged against a single instrument record, so the first step is opening the right one. Go to the Asset Ledger at /manager/asset-ledger and search or filter by asset tag, serial number, manufacturer, or location, then open the record to land on its asset detail page. If you are at the bench, scanning the printed QR label on the instrument is faster. Each label encodes a deep link that opens the same instrument record, so a phone-camera scan takes you straight to the asset detail page (and into the Axiospec mobile app when it is installed). - Asset Ledger: open /manager/asset-ledger, find the instrument, and open its record. - QR scan: scan the device label to jump directly to the instrument record. - From the dashboard, an instrument flagged Due Soon or Overdue links straight to its record. Tip: If you cannot log a calibration, check your access. The action is role-gated, and auditor (read-only) accounts see the record and history but cannot log results. ### Open the Log Calibration sheet On the asset detail page, select Log Calibration in the header. A side sheet titled Log Calibration opens with the entry form. The advanced metrology fields are optional, so a simple pass can be a few fields, while a full metrology record can capture readings and environment. When the instrument has a viewable standard operating procedure linked to its active calibration plan, a View SOP button appears at the top of the sheet so you can open the procedure in a new tab before you start. - Calibration Date defaults to today; change it if you are back-dating bench work. - Reference Standard Used records traceability; type the standard or pick from the suggested list (for example, Gage Block Set #4 or a NIST-traceable weight set). - Temperature and Humidity capture the environment; the temperature unit toggle lets you enter Celsius or Fahrenheit. Tip: Calibrating the same instrument the same way each time? Repeat the last calibration in a tap to pre-fill the sheet from the previous record, then adjust the readings and submit. ### Record the result and readings Set the Result for this calibration. The options are Pass, Pass with Adjustment (an adjusted instrument that now passes), Limited Calibration (a restricted or partial pass), Fail, and Damaged. Choose Limited Calibration only when the instrument is usable within stated limits, and use Pass with Adjustment when you brought a drifting instrument back into tolerance. In the Readings section, enter the Nominal, Tolerance, As Found, and As Left values where they apply. As Found captures the instrument's state before any adjustment; As Left captures it afterward. These build the as-found and as-left record that auditors look for. Axiospec helps catch mistakes: if an As Found or As Left reading falls outside nominal plus or minus tolerance, the Result is automatically set to Fail and the sheet tells you why. Limited Calibration requires you to fill in Restriction Notes (for example, the valid range) before you can submit. - Pass: the instrument met its tolerance with no adjustment. - Pass with Adjustment: it was adjusted and now meets tolerance (As Found and As Left are highlighted). - Limited Calibration: usable within limits; Restriction Notes are required. - Fail or Damaged: the result quarantines the instrument (status Out of Service) pending review. Tip: Use the Notes field for remarks reviewers should see, such as the procedure followed or anything unusual at the bench. ### Attach the certificate or evidence photo Under Certificate & Evidence Photos, click to upload or drag and drop your files. PDF and image files are supported, so you can attach an external calibration certificate or a photo of the bench setup, display reading, or seal. The first file you add is treated as the primary certificate (it is tagged Certificate in the list), and any additional files are kept as supporting evidence. You can add several photos and remove any before you submit. Files attach to this specific calibration event, so the certificate stays linked to the exact result it documents. - First file = primary certificate; additional files = evidence photos. - Drag and drop or click the upload area to browse. - You can also attach a certificate later from the calibration history row using the paperclip action. ### E-sign and submit When you submit, Axiospec writes the event to a tamper-evident, hash-chained ledger with a timestamp, so the record cannot be silently altered after the fact. If your workspace policy or the specific asset requires it, an electronic signature prompt appears and you re-authenticate to sign the submission. A signed event shows a shield indicator in the calibration history. The submit button reflects what happens next. When supervisor approval is required for the asset, the button reads Submit for Review and the event is queued for a reviewer. When approval is not required, it reads Record Calibration and the result takes effect immediately. Either way, the event is captured in the ledger first. - Submit for Review: the asset requires approval, so the result waits in the queue. - Record Calibration: approval is not required, so the result is recorded at once. - If the instrument is quarantined and your result passes, check the option to return it to service (this clears quarantine once the result is accepted). ### Approval and automatic status updates Calibrations that need a sign-off route through a maker-checker flow. Submissions land in the review queue at /manager/approvals, where a different manager or administrator approves or rejects them. You cannot approve or reject a calibration you submitted yourself; another reviewer must handle it. A rejection includes a reason that stays in the audit trail, and the result is kept out of the accepted compliance record. Once a calibration is recorded (or approved, when review is required), the instrument's compliance status and next-due date update automatically based on the result and the calibration interval. A passing result moves the asset toward In Tolerance and recalculates Calibration Due, which surfaces as Due Soon as the date approaches and Overdue once it passes. A Fail or Damaged result quarantines the asset as Out of Service until it is reviewed. You do not edit these dates by hand. - In Tolerance: the instrument is within its calibration interval. - Due Soon: the next calibration date is approaching. - Overdue: the calibration interval has lapsed. - Out of Service (quarantined): set by a Fail or Damaged result, pending review. Tip: Axiospec keeps traceable, audit-ready records of what you logged and who signed off. It is a documentation and workflow tool, and your own processes and scope still determine whether you meet a given standard. --- ## Use the Axiospec mobile app https://axiospec.com/guides/mobile-app Last updated: 2026-06-30 Install the iOS or Android app, scan an asset, and log calibrations with photos and e-signatures from the floor, even offline. The Axiospec mobile app lets technicians log calibrations and checks right at the instrument, from a phone, with photos and e-signatures. It uses the same account and data as the web app, so anything you capture on the floor shows up everywhere else. ### Get the app and sign in The native iOS and Android apps are live on the App Store and Google Play. They share one login and one set of data with the Axiospec web app, so there is nothing extra to set up. Whatever your workspace contains on the web is what you see on your phone. 1. On iPhone or iPad, open the App Store and search for Axiospec, or use the App Store link on the Axiospec site. On Android, open Google Play and search for Axiospec, or use the Google Play link on the site. 2. Install the app and open it. 3. Sign in with the same email and password you use for the Axiospec web app. If your workspace uses single sign-on, sign in the same way you do on the web. 4. After sign-in you land in your workspace with the same assets, sites, and permissions you already have. Your role (technician, manager, or read-only auditor) carries over, so you only see and do what your role allows. Tip: No phones allowed on your floor? You do not need the app at all. The full calibration workflow also runs in any web browser on a bench PC or shared terminal. ### Find or scan an asset Every calibration starts from an asset. On the floor, scanning is usually the fastest way to pull up the right instrument without typing a serial number. You can also search your registry by hand when there is no label to scan. - Scan the QR code on the instrument label to jump straight to that asset. - Search the asset list by tag, serial number, name, or description when there is no code to scan. - Open an asset to see its current calibration status (In Tolerance, Due Soon, Overdue, or Out of Service) and its calibration history before you start work. Tip: If your labels do not have QR codes yet, you can print QR labels from Axiospec so technicians can scan instead of type going forward. ### Log a calibration or check from your phone Once you have the right asset open, logging the work is a short form. The goal is to capture the reading, the result, and your e-signature in seconds, then move on to the next instrument. When you submit, the record is written to the tamper-evident, hash-chained ledger with a timestamp and your e-signature, the same ledger the web app writes to. Changes that need oversight follow the maker-checker approval flow, so a reviewer can approve them later from the web or their own phone. 1. From the open asset, start a new calibration entry (for example, Log Calibration). 2. Enter the readings. You can type them, or dictate hands-free when gloves or grease make typing impractical. 3. Record the result: Pass, Fail, Limited, or Adjusted. 4. Attach any photos and confirm the details (see the next section for capturing photos). 5. Apply your e-signature and submit. The entry is added to the asset's history and its calibration status updates accordingly. Tip: Logging a Fail or an Out of Service action is how an instrument gets quarantined, so capture a photo and a clear note when you do. ### Capture photos Photos give your records context that numbers alone cannot: the instrument condition, the as-found reading on a display, a seal, or a label. Axiospec lets you attach photos to a calibration record as you log it. Attached photos travel with the record into the ledger and into your audit pack exports, so the visual evidence stays tied to the exact calibration event it documents. 1. While logging a calibration, choose to add a photo. 2. Take a new photo with your phone camera, or pick an existing image from your library. 3. Add as many photos as the work needs (for example, as-found and as-left), then submit the record with your e-signature. ### Work offline and sync when you are back online Shop floors and remote sites often have weak or no signal. The mobile app is built for that. You can keep working without a connection, and your work is not lost. When you are offline, calibration entries (including their photos and e-signatures) queue locally on your device. As soon as the connection comes back, they sync automatically to your workspace, so floor work is never blocked by spotty WiFi. - Capture calibrations and checks while fully offline; the app keeps working. - Entries queue safely on the device until a connection returns. - Syncing happens automatically when you are back online, no manual upload step. - Once synced, the records appear on the web app and in exports exactly like any other entry. Tip: Before heading to a no-signal area, open the assets you expect to work on while you still have a connection so their details are loaded and ready. ### Use favorites and remember it is one account If you calibrate the same instruments often, favorites keep them within easy reach so you do not have to search or scan every time. Mark an asset as a favorite and it stays in a quick-access list on your phone. Everything you do on mobile is the same account and the same data as the web app. There is no separate mobile database to reconcile. A reading you log on your phone shows up in the Asset Ledger on the web, feeds the same due-date tracking, and is included when a manager exports an audit pack from the Audit Center. - Mark frequently used instruments as favorites for fast access on the floor. - Favorited assets stay handy across sessions, so repeat work is one tap away. - Your mobile entries appear instantly for managers and auditors on the web. - Approvals can be handled on either device, so a reviewer can approve your work right from their phone. --- ## Export an audit-ready pack https://axiospec.com/guides/audit-pack-export Last updated: 2026-06-30 Generate a Calibration Audit Report PDF and manifest CSV from the Audit Center, plus per-asset certificates, to produce records for an audit. When an assessor asks for your calibration records, Axiospec assembles them into a single, downloadable pack. This guide shows you how to generate the audit pack, verify your ledger, and pull individual certificates so you can hand over clean, traceable documentation. ### Start in the Audit Center The Audit Center (Audit Center in the left nav, route /manager/audit-center) is where you compile evidence for a regulator or auditor and review recent export activity. It has two cards you will use most: Ledger Integrity and Generate Audit Archive. Open it before an audit so you can verify your records are intact and produce the pack in one place. Everything generates on demand, so the pack always reflects your current data at the moment you export. Tip: Recent exports are listed at the bottom of the page with the date, who requested them, and a Download action, so you can re-pull a package you generated earlier. ### Verify the ledger chain first Calibration records are written to a tamper-evident, hash-chained ledger. The Ledger Integrity card walks that chain for every committed calibration record in your workspace and reports any entry that was altered after it was approved. Running this before you export gives you a clean integrity result to point to, and confirms there are no surprises in the records you are about to hand over. 1. In the Audit Center, find the Ledger Integrity card. 2. Click Verify ledger chain. 3. Read the result. A valid chain reports the number of committed calibration entries verified end-to-end, with the time it was checked. 4. If a mismatch is reported, note the flagged ledger entry and contact support@axiospec.com, since an altered committed record is a security-sensitive event. ### Generate and download the audit pack The audit pack is a single ZIP archive built on demand. It contains two files: a Calibration Audit Report (audit_summary.pdf) and a manifest (audit_manifest.csv) that lists your assets and ledger entries. 1. In the Audit Center, go to the Generate Audit Archive card. 2. Click Generate Compliance Archive. The button shows progress while the documents compile. 3. When the download starts, save the ZIP file. It also appears in Recent Exports with a Download action for later retrieval. 4. Open the ZIP and confirm both files are present before sharing it with your assessor. Tip: You can also kick off the same export from the Export Audit Trail button on your Dashboard, and it will still show up in the Audit Center's Recent Exports list. ### What is inside the pack The Calibration Audit Report PDF gives an assessor a readable narrative of your program, and the manifest CSV gives them the underlying data to filter and cross-check. - Status summary: a dashboard count of total assets broken down by In Tolerance, Due Soon, Overdue, and failed items. - Integrity and verification: the result of walking the tamper-evident ledger, including the number of entries verified and the chain's head and genesis hashes. - Calibration trail: each ledger entry with the asset, event, status, who performed it, when it was performed, and the Pass / Fail / Limited / Adjusted result. - Out-of-tolerance items: a dedicated section listing assets and events with Fail, Limited, or damaged results, with as-found and as-left readings. - Sign-offs: an asset roster with owners, procedures, intervals, and next-due dates, plus the performed-by and approval attribution carried through the records. - Manifest CSV: one row per asset and one row per ledger entry, covering tags, serials, site and location, workspace custom fields, results, readings, uncertainty and decision-rule columns, reference standards, certificate numbers, and the record and previous hash values for each entry. ### Download a single asset's certificate When an auditor wants documentation for one specific instrument, you do not need the whole pack. Each asset has its own Certificate of Calibration, generated from its latest approved calibration. The certificate is laid out in three sections: Instrument (tag, manufacturer, model, serial, location, interval), Calibration (performed date, result, nominal value, tolerance, as-found and as-left readings, reference standard, environment, certificate number), and Attestation (performed by, approval, and approval time). It also carries the tamper-evident record hash. 1. Open the Asset Ledger (route /manager/asset-ledger) and select the instrument to open its detail page (/manager/asset-ledger/:id). 2. In the page header, click Download Certificate. 3. Save the PDF when it is ready. 4. If you see a message that there is no approved calibration to certify yet, log and approve a calibration for that asset first, then try again. Tip: An asset needs at least one approved calibration before a certificate can be produced, since the document reflects an approved ledger record. ### Scope the pack by date or site Auditors usually care about a defined window or a single facility. You can narrow what goes into your evidence so the pack matches the scope being assessed rather than your entire history. Scope by date by aligning the records you present to the audit period, and use the calibration trail and manifest CSV (which carry the performed and exported timestamps) to filter to the dates in question. Scope by site by working from a single facility's assets, since every asset, certificate, and manifest row carries its site and location so a multi-site workspace can present one site at a time. - By date: rely on the performed-at timestamps in the calibration trail and the manifest CSV to bound the records to the audit window. - By site: each row and certificate is tagged with its site and location, so you can present the records for the facility under review. ### What the pack does and does not do Axiospec produces the documentation: traceable, audit-ready records assembled from a tamper-evident ledger with timestamps and e-signatures, and changes that matter routed through a maker-checker approval flow. That gives you consistent, defensible evidence to hand over. Axiospec does not certify, guarantee, or ensure that you pass an audit. The outcome depends on your own processes, the completeness of the data you have entered, your scope, and your assessor. Treat the pack as the evidence you bring to the audit, not the verdict. --- ## Manage sites, users, and access https://axiospec.com/guides/managing-sites-and-users Last updated: 2026-06-30 Invite teammates, assign roles, set up sites and locations, and scope who sees what across a multi-site workspace. As an administrator you control who can work in your Axiospec workspace, what they can do, and which sites they can see. This guide walks through inviting users, assigning roles, setting up sites and locations, and managing your plan. ### Where to administer your workspace Administration lives in two places. Team membership and roles are managed under Team Settings, and your workspace-wide configuration sits under Organization Settings, Sites & Locations, and Notifications. Your plan and seats are on the Team & Billing page. Workspace administration is limited to Admin and Super Admin roles. If you open the Organization Settings, Sites & Locations, or Locations page without admin access, you are sent back to your profile automatically. Managers can still reach the Team page to invite and manage technicians. - Team: /manager/settings/team (invite users, change roles, scope site access, revoke access) - Sites: /manager/settings/sites (facilities and the locations that belong to each) - Workspace: /manager/settings/workspace (name, logo, timezone, approval and signature policy) - Team & Billing: /manager/team-billing (roster, plan, and subscription) Tip: Unlimited users are included on every plan, so add everyone who touches calibrations. There is no per-seat charge to weigh. ### Invite users and understand the roles Open Team Settings and select Invite User. Enter the person's first name, last name, email, and a role. The first and last name are required because they appear on audit records, calibration entries, and e-signatures. Invited users show as Pending until they accept, then move to Active. Roles define what each member can do (this is enforced on the server, not just hidden in the UI). Pick the least-privileged role that still lets the person do their job. - Admin: full workspace control. Manages all members and roles, billing, sites, and workspace settings. Sees every site. - Manager: runs the day-to-day program. Manages the asset register, logs calibrations, reviews maker-checker approvals, and can invite and manage Technicians. - Technician: logs calibrations and uploads documents. Cannot manage the asset register by default (an admin can turn this on per workspace). - Auditor: read-only. Can review records and exports but cannot log calibrations or change data. - Super Admin: a hidden support role; you will not normally assign or see it. 1. Go to Team Settings. 2. Select Invite User. 3. Enter first name, last name, and email address. 4. Choose a role from the Role list (your own role limits which roles you can grant). 5. Optionally scope the invite to specific sites (see the multi-site section below). 6. Select Send Invitation. The user appears as Pending until they accept. Tip: Managers can only invite and manage Technicians. To add another Admin, Manager, or Auditor, an Admin must send the invite. ### Change roles, edit users, and revoke access Each member row has an actions menu. Use Edit User to update a person's name, email, home location, and status; Change Role to move them between roles; and Revoke Access to remove them from the workspace. You cannot change your own role or status, and you cannot revoke your own access. Revoking access archives the member so they can no longer sign in, but it does not erase their history. Calibrations they recorded stay in the ledger with their name and timestamp, which is what keeps your records traceable. Role changes take effect on the user's next sign-in. - Edit User: update profile details, set a home (default) location, or change status between Active, Pending, and Archived. - Change Role: promote or demote within the roles you are allowed to assign. - Revoke Access: archive the member; their past records remain attributed to them. - Home location is only a convenience default on forms. It does not limit which sites a person can see. ### Set up sites and locations If your organization runs more than one facility, model each one as a Site under Settings (Sites). A site is a physical facility (a plant, a building, a lab). Within each site you create Locations, which are the buildings, labs, benches, and stations where instruments actually live. When you create an asset you pick its location, and the asset's site follows from that location. One site is marked Default and is used whenever a site is not specified. To create a site, select Add site, enter at least a name (code, address, and timezone are optional), and save. Manage locations in the Locations card below: add a location, assign it to a site, rename it, or move it between sites. 1. Go to Settings (Sites). 2. Select Add site, enter a name (optionally a code, address, and timezone), then Create site. 3. Set your most-used facility as the default with Set default. 4. In the Locations card, type a location name, choose its site, and select Add. 5. Use the per-location site picker to move a location to a different site as your layout changes. Tip: Deleting a site does not delete its locations or assets. Locations under it become Unassigned and assets keep their location. You cannot delete the default site until you set another site as default first. ### Scope who sees what (site access) A site is an access boundary. By default, a new user with no site grants has full workspace access and can see every site. To narrow someone's view, grant them specific sites: open Edit User (or set it on the invite), then select the sites they should see under Site access. Once you select one or more sites, that user is restricted to only those sites; clearing all selections restores full access. Admins and Super Admins are never restricted by site, so the Site access control does not appear for them. Site grants only scope Managers, Technicians, and Auditors. For each granted site you can leave the role on Inherit (use their workspace role there) or set a different per-site role, for example making someone a Manager at one site and a Technician at another. In version 1, site access governs visibility and the scope of a user's actions. As with roles, these controls gate what shows up in the interface, and the server independently enforces the same boundaries on every request. - No sites selected: full workspace access (this is the default for new users). - One or more sites selected: the user only sees and works within those sites. - Per-site role: leave on Inherit to reuse the workspace role, or override it for that site. - Admins and Super Admins always see everything, regardless of grants. ### Organization settings and policy Organization Settings holds organization-wide configuration that shapes how records look and how strict your process is. Your workspace name and logo appear on audit PDFs, exports, and certificates, so set them before you share anything externally. The timezone and date format you choose are used for audit timestamps and throughout the app. Two policy toggles control rigor. Require Approval for Calibration Events turns on the maker-checker flow so every calibration must be reviewed and approved before it is committed, and it adds the Approvals tab to the sidebar. Require Electronic Signatures forces users to re-authenticate when approving high-risk calibrations. You can also let technicians manage the asset register, and configure when due-date reminders go out and who receives them. - Organization Profile: name and company logo for reports and certificates. - Approvals & Signatures: require approval (maker-checker) and require e-signatures. - Team Permissions: allow technicians to add, edit, and bulk-import assets. - Localization: workspace timezone and date format for audit timestamps and exports. - Calibration Reminders: lead times and recipient emails for due-date digests. Tip: These settings help you keep traceable, audit-ready records. Whether your program meets a given standard depends on your own processes, scope, and assessor. ### Manage your plan and seats Open Team & Billing to view your current plan and manage your subscription. Unlimited users are included at every tier, so growing your team never raises your bill. Only Admins and Super Admins can change the subscription. Choose a billing cycle (monthly or yearly), then select a plan to start checkout, which is handled securely through Stripe. Once you are subscribed, Manage Subscription & Billing opens the Stripe customer portal where you can update payment methods, download invoices, and change your plan. Team & Billing covers your plan and subscription only. To manage team members, roles, invites, and locations, use the Go to Team Settings link, which opens the Team Settings page. 1. Go to Team & Billing. 2. Pick a billing cycle (Monthly or Yearly). 3. Select a plan to begin checkout through Stripe. 4. After subscribing, use Manage Subscription & Billing to update payment details or invoices. 5. Use Go to Team Settings to invite or adjust members on the Team Settings page. --- ## Calibration requirements by ISO standard https://axiospec.com/guides/iso-calibration-requirements Last updated: 2026-09-06 What each major quality standard asks for calibration, from ISO 9001 clause 7.1.5 to ISO/IEC 17025 and ISO 13485 clause 7.6, compared in one place. There is no single ISO standard that covers calibration for everyone. What applies to you depends on what your quality system is certified against and whether you run a calibration lab or just use measuring equipment in production. This guide summarizes what each major standard asks for, and the requirements they share. ### Is there a single ISO standard for calibration? No. Two standards are about calibration itself: ISO/IEC 17025 sets the competence requirements for testing and calibration laboratories, and ISO 10012 defines a measurement management system for the equipment and processes behind measurement. Most quality standards, including ISO 9001, ISO 13485, AS9100, and IATF 16949, have no separate calibration standard. They fold the calibration requirements into one clause on monitoring and measuring resources. So the requirements that apply to you follow your certification. A production shop certified to ISO 9001 works from clause 7.1.5. A medical device manufacturer works from ISO 13485 clause 7.6. A calibration laboratory works from ISO/IEC 17025. This is a starting point for understanding scope, not a substitute for the standard text or your assessor's interpretation. See also: Browse calibration requirements for all 15 standards (https://axiospec.com/standards) ### The requirements every standard shares Across ISO 9001, ISO/IEC 17025, ISO 13485, AS9100, and IATF 16949, the calibration expectations rhyme. If you can satisfy the five points below, you are close to what most auditors look for, whatever the clause number. - Calibrate or verify against traceable standards. Equipment that affects the validity of results is calibrated or verified against a reference with a documented link to a national or international standard (the SI), or to a stated basis where no standard exists. - Do it at defined intervals. Each instrument has a calibration interval set on a documented basis, not left to chance. - Identify calibration status. Anyone can tell whether an instrument is in calibration, due, or out of service, so nobody unknowingly uses equipment that is out of date. - Safeguard against invalidating adjustments. Settings and adjustments that would invalidate the calibration are protected. - Act when something is found out of tolerance. When an instrument is found out of calibration, you assess and record the validity of previous results and act on any affected product or measurements. Records are retained throughout. Tip: The differences between standards are mostly in emphasis and record depth, not in the underlying principle. A single traceable, tamper-evident calibration record can satisfy several standards at once. ### ISO 9001: clause 7.1.5 ISO 9001:2015 places calibration in clause 7.1.5, Monitoring and measuring resources. Clause 7.1.5.1 requires that the resources you use to verify conformity are suitable, maintained to stay suitable, and supported by retained records. Clause 7.1.5.2, Measurement traceability, applies when traceability is a requirement or you consider it essential: instruments are calibrated or verified against standards traceable to international or national standards (or the basis is recorded), identified to determine their status, and safeguarded against adjustments that would invalidate them. When an instrument is found unfit, ISO 9001 expects you to determine whether previous measurement results were affected and take appropriate action. See also: ISO 9001 calibration requirements and software (https://axiospec.com/standards/iso-9001) ### Can you calibrate in-house under ISO 9001? Yes. ISO 9001 does not require an outside laboratory, and it does not require the lab you use to be accredited. Clause 7.1.5.2 requires that instruments are calibrated against standards traceable to international or national standards. You can meet that in-house if the reference standards you calibrate against were themselves calibrated by a traceable source, so the chain back to the SI stays unbroken. In practice, an auditor reviewing in-house calibration looks for four things: a documented procedure for each type of calibration you perform, evidence that the people doing the work are competent, current certificates for your reference standards showing their traceability, and a record of each in-house calibration with the readings, the standard used, and the result. External accredited calibration still earns its keep for your reference standards themselves, for instruments that need tight uncertainty, and for customers who ask for ISO/IEC 17025 certificates. Most programs land on a mix: reference standards go out to an accredited lab, and working instruments are calibrated in-house against them. Axiospec tracks both in one place. In-house events record the reference standard used, and instruments on external calibration carry the vendor, the scheduled date, and an out-for-calibration status, so nothing disappears into a courier box. See also: ISO 9001 calibration requirements and software (https://axiospec.com/standards/iso-9001) See also: Metrological traceability explained (https://axiospec.com/guides/metrological-traceability-explained) ### ISO/IEC 17025: clauses 6.4 and 6.5 ISO/IEC 17025:2017 is the standard for the competence of testing and calibration laboratories, so its calibration requirements are the most detailed. Clause 6.4, Equipment, requires that equipment affecting results is calibrated, uniquely identified, labeled with its calibration status, and supported by records of every calibration, intermediate check, and adjustment. Clause 6.5, Metrological traceability, requires that measurements are traceable to the SI through an unbroken chain of calibrations, each contributing to the measurement uncertainty. Because a 17025 lab issues results that others rely on, its record and uncertainty requirements go beyond what a production ISO 9001 site needs. See also: ISO/IEC 17025 calibration software and traceability (https://axiospec.com/standards/iso-17025) ### ISO 13485: clause 7.6 ISO 13485:2016 covers quality management for medical devices, and clause 7.6, Control of monitoring and measuring equipment, carries the calibration requirements. Equipment is calibrated or verified at defined intervals against standards traceable to international or national standards (with the basis recorded where none exists), adjusted as necessary, identified to determine its status, and safeguarded from adjustments that would invalidate results. When equipment is found not to conform, you assess and record the validity of previous results and take action on the equipment and any affected product. Records are maintained throughout. See also: ISO 13485 calibration requirements and clause 7.6 (https://axiospec.com/standards/iso-13485) ### AS9100: aerospace, on top of ISO 9001 AS9100D uses ISO 9001:2015 as its base, so calibration still lives in clause 7.1.5, but aerospace adds expectations that matter at audit. Suppliers are expected to control measuring equipment tightly, maintain a register with recall so out-of-calibration equipment can be found and evaluated, account for the environmental conditions of measurement, and keep the records primes and Nadcap assessors ask for. See also: AS9100 calibration management software (https://axiospec.com/standards/as9100) ### IATF 16949: automotive, with MSA IATF 16949:2016 sits on ISO 9001 and adds automotive requirements. Alongside calibration and verification records (clause 7.1.5.2.1) and requirements for external calibration laboratories (clause 7.1.5.3), it calls for measurement systems analysis, clause 7.1.5.1.1, to study the variation in your measurement systems, typically through Gage R&R studies. See also: IATF 16949 calibration and MSA support (https://axiospec.com/standards/iatf-16949) ### ISO 10012: a measurement management system ISO 10012:2003 is not a certification most companies pursue on its own, but it is the reference for a measurement management system. It defines metrological confirmation (the calibration plus the verification that an instrument is fit for its intended use) and the control of measurement processes. It is a useful framework when you want your calibration program to be systematic rather than ad hoc. See also: ISO 10012 measurement management (https://axiospec.com/standards/iso-10012) ### How often does equipment need to be calibrated? No standard sets a universal interval. They require calibration at defined intervals and expect the interval to have a documented, defensible basis rather than a number pulled from the air. Common inputs are the manufacturer's recommendation, how the instrument is used and how critical its measurements are, its history of staying in tolerance, and any regulatory or customer requirement. A risk-based, reliability-informed interval is easier to defend than a flat one-year default. Axiospec shows the as-found in-tolerance rate and, once an instrument has come back out of tolerance, computes a reliability-based recommended interval from each instrument's own calibration history so the number has evidence behind it, but the interval you set stays your decision. See also: Free calibration interval calculator (https://axiospec.com/tools/calibration-interval-calculator) ### How Axiospec helps you meet these requirements Axiospec is one system for the requirements these standards share. It keeps a live calibration status on every instrument, records the reference standard and certificate behind each calibration so traceability is visible, and writes every event to a tamper-evident ledger with timestamps and e-signatures. When an instrument is found out of tolerance, you reverse-trace a drifted reference standard to every calibration it stood behind. The calibration form and certificate adapt to the standards you select, and you can export a complete, audit-ready pack for any instrument in one click. Whether you pass an audit still depends on your processes, scope, and assessor. Axiospec helps you produce clean, traceable, defensible records so that part is not the problem. See also: See it in a live demo, no signup (https://axiospec.com/demo) See also: See plans and pricing (https://axiospec.com/pricing) ### Common questions Q: What does ISO 9001 require for calibration? A: Clause 7.1.5 covers monitoring and measuring resources. Where measurement traceability is a requirement, equipment must be calibrated or verified at defined intervals against standards traceable to international or national measurement standards, identified so its calibration status can be determined, and safeguarded from adjustments that would invalidate the results. When equipment is found unfit, you must determine whether previous measurement results were affected and take appropriate action. Records of the basis for calibration must be retained. Q: How is ISO/IEC 17025 different from ISO 9001 on calibration? A: ISO 9001 treats measuring equipment as something to keep controlled, traceable, and recallable. ISO/IEC 17025 goes considerably further because the laboratory's product is the measurement itself. Clause 6.4 covers equipment and its records, clause 6.5 covers metrological traceability, and clause 7.8 sets what a calibration certificate must contain, including measurement uncertainty and, where conformity is stated, the decision rule. A 17025 record carries the uncertainty and decision rule that a 9001 record generally does not. Q: What does ISO 13485 clause 7.6 require? A: Clause 7.6 mirrors the ISO 9001 requirement but is stricter about the consequences of failure, which suits medical devices. Equipment must be calibrated or verified at specified intervals against traceable standards, with the basis recorded where no such standard exists, and must be protected from adjustments that would invalidate results. When equipment is found not to conform, you must assess and record the validity of previous measuring results and take action on the equipment and any product affected. Q: What do AS9100 and IATF 16949 add? A: Both build on ISO 9001 clause 7.1.5 rather than replacing it. AS9100 adds aerospace expectations around recall of equipment found out of calibration and around the records a prime or a customer can ask to see. IATF 16949 adds the automotive measurement systems analysis expectations, so Gage R&R, bias, linearity, and attribute agreement studies sit alongside the calibration records, and it expects calibration records to carry readings and traceability in more detail than ISO 9001 alone asks for. --- ## How to set calibration intervals https://axiospec.com/guides/how-to-set-calibration-intervals Last updated: 2026-09-06 How to determine and justify a calibration interval: manufacturer guidance, risk and usage, reliability from your own as-found history, and what auditors look for. No standard tells you to calibrate every twelve months. They require calibration at defined intervals and expect the interval to have a documented, defensible basis. This guide explains how to set that interval, refine it with your own data, and defend it at audit. ### Why there is no universal interval A calibration interval is how often an instrument is recalibrated. No quality standard sets a fixed number. ISO 9001, ISO/IEC 17025, ISO 13485, AS9100, and IATF 16949 all require calibration at defined intervals and expect the interval to rest on a documented basis rather than a habit. A flat one-year default is common, but it is weak to justify and often either wastes money on stable instruments or lets critical ones drift too long. The right interval balances the cost and downtime of calibrating against the risk of using an instrument that has drifted out of tolerance since its last calibration. See also: What each ISO standard requires for calibration (https://axiospec.com/guides/iso-calibration-requirements) ### The inputs that set a defensible interval Whatever method you use, these are the factors that justify an interval. Record which ones drove your decision so the interval holds up when an assessor asks. - Manufacturer guidance. The maker's recommended interval is a reasonable starting point, especially before you have history. - How critical the measurement is. Tighter tolerances and higher product or safety risk argue for shorter intervals. - How the instrument is used. Heavy use, harsh environments, transport, and shop-floor handling all shorten the interval an instrument can safely hold. - Its own history. How often the instrument has come back in or out of tolerance at calibration is the strongest evidence of how long it can hold its interval. - Regulatory or customer requirements. A contract or regulation may fix a maximum interval regardless of your analysis. ### Method 1: Start from guidance, then refine When an instrument is new and you have no history, start from the manufacturer's recommended interval plus any customer or regulatory requirement, then adjust as data accumulates. Recognized interval-analysis frameworks such as NCSLI RP-1 and ILAC-G24 describe this approach. It is defensible on day one and gets better as you gather results. ### Method 2: A reliability-based interval from your own data Once you have several calibrations for an instrument, set the interval so a target in-tolerance reliability is maintained, for example keeping at least 90 to 95 percent of calibrations in tolerance as-found. If too many come back out of tolerance, the interval is too long and you shorten it. If an instrument is reliably in tolerance calibration after calibration, the interval may be safely lengthened, saving cost and downtime. This is the most defensible method because the number comes from the instrument's own behavior. Axiospec shows each instrument's as-found in-tolerance rate on the asset, and once something has come back out of tolerance it computes a reliability-based recommended interval against a 90 percent in-tolerance target, so the evidence sits next to the asset. The interval you set stays your decision. See also: Free calibration interval calculator (reliability target) (https://axiospec.com/tools/calibration-interval-calculator) ### Watch drift, not just pass or fail An instrument that passes every calibration but drifts steadily toward its tolerance limit is telling you the interval is getting risky before it ever fails. Charting the as-found reading against the tolerance band over time surfaces that trend early, so you can shorten the interval before an out-of-tolerance event affects product. See also: Free drift rate and interval calculator (https://axiospec.com/tools/drift-rate-interval-calculator) ### Adjusting intervals up and down Intervals are not set once. Lengthen them when history clearly supports it, to cut cost and downtime. Shorten them after an out-of-tolerance result, when an instrument is used harder, or when the measurement becomes more critical. The important part for an audit is that each change has a recorded basis, so the interval is never an unexplained number. ### What auditors look for An assessor is not checking for a specific interval. They are checking that you have a documented, consistently applied basis for the intervals you set, that you review them against each instrument's history rather than leaving them fixed forever, and that you act when equipment is found out of tolerance. A calibration record that carries the interval, the basis, and the as-found and as-left readings answers all three. See also: Calibration requirements by ISO standard (https://axiospec.com/guides/iso-calibration-requirements) ### How Axiospec helps Axiospec shows the as-found in-tolerance rate and, once an instrument has come back out of tolerance, computes a reliability-based recommended interval and charts drift from each instrument's own calibration history, sets the next due date automatically from the interval and last calibration, and surfaces what is due, due soon, and overdue on a Due Calendar. Every interval and the basis for it lives on a tamper-evident record. The analysis is advisory, so the call stays yours. See also: See it in a live demo, no signup (https://axiospec.com/demo) See also: See plans and pricing (https://axiospec.com/pricing) ### Common questions Q: How do you choose a calibration interval? A: Start from the manufacturer's recommended interval plus any customer or regulatory requirement, then refine it with your own calibration history. The factors that justify an interval are manufacturer guidance, how critical the measurement is, how hard the instrument is used, its own in-tolerance history, and any contractual or regulatory maximum. Record which of these drove the decision. An assessor is not checking for a specific number. They are checking that you have a documented, consistently applied basis for it. Q: Is a calibration interval required to be 12 months? A: No. No quality standard sets a fixed number. ISO 9001, ISO/IEC 17025, ISO 13485, AS9100, and IATF 16949 all require calibration at defined intervals and expect the interval to rest on a documented basis rather than a habit. A flat one-year default is common but weak to justify, and it often either wastes money on stable instruments or lets critical ones drift too long. Q: What is a reliability-based calibration interval? A: A reliability-based interval is set so a target in-tolerance rate is maintained, for example keeping at least 90 to 95 percent of calibrations in tolerance as-found. If too many come back out of tolerance, the interval is too long and you shorten it. If an instrument is reliably in tolerance calibration after calibration, the interval may be safely lengthened, saving cost and downtime. This is the most defensible method because the number comes from the instrument's own behavior. Recognized frameworks such as NCSLI RP-1 and ILAC-G24 describe the approach. Q: Can you extend a calibration interval, and how do you defend it? A: Yes. Intervals are not set once. Lengthen them when the instrument's own history clearly supports it, and shorten them after an out-of-tolerance result, when the instrument is used harder, or when the measurement becomes more critical. The part that matters at audit is that each change has a recorded basis, so the interval is never an unexplained number. A calibration record carrying the interval, the basis, and the as-found and as-left readings answers what an assessor asks. Q: Why watch drift instead of just pass or fail? A: An instrument that passes every calibration but drifts steadily toward its tolerance limit is telling you the interval is getting risky before it ever fails. Charting the as-found reading against the tolerance band over time surfaces that trend early, so you can shorten the interval before an out-of-tolerance event affects product. A pass or fail alone hides that movement entirely. --- ## Metrological traceability, explained https://axiospec.com/guides/metrological-traceability-explained Last updated: 2026-09-06 What metrological traceability means, how the calibration chain to NIST and the SI works, and what "NIST traceable" really proves. Metrological traceability is what lets you say a measurement is trustworthy, not just a number on a screen. It is the documented, unbroken chain of calibrations that ties your instrument back to a national or international reference, with a stated uncertainty at every step. This guide explains the traceability chain in plain terms, what "traceable to NIST" actually means, and how to check that your own certificates hold up. ### What metrological traceability actually is Metrological traceability is a property of a measurement result, not of an instrument or a lab. The international vocabulary of metrology (VIM, published as JCGM 200) defines it as the property of a result whereby the result can be related to a reference through a documented, unbroken chain of calibrations, each contributing to the measurement uncertainty. Read that definition slowly, because every word earns its place. "Documented" means the chain is written down and can be produced on request. "Unbroken" means there are no gaps where you simply trust that something was fine. "Chain of calibrations" means each link is an actual calibration against a better reference. And "each contributing to the measurement uncertainty" means traceability and uncertainty travel together. You cannot have one without the other. In practice, traceability is what turns a reading into evidence. When an auditor asks how you know your caliper reads correctly, the answer is not that it looks right. The answer is the chain. - It describes a result, established through the instrument that produced it, not a brand or a sticker. - It requires a reference to relate the result back to, usually the relevant SI unit. - It requires documentation you can actually produce, not an assumption. - It carries an uncertainty that grows as you move down the chain. ### The traceability chain, link by link The chain is a hierarchy. Your working instrument is calibrated against a reference standard. That reference standard is itself calibrated by a calibration laboratory. That laboratory maintains its own standards traceable to a national metrology institute, such as NIST in the United States, and the national institute realizes the SI unit itself. Each arrow in that path is a calibration with its own certificate and its own uncertainty. A useful way to picture it: the further you sit from the SI unit, the more accumulated uncertainty you carry. That is normal and expected. The point of the chain is not zero uncertainty, it is known and stated uncertainty at every level, so you can decide whether an instrument is good enough for the job in front of you. - Working instrument (the caliper, gauge, or meter you use day to day) - Reference or transfer standard (a better instrument used to check the working one) - Calibration laboratory, ideally ISO/IEC 17025 accredited for the specific measurement - National metrology institute, for example NIST in the US - The SI unit itself, as realized by the national or international system Tip: Traceability is only as strong as its weakest link. One undocumented step anywhere in the chain breaks traceability for everything below it. ### Why measurement uncertainty is part of the deal Traceability without a stated uncertainty is incomplete. A certificate that reports a result but no uncertainty has told you where the pointer landed without telling you how sharp the pointer is. You cannot judge conformance, and you cannot compare it against your tolerance. Every calibration in the chain adds uncertainty. The reference standard is not perfect, the comparison process is not perfect, and the environment is not perfect. A good calibration certificate accounts for these contributions and reports a combined uncertainty, usually as an expanded uncertainty at a stated coverage. When you then use that instrument, its uncertainty flows into the uncertainty of your own measurements. This is why chasing the most accurate lab is less useful than matching uncertainty to your tolerance. If your process tolerance is wide relative to the instrument uncertainty, you have margin. If it is tight, the uncertainty budget deserves real attention. ### What does "NIST traceable" mean? The myth to avoid "NIST traceable" is one of the most misused phrases in calibration. NIST is the national metrology institute for the United States, so a legitimate US traceability chain will often lead back to NIST. But the phrase on its own is a claim, not proof. A certificate stamped "NIST traceable" does not automatically demonstrate traceability. What actually matters is the substance behind the claim: an unbroken, documented chain of calibrations, each with a stated uncertainty, performed by competent labs. NIST itself has long cautioned that traceability is established by the evidence, not by a phrase, and that no single label guarantees it. The strongest evidence you can look for is calibration by an ISO/IEC 17025 accredited laboratory whose accreditation scope covers the specific measurement, because accreditation involves independent assessment of both the traceability and the reported uncertainty. Even then, be precise in your own records: traceability is demonstrated by the documented chain, and conformance or accreditation status is determined by an accreditation body or assessor, never by a sticker or by software. Tip: Treat "NIST traceable" as a claim to verify, not a conclusion. Ask for the reference standard, its certificate, the accreditation, and the uncertainty behind it. ### How a calibration lab demonstrates traceability (ISO/IEC 17025) If you use an external lab, ISO/IEC 17025 is the standard that defines how they establish traceability. Clause 6.5 of ISO/IEC 17025 requires the laboratory to ensure that measurement results are traceable to the SI through a documented, unbroken chain of calibrations, each contributing to the measurement uncertainty. The standard points to specific acceptable routes for that traceability: calibrations provided by a competent laboratory (accreditation is the usual way competence is demonstrated), or values from a national metrology institute, or, where those are not possible, certified reference values from a competent producer. In short, an accredited lab is not just asserting traceability, it is following a defined framework and is periodically assessed against it. See also: ISO/IEC 17025 for calibration, explained (https://axiospec.com/standards/iso-17025) See also: Calibration requirements by ISO standard (https://axiospec.com/guides/iso-calibration-requirements) ### How to check your own calibration certificate shows traceability You do not need to be a metrologist to sanity-check a certificate. You are looking for the pieces that make the chain visible and the result usable. If any of them are missing, the traceability claim is weaker than it looks, and it is fair to ask the provider for the rest. - The reference standard used, identified specifically enough that you could trace it (an ID or asset number, not just a master standard). - Evidence that the reference standard is itself in calibration, ideally a reference to its own certificate. - The accreditation behind the calibration, including the accreditation body and, ideally, that the measurement falls inside the lab's accredited scope. - A stated measurement uncertainty for the reported results, with a coverage factor or confidence level. - The calibration date, environmental conditions where relevant, and a clear statement of what was measured. Tip: If a certificate reports results with no uncertainty at all, that is a red flag on its own, regardless of any traceability wording. ### How Axiospec keeps the chain on the asset Traceability tends to break down in the filing cabinet, not in the lab. The calibration was fine, but two years later nobody can find which reference standard was used or where its certificate went. Axiospec is built so the chain lives on the asset itself. When you log a calibration, you record the reference standard used, a link to its certificate, and the provider that performed the work, so the evidence of the chain is attached to the instrument and to the specific event, not scattered across emails and PDFs. That means when an auditor asks how you know a reading is trustworthy, you can show the chain from the asset in a few clicks. It also works in reverse. If a reference standard is later found to be out of tolerance, you can trace forward to the measurements it stood behind and review what may be affected, instead of guessing. This is advisory and evidentiary: Axiospec organizes and surfaces the chain you have built, and helps you spot gaps, but it does not determine conformance or accreditation status. That judgment belongs to your assessor or accreditation body. See also: See a traceable calibration record in the demo (https://axiospec.com/demo) See also: How to log a calibration in Axiospec (https://axiospec.com/guides/logging-a-calibration) ### Common questions Q: What does metrological traceability actually mean? A: Metrological traceability is an unbroken chain of documented calibrations linking your measurement back to a recognized reference, normally an SI unit realized by a national metrology institute such as NIST. Each link in the chain has a stated measurement uncertainty, and the uncertainties accumulate as you move down from the national standard to the working instrument on your floor. Traceability is a property of a measurement result, not a badge a company holds. Q: What does NIST traceable really prove? A: Less than most buyers assume. The phrase only means something when the certificate shows the actual chain: the reference standard used, its own calibration certificate number, the calibrating laboratory, and the measurement uncertainty at each stated point. A certificate that says NIST traceable with no reference standard identified and no uncertainty stated is a marketing phrase, not evidence. NIST does not certify or endorse companies, so any claim of being a NIST certified or NIST approved provider is a red flag. Q: What should I check before approving a calibration supplier? A: Ask for the scope of accreditation, not just the certificate. A laboratory is accredited for specific measurement quantities, ranges, and uncertainties, and work outside that scope is not covered even though the lab is genuinely accredited. Check that the accreditation is current and issued by a recognized body, that the specific parameter and range you need appear on the scope with a stated calibration and measurement capability, that the certificates they issue carry the reference standard and its certificate number, that measurement uncertainty is stated at each point, and that the decision rule behind any pass statement is on the certificate. Q: Does an accredited lab mean every calibration it does is accredited? A: No, and this catches people out. Accreditation is granted against a defined scope covering particular measurement quantities, ranges, and uncertainty capabilities. The same laboratory can perform work outside that scope, and that work is not accredited even though the company is. Certificates normally distinguish the two, so read which category yours falls into rather than assuming the accreditation logo covers everything on the page. --- ## Calibration certificate requirements: what a certificate must contain https://axiospec.com/guides/calibration-certificate-requirements Last updated: 2026-09-06 The required elements of a calibration certificate under ISO/IEC 17025 clause 7.8, what as-found and as-left readings and uncertainty mean, and how to read one you receive. A calibration certificate is the objective evidence that an instrument was calibrated, and it is the first document an auditor asks to see. This guide covers what a certificate must contain, based on ISO/IEC 17025 clause 7.8, what the key parts mean (as-found and as-left readings, measurement uncertainty, the decision rule), and how to read a certificate you receive from a vendor. ### What a calibration certificate is, and why it matters A calibration certificate is the record that documents a single calibration event: it states what instrument was calibrated, against what reference, on what date, with what results, and how confident you can be in those results. It is the objective evidence that the calibration actually happened and what it found. It matters because it is the primary artifact of a calibration program. When an auditor reviews your equipment, the certificate is what they ask for to confirm an instrument is in calibration, traceable, and fit for use. A missing, incomplete, or unclear certificate is one of the most common calibration findings, so knowing what a good one contains is worth the few minutes it takes. Tip: A certificate documents one calibration event at a point in time. It is not a warranty that the instrument will stay in tolerance until its next due date; that is what the calibration interval and status tracking are for. ### The required elements (ISO/IEC 17025 clause 7.8) ISO/IEC 17025:2017, the standard for the competence of testing and calibration laboratories, sets out reporting requirements in clause 7.8. Clause 7.8.2 lists the common information a report must contain, and clause 7.8.4 adds the requirements specific to calibration certificates. Taken together, a calibration certificate should include the items below. Even if your instruments are calibrated in-house rather than by an accredited lab, this is a sound checklist for a complete record. The exact wording and clause numbering are in the standard itself; treat this as a practical summary, not a substitute for the standard text or your assessor's interpretation. 1. A title (for example, Calibration Certificate) and a unique identification of the certificate, such as a certificate number, with each page identified so pages cannot be mixed up. 2. The name and address of the laboratory that performed the calibration, and the location where it was performed if different. 3. Unique identification of the item calibrated: a description, manufacturer, model or type, and serial number or your asset ID, along with its condition where relevant. 4. The date of the calibration. Certificates commonly also show the date the item was received and the date the certificate was issued. 5. The calibration method or procedure used to perform the work. 6. The measurement results with their units of measurement, typically reported as-found (before any adjustment) and as-left (after adjustment). 7. The measurement uncertainty of the results, stated in the same units as the measurand (17025 requires uncertainty to be reported for calibration results). 8. A metrological traceability statement: the reference standards used and how the results are traceable, usually to the SI through an unbroken chain of calibrations. 9. The environmental conditions (such as temperature and humidity) where they affect the validity of the results. 10. A statement of conformity and the decision rule applied, when a pass/fail or in-tolerance statement against a specification is given. 11. The name, function, and signature or equivalent authorization of the person(s) approving the certificate. Tip: If a certificate is missing traceability, uncertainty, or a clear identification of the item, those are exactly the gaps an assessor tends to catch. Check for them before you file it. See also: ISO/IEC 17025 calibration software and traceability (https://axiospec.com/standards/iso-17025) See also: Calibration requirements by ISO standard (https://axiospec.com/guides/iso-calibration-requirements) ### As-found and as-left readings, and why both belong on the certificate As-found is the reading the calibration technician recorded before making any adjustment, and as-left is the reading after adjustment. A certificate that shows both tells the full story of the visit rather than just the final state. The as-found data is what protects you when an instrument comes back out of tolerance. If it was reading out of spec before adjustment, you have to ask what measurements or product that instrument touched since its last good calibration, and act on anything affected. Without an as-found value you cannot make that assessment, which is why standards expect you to evaluate the validity of previous results when an instrument is found unfit. As-left readings confirm the instrument was returned to within tolerance (or, for a pass with no adjustment, that as-found and as-left are the same). When no adjustment was needed, a certificate may simply report the readings once and state that no adjustment was made. - As-found: the state of the instrument on arrival, before adjustment. Drives your assessment of past measurements if it is out of tolerance. - As-left: the state after any adjustment. Confirms the instrument is fit to return to service. - No adjustment made: as-found and as-left are effectively the same, and the certificate should say so. See also: As-found vs as-left: what the readings mean (https://axiospec.com/guides/as-found-as-left-readings) ### Measurement uncertainty and the decision rule No measurement is exact. Measurement uncertainty is the quantified doubt about a result, the range within which the true value is expected to lie, usually reported at a stated coverage (commonly a coverage factor k=2, roughly 95 percent). A calibration result on a 17025 certificate is expected to carry its uncertainty, because a value without an uncertainty cannot be properly compared against a tolerance. That comparison is where the decision rule comes in. When a certificate states conformity (a pass, fail, or in-tolerance statement against a specification), the decision rule is the documented way uncertainty is taken into account in making that statement. A simple decision rule compares the result directly to the tolerance limits; a guard-banded rule narrows the acceptance limits by some portion of the uncertainty to reduce the risk of a false accept. ISO/IEC 17025 requires that when a statement of conformity is made, the decision rule is documented and the statement identifies which results it applies to. The practical point: a decision rule and a guard band manage the risk of calling something in tolerance when it might not be. The specifics belong to the calibrating lab and your own risk tolerance, so this is background for reading a certificate, not a rule Axiospec sets for you. Tip: If a certificate gives a pass/fail statement, look for the decision rule behind it. A pass under a strict guard-banded rule carries less risk than a bare comparison to the limits. See also: Metrological traceability, explained (https://axiospec.com/guides/metrological-traceability-explained) ### Accredited vs non-accredited certificates An accredited calibration certificate is issued by a laboratory that has been assessed by an accreditation body (for example, a signatory to the ILAC arrangement) and found competent to perform that specific calibration. Such a certificate carries the accreditation body's mark or logo, the lab's accreditation number, and the calibration falls within the lab's published scope of accreditation. That scope, and the mark, are what make it accredited. A non-accredited certificate can still be perfectly valid and traceable; it simply does not carry third-party accreditation for that measurement. Whether you need accredited calibration depends on your own requirements and your customers'. Some contracts and standards call for accredited calibration of certain equipment; others accept traceable in-house calibration. Accreditation is granted by an accreditation body assessing a laboratory, never by software. No tool, including Axiospec, can make a certificate accredited. Software can capture and organize the certificate; only the accredited lab and its accreditation body can confer accreditation. - Accredited: carries the accreditation body's mark, the lab's accreditation number, and the calibration is within the lab's scope of accreditation. - Traceable but not accredited: results are traceable to the SI, but the specific measurement is not covered by third-party accreditation. - Check your requirement: confirm whether your standard, regulator, or customer requires accredited calibration for a given instrument before assuming a non-accredited certificate is enough. ### How to read a vendor's certificate: what to check When a certificate comes back from an external calibration lab, do not just file it. A quick review catches the problems that would otherwise surface at your next audit, when it is harder to fix. - Identity: does the certificate name your exact instrument, by manufacturer, model, and serial number or asset ID? A certificate for the wrong serial number is a common and costly mix-up. - Dates: is the calibration date present, and does it fit your interval so you can set the correct next-due date? - Results and units: are as-found and as-left readings shown, with units, and is anything flagged out of tolerance? - Uncertainty: is a measurement uncertainty reported for the results? - Traceability: does it state the reference standards used and that the results are traceable to national or international standards (the SI)? - Conformity and decision rule: if it states a pass or in-tolerance result, is the decision rule identified? - Accreditation: if you require accredited calibration, does it carry the accreditation mark and is the measurement within the lab's scope? - Authorization: is it signed or otherwise authorized by a named, responsible person? Tip: If an as-found reading came back out of tolerance, that is your signal to assess the measurements and product that instrument touched since its last good calibration, not just to file the paperwork. ### How Axiospec generates a certificate from the record Axiospec captures the fields a good certificate needs as you log a calibration, then generates a Certificate of Calibration from the approved record in one click. The certificate is laid out in three sections: the instrument (tag, manufacturer, model, serial, location, interval), the calibration (performed date, result, nominal value, tolerance, as-found and as-left readings, reference standard, environment, certificate number), and the attestation (who performed it, the approval, and the approval time). It also carries the tamper-evident record hash from the ledger, so the document ties back to a specific, unaltered entry. When you select the standards your program follows, the calibration form and certificate adapt to capture the metrology and traceability fields those standards emphasize, so the record you build lines up with what your assessor expects to see. One honest limit: Axiospec produces and organizes the documentation, but it does not and cannot make a certificate accredited or guarantee an audit outcome. Accreditation is the accreditation body's determination about a laboratory, and conformity is your assessor's call. Axiospec's job is to make sure the record behind the certificate is complete, traceable, and defensible. Tip: An instrument needs at least one approved calibration before Axiospec can produce its certificate, since the document reflects an approved ledger record. See also: Calibration requirements by ISO standard (https://axiospec.com/guides/iso-calibration-requirements) See also: See it in a live demo, no signup (https://axiospec.com/demo) ### Common questions Q: What has to be on a calibration certificate under ISO/IEC 17025? A: Clause 7.8 sets the required elements. In practice a compliant certificate identifies the laboratory and the customer, uniquely identifies the certificate and the item calibrated, gives the date of calibration and the dates of receipt where relevant, names the method used, identifies the reference standards with their own traceability, reports the results with the measurement uncertainty, and is authorized by the person accepting responsibility for the content. Where a statement of conformity is given, clause 7.8.6 also requires the decision rule to be documented and stated. Q: Does a calibration certificate have to state measurement uncertainty? A: For an ISO/IEC 17025 accredited calibration, yes. The uncertainty is what makes the result usable, because without it you cannot tell whether a reading near a limit is really inside it. Certificates from a supplier working to ISO 9001 alone often omit uncertainty, which is one of the practical differences between buying an accredited calibration and buying a calibration. Q: What is a decision rule on a calibration certificate? A: A decision rule is the documented policy that turns a measured value and its uncertainty into a pass or fail statement. It says how much of the uncertainty is taken into account before conformity is declared, for example by subtracting the expanded uncertainty from the tolerance limit. ISO/IEC 17025 requires the rule to be documented, agreed with the customer, and stated on the certificate whenever a statement of conformity is given, so the reader can see what produced the word pass. Q: How do I read a calibration certificate I received? A: Read it in two steps. First look at the as-found column. If every point is inside the tolerance limits, the instrument was still measuring correctly through the whole period since its last calibration, and the measurements it made in that period stand. If any as-found point is outside the limits, the instrument was reading wrong for some unknown part of that interval and you need an impact assessment. Then check the as-left column to confirm the instrument left calibration inside tolerance. Also confirm the reference standard, its certificate number, the stated uncertainty, and the decision rule are all present. --- ## How to migrate calibration data without losing history https://axiospec.com/guides/how-to-migrate-calibration-data Last updated: 2026-07-27 A step-by-step plan for migrating calibration data from a spreadsheet or legacy system: export what you have, import your registry, bring calibration history and certificates over, and verify everything landed. Migrating calibration data is the part of switching tools that teams dread, and it is why so many quality programs stay on software or spreadsheets they have outgrown. The good news: a calibration dataset is small by modern standards, it has a predictable shape, and the move usually fits in an afternoon once you know the order of operations. This guide walks the migration in five steps: export, registry, history, certificates, verify. It applies whether you are coming from a spreadsheet, GAGEpack, GAGEtrak, IndySoft, or something homegrown. ### The three layers of a calibration migration A complete migration moves three layers of data, and it helps to treat them separately. The first is the asset registry: the list of instruments with their tags, descriptions, serial numbers, locations, and calibration intervals. The second is the calibration history: the record of past events on each instrument, with dates, results, and who did the work. The third is the certificate files: the PDFs from your vendors or your own bench that back those events up. Most migrations move only the first layer and quietly abandon the other two, which is how an audit question like show me the last three calibrations for this gage ends up answered from a filing cabinet. Axiospec imports all three, and this guide covers each in turn. Tip: Decide up front how much history you need. Many teams bring full history for critical instruments and only the most recent calibration for the rest. Auditors care most about the current record and the chain behind recent decisions. ### Step 1: Export what you have, and keep a copy untouched Get your data out of the current system first. GAGEpack and GAGEtrak both export to CSV or Excel, and a spreadsheet already is the export. Other systems vary, so check yours, and if you cannot get a clean file out, send us whatever it does produce. Pull three things: the instrument list, the calibration event history if your system can produce one, and the folder of certificate PDFs. Make one copy of the raw export and never edit it. Do all cleanup in a working copy. If anything looks off after the move, the untouched original is your reference for what the old system actually said. Tip: Keep the old system read-only but accessible until the migration is verified. You want it as a reference, not as a live system two people are still updating. See also: Coming from GAGEpack? Start here (https://axiospec.com/compare/gagepack-alternative) See also: Coming from GAGEtrak? Start here (https://axiospec.com/compare/gagetrak-alternative) ### Step 2: Import your asset registry first The registry goes first because everything else attaches to it. Axiospec's Bulk Import reads your CSV or Excel file, suggests a column mapping from your headers, and checks every row of a CSV or TSV before you commit, showing how many are ready and how many will be skipped and why. Excel files get a five-row preview and are checked on the server as they import. Imperfect data does not block you. Soft problems, like an unrecognized date format or a blank optional field, come through as warnings you can fix later; only genuinely broken rows are skipped, and the importer tells you which and why. If a row matches an asset tag that already exists, you choose what happens: skip it, update the existing asset, or stop and review. See also: Full walkthrough: import your asset registry (https://axiospec.com/guides/importing-your-registry) See also: Try it right now: the live demo runs this exact import wizard on your own file, no signup (https://axiospec.com/demo) ### Step 3: Bring your calibration history over History is the layer teams assume they will lose, and the reason many never switch. In Axiospec it is a first-class import: one row per past calibration event, with the asset tag, the date, the result, the certificate number if you have one, and the technician who did the work. One detail worth knowing: the record's performer is whoever ran the import, and the original technician is carried as record data. Each row becomes a real record on that instrument's timeline, not a note pasted into a comment field. Once history is in, each instrument's next due date is computed from its most recent calibration and its interval, so your schedule picks up exactly where the old system left off instead of restarting from the import date. See also: How a calibration is logged going forward (https://axiospec.com/guides/logging-a-calibration) ### Step 4: Attach certificate PDFs in bulk Certificates do not have to be attached one instrument at a time. Axiospec's bulk certificate upload takes a whole folder at once, matches filenames against your asset tags, and shows you the matches for review before anything is registered. Files it cannot match automatically, you match by hand in the same review screen, and the rest upload in parallel. Tip: A consistent naming scheme like TAG-0142_2026-03-14.pdf makes matching nearly automatic. If your old system exports certificates in bulk, have it name the files by asset tag. ### Step 5: Verify the move, and undo if something is wrong Verification is a short checklist, not a leap of faith. Compare instrument counts per site against your untouched export. Spot-check five to ten critical instruments end to end: the due date, the current status, the most recent calibration event, and that its certificate opens. Then skim the Due Calendar for anything obviously wrong, like half the shop coming due the same week. If a mapping was wrong, you do not hand-fix hundreds of records. A registry load lands as one batch an admin can undo from the dashboard, so the recovery path there is undo, fix the file, and run it again. A calibration history load is not batched that way, so fix and re-import only the rows that failed. Large imports also resume where they left off if the upload is interrupted, rather than starting over. See also: Prove it at audit time: the audit pack export (https://axiospec.com/guides/audit-pack-export) ### Migrating from GAGEtrak, GAGEpack, or GageList All three export to CSV or Excel, and that export is all the importer needs. Column names differ between tools, but the import wizard suggests a mapping from your headers and lets you correct anything it guessed wrong before a single row is saved. The pattern is the same regardless of source: export the equipment or gage list first and import it as your registry, then export the calibration event history and import it as history. If your old tool exports certificates as PDFs, bring those in the bulk certificate step. And if the export looks complex, that is normal for a long-lived database; send it to us instead and we will map it for free. See also: Moving off GAGEtrak? What to look for (https://axiospec.com/compare/gagetrak-alternative) See also: Moving off GAGEpack? What to look for (https://axiospec.com/compare/gagepack-alternative) ### If you would rather not do any of this Every plan, including the free one, comes with free white-glove migration. Send us your export in whatever shape it is in, and the team maps and loads it for your review, usually within a couple of business days. It runs over email, asynchronously, and there is no call to schedule. If you are still deciding whether to switch at all, start with the live demo. It opens a working calibration program with no signup, so you can see what the end state looks like before you move a single row. See also: Deciding whether to switch at all? Start here (https://axiospec.com/blog/switching-calibration-software) See also: Still comparing tools? See the full comparison (https://axiospec.com/compare/best-calibration-management-software) See also: See the end state in the live demo, no signup (https://axiospec.com/demo) --- ## The calibration audit prep checklist https://axiospec.com/guides/calibration-audit-prep-checklist Last updated: 2026-07-30 A working checklist for anyone who owns a calibration program. Fifty questions phrased the way an auditor tends to ask them, each with a one line picture of what a good answer looks like. Six universal sections plus supplements for ISO 9001, ISO/IEC 17025, AS9100, ISO 13485, and IATF 16949. Print this and walk your program with it. Each item is phrased the way an auditor tends to ask it, with a one line picture of what a good answer looks like. One honest note before you start: no checklist passes an audit, and no software does either. Audits are passed by the processes behind the answers, and your assessor makes the call. This list exists to help you find the gaps before your auditor does. Run through Part 1 first, whatever standard you follow, then add the Part 2 supplement that matches your certification. Do it four to six weeks before the audit so there is time to fix what you find, and give every unchecked box an owner and a date. The clause references are practical summaries, not a substitute for the standard text or your assessor's interpretation. ### Part 1, section 1: Equipment register - Can you produce a complete list of every instrument that affects product or result quality? Good: one live register, each instrument uniquely identified, nothing tracked on the side in a drawer or a personal spreadsheet. - Does every register entry match a physical instrument, and every instrument match an entry? Good: the tag on the bench matches the register, serial numbers agree, and a floor walk turns up no unlisted gages. - Are employee-owned and customer-owned instruments included when they are used to accept product? Good: a personal caliper used at final inspection appears on the register like any other gage. - Is there a defined way to add, retire, or quarantine an instrument? Good: retired equipment is marked out of service and physically controlled, not just deleted from the list. - Do indication-only or no-calibration-required instruments carry that status with a justification? Good: a recorded basis for each exemption, not an unlabeled gap an auditor finds first. ### Part 1, section 2: Due-date control - Does every active instrument have a calibration interval and a next-due date? Good: no blank interval fields, and the next-due date follows from the last calibration plus the interval. - Can you show the basis for the intervals you set? Good: manufacturer guidance, usage, criticality, or the instrument's own in-tolerance history, recorded, not habit. - Can you list everything due in the next 30, 60, and 90 days? Good: a due list anyone can pull in minutes, not a manual sweep of a spreadsheet. - Is anything overdue right now, and if so, is it out of use? Good: overdue equipment is identified, removed from service or quarantined, and the decision is recorded. - Are interval changes recorded with a reason? Good: each lengthening or shortening has a documented basis, such as repeated in-tolerance results or an out-of-tolerance event. See also: How to set calibration intervals (https://axiospec.com/guides/how-to-set-calibration-intervals) ### Part 1, section 3: Out-of-tolerance handling - When an instrument comes back out of tolerance, is there a defined response? Good: a documented procedure covering the instrument, the assessment of prior results, and product disposition. - Can you show a real out-of-tolerance event worked end to end? Good: the event, the impact assessment, the affected measurements or product, and the disposition, all on record. - Do calibration records capture as-found readings so an impact assessment is even possible? Good: as-found readings before adjustment and as-left readings after, on every event. Without as-found data you cannot judge past results. - Can you trace what a drifted instrument touched? Good: enough usage records to work back from a reference standard to every calibration it stood behind since its last good calibration. - If suspect product may have shipped, who decides on customer notification? Good: a named role and a recorded decision, not an assumption that someone else handled it. See also: As-found and as-left readings explained (https://axiospec.com/guides/as-found-as-left-readings) ### Part 1, section 4: Records integrity - Can you produce the complete calibration history for any instrument on request? Good: every calibration, check, and adjustment over the instrument's life, retrievable in minutes. - Does each record show who performed the work and who approved it? Good: attributable records with names, dates, and signatures or e-signatures. - Are records protected from silent edits and deletion? Good: changes are controlled and visible. A record cannot be quietly altered after the fact. - Are retention periods defined and actually met? Good: a stated retention period that satisfies your standard, customers, and regulators, and records that old really exist and are legible. - Are your calibration certificates complete? Good: instrument identity, date, method, results with units, as-found and as-left readings, uncertainty where required, a traceability statement, and an authorizing signature. See also: Calibration certificate requirements: what a certificate must contain (https://axiospec.com/guides/calibration-certificate-requirements) ### Part 1, section 5: Traceability chain - Can you name the specific reference standard behind any given calibration? Good: the record identifies the reference standard by ID, not master gage. - Are your reference standards themselves in calibration, with certificates on file? Good: each reference standard has a current certificate and its own documented traceability. - Does the chain reach a national or international measurement standard? Good: a documented, unbroken chain from working instrument to reference standard to an accredited lab or national metrology institute, with uncertainty stated at each link. - Do you review vendor certificates when they come back, before filing them? Good: a quick check of identity, dates, results and units, uncertainty, traceability, and signature. Problems are chased at receipt, not discovered at audit. - Where accredited calibration is required, is the work within the lab's accredited scope? Good: the certificate carries the accreditation body's mark and the measurement falls inside the lab's published scope. See also: Metrological traceability explained (https://axiospec.com/guides/metrological-traceability-explained) ### Part 1, section 6: Training and competence - Can you show who is authorized to perform calibrations, and on what basis? Good: a competence record for each person, tied to the types of calibration they perform. - Are training records current for the people doing the work today? Good: records match the current staff list. No calibrations are signed by people with no competence record. - Do documented procedures exist for in-house calibrations, and do records reference them? Good: a method for each calibration type, and records that cite the method actually used. - Does a named person own the calibration program? Good: one role responsible for the register, the schedule, and the response when something fails. ### Part 2 supplement: ISO 9001, clause 7.1.5 Add the supplement that matches your certification. These build on Part 1, they do not replace it. - Can you show that monitoring and measuring resources are suitable and maintained (7.1.5.1)? Good: retained records of fitness for purpose for the equipment behind conformity decisions. - Where traceability is required, is equipment calibrated or verified against traceable standards at defined intervals (7.1.5.2)? Good: every such instrument has a traceable calibration or verification on record, on schedule, or the basis is recorded where no standard exists. - Is calibration status identifiable on each instrument? Good: anyone at the bench can tell whether an instrument is in calibration, due, or out of service. - Is equipment safeguarded from adjustments that would invalidate results? Good: seals, access controls, or protected settings, and a record when a safeguard is broken. - When equipment is found unfit, do you determine whether previous results were affected? Good: a documented determination and the corrective action taken, every time. See also: ISO 9001 calibration requirements (https://axiospec.com/standards/iso-9001) ### Part 2 supplement: ISO/IEC 17025 - Is every equipment item that affects results uniquely identified and labeled with its calibration status (clause 6.4)? Good: labels current, register matching the bench, no ambiguity about the state of any item. - Are records kept of every calibration, intermediate check, and adjustment (clause 6.4)? Good: intermediate checks are recorded events with results, not undocumented habits. - Can you demonstrate metrological traceability to the SI through an unbroken chain of calibrations (clause 6.5)? Good: each link documented with its own certificate and its own contribution to measurement uncertainty. - Do reported results carry measurement uncertainty, and is your decision rule documented (clause 7.8)? Good: uncertainty stated with the result, and wherever you state conformity, the decision rule behind the statement is identified. - Are technical records attributable, protected from unauthorized change, and sufficient to repeat the work (clause 7.5)? Good: enough recorded detail to reconstruct the calibration, and no way to alter the record without a trace. See also: ISO/IEC 17025 calibration software (https://axiospec.com/standards/iso-17025) ### Part 2 supplement: AS9100, on top of ISO 9001 - Does your equipment register support recall? Good: when an instrument is found out of calibration you can find it, pull it, and evaluate what it touched, quickly. - Are environmental conditions recorded where they affect the measurement? Good: temperature and humidity captured when they matter, with the requirement defined in the method. - Will your records survive the retention your contracts require? Good: records legible, retrievable, and backed up for the life of the contract, which in aerospace can mean decades. - Can you produce the calibration evidence a prime or Nadcap auditor asks for, fast? Good: the complete history for any instrument in one pack, not a week of archaeology. See also: AS9100 calibration management (https://axiospec.com/standards/as9100) ### Part 2 supplement: ISO 13485, clause 7.6 - Are documented procedures in place for the control of monitoring and measuring equipment? Good: the procedure exists, is controlled, and matches what people actually do. - Is equipment calibrated or verified at specified intervals against traceable standards, with the basis recorded where none exists? Good: every interval and traceability basis on record, including the justification for any non-standard reference. - Is calibration status identified and equipment safeguarded, including during handling and storage? Good: visible status on each item, and protection against adjustment, damage, or deterioration that would invalidate results. - When equipment is found out of calibration, are validity assessments recorded and affected product acted on? Good: a recorded assessment of prior results, action on the equipment and any affected product, all retained. See also: ISO 13485 calibration requirements (https://axiospec.com/standards/iso-13485) ### Part 2 supplement: IATF 16949, section 7.1.5 - Do you have measurement systems analysis for the gauges in your control plan (7.1.5.1.1)? Good: statistical studies, typically Gage R&R, for each type of inspection and test equipment system named in the control plan, using methods your customer accepts. - Do calibration records cover every gauge that supports product conformity, including employee-owned and customer-owned equipment (7.1.5.2.1)? Good: no gauge used for acceptance is off the record because of who owns it. - Do records include as-received (as-found) and after-adjustment (as-left) readings? Good: both readings on the record for every calibration and verification event. - When a gauge is found out of calibration, is there evidence of risk assessment and customer notification where suspect product may have shipped? Good: the recorded disposition and the notification, with dates. - Do your external calibration labs meet 7.1.5.3.2? Good: accredited to ISO/IEC 17025 with the calibration in scope, or otherwise customer approved, with the evidence on file. See also: IATF 16949 calibration and MSA (https://axiospec.com/standards/iatf-16949) ### After the walkthrough Count your unchecked boxes and sort them into two piles: record gaps you can close before the audit, and process gaps that need a real fix. Fix the process gaps first. An auditor who finds a tidy record over a broken process will keep digging. And keep the honest framing. This checklist can show you where you stand. It cannot pass the audit for you, and neither can any tool. Your processes, your evidence, and your assessor decide that. Tip: Print this page and mark it up by hand. A checklist you can carry to the bench beats one that stays in a browser tab. ### About this checklist This checklist is published by Axiospec, a calibration management platform built by CaliTech LLC. It stands on its own. Use it with whatever you run today, paper, spreadsheet, or software. If the evidence side is where your program struggles, that is the part Axiospec handles: a live equipment register, due-date control, tamper-evident calibration records, and the traceability chain captured on each instrument. The free plan is the full platform for up to 50 active assets with unlimited users and no credit card. Axiospec documents your calibration program. It does not certify compliance, and it never will. That call belongs to your assessor. See also: See a working program in the live demo, no signup (https://axiospec.com/demo) --- ## Guard Banding in Calibration Explained https://axiospec.com/guides/guard-banding-in-calibration Last updated: 2026-09-06 A guard band narrows your acceptance limits by a share of the measurement uncertainty so a borderline reading cannot be falsely passed. Plain definition, the common methods, how it connects to TUR and ISO/IEC 17025 decision rules, and a worked example you can check with our free calculator. Guard banding is the practice of tightening your acceptance limits by a portion of the measurement uncertainty, so an instrument only passes when the reading, uncertainty included, truly sits inside tolerance. It is how calibration programs control the risk of a false accept, and it is the working mechanism behind most ISO/IEC 17025 decision rules. This guide gives you the plain definition, the common methods, a worked example with real numbers, and where the practice fits in an audit. ### What is a guard band? Guard banding, sometimes written as a single word, guardbanding, is how a calibration program keeps that uncertainty from deciding a borderline result by luck. Every calibration reading carries measurement uncertainty. When a reading lands close to a tolerance limit, that uncertainty means the true value could sit on either side of the limit, so a bare pass or fail comparison is a coin flip you are not acknowledging. A guard band closes that gap: you move the acceptance limit inward from the tolerance limit by an amount based on the uncertainty, and you make the pass or fail call against the tighter acceptance limit instead. The vocabulary matters in an audit, so it is worth keeping the terms straight. - Tolerance limits are what the instrument must meet, set by the specification or your process requirement. - Acceptance limits are the tighter limits you actually decide against, after the guard band is applied. - The guard band is the distance between the two, usually sized from the expanded measurement uncertainty. - A false accept is passing an instrument whose true value is out of tolerance. A false reject is failing one that is actually fine. Guard banding trades a few more false rejects for far fewer false accepts. Tip: If your certificates state pass or fail with no decision rule and no uncertainty, a borderline reading is being decided by luck. That is the exact situation guard banding exists to fix. ### Why guard band at all? The cost of a false accept A false reject costs you an unnecessary adjustment or a repeated calibration. A false accept costs you an out-of-tolerance instrument quietly approving product, sometimes for a full calibration interval, followed by the reverse traceability exercise of working out which measurements it touched. The two mistakes are nowhere near symmetrical, which is why programs deliberately bias the decision against false accepts. The formal framework for this is measurement decision risk, treated in depth by JCGM 106:2012. In US practice, ANSI/NCSL Z540.3 puts a hard number on it: where it applies, the probability of a false accept must not exceed 2 percent. You do not need the full statistics to run a sound program, but you do need a documented rule that says how your limits account for uncertainty. ### The common guard banding methods Your test uncertainty ratio decides how much any of this bites. With a strong TUR, the uncertainty is a small slice of the tolerance and the guard band barely moves your limits. As TUR drops toward 1:1, the guard band swallows the tolerance, which is the standard's way of telling you the measurement is not good enough for the decision you are asking it to make. - Subtract the full expanded uncertainty: acceptance limit = tolerance limit minus U95. This is the simple, conservative rule described in ILAC-G8 guidance. It is easy to defend and easy to compute. - Risk-based scaling: size the guard band so the calculated false-accept probability meets a target, such as the 2 percent ceiling in Z540.3. Tighter math, smaller guard bands when your uncertainty is small. - Percentage of tolerance: some programs use a fixed fraction of the tolerance as the guard band. Simple to administer, but it ignores your actual uncertainty, so it can be too loose or needlessly tight. - No guard band, stated openly: simple acceptance is also a legitimate documented decision rule. What is not legitimate is silence about which rule you used. See also: Check your TUR with the free calculator (https://axiospec.com/tools/tur-tar-calculator) ### A worked example Run your own numbers in the free guard band calculator. It applies the same logic and shows the acceptance limits alongside the tolerance so you can see exactly what the rule did. 1. A caliper is verified at a point with a tolerance of plus or minus 0.010 mm. 2. Your calibration process has an expanded uncertainty (U95) of 0.002 mm at that point. 3. Applying the simple ILAC-G8 style rule, each acceptance limit moves inward by 0.002 mm, giving acceptance limits of plus or minus 0.008 mm. 4. The as-found reading deviates by 0.009 mm. That is inside tolerance but outside the acceptance limits, so the decision rule does not pass it. 5. The right response is an adjustment or an investigation, recorded as such. The reading was never a clean pass, and now your records say so honestly. See also: Open the guard band calculator (https://axiospec.com/tools/guard-band-calculator) See also: Estimate false-accept risk for a specific reading (https://axiospec.com/tools/conformance-probability-calculator) ### Guard banding and ISO/IEC 17025 decision rules ISO/IEC 17025 requires that when a laboratory states conformity to a specification, the decision rule is documented, agreed with the customer, and stated on the certificate. The guard band is not the rule itself. The rule is the policy; the guard band is the mechanism the policy uses. A certificate that says pass should let the reader see which rule produced that word. If you buy calibration rather than perform it, this is a purchasing question too: ask your provider which decision rule they apply, and check that it appears on the certificates you file. For the fuller treatment of decision rules, TUR, and how they drive calibration intervals, see the dedicated guide. See also: ISO/IEC 17025 decision rules and calibration intervals (https://axiospec.com/guides/iso-17025-decision-rules-and-calibration-intervals) See also: Calibration for ISO/IEC 17025 (https://axiospec.com/standards/iso-17025) ### Putting it into practice If you run your program in Axiospec, the ISO/IEC 17025 tailoring adds measurement uncertainty and traceability fields to each calibration record and certificate, and the metrology insights card computes TUR from what you enter. The free plan is the full platform for up to 50 active assets. Axiospec documents your decision rules and evidence. It does not certify compliance; your assessor decides that. 1. Establish the expanded uncertainty for each calibration point you make decisions at. Without U, no guard band method has an input. 2. Choose one decision rule per measurement type, write it down, and apply it consistently. Auditors accept almost any defensible rule; they do not accept an undocumented one. 3. Compute the acceptance limits before the work, so the technician decides against them at the bench, not after the fact. 4. Watch the borderline as-found readings. A reading inside tolerance but outside the acceptance limits is your early warning that an instrument is drifting toward trouble. 5. Keep the rule on the certificate, so the record shows both the reading and the policy that judged it. See also: See it in the live demo, no signup (https://axiospec.com/demo) ### Common questions Q: What is a guard band in calibration? A: Guard banding, also written as one word as guardbanding, narrows your acceptance limits inward from the tolerance limits by an amount based on the measurement uncertainty, so an instrument only passes when the reading, uncertainty included, truly sits inside tolerance. Every calibration reading carries uncertainty. When a reading lands close to a tolerance limit, the true value could sit on either side, so a bare pass or fail comparison is a coin flip. The guard band closes that gap by making the call against the tighter acceptance limit. Q: What is the difference between a tolerance limit and an acceptance limit? A: Tolerance limits are what the instrument must meet, set by the specification or your process requirement. Acceptance limits are the tighter limits you actually judge against once the guard band is applied. The guard band is the distance between them. A reading can be inside tolerance but outside the acceptance limits, which is not a clean pass and should be recorded as an adjustment or an investigation. Q: What are the common guard banding methods? A: Four are in general use. Subtract the full expanded uncertainty, so the acceptance limit is the tolerance limit minus U95, which is the simple conservative rule in ILAC-G8 guidance. Risk-based scaling sizes the guard band so the calculated false-accept probability meets a target such as the 2 percent ceiling in ANSI/NCSL Z540.3. Percentage of tolerance uses a fixed fraction of the tolerance, which is simple to administer but ignores your actual uncertainty. Simple acceptance with no guard band is also a legitimate documented decision rule. What is not legitimate is silence about which rule you used. Q: Can you show a worked guard band example? A: A caliper is verified at a point with a tolerance of plus or minus 0.010 mm, and the calibration process has an expanded uncertainty (U95) of 0.002 mm at that point. Applying the simple ILAC-G8 style rule, each acceptance limit moves inward by 0.002 mm, giving acceptance limits of plus or minus 0.008 mm. An as-found reading that deviates by 0.009 mm is inside tolerance but outside the acceptance limits, so the decision rule does not pass it. The right response is an adjustment or an investigation, recorded as such. Q: How does guard banding relate to ISO/IEC 17025 decision rules? A: ISO/IEC 17025 requires that when a laboratory states conformity to a specification, the decision rule is documented, agreed with the customer, and stated on the certificate. The guard band is not the rule itself. The rule is the policy and the guard band is the mechanism the policy uses. A certificate that says pass should let the reader see which rule produced that word. If you buy calibration rather than perform it, ask your provider which decision rule they apply and check that it appears on the certificates you file. Q: Why does a false accept matter more than a false reject? A: A false reject costs you an unnecessary adjustment or a repeated calibration. A false accept costs you an out-of-tolerance instrument quietly approving product, sometimes for a full calibration interval, followed by the reverse traceability exercise of working out which measurements it touched. The two mistakes are nowhere near symmetrical, which is why programs deliberately bias the decision against false accepts. ANSI/NCSL Z540.3 puts a hard number on it where it applies: the probability of a false accept must not exceed 2 percent. --- ## Cloud Calibration Software: What It Is and When It Wins https://axiospec.com/guides/cloud-calibration-software Last updated: 2026-08-10 What cloud calibration software is, the honest tradeoffs against on-premise (data residency, control, IT burden), who it suits, and what to look for. Where Axiospec fits: browser plus native apps, a real free tier, and records built to hold up in an audit. Full disclosure up front: Axiospec is one of the tools in this guide, so weigh our take accordingly. Cloud calibration software runs in a browser, with native phone apps alongside it, so there is no server to install and no IT project to schedule. This guide covers what cloud actually means for a calibration program, the honest tradeoffs against on-premise, and who it suits. ### What cloud calibration software actually is Cloud, also called web-based or online, means the software runs on the vendor's servers and you reach it through a browser. The better tools add native iOS and Android apps so a technician can work from the shop floor or out in the field. You do not install a server, patch it, or back it up. The vendor handles the hosting, updates, and backups. The practical effect is simple. You sign in from any browser, a phone, or a tablet, and everyone sees the same records. Multi-site teams can run one system with per-site views instead of a separate spreadsheet on each plant's shared drive. ### Cloud vs on-premise: the honest tradeoffs Cloud is not automatically the right answer. It trades some control for less setup and less maintenance. Here is the plain version of what you give and get. - Data residency and control: on-premise keeps records on hardware you own. Cloud stores them on the vendor's infrastructure. If a contract or policy says your calibration data cannot leave your building, that is a real constraint, and cloud may not fit. - Updates: cloud vendors push updates to everyone. You get fixes and new features without a rollout, but you do not control the timing. On-premise lets you freeze a version until you are ready. - IT burden: cloud takes server setup, patching, and backups off your plate. On-premise puts them back on it, which means someone has to own that work. - Internet dependence: the browser side needs a connection. Good mobile apps let a technician log a reading offline and sync later, but you should confirm that before you rely on it. - Cost shape: cloud is usually a flat monthly or annual subscription. On-premise is often a larger upfront license plus an ongoing maintenance fee. ### Who cloud calibration software suits Cloud tends to win for teams that want to replace spreadsheets or paper without standing up infrastructure first. It fits a specific profile well. It fits less well for air-gapped facilities or organizations under a data-residency mandate that rules out hosted storage. Most modern cloud tools encrypt data in transit, but residency is a policy question, not a security one, so decide it on your own rules rather than on the vendor's assurances. - Small to mid-size teams with no dedicated IT group to run and secure a server. - Multi-site operations that want one shared system instead of one spreadsheet per location. - Teams doing field or bench logging, where a technician needs the instrument record on a phone right next to the gage. - Anyone who wants to start this week rather than schedule a rollout for next quarter. Tip: If data residency is your blocker, ask a cloud vendor where the data is hosted and whether that region is fixed in the contract before you rule cloud out. ### What to look for in a cloud calibration tool Once you know cloud fits, the checklist is the same one you would use for any calibration system. A few things matter more than the marketing. Records that hold up. Look for a change history that is attributed and timestamped, electronic signatures, and calibration certificates attached to each instrument. This is what keeps records audit-ready. The software supports your program; certification still depends on your own processes, scope, and assessor. Due-date tracking. You want next-due dates computed per instrument, a calendar view, and due-soon and overdue counts, so recalls do not quietly slip past. Standards fit. Check that the tool matches the standard you actually work to, whether that is ISO 9001, ISO/IEC 17025, AS9100, ISO 13485, or IATF 16949. Most modern cloud tools cover the common ones, but the fields and workflows differ. Mobile that earns its keep. Scanning a QR or barcode label to pull an instrument's record, logging at the bench, and printing your own labels beats typing an asset number into a form. See also: ISO/IEC 17025 in Axiospec (https://axiospec.com/standards/iso-17025) See also: Best calibration management software compared (https://axiospec.com/guides/choosing-calibration-management-software) ### Where Axiospec fits Axiospec is a cloud option: browser plus native iOS and Android apps, no server to run. Multi-site is supported with per-site views, so each location sees its own instruments while you keep one system. On records, it is built to hold up. There is a tamper-evident, hash-chained audit trail where every change is attributed to a user and timestamped, electronic signatures on records, an immutable maker-checker ledger, and calibration certificates attached to each asset. When an audit comes, a one-click audit-pack export gives you PDF and CSV with an integrity page. It helps you keep records audit-ready; it does not certify you on its own. For due dates, it computes the next-due date per instrument and rolls that into a Calibration Due Calendar, due-soon and overdue counts, and reminders so recalls do not slip. On standards, it covers the record-keeping behind ISO 9001, ISO/IEC 17025, AS9100, ISO 13485, and IATF 16949, and the ISO/IEC 17025 tailoring adds measurement uncertainty and traceability fields. Built-in MSA and Gage R&R are there when you need them. On mobile, a technician scans a QR or barcode label to pull a record and log a calibration at the bench or in the field, prints asset labels you produce yourself for free, and can use voice input for readings. On price and lock-in, the free plan covers up to 50 active instruments with unlimited users and no credit card. Paid plans run 59 to 229 dollars a month, flat, with unlimited users. Import is self-serve from a spreadsheet, and you can export everything anytime, so nothing is trapped. See also: See plans and the free tier (https://axiospec.com/pricing) ### Try it before you commit The fastest way to judge a cloud calibration tool is to use one. A live demo runs on sample data at /demo with no signup, so you can click through the audit trail, the due calendar, and the mobile logging flow before you decide anything. If it fits how your shop works, the free plan lets you load your own instruments without a card and keep going from there. See also: Open the live demo (https://axiospec.com/demo) --- ## Calibration Software With a Mobile App: Logging at the Instrument https://axiospec.com/guides/calibration-software-mobile-app Last updated: 2026-08-10 Why logging calibrations at the instrument beats retyping them at a desk, what a real mobile calibration app should do (scan to pull a record, log on the spot, voice input, printable labels), and how the scan-to-log flow works in Axiospec native iOS and Android apps. Full disclosure up front: Axiospec is one of the tools this guide talks about, so weigh our take accordingly. We built native mobile apps because we kept watching people write calibration readings on a clipboard, then retype them at a desk an hour later. This guide is about why logging at the instrument matters, what a mobile calibration app should actually do, and how the pieces fit together. ### Why logging at the instrument beats logging at a desk Most calibration errors are not measurement errors. They are copying errors. Someone reads 0.9998 on the gage, writes it on a clipboard, and later types 0.9988 into a spreadsheet. The measurement was fine. The record is wrong, and nobody can tell which number to trust. Logging at the instrument removes the gap where those mistakes live. You record the reading once, in the place where you took it, while you can still see the display. There is no clipboard step, no end-of-day retyping, no stack of paper that grows for a week before anyone enters it. The lag matters as much as the accuracy. When entries wait, due dates drift, a tool can go back into service before its record is updated, and the person who ran the check is not always the person who transcribes it. Capturing the result on the spot keeps the timestamp honest and keeps the person who did the work attached to the record. ### What "mobile" actually means, and why it varies so much "Mobile app" means different things across calibration software, so it is worth asking what you are actually getting. Some tools ship a mobile-friendly web page and call it an app. Some have a real app, but only for viewing records, not for logging them. A few, including ours, run native iOS and Android apps built for capturing work on the floor. Depth varies a lot between products, and none of it shows up in a feature checklist. The honest move when you shop is to test the log flow on an actual phone, in an actual shop, before you commit. A demo on a laptop will not tell you whether the scan is quick or whether the reading screen fights you when your hands are full. ### What to look for in a mobile calibration app A few capabilities do the real work. When you compare tools, these are the ones worth testing rather than taking on trust: - Scan to pull a record: point the camera at a QR or barcode label on the instrument and its history opens, with no searching by ID. - Log at the point of use: enter the calibration where you took it, at the bench or in the field, not back at a desk. - Voice input for readings: speak the numbers when your hands are gloved or full. - Printable labels you make yourself: tag every instrument with a scannable label without ordering custom stock. - Native apps, not a shrunk-down website: better camera access and a screen built for entry. - One set of records: whatever you log on the phone is the same record your team sees in the browser, with the next-due date recomputed. Tip: Test the scan-to-log flow on a real phone in a real shop before you commit. A laptop demo will not tell you whether the scan is quick or whether the entry screen works with gloves on. See also: Best calibration management software (https://axiospec.com/guides/choosing-calibration-management-software) ### How the scan-to-log flow works Here is the flow we built, and roughly what a good one looks like anywhere. You print an asset label. Ours are free and you print them yourself, so tagging a hundred instruments does not mean buying a hundred custom tags. You stick the label on the instrument, the case, or the storage slot. At the bench, you open the app and scan the label. The record for that exact instrument comes up: its history, its interval, when it is next due. You log the calibration right there. If your hands are gloved or full, you can speak the readings instead of typing them. When you save, the entry is attributed to you and timestamped, and the next-due date is recomputed on the spot. Nothing waits for a desk. Across sites, the person working in the browser sees the same record you just wrote, with per-site views so each location sees its own instruments. ### The records still have to hold up later Fast capture only helps if the record survives scrutiny months later. This is the part people underrate when they shop for a mobile app. Every change in Axiospec is attributed to a user and timestamped, and the history is kept in a tamper-evident, hash-chained audit trail. Records support electronic signatures and run through an immutable maker-checker ledger, so an approval is a real approval and edits do not quietly overwrite each other. Calibration certificates attach to the asset they belong to. When an auditor or a customer asks, you export a one-click audit pack, PDF and CSV, with an integrity page. If you work to ISO/IEC 17025, tailoring adds measurement uncertainty and traceability fields, and there is built-in MSA and Gage R&R when a study needs to be on record. None of this certifies you. Software does not do that. Certification depends on your own processes, your scope, and your assessor. What the records do is help you keep them audit-ready, so the entry you made at the bench is still defensible when someone reads it later. See also: ISO/IEC 17025 in Axiospec (https://axiospec.com/standards/iso-17025) ### Try the scan-to-log flow on your phone The only real test is your own instruments in your own shop. We keep a live demo on sample data at /demo with no signup, so you can walk the scan-to-log flow and the record trail before you talk to anyone. If it fits, the free plan covers up to 50 active instruments with unlimited users and no credit card, and paid plans are flat at 59 to 229 dollars a month. Import your list from a spreadsheet to start, and export everything anytime. No lock-in. See also: See the live demo (https://axiospec.com/demo) See also: Plans and pricing (https://axiospec.com/pricing) --- ## Calibration Software With an Audit Trail: What Assessors Actually Want https://axiospec.com/guides/calibration-software-audit-trail Last updated: 2026-08-10 What an audit trail actually has to do in a calibration program, the three tests an assessor applies (attributable, timestamped, tamper-evident), why a spreadsheet fails them, and what tamper-evident really means. How a hash-chained ledger and one-click audit pack keep records defensible. Full disclosure up front: Axiospec is one of the tools we build, so weigh our take accordingly. This is the plain-language version of what an audit trail actually has to do in a calibration program, and why a spreadsheet quietly fails at it. One thing to say clearly before we start: an audit trail does not make you compliant. It makes your records defensible when an assessor starts asking who changed what, and when. ### What an audit trail is, in calibration terms An audit trail is a running record of every change to a calibration record, tied to a named person, stamped with a time, that cannot be edited after the fact without leaving a trace. That is the whole idea. Not a log you keep for fun, but proof that the record you are showing today is the record as it was entered and approved. Assessors reduce this to three plain tests. Is each entry attributable to a real user, not a shared login. Is it timestamped, so the sequence of events is clear. Is it tamper-evident, meaning a later change is detectable rather than silent. A record that passes all three tells a story someone can trust. A record that fails any one of them is just data, and data is easy to argue with. ### What an assessor opens first When someone audits your calibration records, they are not testing whether you love metrology. They are testing whether your records tell a consistent story and whether that story can be trusted without taking your word for it. In practice they go looking for a short list of things. - Traceability: can you show the certificate for the reference standard used to calibrate this instrument, and follow it back toward a national reference. - Attribution: who performed the calibration, and who reviewed or approved it, as named people rather than initials in a cell. - Dates: the calibration date, the next-due date, and whether the recall actually happened on time or slipped. - Change history: if a reading or a due date was corrected, is the original value still visible along with who changed it and why. - Integrity: can anyone prove that the record on screen today is the record as it was signed, not a quietly edited copy. Tip: Before you buy anything, ask a vendor to make an edit in front of you, then show you exactly where that edit was recorded. If they cannot, the audit trail is thinner than the brochure. ### Why a spreadsheet fails the test Spreadsheets are good at math and poor at evidence. Any cell can be overwritten, and nothing in the file records what it used to say or who changed it. Track changes is off by default and simple to strip out. A shared file has no reliable identity behind an edit, so an entry from one person is indistinguishable from an entry from another. There is no built-in link between an instrument and its certificate PDF, so the proof lives in a separate folder that may or may not still match. None of this means your numbers are wrong. It means you cannot prove they were not changed, and proving that is the entire job of an audit trail. This is why most modern cloud tools stop editing cells in place and instead write every change to a log the user cannot alter. Once the record of the change lives somewhere the person making the change cannot reach, the story holds up. See also: Compare calibration management tools (https://axiospec.com/guides/choosing-calibration-management-software) ### What tamper-evident actually means This is where the words matter. Tamper-proof is a marketing word, because you cannot stop a determined administrator from touching a database. Tamper-evident is the honest one: you make any change detectable. Axiospec does this with a hash-chained ledger. Each record is linked to the one before it with a cryptographic hash, so a silent edit breaks the chain and shows up instead of hiding. The rest is the plumbing an assessor expects. Every change is attributed to a user and timestamped. Records carry electronic signatures. An immutable maker-checker ledger keeps the person who entered a result separate from the person who approved it, so no single account can quietly do both. Calibration certificates attach to each asset, so the evidence travels with the instrument rather than sitting in a folder somewhere. You can log a calibration at the bench from an iOS or Android app by scanning the QR or barcode label on the instrument, and the same rules apply to those entries. ### How this maps to the standards Named standards do not hand you a feature checklist, and no tool can grant you a certificate. What they share is an expectation that records are controlled, attributable, and retrievable. ISO/IEC 17025 leans hardest on measurement traceability and stating uncertainty. AS9100 and ISO 13485 care about record control and approvals. ISO 9001 and IATF 16949 expect calibrated equipment with retained evidence behind it. Axiospec supports these programs by keeping records audit-ready, but certification depends on your own processes, scope, and assessor. The tool covers the record-keeping side: the hash-chained trail, signatures, attached certificates, and due-date tracking. For an ISO/IEC 17025 program, the 17025 tailoring adds measurement uncertainty and traceability fields, and built-in MSA and Gage R&R help you back up the measurement decisions themselves. What Axiospec does not do is run your process for you, so treat any tool as evidence infrastructure, not a shortcut through the assessment. See also: ISO/IEC 17025 record expectations (https://axiospec.com/standards/iso-17025) ### What audit-ready looks like day to day The practical payoff is that on the day an audit is scheduled, you are not rebuilding anything. The trail already exists because it was written as the work happened. When the assessor asks for records, one-click audit-pack export gives you a PDF and CSV with an integrity page, so the proof and the data leave together. The rest of the week it does quieter work. The system computes the next-due date for each instrument, and a Calibration Due Calendar with due-soon and overdue counts shows what is coming while there is still time to act on it. Reminders keep recalls from slipping, which is the failure most audits actually catch. If you want to see how the trail reads without signing up, the live demo runs on sample data. Make an edit, then go look at where it was recorded. That is the fastest way to judge whether an audit trail is real or just a label. See also: Try the live demo, no signup (https://axiospec.com/demo) --- ## How to Track Calibration Due Dates in Software (and Stop Recalls Slipping) https://axiospec.com/guides/track-calibration-due-dates Last updated: 2026-08-10 How software computes next-due dates, surfaces due-soon and overdue instruments, and sends reminders so recalls stop slipping past an audit. Plus the at-a-glance readiness views (Due Calendar, due-soon and overdue counts) and how to keep the dates honest at the bench. Full disclosure: Axiospec is one of the tools in this guide, so weigh our take accordingly. The recurring problem is simple. An instrument goes past its due date, nobody notices, and it turns up overdue during an audit. This is how software computes next-due dates, surfaces due-soon and overdue instruments, and reminds you before a recall slips. ### The problem: overdue instruments found during an audit Almost every calibration program starts on a spreadsheet. It works until it does not. One person owns the file, they update it when they remember, and the due dates drift out of date. Then an auditor pulls a caliper, checks the sticker, and it expired four months ago. Now you are writing a nonconformance and reviewing every measurement that instrument touched since it went overdue. The spreadsheet is not really the villain. The problem is that a static file cannot tell you what changed today. It does not know that a gage was calibrated last week, or that three more come due on Friday. Someone has to look, and people are busy. Tracking due dates in software handles the part humans are bad at: watching a moving list every single day. ### How software computes the next-due date The core calculation is small. Take the last calibration date, add the calibration interval, and you get the next-due date. If a micrometer was calibrated on January 10 with a 12-month interval, it is due on January 10 the following year. Software does this for every instrument at once and keeps the date current as new calibrations are logged. The interval is the judgment call, not the math. Set it too long and you risk using an instrument that has drifted. Set it too short and you pay for calibrations you did not need. Interval is driven by how the instrument is used, its history, and the standard you work to. If you are still deciding, the interval guide and calculator below walk through it. See also: How to set calibration intervals (https://axiospec.com/guides/how-to-set-calibration-intervals) See also: Calibration interval calculator (https://axiospec.com/tools/calibration-interval-calculator) ### Due-soon, overdue, and reminders A due date on its own is just a number in a cell. What keeps recalls from slipping is turning that date into a status you can act on, plus a reminder that reaches a person before the date passes. - Due soon: instruments coming due inside a window you choose, so there is time to schedule the work or send the item out. - Overdue: instruments past their due date, counted and separated so they are impossible to miss. - Reminders: notifications ahead of a due date, so the right person acts while there is still runway. - Status counts: a running tally of how many instruments are current, due soon, and overdue across the whole shop. Tip: Set due-soon far enough ahead to cover send-out time. If an external lab needs two weeks to turn a gage around, a 7-day warning is already late. ### An at-a-glance readiness view Counts are useful, but people also think in dates. A calendar view covers most of what a quality lead needs on a Monday morning. A Calibration Due Calendar lays out what comes due by date, so you can see a heavy week before it arrives and plan around it. Alongside it, status counts summarize the whole registry: how many instruments are current, how many are due soon, and how many are overdue. Selecting a count filters straight to that list. Together they are the view you want open when someone asks whether you are ready for an audit, instead of digging through a spreadsheet to answer. Software supports that readiness. It does not certify it. Whether you pass still depends on your own processes, your scope, and your assessor. The value is that the record is kept audit-ready as you work, not rebuilt the night before. ### Keeping the dates honest at the bench Due-date tracking only works if the last-calibration date is accurate. That breaks down when logging a calibration means walking back to a desk and updating a file later, or never. With native iOS and Android apps, you can scan a QR or barcode label on the instrument, pull up its record, and log the calibration right at the bench or in the field. You can print your own asset labels for free, and use voice input for readings. Every entry is attributed to a user and timestamped on a tamper-evident, hash-chained audit trail, with calibration certificates attached to each asset. When an auditor asks for proof, it is a one-click audit-pack export, PDF and CSV with an integrity page, rather than a scramble. ### How Axiospec handles due dates Axiospec computes the next-due date for every instrument, counts what is due soon and overdue, and sends reminders so recalls do not slip. The Due Calendar and the clickable status counts give you the at-a-glance view. It runs in the browser with native iOS and Android apps, supports multiple sites with per-site views, and fits standards including ISO 9001, ISO/IEC 17025, AS9100, ISO 13485, and IATF 16949. There is a free plan for up to 50 active instruments with unlimited users and no credit card, and you can import from a spreadsheet and export everything anytime. The fastest way to judge whether the due-date views fit how you work is to look at them with data already in place. The live demo runs on sample data with no signup. See also: Try the live demo (no signup) (https://axiospec.com/demo) See also: See pricing and the free plan (https://axiospec.com/pricing) --- ## Approving a calibration supplier and keeping an approved supplier list https://axiospec.com/guides/approving-a-calibration-supplier Last updated: 2026-09-06 How to evaluate, approve and re-approve an external calibration lab, what to check on the scope of accreditation, and what an approved supplier list needs to carry for a calibration provider. Two people arrive at this page. One needs an approved supplier list they can build today. The other has a quote from a calibration lab and wants to know what to check before signing it. This guide covers both. They are the same job seen from two ends. The approved supplier list is where the decision gets recorded. The vetting is how you make the decision worth recording. A calibration lab is unusual among your suppliers. It is an external provider you have to control. It is also a link in the chain that makes your own measurements defensible. Get the second part wrong and every measurement made with that instrument becomes questionable. That is why a calibration supplier needs more than the generic row a fastener distributor gets. ### Why a calibration lab is not an ordinary supplier Most external providers only have to meet a purchase requirement. A calibration lab does two jobs at once. Both of them sit inside your quality system. First, it is an external provider. ISO 9001:2015 clause 8.4.1 requires you to determine and apply criteria for evaluating, selecting, monitoring the performance of and re-evaluating external providers. It also requires records of those activities and of any necessary actions arising from them. That is four separate activities, not one. Approving a lab in 2021 covers the first two. Monitoring and re-evaluation are the two left undone. Those are the two an auditor will ask you to show evidence for. Second, it is a link in your traceability chain. When your instrument comes back with a certificate, the validity of every measurement you make with that instrument rests on the work that lab did. Sending the gauge out does not move that obligation off your system. It adds a supplier control obligation on top of it. That dual role has a practical consequence. Ordinary supplier control asks whether the goods arrived on time and conformed. Calibration supplier control also asks whether the lab was technically capable of the specific measurement you bought. It asks that at the range you use, to an uncertainty small enough for your tolerance. A lab can be reliable commercially and still be the wrong lab for your torque wrench. See also: What metrological traceability actually proves (https://axiospec.com/guides/metrological-traceability-explained) See also: What each standard requires for calibration (https://axiospec.com/guides/iso-calibration-requirements) ### What the standards actually require, and what they do not This is where most published advice overstates the case. It is worth being exact. ISO 9001 does not require an approved supplier list. The words do not appear in the standard. Clause 8.4.1 requires you to set criteria for evaluating, selecting, monitoring and re-evaluating external providers. It then requires you to apply those criteria and keep the records. The criteria are the part auditors ask for first. A list is simply the ordinary way people hold the records. ISO 9001 also does not require your calibration lab to be accredited. Its traceability rule applies where traceability is a requirement, or where you judge it essential to confidence in your results. Where it applies, the equipment has to be calibrated or verified against measurement standards traceable to international or national measurement standards. The standard also tells you to take the effectiveness of the provider's own controls into consideration when you decide how much control to apply. Accreditation is the strongest evidence available. It only carries that weight for work sitting on the lab's published scope. It is not named as a requirement. Aerospace is stricter. AS9100D clause 8.4.1.1 requires a register of external providers that records approval status and the scope of that approval. It also requires you to define the process, the responsibility and the authority for deciding approval status and for changing it. The status examples in the standard are approved, conditional and disapproved. The scope examples are product type and process family. Listing a lab as simply approved, with no scope, leaves out a required element of the register. Automotive is the strictest. IATF 16949 names calibration services explicitly in the scope of supplier control. Its external laboratory clause requires the lab to have a defined scope covering the service you buy. The lab must then either be accredited to ISO/IEC 17025 or a national equivalent with that service inside the accreditation scope, or be documented as acceptable to your customer. Where accreditation is the route, the certificate or report has to carry the mark of a national accreditation body. A narrow route also allows the equipment manufacturer to calibrate its own equipment when no qualified lab is available. Medical devices sit in between. ISO 13485 uses its purchasing clause rather than the ISO 9001 numbering. It requires selection and control criteria proportionate to the risk associated with the medical device. It does not require accreditation either. It requires you to justify and record your reasoning. Since 2 February 2026 the FDA's Quality Management System Regulation incorporates ISO 13485:2016 by reference. US device makers now meet the purchasing control obligation through that clause rather than through the old 21 CFR 820.50 wording. Calibration laboratories themselves run the same loop. ISO/IEC 17025 requires a lab to have a procedure and records covering how it defines requirements for what it buys. The same procedure has to cover how it evaluates, selects, monitors and re-evaluates its own external providers, how it checks conformity before use, and what actions it takes from those evaluations. When you buy accredited calibration, part of what you are buying is a supply chain that has already run this control loop on its own reference standards. - No standard in this group sets a re-evaluation frequency. Annual is convention, not requirement. - No standard sets a record retention period for supplier files. That comes from your contracts, your regulator and your own retention rules. - No standard requires an on-site audit of a calibration lab. Aerospace requires you to communicate any such activity you intend to perform. - None of them define the phrase NIST traceable. It is purchase order and certificate language rather than a defined term. On its own it proves nothing. What you have to be able to evidence is metrological traceability, and NIST publishes its own policy on what a claim of traceability to NIST should be able to show. See also: Requirements by standard (https://axiospec.com/guides/iso-calibration-requirements) See also: Accredited versus certified (https://axiospec.com/guides/iso-17025-accreditation-vs-certification) ### Write the requirement before you request quotes Most of the pain in calibration purchasing comes from buying an undefined service. The certificate arrives, it is missing something you needed, and by then the instrument is back in use. Every standard in this area asks you to communicate requirements to the provider before work starts. For calibration that is a short list. It belongs on the purchase order or in a standing agreement rather than in an email thread. - The parameters, ranges and points you actually use, not the manufacturer's default point set. - Your tolerances, if they differ from the manufacturer specification. - Whether accredited calibration is required, named per parameter. Many labs sell an accredited service and a cheaper non-accredited one under the same brand. - As-found data required, before any adjustment. As-left data required after adjustment or repair. - Reported measurement uncertainty, with the coverage factor stated. - Whether you want a statement of conformity, and under which decision rule. If you do not specify one, you inherit the lab's. - Out-of-tolerance notification. Require the lab to report an as-found out-of-tolerance condition in writing, to a named person, within a stated number of days. - Whether subcontracting is permitted. If it is, say whether it needs your prior approval and must be identified on the certificate. - Adjust only with approval, if a silent adjustment would cost you your as-found evidence. - Turnaround commitment, and the asset identifiers you want printed so the certificate names your serial numbers. - Whether a due date may be printed on the certificate or the label. ISO/IEC 17025 says a calibration certificate or calibration label shall not carry a recommended calibration interval unless you agreed to it. The same clause lets legal regulations override that. In most cases the interval is yours to set. Tell the lab which date to print, or tell it to print none. Tip: As-found data is the one line people skip and the one they regret. When an instrument comes back out of tolerance, you have to decide whether the measurements it made since its last calibration are still valid. A certificate that says adjusted and returned in tolerance, with no as-found readings, makes that assessment much harder. Ask for it in writing, on the purchase order, before the first shipment. See also: What a calibration certificate must carry (https://axiospec.com/guides/calibration-certificate-requirements) See also: Decision rules and guard banding (https://axiospec.com/guides/guard-banding-in-calibration) ### The scope of accreditation is the document that matters Accreditation produces two documents. A certificate of accreditation is one page saying the lab is accredited. A scope of accreditation is the table of what the lab is actually accredited to do. A supplier who sends you only the certificate has not answered your question. The scope lists, for each capability, the measurand or type of instrument, the method, the measurement range with any other relevant parameters, and the measurement uncertainty. Those elements together are one calibration and measurement capability, usually shortened to CMC. The uncertainty figure is part of the CMC and not the whole of it. It only applies inside the range, method and conditions on the same line. Column headings vary by accreditation body. Some head the uncertainty column CMC. Others call it expanded uncertainty of measurement. Scanning for those three letters can make you miss it. A genuinely accredited lab can be outside its scope for your job in more ways than most buyers expect. - The parameter is not listed at all. Accreditation is granted per measurement, not per company. - Your range falls outside the listed band. A row covering 0 to 55 ohms does not cover 400 ohms. - The direction is wrong. Accredited to measure a quantity is not the same as accredited to source or simulate it. - The site is wrong. Accreditation is issued to a facility. Certificate numbers often carry a location suffix. A multi-site company can have one accredited site and three that are not. - On-site work is different from bench work. Field uncertainties are normally worse than the bench figure, and some scopes cover only one mode. - The service is on the scope but the lab does not sell it commercially. Some directories flag commercial availability. - You ordered the cheaper non-accredited tier without noticing. See also: How accreditation scopes work (https://axiospec.com/guides/iso-17025-accreditation-vs-certification) See also: US accredited calibration lab landscape (https://axiospec.com/guides/us-accredited-calibration-lab-landscape) ### Reading a CMC, and why your job uncertainty is bigger A CMC is the smallest uncertainty the lab can achieve when calibrating a near-ideal device under normal conditions. It is a floor, not a promise about your instrument. Most instruments sent out for calibration are not near-ideal. The uncertainty reported on your certificate has to cover contributions from your device. So it is equal to or larger than the CMC on the scope, and it is usually larger. One firm rule follows. An accredited lab must not report an uncertainty smaller than its published CMC for that work. A reported value that lands exactly on the CMC is not a defect on its own. That happens when your device adds little and the figures round to the same number. What should make you look harder is one identical uncertainty printed across clearly different items. Ask the lab how it evaluated the contribution from your instrument. Compare the CMC to the tolerance you will actually apply. Do it on the scope line that matches your parameter and your range. A scope lists many CMCs. It does not hold one number for the lab. Put both figures on the same basis before you judge them. Percent of reading and percent of span are not the same thing. Run the comparison at a real test point. If your acceptance limit works out to 0.1 percent of reading at that point and the matching CMC is 0.25 percent of reading, no reputation fixes that gap. The common expectation is a test uncertainty ratio of at least 4 to 1, or a documented false-accept risk analysis instead. The uncertainty printed on your certificate will be at least the CMC and usually more. A ratio that looks marginal on the scope is worse on the job. CMC values legitimately take several forms. A single value across a range. A low to high range. A percentage of reading. A percentage plus a floor. A formula that scales with length. A table of discrete points. A single bounding value written as less than or equal to some figure across a range is normal, and the accreditation body assessed that format before it went on the scope. Do not raise that as a defect. Raise it when the number is a best case rather than a bound, such as uncertainty as low as some figure. Raise it when no coverage factor or confidence level is stated. Raise it when the value is not tied to a named parameter, range and method. See also: Test uncertainty ratios and decision rules (https://axiospec.com/guides/guard-banding-in-calibration) ### Verify at the accreditation body, not from the emailed PDF This whole sequence takes a few minutes per supplier. It takes more than one lookup because the US has no single register. Two bodies can also disagree about the same lab at the same address. Note which changes get published. Suspensions and withdrawals are generally made public. A quiet reduction in scope is the change most likely to affect you and the least likely to be announced. Scopes carry their own revision dates and can be cut part way through a cycle, not only at renewal. That is a reason to re-check the live scope on a schedule rather than to rely on being notified. 1. Get the legal entity name and site address from the quote, not from the brochure. Trade names and parent brands do not carry accreditation. 2. Open the accreditation body's public directory and search for that legal entity at that address. Do not work from the PDF the supplier sent. A file tells you what was true the day it was saved. Accreditation can be suspended, withdrawn or reduced since then. 3. Check the accreditation status and the valid-to date. Read the status word carefully. Some bodies use terms like extended for an active accreditation carrying an extension, which is not a separate state. 4. Match the certificate number including any site suffix. 5. Compare the scope revision date on the directory copy against the copy you were sent. A scope can be revised and lose a row you relied on. 6. Find your parameter as an actual row. Confirm your range sits inside the listed band and the direction matches. 7. Read the uncertainty on that row against your tolerance. 8. Check the mode. If you need on-site work, the row or its footnotes must allow field service. 9. Save the evidence. Print or save the directory page and the scope with the date you retrieved them, and record who checked. See also: Directory-reading traps by accreditation body (https://axiospec.com/guides/us-accredited-calibration-lab-landscape) ### Checking the certificate when it comes back Approving a supplier is one control. Checking the output is a separate one, and the standards treat it that way. The incoming review of a returned certificate is where supplier control and traceability meet. Read the full certificate element list on the certificate requirements guide rather than here. The checks specific to a supplier decision are these. - The item identification matches the asset record, by serial number. - Measurement uncertainty is stated, in usable units, with the coverage factor. - There is a real traceability statement, not just the phrase NIST traceable. - As-found data is present when the unit was adjusted or repaired, if you required it. - The accreditation symbol or a text reference to accreditation appears, if you ordered accredited work. - Mixed reports flag the non-accredited lines. A report containing no accredited results should carry no accreditation reference anywhere, including on covering letters. - Results obtained from an external provider are clearly identified. That is how you find out your work was subcontracted. - Any pass or fail statement names the decision rule applied. - The reported uncertainty is at least the CMC on the scope line matching the parameter and range actually calibrated. Compare like for like, at the same coverage factor. A value below the published CMC needs an explanation from the lab. A value sitting right on it does not. See also: Certificate elements in full (https://axiospec.com/guides/calibration-certificate-requirements) ### What a calibration row on the approved supplier list has to carry A generic supplier row breaks on a calibration lab, for four reasons. Certification and accreditation are different objects. Accreditation is limited to a scope that lives in a separate document with its own date. Accreditation is site-specific. And field work is a distinct activity from bench work. So the structure that works is a parent row per supplier site, with child rows for each approved measurement area. A single flat row per company forces the over-broad entry that causes most of the damage. Beyond the usual identity and status columns, a calibration supplier row needs these. - Supplier legal name and the specific site performing the work, with address. - Discipline and parameter, with the range. Torque 5 to 500 newton metres is a scope line you can check. Torque on its own is a wish. - The tightest instrument tolerance you may send this lab, recorded per scope line you actually use. Work the planning figure from the CMC for that parameter and range and your required ratio. Treat it as a best case. The number that has to meet your ratio is the uncertainty printed on the certificate, and that is usually larger than the CMC. - Accredited or non-accredited service, per parameter. - On-site or field service approved, recorded separately from bench work. - An explicit not approved for line. It is the cheapest field on the list and the one that stops the wrong purchase order. - Accreditation body, certificate number with its site suffix, and the scope document reference with its own revision date. - The date you verified the accreditation in the body's directory, and who checked it. This is the highest-value field most lists do not have. - Approval status from a fixed value set, the basis for approval, the approval date and a named person who approved it. - Your re-evaluation due date, kept as a separate column from the supplier's certificate expiry date. People merge these two and then treat an unexpired certificate as an up-to-date evaluation. - A pointer to where the flowed-down requirements live. That means the purchase order text, the quality clauses or the service agreement. See also: Free approved supplier list builder with CSV export (https://axiospec.com/tools/approved-supplier-list-template) ### Using the free ASL template Our approved supplier list builder runs entirely in your browser. Nothing is uploaded. It gives you seven editable columns per row: supplier, category, approval status, certification, certificate expiry, scope supplied and last audit. Status is a fixed set of Approved, Conditional, Disqualified and Pending. The certification column is a fixed set too. It offers ISO 9001, AS9100, IATF 16949, ISO 13485, ISO/IEC 17025 and None, and it takes one value per row. Read the ISO/IEC 17025 entry as accreditation rather than certification. A calibration lab is accredited to 17025 by an accreditation body. It is not certified to it. That distinction decides what the row is actually worth. It flags certificates that have expired or that expire within 90 days. It counts your suppliers by status. It lists the ones needing attention with the most overdue first, and it counts separately any supplier that has a certification recorded and no expiry date. The CSV and TSV export carries eight columns rather than the seven on screen. The extra one sits between certificate expiry and scope supplied. It holds a certificate status worked out from the expiry date you typed in. Treat that as a chase list. A scope can be cut or an accreditation suspended long before the printed date runs out. The columns above that the builder does not have, such as approval basis, approval owner, risk tier and next review date, are ones you add in your own spreadsheet after exporting. That is deliberate. The export stays readable, and your columns are yours. For the performance side, the supplier scorecard calculator publishes its formulas and defaults so you can see how a score is built. It was designed for goods, so translate the inputs for a lab. Certificates received stands in for lots received. Certificates returned with errors or needing reissue stands in for rejects. Instruments returned late against the promised turnaround is your delivery metric. Out-of-tolerance findings reported by the lab, against those found later by you, is worth tracking on its own. If you would find automatic tracking of supplier accreditation certificates and scopes useful, there is a page describing what we are considering building. It is not available today. Read every line on it as intent, not as a product. See also: Approved supplier list template (https://axiospec.com/tools/approved-supplier-list-template) See also: Supplier scorecard calculator (https://axiospec.com/tools/supplier-scorecard-calculator) ### Conditional approval, and making status mean something Conditional approval is a real, recordable state, and it is where the list earns its keep. It is not a status word on its own. It is four things, and it is not conditional approval unless all four are present. The restriction, stating what they may and may not be used for. The end date. A named owner who closes it out. And the exit evidence, meaning what must be produced to move to approved, or the row drops to suspended. Common shapes for a calibration lab. Approved for dimensional only while a torque scope extension is assessed. Approved through a fixed date while an accreditation renewal closes. Approved for one purchase order, then review. Approved with 100 percent incoming certificate review. Approved only for work where your end customer has accepted this lab. One more shape needs its own note. Not accredited, but audited by you, with the chain to SI and the stated uncertainty on file. Record loudly that this is not accredited calibration. The missing accreditation mark is the least of it. Nobody outside your own audit has assessed the method or the uncertainty. Your customer or your registrar can still reject the result. Automotive and aerospace flowdowns usually want accreditation or written customer acceptance instead. The rule that makes the whole thing work is that status has to gate a purchase order rather than sit beside one. If the only consequence of conditional is a colour on a spreadsheet, it is approved with a note. Two diagnostics. If any conditional row is older than its own condition, that is your finding. And if every row on your list says approved, the status column has never been used. ### Re-evaluation, and the triggers that beat the calendar No standard names an interval. Annual is the common default. Risk-tiered variants are widespread, with shorter cycles for sole-source or high-consequence suppliers and longer ones for low risk. Depth tiers too, from a desk review of documents through a questionnaire and a remote review up to an on-site audit. Run the periodic re-evaluation on your own clock. Do not anchor it to the supplier's accreditation cycle, because those cycles usually run longer than a year. Then keep a separate expiry watch that fires 60 to 90 days before the accreditation expiry rather than on it. That leaves time to requalify or line up an alternative before instruments come due. A lapse discovered on the day of expiry is already a problem for anything in transit. Tier by what the instrument controls, not by what the calibration costs. A cheap calibration on the gauge that releases product outranks an expensive one on a facilities thermometer. Scheduled review is the floor. These force a review immediately. - Accreditation expired, suspended, withdrawn or surrendered. - Scope reduced, or the uncertainty values on your parameter got worse. A body can cut or partly suspend a scope at any point in the cycle, not only at renewal. Compare the new scope against the previous version. Reductions do not announce themselves. - Change of accreditation body. - The lab moved site, was acquired, or changed the signatory or the key technician for your discipline. - The lab began subcontracting work it used to perform itself, or you discovered it already was. - A certificate arrived missing a required element, or the wrong instrument was identified. - An out-of-tolerance result reported late, or found by you rather than reported by them. - An instrument came back and failed your own verification. - You started buying something new from them. New parameter, wider range, tighter tolerance. The existing approval does not cover it and nothing in a normal purchase process notices. - A long gap with no orders. Requalify before using a dormant supplier again. ### When no accredited source exists Sometimes the parameter you need is not on anyone's scope. Sometimes the only competent source is the equipment manufacturer. This is a legitimate situation and it has a defensible route through it. Options, roughly in order of strength. Search other accreditation bodies' directories by parameter keyword rather than by lab name, since a different lab may already cover it. Split the order, sending covered parameters to the accredited lab and the uncovered one elsewhere, with the split explicit on the purchase order so the certificate marking matches. Ask the lab to extend its scope, which is real but slow. Go to the manufacturer or a national metrology institute for exotic parameters, checking what accreditation the service centre holds and for which site. Calibrate in house against traceable references with your own documented uncertainty budget, where your standard allows it. Or accept non-accredited but traceable calibration and document why. The last route carries real work. Where accreditation is absent, the evidence you are expected to hold looks a lot like what an assessor would examine. That means method validation records, the uncertainty evaluation, traceability documentation, evidence of ongoing validity of results, personnel competence, equipment records, and facility and environmental controls. That is a substantial file, which is why this route is usually a last resort rather than a saving. Whichever route you pick, check your own obligations first. ISO 9001 leaves the decision to you as long as you apply your own criteria and keep the records. IATF is tighter. The external lab must have the specific service in its defined scope. It must then either be accredited to ISO/IEC 17025 or a national equivalent with that service in the accreditation scope, or be documented as acceptable to your customer. The same clause carries a note for this exact case. Where no qualified laboratory is available for a given piece of equipment, the equipment manufacturer may perform the calibration. You then have to meet the controls IATF sets for an internal laboratory. Keep the evidence either way. Record what you checked and what you found, the date, the reason the gap was acceptable, and who approved it. See also: Check what your standard actually allows (https://axiospec.com/guides/iso-calibration-requirements) ### Diagnostics you can run on your current list today The common failure is not a dramatic one. The list gets built for an audit. Nothing in the buying process ever reads it. It stops being true one supplier at a time while still looking finished. These checks take about twenty minutes. 1. Sort by approval date. If most rows share one date, the list was made in one sitting and has not moved. 2. Sort by re-evaluation due date. Count the rows in the past. Count the blanks. Blank is worse than overdue. 3. Count rows with any status other than approved. Zero means the status column is decorative. 4. Pull the last twelve months of calibration purchase orders and match each supplier to a row. Suppliers with no row are your shadow list. 5. Take your three highest-spend calibration suppliers. For each, open the accreditation body directory and confirm the accreditation is live, the site matches the ship-to address, and the scope covers the instruments you actually sent. 6. Check whether the certificate expiry column and the re-evaluation column ever hold different dates. If they are always equal, one is being copied into the other and no independent evaluation is happening. 7. Ask who owns the list. If the answer is a department, no one owns it. See also: Rebuild the list in the free template (https://axiospec.com/tools/approved-supplier-list-template) ### Where Axiospec fits Axiospec is cloud calibration management software from CaliTech LLC. It is a documentation and workflow tool. It does not certify or accredit anyone, and it cannot make a supplier approved. The approval decision and the approved supplier list stay yours. What it holds is the other half. That is the calibration records the supplier decision governs. Records land in a tamper-evident hash-chained ledger, with optional maker and checker approval, where the server refuses to let the person who logged a calibration approve it. When you select a standard, the fields that standard requires are marked on the calibration form and the save is blocked until they are filled. Enforcement is on by default. An admin can relax it per workspace, and a brand new workspace is exempt only until its first calibration. The one exception is the certificate itself: because it is a file upload it stays advisory in the form, though the REST API does enforce it. There are per-instrument uncertainty budgets and built-in AIAG MSA studies. Native iOS and Android apps give you offline capture and QR scanning on every plan. A self-serve CSV and Excel import reads GAGEtrak and GAGEpack exports. The free plan is permanent. It is not a trial. It covers 50 instruments with unlimited users. A new workspace runs on Professional for its first 45 days. After that it stays free at 50 instruments unless you move to a paid tier. Paid tiers are 59, 129 and 229 US dollars per month with unlimited users. The two supplier tools linked from this guide, the approved supplier list builder and the supplier scorecard calculator, are free and need no account. The certificate expiry page is not a tool. It describes something we are considering building. See also: Approved supplier list template (https://axiospec.com/tools/approved-supplier-list-template) See also: Supplier scorecard calculator (https://axiospec.com/tools/supplier-scorecard-calculator) ### Common questions Q: What should I check before approving a calibration supplier? A: Check the scope of accreditation, not the certificate. The certificate says a lab is accredited. The scope says for what. Confirm your specific measurement parameter appears as a row. Confirm your range sits inside the listed band. Confirm the row covers the service you need, because measuring a quantity is not the same as sourcing it. Then check the stated uncertainty against your tolerance. Confirm the accreditation is held by the legal entity and the site that will do the work, since accreditation is issued per facility. Verify all of it in the accreditation body's public directory rather than from a PDF the supplier emailed you, because accreditation can be suspended, withdrawn or reduced since that file was saved. Then agree your requirements in writing before the first order. That means as-found and as-left data, reported uncertainty, the decision rule behind any pass statement, out-of-tolerance notification, and whether subcontracting is allowed. Q: Does ISO 9001 require an approved supplier list? A: No. The phrase does not appear in ISO 9001. What the standard requires is that you determine and apply criteria for evaluating, selecting, monitoring and re-evaluating external providers. It also requires you to retain records of those activities and of any necessary actions arising from them. The criteria are the part auditors ask for first. A tidy list with nothing behind it is a common finding. A list is simply the ordinary way to hold those records, which is why nearly everyone builds one. Aerospace is different. AS9100D does require a register of external providers carrying approval status and the scope of that approval. Q: Does my calibration lab have to be ISO/IEC 17025 accredited? A: It depends on which standard you work to. ISO 9001 does not require it. Its traceability rule applies where traceability is a requirement, or where you treat it as essential to confidence in your results. In that case the equipment has to be calibrated or verified against measurement standards traceable to international or national measurement standards. ISO 9001 also tells you to take the provider's own controls into consideration when deciding how much control to apply. ISO 13485 does not require accreditation either. It requires supplier control proportionate to the risk associated with the device. IATF 16949 comes closest to requiring it. An external laboratory must have a defined scope covering the service you buy. On top of that, either the lab is accredited to ISO/IEC 17025 or a national equivalent with that service in its accreditation scope, or you hold evidence the lab is acceptable to your customer. Where accreditation is the route, the certificate has to carry the mark of a national accreditation body. Aerospace picks up the expectation through customer flowdown rather than through AS9100D itself. Accreditation is usually the cheapest way to satisfy your own criteria. It is a means, not a universal requirement. Q: What is a scope of accreditation and how do I read it? A: It is a separate document from the accreditation certificate, and it is the one that answers your question. It lists, per capability, the measurand or type of instrument, the method, the measurement range with any other relevant parameters, and the measurement uncertainty. Those elements together are one calibration and measurement capability, or CMC. The uncertainty figure is part of the CMC, not the whole of it, and it only applies inside the range, method and conditions on the same line. Treat that figure as a floor. It is the smallest uncertainty the lab can reach on a near-ideal item under routine conditions, so the uncertainty printed on your own certificate will be that value or larger. Column headings vary by accreditation body. Some use the letters CMC and some say expanded uncertainty of measurement, so read the footnotes. To read a row, find the one matching your parameter. Confirm your range falls inside the listed band. Check whether the row covers measuring the quantity or sourcing it, because many scopes list those separately. Then compare the listed uncertainty against your tolerance as a first screen. Also check the footnotes for restrictions such as field-only or bench-only service. Q: Is the CMC on the scope the uncertainty I will get on my certificate? A: No, and it should not be. A CMC is the smallest uncertainty the lab can achieve calibrating a near-ideal device under normal conditions. Most instruments sent in are not near-ideal, so the uncertainty reported for your job includes contributions from your device and is usually larger. One rule is firm. An accredited lab must not report an uncertainty smaller than its published CMC for that work, so a number below the scope value needs an explanation rather than thanks. A reported value that lands exactly on the CMC is not a defect on its own. That happens when your device adds little and the figures round to the same number. What is worth questioning is the same uncertainty printed on every line across clearly different items. Ask the lab how it evaluated the contribution from your instrument. On-site work usually carries a larger uncertainty because of the site environment and the transport of the lab's standards, so compare it against the on-site rows of the scope rather than the bench rows. Q: How often should I re-evaluate a calibration supplier? A: No standard sets an interval. Annual is the common default and risk tiering is widespread, with shorter cycles for sole-source or high-consequence suppliers. Run that periodic re-evaluation on your own clock rather than on the supplier's accreditation cycle, because accreditation cycles usually run longer than a year. Then keep a separate expiry watch that fires 60 to 90 days before the accreditation expiry rather than on it, so you have time to requalify or line up an alternative. Keep your re-evaluation due date as a separate field from the supplier's certificate expiry date. Merging them means an unexpired certificate silently counts as a current evaluation. Then add event triggers. Those include a scope reduction, which a body can post at any point in the cycle rather than only at renewal, suspension or withdrawal, a site move or acquisition, a certificate missing a required element, a late out-of-tolerance notification, or you starting to buy a parameter or range the existing approval never covered. Q: Why does as-found data matter so much on a calibration certificate? A: Because it is the clearest evidence you have of the instrument's condition before the lab touched it. Every one of the main quality standards requires you to determine whether previous measurement results were affected when an instrument is found unfit for use. That duty stands whether or not you have the data. Without as-found readings you cannot bound the error, so you fall back on worst-case assumptions, your own intermediate checks, or re-inspection of product. In practice that means treating everything measured since the last calibration as suspect until you prove otherwise. As-found readings will not tell you when the drift started. They do tell you how far off the instrument was at the end of the interval, and that is what narrows the suspect population. ISO/IEC 17025 requires results before and after any adjustment or repair to be reported if they are available, and a lab that adjusts without recording as-found readings has nothing to report. So specify as-found data as a purchase requirement rather than assuming it. If you already hold a certificate without it, ask the lab whether it retained the readings before you write the product off. Q: Can an accredited lab issue a non-accredited calibration? A: Yes, routinely. Many labs sell an accredited service and a cheaper traceable or commercial service on the same instrument, and the difference is often a single line on the purchase order. Work can also fall outside the accreditation because the parameter or range is not on the scope, because it was performed at a site or in a mode the scope does not cover, or because it was subcontracted. Under the accreditation-marking policies, a report containing no accredited results should carry no accreditation symbol or reference anywhere, and a mixed report should identify which results fall outside the scope. So read the certificate rather than the logo. Record on your approved supplier list which service level you approved for each parameter. --- ## Tolerance Stack-Up Analysis: Worst Case and RSS https://axiospec.com/guides/tolerance-stack-up-analysis Last updated: 2026-09-08 How to run a linear tolerance stack-up. Closing the loop, rebasing unequal tolerances, the worst case and root sum square methods, what RSS actually assumes, and how far wrong it goes when those assumptions fail. A tolerance stack-up answers a question every assembly drawing raises and few of them answer: given what each part is allowed to be, how much can this gap actually vary? The arithmetic is not hard. Getting it right depends on closing the loop properly, rebasing tolerances that are not symmetric, and being honest about which method you are entitled to use. This guide covers the linear case, which is most of the work in practice. ### Close the loop first Before any arithmetic, define the loop. It runs from one face of the gap you care about, through every part that touches on the way, and back to the other face. Every contributor between those two faces appears exactly once. Nothing outside the loop is allowed to move the gap. Give each contributor a direction. Use plus when growing that dimension opens the gap and minus when it closes it. Use a fraction when only part of a dimension enters the loop, for example 0.5 for a radius taken off a diameter. An incomplete loop is the failure that no amount of careful arithmetic recovers. If thermal growth, clamp-up, plating thickness or gasket crush moves your gap, those are contributors and they need to be in the list. ### Rebase every contributor, including the awkward ones Both methods need each contributor expressed as a mean and an equal half tolerance. The mean is the midpoint of the printed limits. The half tolerance is half the span between them. For a symmetric dimension this changes nothing. For an unequal or unilateral one it changes everything. A dimension of 50.000 +0.200 / -0.000 has a mean of 50.100 and a half tolerance of 0.100. Treating it as 50.000 plus or minus 0.200 gets both numbers wrong and shifts the whole stack in one direction. This is the step hand calculations skip most often, and because it shifts rather than widens the result, it produces an answer that looks reasonable and is not. Tip: Repeated identical parts are separate terms. Five spacers at plus or minus 0.050 are five contributors, not one contributor of 0.250. It matters enormously for RSS, where five terms of 0.050 give 0.112 rather than 0.250. ### Worst case, the arithmetic method The mean gap is the signed sum of the means. The worst case half width is the sum of the absolute sensitivities times the half tolerances. The gap runs from the mean minus that half width to the mean plus it. Worst case is a genuine bound. It assumes only that every part stays inside its stated limits and that your loop is complete and correctly signed. It makes no assumption about distributions and none about independence, which is why correlation between parts cannot break it. A bound stays a bound whether the contributors move together or not. What worst case does not tell you is how likely the extreme is. In a five part stack of centred, independent parts the chance of reaching the worst case is vanishingly small. The method never claims otherwise, so it should never be quoted with a percentage attached. See also: Free tolerance stack-up calculator (https://axiospec.com/tools/tolerance-stackup-calculator) ### Root sum square, the statistical method The RSS half width is the square root of the sum of the squared, sensitivity-weighted half tolerances. Signs drop out of the tolerance term because of the squaring, though they still govern the mean gap. It works in two steps and only one of them is an assumption. Step one is exact: for independent random variables the variance of a weighted sum is the weighted sum of the variances. Step two is the assumption: if every tolerance is the same multiple of its own standard deviation, that common multiplier cancels and you may root sum square the tolerances directly. If the sigma levels differ between contributors, the plain formula is wrong. Do not tell anyone the arithmetic fails without normality. It does not. Normality is needed for the percentage claim, not for the algebra. ### What RSS assumes, and how each assumption breaks None of these are technicalities. They are the difference between a number you can put on a drawing and a number that will be contradicted by the first production run. - Independence. No shared cause between contributors. This fails for two features cut in one setup, parts from one mould cavity, parts from one bar of stock, one fixture, or anything driven by a common temperature. - Centred processes. Each process mean sits at the middle of its tolerance. Tool wear, machine warm-up and a supplier biasing toward the safe material condition all break this, and a known mean offset adds arithmetically rather than in quadrature. - A common sigma level. Every tolerance is the same multiple of its own standard deviation, and you state which. Plus or minus 0.1 at three sigma and plus or minus 0.1 at six sigma are different claims about the same number. - Roughly normal contributors, or enough of them that the sum is. Sorted or fully inspected parts are truncated. Multi-cavity and multi-spindle output is multi-modal. Parts made to a go gauge pile up against one limit. - No single dominant term. If the largest squared term is more than half the sum of squares, the assembly inherits that one part and the normal argument is weak. ### How far wrong RSS goes when the assumptions fail A worked case makes it concrete. Take two contributors of equal half tolerance whose values are spread uniformly across their limits, which is roughly what a sorted or loosely controlled process produces. Their sum is triangular rather than normal. Classic RSS puts the three sigma half width at 1.414 times the tolerance. The true central 99.73 percent half width of that triangle is 1.896 times it. And the fraction of assemblies falling outside the RSS band is 8.58 percent, not the 0.27 percent the normal assumption implies. That is a factor of about thirty on the fallout rate, in the direction that costs money. The arithmetic was correct throughout. The distribution assumption was not. ### Running a stack-up 1. Define the loop. Start at one face of the gap, walk through every part that touches, and finish at the other face. List each contributor once. 2. Give each contributor a direction: plus if growing it opens the gap, minus if it closes it, and a fraction when only part of the dimension enters the loop. 3. Rebase every contributor to a mean and an equal half tolerance from its printed limits. Do this even when the tolerance looks symmetric, so the unequal ones cannot slip through. 4. Compute the mean gap as the signed sum of the means. 5. Compute the worst case half width as the sum of the absolute sensitivities times the half tolerances. This is your bound. 6. Check your signs. Recompute the maximum and minimum gap straight from the printed limits, with no rebasing, and confirm both routes agree. If they do not, a sign or a conversion is wrong. 7. Decide whether you are entitled to a statistical result. Check the number of contributors, whether any one dominates the variance, and whether you have capability evidence for every part. 8. If you are, compute the RSS half width and state the sigma level it assumes. If you are not, stop at worst case and say so. See also: Run this in the calculator (https://axiospec.com/tools/tolerance-stackup-calculator) ### Choosing between them Use worst case by default, and always when a single non-conforming assembly is unacceptable. That covers safety-critical fits, sealing, prototypes, single builds, low volume, spares that must interchange, and anything you cannot rework or select-fit. Use it whenever you have no process data, and whenever the loop has fewer than about four contributors. Use RSS for volume production where a small, quantified and detectable fallout is acceptable, and where you have capability evidence on every contributor or a supplier commitment to a stated capability. It pays when several contributors are of similar size. It pays almost nothing when one term dominates. Never use RSS silently. If the design depends on it, the drawing has to carry the statistical tolerancing requirement, because a supplier shipping every part at one limit is fully conforming and your RSS number was never true. ### On standards, plainly There is no standard that gives a general tolerance stack-up procedure. It is worth knowing that, because plenty of material implies otherwise. ISO 286-1 computes fit clearances arithmetically from the limits, where maximum clearance is the hole upper limit minus the shaft lower limit. That is a worst case stack on a two part loop, and it is the only standardised piece of this arithmetic. Do not stretch it further than two parts. ASME Y14.5 defines the dimensioning and tolerancing language and what limits mean. It gives no stack-up formulas. The methods here come from engineering practice and from textbooks, notably Fischer's Mechanical Tolerance Stackup and Analysis and Drake's Dimensioning and Tolerancing Handbook. If someone cites a standard for RSS stack-up, ask which clause. The honest answer is that the practice is conventional rather than specified. See also: Choosing a fit: press, transition and clearance (https://axiospec.com/guides/press-fit-tolerance-transition-and-clearance-fits) ### A stack-up is not an uncertainty budget The two are easy to conflate because both combine contributors in root sum square, and quality engineers meet both. A tolerance stack-up combines the permitted variation of parts to predict how an assembly will vary. A measurement uncertainty budget combines sources of doubt about a measurement to state how well you know a value, then expands the result by a coverage factor to a stated confidence. A tolerance is a permission granted to a process. An uncertainty is a statement about knowledge. They answer different questions and a number from one does not transfer into the other without saying which you mean. See also: Measurement uncertainty budget calculator (https://axiospec.com/tools/measurement-uncertainty-budget-calculator) See also: Guard banding and decision rules (https://axiospec.com/guides/guard-banding-in-calibration) ### Where Axiospec fits Axiospec does not run stack-ups. It is calibration management software, and the tolerance stack-up calculator on this site is a free standalone tool with no account behind it. The connection is the gauge doing the measuring. A stack-up tells you how much your assembly can vary. It says nothing about whether the instrument checking it is still reading true. Axiospec keeps that side: calibration status on every instrument, as-found and as-left readings, and per-instrument uncertainty budgets that feed a test uncertainty ratio. If your stack-up says a feature has 0.05 mm of room and the gauge measuring it carries an uncertainty of 0.02 mm, the stack-up was only half the analysis. ### Common questions Q: What is tolerance stack-up analysis? A: It is the arithmetic that tells you how much a gap or a fit can vary once you add up the tolerances of every part between its two faces. You define a loop from one face of the gap, through every part that touches, and back to the other face. Each contributor gets a direction, plus if growing it opens the gap and minus if it closes it. Then you combine the tolerances, either arithmetically for a bound or in quadrature for a statistical prediction. Q: What is the difference between worst case and RSS tolerance analysis? A: Worst case adds the tolerances arithmetically. It is the widest the gap can be if every part sits at its worst limit at once, so it is a genuine bound and it needs no assumption about distributions or independence. RSS adds them in quadrature, giving a narrower band that describes a population of assemblies rather than a bound. RSS rests on assumptions worst case does not need, and real parts do fall outside an RSS band. Q: What does RSS stand for in tolerance analysis? A: Root sum square. You square each sensitivity-weighted half tolerance, add the squares, and take the square root. It is sometimes written RMS, root mean square, in the same context. Adding variances in quadrature is exact for independent random variables, so the arithmetic itself is not in question. The assumption is in going from variances to tolerances, which works only when every tolerance is the same multiple of its own standard deviation. Q: Why do I have to rebase unequal tolerances before adding them? A: Because both methods need a mean and an equal half tolerance for every contributor. A dimension of 50.000 +0.200 / -0.000 is centred on 50.100 with a half tolerance of 0.100, not on 50.000. Skipping this shifts the answer rather than widening it, so the stack-up comes out confidently wrong in one direction. It is the single most common error in a hand calculation. Q: How many contributors do I need before RSS is reasonable? A: About four as a rough floor, and that is a judgment rather than a rule. Below that there is no central limit argument, so the sum keeps whatever shape the individual parts have and the normal percentages do not apply. Also check whether one contributor dominates. If the largest squared term is more than half the sum of squares, the assembly inherits that one part's behaviour and the statistical argument is weak no matter how many terms you have. Q: How wrong can RSS be when its assumptions fail? A: Materially wrong, and in the unsafe direction. Take two contributors of equal tolerance whose values spread uniformly across their limits, which is what a loosely controlled or sorted process looks like. Their sum is triangular. Classic RSS puts the three sigma half width at 1.414 times the tolerance, but the true central 99.73 percent half width is 1.896 times it, and the fraction falling outside the RSS band is 8.58 percent rather than 0.27 percent. The arithmetic did not fail. The distribution assumption did. Q: Is there an ISO or ASME standard for tolerance stack-up? A: Not for the general procedure. ISO 286-1 computes fit clearances arithmetically from the limits, which is a worst case stack on a two part loop, and that is the only standardised piece of this arithmetic. ASME Y14.5 defines what the tolerances mean and gives no stack-up formulas. The methods come from engineering practice and textbooks rather than from a clause, so anyone citing a standard for RSS stack-up should be asked which clause. Q: Is a tolerance stack-up the same as a measurement uncertainty budget? A: No, though the arithmetic rhymes and both use root sum square. A stack-up combines the permitted variation of parts to predict how an assembly will vary. An uncertainty budget combines sources of doubt about a measurement to state how well you know a value, then expands the result by a coverage factor to a stated confidence. A tolerance is a permission granted to a process. An uncertainty is a statement about knowledge. Do not carry a number from one into the other without saying which you mean. --- ## Press Fit Tolerance, Transition Fit and Clearance Fit https://axiospec.com/guides/press-fit-tolerance-transition-and-clearance-fits Last updated: 2026-09-08 How to choose a fit from what the joint has to do, rather than by picking something that looks about right off a table. Clearance, transition and interference, why bearing seats follow the bearing catalogue instead of the fits system, and what gauge uncertainty does to the accept or reject decision. Most people arrive at this subject holding a designation and wanting a number. H7. g6. Light press. The number is the last thing you should be reaching for, and you will not find one on this page. What you will find is the reasoning that produces it, which is the part no table gives you. This guide works from what the joint has to do, through the mechanism that makes each kind of fit work, to the question almost nobody covers: how you prove a part actually met the fit once you have specified it. ### Start from the function, not from a table Two reading rules make the rest of this page usable. The letter in a tolerance class sets where the tolerance zone sits relative to the basic size. The number, the IT grade, sets how wide that zone is. For most classes those are separate choices, and that separation is what makes the system compact. It is not universal. A few classes are defined in terms of the grade itself, and several letters carry a correction that depends on the grade as well. Those positions have to be read from the table rather than reasoned out. Capital letters are internal features, which the standard calls holes. Lowercase letters are external features, which it calls shafts. A fit is always a pair and it is written hole first, as in H7/g6. The case is not decoration. It tells you which member of the pair you are looking at, and the same letter in the two cases does not describe the same zone. What the case does not tell you is which side of the basic size the zone falls on. That comes from the letter, and for several letters it moves with the grade as well. Almost everything else follows from two facts. An H hole is never smaller than the basic size. An h shaft is never larger than it. Hold those two and you can reason your way through a great many fits without reading a single value. What the standard will not do is tell you whether the joint works. It has no opinion on your load, your temperature, your lubricant, your assembly method or how often the thing has to come apart. Choosing the fit is engineering. The designation is only how you write the answer down. Tip: Hole and shaft are generic terms for internal and external features of size. Nothing has to be round. A slot width and the key that goes in it are toleranced with the same letters and grades. ### Choosing a fit, step by step Work down this list in order. The early questions eliminate most of the search space, and the last one is the only place a letter appears. 1. Ask what the joint is for. There are four answers. It allows relative motion. It locates parts while something else carries the load. It transmits load by friction through the fit itself. Or it holds a bought-in precision component. 2. If it holds a bought-in component, stop and open that component's catalogue. Bearings, seals, bushings and linear rail blocks all carry their own fit recommendations, and those override the general system. 3. If it moves, size the clearance from the lubricant film, the differential thermal growth, the form error on both parts, the contamination you expect and any wear you are prepared to live with. Clearance is a designed dimension, not a leftover. 4. If it only locates, decide what actually carries the load. A key, a spline, bolts or a flange means the fit only has to hold concentricity. That is transition territory, or a light interference at most. 5. If the fit is the only load path, size the contact pressure and check the hoop stress in the outer member. You are doing a stress calculation, not picking a letter off a list. 6. Ask how it comes apart and where. Never, in a factory with a press, or in the field at two in the morning with what is in the van. Those are three different fits. 7. Check the cross-cutting effects before you commit. Operating temperature, rotational speed, dissimilar materials, plating and coatings can each undo a correct designation. 8. Only now choose the classes. Specify the hole one IT grade coarser than the shaft unless you have a reason not to, because a hole is harder to hold to size than a shaft for the same manufacturing effort. Tip: A single class is not a fit. H7 on its own tells you nothing about how the joint behaves. You need both members before you can say anything. ### If it has to move: what sets the clearance Clearance is a functional dimension and it should be arrived at deliberately. Add up the lubricant film you need, the differential growth between the two parts at operating temperature, the form error each part is allowed, the dirt you expect to live with and the wear you will accept before the joint is scrap. That sum is your minimum clearance. The class is chosen to cover it, not the other way round. Some cases hand you the answer through their own physics. A hydrodynamic journal runs on a film whose thickness, power loss and stability all come out of the clearance. Too much clearance and the film collapses at low speed. Too little and you get heat and then seizure. That is a bearing calculation, and it gives you a target clearance that you then find a class to cover. Leakage through an annular gap is extremely sensitive to the gap. A valve spool or a plunger clearance is set by permitted leakage, and small changes in the gap make large changes in the flow. Anything running hot, dirty or unlubricated wants more clearance than the same joint running clean and cool. ### If it only has to locate: transition fits and what they do not promise A transition fit is one where the hole and shaft tolerance zones overlap. A given pair can come out with a small clearance or a small interference depending on where each part happened to land inside its own zone. That is the definition, and it carries a consequence most explanations skip. A transition fit does not have an answer. It has a distribution. And that distribution is not an even split between the two outcomes, which is the assumption people quietly make. Where it lands is set by where your two processes actually run inside their zones, and processes do not sit in the middle. A reamer produces holes that drift across the zone as the tool wears. Machinists routinely bias shafts toward the high end and holes toward the low end, because an oversize shaft or an undersize hole can be recut while the opposite is scrap. In a hole-basis pair both of those biases push the same way, toward interference. So assembly planning has to work for both outcomes. If the process cannot cope with a loose one, or the function depends on grip, a transition fit is the wrong choice no matter how good the average looks. Use it where you want accurate concentric location with very little radial play, and where something else is carrying the load. ### If the fit is the load path: interference, and why more is not safer An interference fit holds by friction. The interference stretches the hub and compresses the shaft, that elastic recovery produces contact pressure at the interface, and the holding force is that pressure multiplied by the contact area multiplied by the coefficient of friction. Everything else follows from that sentence. Two scaling facts are worth carrying around, and they come from the same place. The friction force is contact pressure times contact area times the coefficient of friction, and the contact area grows with both diameter and engagement length. So axial holding capacity grows with both. Torque capacity grows with the same product and then picks up one more factor of diameter, because that friction force acts at a radius. At the same contact pressure, doubling the diameter roughly doubles the axial capacity and roughly quadruples the torque capacity. Now the reason more interference is not safer. The contact pressure that grips the shaft also puts the hub bore into tension, and for a hub with a free outer surface the tensile hoop stress at the bore is larger than the contact pressure that produced it, at any wall thickness. Push the interference up and you are raising a stress that is already the highest in the part. Thin-walled hubs are where this bites hardest, because contact pressure is strongly sensitive to wall ratio when the wall is thin and only weakly sensitive when it is thick. A thin hub gives you little grip for a lot of stress. Surface finish quietly takes some of your interference away. Pressing flattens the asperities on both surfaces, so the effective interference after assembly is less than the interference you measured before it. The loss depends on the finish of both parts and it does not scale with diameter, which means a small interference fit is proportionally far more sensitive to surface finish than a large one. A shrink or expansion fit avoids the problem, because the surfaces are not sliding against each other under pressure during assembly, so it gives more holding capacity than a cold press at the same nominal interference. Two more things that catch people out. Pressing a thin-walled bushing into a housing closes its bore. In the thin-wall limit the wall moves inward bodily rather than compressing, so the bore diameter closes by very nearly the full diametral interference. Machining that bore to final size before pressing is therefore a mistake, and the usual answer is to finish it after assembly. And two assemblies that both conform to the same designation can need very different press forces, because one pair may sit at opposite ends of their zones from the other. A press force limit set from one sample is not a process control. Tip: A keyway cut into a hub bore puts a stress concentration straight through the most highly stressed region of the hub. A key and an interference fit on the same joint do not share the transmitted load in any predictable ratio. Decide which one is the design load path and treat the other as insurance. ### If it holds a bearing: the catalogue decides, not the fits system Go to the bearing maker's catalogue for that part number and use what it says. This is not deference for its own sake. Rolling bearing bores and outside diameters are toleranced to the rolling bearing standard, ISO 492 for radial bearings, rather than to the general fits system, and both are biased below nominal size. So a shaft class that gives a light transition against an ordinary hole gives real interference against a bearing bore. Reasoning from the general system here gives you a tighter fit than you intended. The decision logic underneath the catalogue is worth knowing, because the tables leave it implicit. The governing question is which ring carries the rotating load. A ring carries a rotating load when the direction of the applied load sweeps around that ring's circumference. That is not the same as the ring itself rotating, and confusing the two is where most of the mistakes come from. The ring carrying the rotating load is the one that needs the interference. Work it through. On a rotating shaft under a load that is fixed in space, which is the ordinary gearbox or motor case, the inner ring carries the rotating load and gets the interference. On a stationary shaft inside a rotating housing, such as a wheel hub, the outer ring carries it. And on an out-of-balance rotor, where the unbalance dominates the load and its direction turns with the shaft, the answer inverts relative to the ordinary case and the outer ring is the one carrying the rotating load. Real rotors carry space-fixed loads too, so check which one actually governs before inverting anything. Get it wrong and the ring creeps. Under a rotating load the ring deflects at the loaded point, that point travels around the seat, and the ring rolls very slowly relative to its seat. The symptom is fretting, reddish-brown oxide debris around the seat, and progressive wear that makes the seat oversize and the problem worse. No amount of axial clamping fixes creep. The other half of the bearing decision is that interference fitting a ring squeezes it, which reduces the bearing's radial internal clearance. Fit selection and internal clearance class have to be decided together. A fit chosen without reference to the clearance class can preload the bearing into itself, which raises running temperature and shortens life. This is the most concrete form of the more-is-safer error. ### If it locates a fixture: dowels are a different problem Dowel fits get treated as a bearing-seat problem almost everywhere, and they are not one. A bearing seat transmits load and never comes apart. A dowel gives repeatable location and usually has to come apart. That difference drives everything. The convention is interference in one part and a locational fit in the other, so the assembly can be separated and put back exactly where it was. Press both and you cannot take it apart without damage, and you have also made the two hole positions agree perfectly or fight each other. Two round pins in two round holes overconstrain the assembly. The centre distance on one part has to match the centre distance on the other exactly, which no process gives you. The usual resolution is to relieve the second pin along the line joining the two holes, so it constrains rotation without also trying to constrain centre distance. Two practical points that cost real money. Blind dowel holes need a vent, because trapped air stops the pin seating fully and trapped fluid can split the part. And holes reamed before heat treatment move in both size and position during hardening, which is why hardened plates get jig ground or wire cut after heat treatment rather than reamed before it. ### Reading the designation you have chosen The IT grade expresses a level of manufacturing precision rather than a physical width. Two features at the same grade and different sizes are about equally hard to make, and they do not have the same permitted variation. The permitted width grows with size, because deflection, thermal growth, measurement uncertainty, tool wear and workholding distortion all grow with size, but it grows less than in direct proportion. Doubling the size does not double the tolerance. The system is stepped rather than continuous. Sizes are divided into ranges and one width applies across a whole range, so the permitted variation is flat inside a step and jumps at the boundary. A designer who nudges a nominal size across a step boundary changes the tolerance without changing anything else on the drawing. That is worth knowing and it is almost never taught. The letters run in bands. Against an H hole, the shaft letters up to and including h give clearance, with the designed clearance shrinking at each step as you move up the alphabet. h is the boundary, and it is the tightest shaft that still cannot produce interference. Around js, j, k, m and n you are in transition territory. From p upward you are into interference. Treat those bands as a map rather than a rule, because the point where transition becomes interference moves with both the nominal size and the grades. That last point generalises into the single most useful correction on this topic. The fit category is a property of the pair of classes, not of the shaft letter on its own. The same shaft letter gives a transition fit against one hole class and something else against another, because changing the grades changes the zone widths and therefore changes whether the zones overlap at all. Anyone who tells you that a given letter is a transition letter, without naming the hole class and both grades, is guessing. - H7/h6 is a clearance fit, not a transition fit. An H hole is never below the basic size and an h shaft is never above it, so the zones cannot overlap whatever the grades. Its minimum clearance is zero, and a fit whose minimum clearance is zero is still a clearance fit. This is the most common misclassification in published explanations. - The descriptive names, sliding, close running, locational transition, medium drive, come from handbook and preferred-metric-fits practice rather than from the text of the fits standard itself. They are useful vocabulary. They are not definitions you can cite. - A hole one grade coarser than the shaft is convention, not law. Equal grades on both members are perfectly legal. They just cost more for the same result. ### Temperature, speed and coatings move the fit after you specify it A size tolerance is a statement about the part at the standard reference temperature of twenty degrees Celsius, which is set by ISO 1, and at no other temperature. Everything in this section is about what happens between that statement and a machine running in a real building. Two parts of the same material at the same uniform temperature keep the same fit in the way that matters. Every dimension scales by the same factor, the interference scales with them, and so the contact pressure is unchanged. The absolute gap moves a little. The character of the fit does not. Dissimilar materials do not have that protection. A steel shaft in an aluminium housing loses interference as the assembly heats, because aluminium expands faster than steel. That has to be checked at the operating temperature rather than on the bench. Worse, repeated thermal cycling of a dissimilar-material interference fit can loosen it progressively, because the parts slip a little on each cycle and do not fully return. Speed does the same thing by a different route. A rotating hub grows radially in proportion to the square of its angular speed, and that growth eats the interference you have at rest. A fit that is correct stationary can be marginal at running speed. Finally, remember that surface treatment happens after machining. Electroplating and hard anodising change the finished dimensions. A coated shaft finishes larger than it was machined and a coated bore finishes smaller. Specify where in the process the dimension applies, or you will get an argument about it later. Tip: Thermoplastics creep under sustained load, so an interference fit in a polymer relaxes over time. Polyamides also absorb atmospheric moisture and grow dimensionally. A metric fit class is an unreliable specification for a moulded part. ### Both parts were in spec and they still would not go together This is the bridge from design into inspection, and it is where two-point measurement quietly lets you down. The first cause is which rule your drawing runs under. In the ISO scheme the default is the principle of independency, stated in the 2011 revision of ISO 8015, so size and form are independent requirements unless the envelope requirement is specifically invoked. Older drawings may not carry that default, so check what the title block invokes. Under ASME Y14.5, rule one requires perfect form at the maximum material condition for a regular feature of size, with form error permitted to grow as the feature departs from that condition. Same nominal drawing, different meaning. A perfectly conforming ISO part can carry form error that an equivalent ASME part could not. The second cause is lobing. An odd-lobed bore, a three-lobed one being the classic, can measure a constant diameter with any two-point instrument in every orientation and still refuse to accept a plug of that diameter. The part passes every micrometer check you can devise and fails to assemble. Odd lobing is characteristically produced by centreless grinding and by three-jaw chucking, so it is not exotic. ### Verifying the fit: what each kind of check actually proves There are two kinds of check and they produce different evidence. Attribute checks give you a decision and no number. Variable checks give you a number. Which you use changes what you can detect later, so this is a bigger decision than it looks. Limit gauges are the attribute case. Under Taylor's principle the GO member checks the maximum material limit over the full length and full form of the feature, so it evaluates size and form together, while the NO-GO member checks the least material limit at individual cross sections with effectively two-point contact. That is why a bore which passes a GO plug is not merely within size, it is within size along its whole length including any bend, taper or lobing. Note that this is the principle rather than a description of every gauge on the shelf. Real NO-GO plugs and rings are often made full form rather than as the two-point check the principle asks for, which means they can be blocked by form error and pass a part that a true two-point check would have caught. The variable case runs on a capability ladder. At coarse grades handheld instruments are genuinely fine. In the middle band, micrometers, dial bore gauges and limit gauges all do the job, and this is where most shop practice sits. At fine grades everything becomes comparative. A bore gauge or an air gauge does not measure a bore, it measures the difference between that bore and a master, so the whole accuracy of the check is inherited from a setting ring or a stack of gauge blocks. At the finest grades you need a temperature-controlled room, soaked parts and a real uncertainty budget, and without those you cannot verify the grade honestly no matter what instrument you buy. Air gauging deserves a mention because quality managers often do not know it is an option. It is non-contact, so it does not wear the part, it is fast enough for production, and it works well in tight bores. The trade is that it is comparative over a narrow range around a setting master, it needs a master for every size, and it responds to surface texture as well as to size. For a CMM, be careful what the specification means. A maximum permissible error figure from an ISO 10360 acceptance test is a machine specification obtained under defined test conditions. It is not the task-specific uncertainty of your measurement. Establishing that requires comparison against calibrated workpieces, which is the method set out in ISO 15530-3. - GO gauges wear in the direction that increases what they accept. A GO plug gets smaller and starts passing undersize bores. A GO ring gets larger and starts passing oversize shafts. Both wear modes fail toward false acceptance, which is the dangerous direction. - An attribute gauge produces no measured value, so nothing in your per-part data can show that the gauge has drifted. There is an indirect signal at process level, because wear moves the reject fraction in a predictable direction, and charting that fraction or re-checking rejected parts on a variable instrument can raise suspicion. It is lagging, it is easily confounded with a genuine process change, and it never tells you which parts were affected. The calibration record is the direct evidence. - Limit gauge tolerance and wear allowance are conventionally set as fractions of the workpiece tolerance. The same physical amount of wear therefore consumes the allowance faster on a gauge used for a fine-grade feature than on one used for a coarse feature. ### What measurement uncertainty does to the accept or reject decision Here is the pivot. As the grade tightens, the tolerance shrinks while the uncertainty of your measurement process stays exactly where it was. So the ratio between them falls purely because someone changed the drawing. At some point the gauge is no longer capable of making the decision the drawing is asking it to make, and nothing about that is visible in the measurement itself. The number that tracks this is the test uncertainty ratio. It takes the tolerance of the characteristic being judged, as a half width, over the expanded uncertainty of the measurement process as you actually perform it. That denominator is the part people get wrong. It has to include the setting master, the comparator, resolution, repeatability, reproducibility across operators, thermal effects and the workpiece itself. Putting the instrument's datasheet accuracy in there instead gives you a test accuracy ratio, which is a different and more flattering number. On the conventions, be precise about where they come from. The familiar four to one ratio derives from United States military calibration practice and is carried into ANSI/NCSL Z540.3 as one route to satisfying its false accept risk limit. The older gauging rule of ten came first, and the military ratio was a deliberate relaxation of it on cost grounds. The gaugemaker's tolerance applied when limit gauges are made, and the AIAG gauge R and R percentage thresholds, express the same underlying idea again at different ratios and for different purposes. So they are related rather than independent. They are still not interchangeable, and quoting one to satisfy a requirement written against another is an argument you lose in an audit. ISO/IEC 17025 sets no numeric ratio at all. It requires that a decision rule be documented and applied consistently. The default rule in ISO 14253-1, the GPS standard on decision rules, subtracts measurement uncertainty from the specification zone, so conformity is only proven inside a narrowed conformance zone, with the supplier proving conformity and the customer proving nonconformity. If your acceptance practice has never been written down, that default is not what you have been doing. One last trap, because it is so common. A gauge repeatability and reproducibility study estimates precision only. It does not include the uncertainty of the reference master and it does not detect bias. An instrument can pass a gauge R and R study comfortably and still have a test uncertainty ratio too poor to judge the tolerance you are pointing it at. See also: Check your TUR with the free calculator (https://axiospec.com/tools/tur-tar-calculator) See also: Guard band calculator (https://axiospec.com/tools/guard-band-calculator) See also: Guard banding and decision rules (https://axiospec.com/guides/guard-banding-in-calibration) See also: Tolerance stack-up analysis (https://axiospec.com/guides/tolerance-stack-up-analysis) ### The mistakes that cost the most - Picking a fit off a list because it looks about right, instead of working out what the joint has to do. - Deriving a bearing seat from the general fits system rather than from the bearing catalogue, which gives you more interference than you intended. - Treating a transition fit as though it will land clearance about half the time. It will land where your processes run, and both common machining biases push the same way. - Adding interference to be safe, when the hoop stress at the hub bore is already higher than the contact pressure you are trying to raise. - Choosing a bearing fit without deciding the internal clearance class at the same time. - Specifying a fit for a joint where a key or bolts carry the load and only concentricity is needed. - Ignoring where in the process the dimension applies, then discovering that plating moved it. - Tightening a grade on the drawing without asking whether the gauge on the floor can still judge it. - Assuming a passed gauge R and R study means the measurement is good enough for the tolerance. ### Why there are no tolerance values on this page, and where to get them The limit and fit tables are published in ISO 286-1 and ISO 286-2, which are copyrighted documents sold by ISO and by national standards bodies. We are not entitled to reprint them and we will not. That applies just as much to a calculator that outputs the same values as it does to a table, which is why you will not find one of those here either. There is a second reason, and it is the one that matters more to you. The published table is the authority. Values generated from the tolerance formulas do not reliably land on the published ones, so a page that quietly computes them is offering you something that looks authoritative and is not. If a number is going on a drawing, it should come from the source. So get the values from a licensed copy. Buy the two parts of the standard from ISO or your national standards body, use a licensed engineering handbook, or use the tables built into your CAD or PLM system if your licence includes them. Any of those gives you a number you can defend in a supplier dispute. A random web table does not. ### Where Axiospec fits Axiospec does not choose fits and it does not hold the tolerance tables. It is calibration management software, and everything above is free reference content with no account behind it. The connection is the gauge. Look back at the two facts in the verification section. A limit gauge wears in the direction that makes it accept more, and a limit gauge produces no measured value at all. Put those together and there is no amount of production data that can tell you a GO plug has gone soft. The calibration record is the only mechanism that can catch it, and the finer the grade the less wear it takes to matter. That is the side Axiospec keeps. Calibration status on every gauge, as-found and as-left readings on every event, and per-instrument uncertainty budgets that feed a test uncertainty ratio so you can see which tolerances your gauges are actually entitled to judge. The as-found reading is the one that earns its keep here. When a plug gauge comes back out of tolerance, the question is not what to do with the gauge. It is which parts you passed with it since the last calibration, and whether any of them shipped. That is a records question, and it is only answerable if the records were kept properly before anyone knew they would be needed. See also: Measurement uncertainty budget calculator (https://axiospec.com/tools/measurement-uncertainty-budget-calculator) See also: As-found and as-left readings (https://axiospec.com/guides/as-found-as-left-readings) See also: Calibration vs verification (https://axiospec.com/guides/calibration-vs-verification) ### Common questions Q: What tolerance do I need for a press fit? A: There is no single answer, and any source that gives you one without asking questions is guessing. A press fit holds by friction. The interference stretches the hub and compresses the shaft, that elastic recovery creates contact pressure, and the holding force is pressure times contact area times the coefficient of friction. So the interference you need depends on the torque or thrust you have to carry, the engagement length, the wall thickness of the hub, both materials, the operating temperature and the surface finish. Work out the contact pressure you need first, check the hoop stress it puts in the hub bore, and only then look for a class that delivers it. Q: What is a transition fit? A: A transition fit is one where the hole and the shaft tolerance zones overlap. A given pair can end up with a small clearance or a small interference depending on where each part happened to land inside its own zone. It exists to give accurate concentric location with very little radial play, on joints where something else carries the load. The important consequence is that it makes no promise about which outcome you get on any individual pair, so your assembly process has to work for both. Q: What is the difference between a clearance fit, a transition fit and an interference fit? A: It comes down to whether the two tolerance zones overlap. In a clearance fit the smallest permitted hole is at least as large as the largest permitted shaft, so every pair you can legally build has play. In an interference fit the largest permitted hole is no larger than the smallest permitted shaft, so every pair needs force, heating or cooling to assemble. In a transition fit the zones overlap, so some pairs come out with play and some with grip. Clearance and interference guarantee an outcome and vary only in amount. Transition guarantees nothing. Q: Is H7/h6 a clearance fit or a transition fit? A: It is a clearance fit, and calling it a transition fit is the most common error in published explanations of this topic. An H hole is never smaller than the basic size. An h shaft is never larger than it. So the two zones cannot overlap whatever the grades are, and no legal combination produces interference. Its minimum clearance is zero, and people see the zero and assume that means transition. A fit whose minimum clearance is zero is still a clearance fit, because zero clearance is not interference. Q: What tolerance should I use for a bearing press fit? A: Go to the bearing maker's catalogue for that part number and use what it says. Rolling bearing bores and outside diameters are toleranced to the rolling bearing standard, ISO 492 for radial bearings, rather than to the general fits system, and both are biased below nominal size. So a shaft class that gives a light transition against an ordinary hole gives real interference against a bearing bore. Reasoning from the general system gives you a tighter fit than you intended. Decide the fit and the bearing internal clearance class together, because interference fitting a ring squeezes it and reduces that clearance. Q: Why did my bearing spin on the shaft? A: Almost always because the ring carrying the rotating load did not have enough interference. A ring carries a rotating load when the direction of the load sweeps around that ring's circumference, which is not the same as the ring itself rotating. Under a rotating load the ring deflects at the loaded point, that point travels, and the ring rolls very slowly around its seat. That is creep, and axial clamping does not stop it. The symptom is fretting, reddish-brown oxide debris and a seat that wears progressively oversize, which makes it worse over time. Q: Should I use hole basis or shaft basis? A: Hole basis is the default and the reason is tooling. Holes are made and checked with fixed-size tools, so every extra hole class you specify means another reamer or broach and another plug gauge. A shaft is turned or ground to whatever size you dial in, so varying the shaft costs nothing extra. Hold the hole at H and vary the shaft. Shaft basis earns its place in two cases: when you are using drawn or ground bar at its as-supplied diameter, and when one continuous shaft carries several components that each need a different fit. Q: How do I check that a part actually meets its fit tolerance? A: Two kinds of check, and they give you different evidence. Limit gauges give a decision and no number. The GO member checks the maximum material limit over the full length and form, so it catches size and form together, and the NO-GO member checks the least material limit at individual cross sections. Variable instruments give a number, but at fine grades they become comparative, so the accuracy is inherited from a setting master. Whichever you use, check the ratio between the tolerance and the uncertainty of the measurement process before you trust the result. Q: Why does this guide not give the ISO 286 tolerance values? A: Because the tables are published in ISO 286-1 and ISO 286-2, which are copyrighted documents sold by ISO and by national standards bodies. We are not entitled to reprint them, and that applies to a calculator that outputs the same values as much as it applies to a table. There is also a practical reason. Values generated from the tolerance formulas do not reliably match the published ones, so a page that quietly computes them looks authoritative and is not. If a number is going on a drawing, take it from a licensed copy of the standard, a licensed handbook, or your CAD system's built-in tables. --- ## The US accredited calibration lab landscape, 2026 https://axiospec.com/guides/us-accredited-calibration-lab-landscape Last updated: 2026-09-12 There is no single public register of accredited calibration laboratories in the United States. Each accreditation body publishes its own directory in its own format. This study collects the public directories of five bodies, A2LA, PJLA, NVLAP, ANAB and IAS, checks every non-derived value against the page it came from, and publishes the result as a free CSV under CC BY 4.0: 1,743 rows, eleven columns, no signup. Dataset: https://axiospec.com/us-calibration-lab-landscape-2026.csv Key figures, September 2026 collection. 722 A2LA US rows resolving to 665 organization names. 352 active PJLA certificates of 407 US rows across all statuses. 78 NVLAP. 486 active ANAB United States certificates of 511 rows, with 422 in its Calibration Labs group and 65 in Forensic Calibration. 20 IAS. The naive sum of active US records is 1,658 and name deduplication gives 1,552; neither is the number of laboratories, and neither belongs in a headline. 303 of the accreditations counted expire during 2026: 139 A2LA, 48 active PJLA, 30 NVLAP, 79 active ANAB and 7 IAS. Why the bodies cannot be added together. A2LA lists per site, so one company with three accredited locations appears three times. ANAB folds satellite sites into a parent record, so 43 of its 511 US rows carry 171 further locations between them. In its Forensic Calibration group ANAB reuses one certificate across many sites; four certificates cover 37 rows, and one state breath-alcohol program is 21 rows on a single certificate. Eight organizations appear in two directories, which is a floor. Six laboratories are listed as available by one body and withdrawn or suspended by another at the same city at the same time. Known limits. The five bodies are not the whole universe: NAC, a United States body and ILAC Mutual Recognition Arrangement signatory for calibration and testing laboratory accreditation, is not collected and belongs in the next version. Two Canadian rows and three Puerto Rico rows sit inside ANAB's United States query and are outside the 486 and 511 figures. The country column carries three spellings, United States, USA and US, one per source. NVLAP scope links are not in the dataset; its lab code is in certificate_number. Directory data carries plain source errors, left as published rather than silently corrected.