Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANREC 4808
Programme managers and systems engineers on NATO programmes deciding whether to use AEP-67 and ALP-10
STANREC 4808 is NATO's voluntary, non-binding recommendation that programmes consider AEP-67 (Engineering, Edition B) and ALP-10 (Integrated Logistics Support, Edition C); it commits no nation to using either.
STANREC 4808, Engineering in NATO Programmes, is a NATO Standardization Recommendation rather than a Standardization Agreement, and that difference is the most important thing about the page: a STANREC does not commit a nation to anything. The document says so plainly, that it is "a non-binding document employed on a voluntary basis and does not require commitment of the nations to implement the standards which are listed in it." A STANAG binds a nation through ratification; a STANREC only invites use.
What it actually contains is short. Its own aim section frames itself as an aid to programme managers (PMs) and systems engineers (SEs) "seeking guidance on how to incorporate best engineering practices into their system life cycle," and its single substantive recommendation is that nations consider two other Allied Publications: AEP-67, Edition B, and ALP-10, Edition C. STANREC 4808 does not restate what either publication requires; it only points a reader toward them.
This is the first edition, Edition 1, promulgated on 23 October 2017, and it supersedes no earlier document. It was approved by NATO's member nations and promulgated by the NATO Standardization Office, so it addresses NATO's nations generally rather than any one country.
AEP-67, Edition B, and ALP-10, Edition C, are the two publications STANREC 4808 recommends for engineering best practice on NATO programmes. It names no clauses of its own for either: whatever engineering or integrated-logistics-support work a supplier actually has to do comes from AEP-67 or ALP-10 themselves, once a nation, programme or contract adopts one of them, not from this recommendation.
STANREC 4808 also names related material without requiring it: STANAG 4728, and NATO's system life cycle management documents AAP-20 and AAP-48.
STANREC 4808 is reviewed at least once every three years, with the result recorded in the NATO Standardization Document Database. A nation or NATO body can propose a change at any time through a standardization proposal to the tasking authority, the CNAD Life Cycle Management Group, and any accepted change is processed at the next review.
STANREC 4808 describes no accreditation body, audit, or certification scheme, which follows from being voluntary rather than binding: there is nothing here to be assessed against. Any evaluation a programme faces would come from AEP-67 or ALP-10 once adopted, or from the contract that adopted them, not from this recommendation.
NATO publishes STANREC 4808 through the NATO Standardization Document Database at no charge. ComplyTrain does not sell it or host a copy; the NSDD listing for STANREC 4808 is the source.
STANREC 4808 itself is a signpost, not a specification: it recommends AEP-67 and ALP-10 and sets no requirements of its own, so there is no product mapping to claim against the STANREC directly. The practical work starts once a programme or contract actually adopts AEP-67 for engineering practice, or ALP-10 for integrated logistics support. At that point what is needed is disciplined evidence: documented procedures for the engineering or logistics activity involved, training records for the programme managers and systems engineers following them, and an audit trail a customer or Government Quality Assurance representative can inspect. ComplyTrain, as a quality management and evidence system, supports that kind of work in general: controlled documents, training records, internal audits, and corrective-action tracking.
ComplyTrain does not perform the engineering or logistics work AEP-67 or ALP-10 describe, and it does not decide whether either publication applies to a given programme. The applicable tier and the standards that come with it are set by the contract and the customer's quality clause. See the standards explorer for what sits alongside STANREC 4808, or talk to us about evidencing engineering or logistics practice on a NATO programme.
Tell us how you need to work with STANREC 4808 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.
No. It states plainly that it is "a non-binding document employed on a voluntary basis" and does not commit any nation to implementing AEP-67 or ALP-10, the two publications it recommends. Whether either applies to a given programme depends on the contract, not on this recommendation.
A STANAG is the agreement by which NATO nations commit to implement a standard, ratified and then implemented domestically. A STANREC, like this one, only recommends: nations are invited to use the publications it names without any ratification obligation.
Two publications: AEP-67, Edition B, and ALP-10, Edition C. It does not restate their requirements; an organisation that needs to know what either publication demands has to read that publication directly.
No. This is its first edition, Edition 1, promulgated 23 October 2017, and it states that it does not supersede any document.
NATO publishes it free of charge through the NATO Standardization Document Database. ComplyTrain does not sell or host copies of NATO documents.
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.
A 90-day plan for the smallest defence suppliers: let the tender set your scope, document what you already do, fix the security basics primes check, and keep the system small enough for two people to maintain.
Learn how to qualify, approve and monitor sub-suppliers, flow down requirements through purchase orders, and keep the records an auditor will ask to see under ISO 9001 clause 8.4 and AQAP.
Learn how to run an ISO 9001 Clause 9.3 management review that turns evidence into decisions, with the right inputs, actionable outputs, and a cadence that fits your risks.