Platform
Modules
By sector
By sector
By standard
Blog
News
Events
ALogP-33
NATO calibration laboratories and the organisations that own test, measurement and diagnostic equipment needing calibration records
NATO's requirements for what a calibration certificate, data sheet and label must contain for test, measurement and diagnostic equipment, so records from any nation's calibration laboratory are comparable.
ALogP-33 is a NATO Allied Logistic Publication that fixes what calibration paperwork has to say, not how the calibration itself is done. Edition B, Version 1 was promulgated on 25 August 2025 and supersedes Edition A, Version 1. Nations record their agreement to use it in STANAG 4704, so it binds the way most Allied Publications do: through the nations' own agreement, not by existing on its own. The document itself is short, just one chapter of substantive text plus two annexes of worked examples, and it exists to solve one problem stated plainly in clause 1.1: "to enable interoperability, the following calibration documentation must be available for every item." When a piece of test, measurement or diagnostic equipment (TMDE) is calibrated by one nation's laboratory and used or checked by another, the paperwork needs to be recognisable regardless of who produced it. That is the whole scope. It says nothing about calibration method, calibration interval policy, or laboratory accreditation.
Clause 1.3 is the core of the document. It requires calibration certificates to have "a defined structure," with informational elements kept under fixed headings that "shall remain unchanged." Eighteen elements are listed: instrument identification by part number, NATO Stock Number, serial number and manufacturer; customer name and contact details; a unique certificate or workorder identifier and calibration date; laboratory name, address, contact information and authorised signatures; a description of the item and the procedure used to calibrate it; the place of calibration, including customer sites and mobile facilities; environmental conditions; the date of receipt or sampling where that matters to the result; the sampling plan and method where relevant; the standards used to perform the calibration, identified by manufacturer, type and serial number; the calibration due date; results before and after any adjustment, with units; a statement that the results relate only to the items tested; measurement uncertainty and a statement of conformity, each only "if required"; a traceability statement; and any notes or interpretations.
Annex A gives a worked example built to that structure, and it settles a question the two-language requirement in clause 1.2 leaves open: where a certificate is bilingual, "text in english is binding." The English wording governs, even where a national-language version sits alongside it.
Two shorter documents round out the requirement. Clause 1.4 requires an equipment data sheet stating the calibration specification the item needs met, to be provided "by the instruments owner upon request"; it may be a trimmed or extended version of the manufacturer's own datasheet, built to cut cost and calibration time or to target features specific to that instrument. Clause 1.6 requires a calibration label once an item passes and the calibration process is finished, showing at minimum the laboratory's identification, the date of calibration, the due date if the customer has agreed one, and a unique identification number, with the calibration technician's name left optional. The laboratory and the customer agree between them what that identifier actually is, whether a workorder number, a certificate number, an asset number, a serial number, or some combination that links the label back to the item. Annex B gives a worked example of the label itself.
ALogP-33 does not set calibration intervals, describe how a laboratory should be accredited, or say what happens when an instrument fails. Two national reservations recorded at promulgation make the room this leaves explicit: Estonia sources calibration from civilian structures and sets intervals from manufacturer recommendations, while the UK affixes labels in accordance with its own Def Stan 05-055. Nobody is assessed against ALogP-33 itself, either. It names no accredited certification body, no notified body and no government surveillance scheme; the only place "conformity" appears is inside the certificate content it specifies, as an optional statement the certificate may carry (clause 1.3), never as something a laboratory or nation is audited against. Clause 1.5.3 does point one step further: measurement results "shall be used for measurement, analysis and improvement (according to ISO 9001)," so what a calibration lab produces under ALogP-33 typically feeds a wider ISO 9001 quality system rather than being checked on its own terms.
The work ALogP-33 describes happens in a calibration laboratory, on the bench, not in software. No compliance platform calibrates an instrument, decides a calibration interval, or issues the certificate or label that clauses 1.3 and 1.6 require; that stays with the laboratory and the instrument's owner.
Where ComplyTrain helps is the record-keeping around it. A calibration certificate, data sheet and label are the kind of documents that need to be held against the specific instrument they belong to, kept retrievable on request the way clause 1.1 expects, and tracked against a due date so a recalibration is not missed. Training records for whoever in an organisation is responsible for requesting and filing that paperwork sit alongside it, and the trail an internal or customer review would ask to see is in one place rather than scattered across shared drives.
Which calibration regime, and which standards sit alongside ALogP-33 on a given programme, is set by the contract and the customer's quality clause, not by this page. See how STANAG 4704 and ISO 9001 relate to it in the standards explorer, or talk to us about how the resulting calibration records get held and evidenced.
Tell us how you need to work with ALogP-33 and what you need from it. We will come back to you about what ComplyTrain can do.
Thank you. Your list is on its way to your inbox, and we will come back to you on what working with these standards in ComplyTrain involves, usually within one business day.
It binds through the agreement NATO nations record in STANAG 4704, not through a contract on its own. A supplier or calibration laboratory meets it in practice when a NATO programme or national procedure requires calibration documentation to follow this structure.
No. The document names no accredited certification body, notified body, or surveillance scheme that assesses compliance with it. It fixes the content of a calibration certificate, data sheet and label; there is nothing set up to certify a laboratory against.
ALogP-33 specifies what a calibration certificate, data sheet and label must contain, for interoperability across NATO nations. ISO 9001 is the wider quality management system that clause 1.5.3 says calibration measurement results should feed into for measurement, analysis and improvement. One fixes a document's content; the other governs the management system around it.
Edition B, Version 1, promulgated 25 August 2025. It superseded Edition A, Version 1, which nations were instructed to destroy on receipt in accordance with their local document-destruction procedure.
No. It requires measurement results to be recorded and accessible so a "useable and economic calibration interval" can be determined and evaluated (clause 1.5.2), but it leaves the interval itself to be set elsewhere, such as by the manufacturer or the customer.
One system for the whole compliance programme. Start with the module you need most.
Collect information the same way every time, and decide in advance what happens next.
Know whether your controls are operating, not just whether a policy says they exist.
Turn the compliance work you already know about into a plan with owners, dependencies and dates.
Know what you can offer, and hold the evidence behind every configuration you offer it in.
Eight built-in reports across every module, scheduled, delivered, and filed where the evidence lives.
The sector news that matters to your organisation - read and rated by AI, and delivered as a scheduled digest in your own language.
AI reads the tender pack and pulls out the requirements, deadlines and rules - then helps you draft the response from your own approved content, with you reviewing every step.
One current register of the suppliers and partners you depend on - each risk-assessed, re-assessing itself on schedule, and wired straight into your risk register.
See every requirement you face - across every standard, plus your own contracts and policies - traced to the documents, evidence and processes that satisfy it.
Identify, score, treat and review your risks in one place - with AI to help anyone run a proper assessment, and a defensible trail behind every decision.
Assign training, prove it was understood, and hold the competence records an auditor asks for.
Draft compliance documents with AI, keep every version under control, and export them beautifully branded - all in one place.
Audits, corrective actions, processes and approvals in one quality system, organised around ISO 9001.
Medical device manufacturers operate under more regulatory pressure than almost any other sector outside pharmaceuticals. The rules govern how you design a device, how you make it, how you track it after it ships, and how you respond when something goes wrong.
Learn how EU dual-use export controls apply to encryption, sensors, and software, how classification works under Annex I, and why sending source code by email can count as an export.
A practical way to turn in-your-head risk management into a register that survives staff turnover and answers the risk questions now showing up in tenders.