An external auditor is in your facility, reviewing your measurement control program. They ask for the calibration certificates for three critical instruments used in final product testing. You provide the documents, which show the instruments were returned from the lab well within their tolerance specifications. But the auditor isn't satisfied. The certificates only contain "as-left" data. There is no record of what the instruments were reading before they were adjusted.
The auditor writes a finding. It's not about a single instrument; it's a systemic deficiency. Without documented as-found data, you have no evidence the instruments were performing correctly during their last service period. Every product decision made using data from those instruments now has a gap in its measurement traceability chain.
This scenario highlights a critical distinction in metrology. As found as left calibration data isn't an optional detail; it's the evidence that connects calibration to every measurement decision made between service cycles. As-found data records the instrument's condition before any adjustment, while as-left data records the condition after all calibration activities are complete.
This guide explains what both readings mean, why quality standards and auditors expect them, what to do when as-found data reveals an out-of-tolerance condition, and how to use this data proactively for interval analysis and contract review.
These two data sets answer fundamentally different questions for your quality system. "As-found" answers, "Was this instrument trustworthy during the period it was in service?" "As-left" answers, "Is this instrument trustworthy going forward?"
The sequence is non-negotiable. As-found data must be recorded before any cleaning, repair, or adjustment. Adjusting the instrument first destroys the evidence of how it was actually performing in your process.
The as-found condition, sometimes called the "as-received" condition, documents an instrument's state when it arrives at the calibration laboratory. A technician compares the instrument's readings at several test points against a reference standard of higher accuracy before making any changes.
Consider a digital multimeter arriving for its annual calibration. Following the calibration procedure, which defines the test points and the connection setup between the reference standard and the instrument, the technician measures its DC voltage function at several points for instance, 1 V, 5 V, and 10 V and records these pre-adjustment readings. This data is the as-found result. It's a direct measurement of the instrument's performance and drift after a full service interval in your operating environment. Where practical, measuring comparable test points from cycle to cycle keeps as-found results directly comparable over time.
Read more: Multimeter Calibration Services | Tescom Calibration Services
After recording the as-found data, the technician performs the calibration, making adjustments if necessary to bring the instrument's performance closer to its nominal value. Once adjustments are complete, the technician measures the same test points again. These post-adjustment readings form the as-left data.
This data confirms the instrument is now performing within its specified tolerance and is ready to be returned to service. When an instrument is found in tolerance (found in tol) and no adjustment is required, the as-found and as-left data may be identical. A complete calibration certificate should clearly state that no adjustment was performed in this case.
As-found and as-left data serve three distinct purposes in a regulated or quality-critical operation. Each one shows why calibration documentation functions as a quality control record, not only a compliance requirement.
Quality management systems like ISO 9001, AS9100, and IATF 16949 require organizations to determine the validity of previous measurement results when equipment is found not conforming to requirements. As-found data is the only objective evidence that makes this determination possible. Without it, an auditor cannot verify whether products tested during the previous calibration cycle were measured with a trustworthy instrument. The entire chain of measurement traceability, which relies on documented evidence linking your instrument back to the International System of Units (SI) through National Metrology Institutes (NMIs) like NIST, is weakened.
For organizations in aerospace, semiconductor, or other regulated verticals, an out-of-tolerance as-found condition is not just a calibration event but a quality event that can require impact assessments on released product. When as-found data shows an OOT condition, it triggers a formal investigation. The organization must trace back through production records, test results, and shipped products to determine if the faulty measurement could have impacted quality or safety. This backward-looking process is reverse traceability in practice, and it starts with the as-found data.
As-found data collected over multiple calibration cycles is the primary input for data-driven interval optimization under guidance such as NCSL International's Recommended Practice RP-1. If an instrument is consistently found well within its tolerance limits at each calibration, the historical data may support a decision to extend the interval. Conversely, if it is found drifting toward its limits, the interval should be shortened. Without a history of as-found data, these decisions become guesswork, often forcing organizations into overly conservative and costly calibration schedules.
An out-of-tolerance (OOT) as-found reading is a serious event that demands a structured response. The data tells you the instrument was out of specification when it was tested, but it doesn't tell you when it drifted out or how many measurements were affected. That uncertainty is what makes a formal impact assessment necessary.
Imagine a Fluke 87V multimeter used for final voltage verification on a production line is sent for calibration. The as-found DC voltage reading at the 10 V test point shows a 1.2% error against a manufacturer's tolerance of ±0.5%. The lab technician records this OOT finding, adjusts the instrument, and the as-left reading confirms a 0.05% error well within tolerance. The instrument is fixed, but the quality team's work is just beginning.
The response process generally involves these steps:
Because it uses calibration records to trace the impact of a measurement problem back through the quality system, this investigation protects both the company and its customers. The same investigation applies to safety-critical instruments like multimeters and pressure gauges, even those designated as 'reference only.' For these instruments, an undetected OOT condition can be a personnel safety risk, so the assessment should consider who relied on the readings, not just which products were affected.
What happens when an instrument's as-found reading is technically in tolerance, but just barely? Consider a thermocouple used to monitor a curing oven. It arrives for calibration and the as-found reading is 0.48 °F high against a tolerance of ±0.50 °F. The instrument passes, but should you trust it?
Measurement uncertainty complicates this judgment. Every calibration measurement has an associated expanded uncertainty (typically reported at a 95% confidence level, or k=2). When an as-found reading is very close to a tolerance limit, the band of uncertainty may cross that limit. In our example, if the measurement uncertainty is ±0.03 °F, the true value could be as high as 0.51 °F outside the tolerance.
This is where decision rules come into play. As required by ISO/IEC 17025:2017, a decision rule describes how measurement uncertainty will be accounted for when stating conformity to a specification. The rule you agree on with your calibration provider determines how a reading this close to the limit is reported.
Which decision rule you apply depends on your quality system and the risk associated with the measurement. Whichever rule applies, a barely-passing as-found result should be treated as a drift warning, not a clean bill of health. Many organizations find that an instrument returning in tolerance but outside of, say, 75% of its tolerance limit warrants a closer look. It's a signal that the instrument may be drifting faster than expected and could inform the decision for the next calibration interval.
Most organizations set calibration intervals based on manufacturer recommendations or industry convention often annually and never revisit them. This can lead to unnecessary costs and equipment downtime, especially when years of as-found data show an instrument has never drifted beyond 30% of its tolerance limit.
Guidance from documents like NCSL International's Recommended Practice RP-1 provides methodologies for adjusting calibration intervals based on historical performance data. ILAC-G24, Guidelines for the Determination of Calibration Intervals of Measuring Instruments, offers complementary methods that can be used alongside RP-1. The logic is straightforward:
This process, known as drift trending, involves plotting as-found readings for the same test points across three or more consecutive calibration cycles. This visual record reveals the instrument's stability, direction, and rate of change over time in its specific application. One in-tolerance as-found result doesn't validate an interval; it only confirms the instrument hadn't drifted out at the moment of test. It's the pattern across multiple cycles that provides a defensible basis for a change.
It is equally important to know where and how the instrument is used as it is to choose the interval itself. A unit operating on a harsh production floor, in a high-vibration environment, or through wide temperature swings will usually drift differently than the same model used in a controlled laboratory. In practice, the operating environment often dictates the rate of drift, which means deployment context should be evaluated alongside historical as-found results before extending or shortening any interval.
You cannot perform any of this analysis without a consistent record of as-found data. Organizations whose calibration certificates only show as-left results have no historical performance record to analyze, forcing them to rely on generic intervals that may not be appropriate for their specific equipment and risk profile.
Many organizations discover during an audit that their calibration certificates are missing as-found data. This gap often traces back to a single oversight: an incomplete contract review. Many calibration providers' default service levels include only as-left results unless the customer's purchase order or contract explicitly requests more.
Quality standards require customers to communicate their requirements clearly to suppliers, and auditors increasingly look for documented evidence that the customer and calibration provider agreed on the scope of work before it began. This proactive conversation should confirm several key items:
If your certificates don't include the data your quality system requires, the first question to ask is whether you specified those requirements in your contract. A clear statement of work helps prevent documentation gaps before they happen. If you have additional questions about what to expect from a calibration provider, our frequently asked questions page is a helpful starting point.
The ability to perform impact assessments, conduct audits, and optimize intervals hinges on receiving complete, accurate, and traceable calibration documentation. Tescom Calibration Services provides calibration with measurements traceable to the SI through NMIs such as NIST. When required by the selected service level, Tescom provides as-found and as-left data, conformity statements, and measurement uncertainty.
Tescom's calibration services span electrical, electronic, RF/microwave, physical, dimensional, pressure, torque, and temperature disciplines, so organizations with a mixed equipment inventory can receive as-found and as-left documentation in a consistent format. For some multimeters, Tescom runs calibrations with Fluke MET/CAL software, which applies the same procedure and test points each cycle so as-found results stay comparable from one calibration to the next. Certificates are also available through Tescom's online portal, where they can be retrieved for audits or impact investigations.
To confirm that your certificates will include the data your quality system requires, request a quote or confirm your reporting requirements with Tescom Calibration Services.
If you also need to purchase new or replacement test equipment, those requests are handled separately through Accredited Labs product sales.
As-found and as-left data are not administrative details on a calibration certificate. They are the evidence chain that connects every calibration event to the product-quality decisions, audit responses, and cost-control initiatives that depend on it.
As-found data tells you whether your instrument was trustworthy during its past service period. As-left data confirms it is trustworthy going forward. Together, they create the documented history that auditors, impact assessments, and interval analysis require.
Take a moment to review your current calibration certificates. Do they include both data sets? If they don't, the contract review conversation is the most important place to start. Ensuring your calibration provider understands and can meet your documentation needs is the first step toward building a defensible and effective measurement assurance program.
Yes. When an instrument is found within tolerance and no adjustment is needed, the certificate may show as-found data with a notation that no adjustment was performed. In this case, the as-found and as-left conditions are effectively the same, and the certificate documents that the instrument was verified and returned without modification.
ISO/IEC 17025:2017 requires laboratories to report results and other relevant information, but the specific inclusion of as-found and as-left data depends on the customer's requirements and the agreed scope of service. This is why contract review agreeing on reporting requirements before calibration is critical for ensuring certificates meet your quality-system needs.
Semiconductor fabrication facilities use as-found data to verify that measurement equipment supporting a process qualification remained within specification throughout the entire qualification period. If as-found data shows an OOT condition, the fab may need to re-evaluate or repeat qualification steps, making this documentation a direct input to process-validation decisions.
Drift trending plots as-found readings for the same test points across consecutive calibration events to reveal the direction and rate of instrument drift over time. Three or more data points are typically needed to identify a meaningful trend. This historical record is the primary input for data-driven calibration interval adjustments under frameworks such as NCSL RP-1.
Many quality systems and industry standards require as-found documentation for instruments whose measurements affect safety even those designated as reference-only. A multimeter used to verify voltage in a lockout/tagout procedure or a pressure gauge monitoring a relief valve is an example where as-found data provides evidence that safety-related measurements were valid.
Measurement uncertainty defines the range within which the true value of a measurement is expected to lie. When an as-found reading is close to the tolerance boundary and the expanded uncertainty (typically at k=2) overlaps that boundary, a simple pass/fail determination becomes unreliable. Decision rules help account for this uncertainty when making conformity statements.