Accreditation
Carbon, Environment and Climate Assurance
Keep environmental capability, historical statement verification and prospective plan validation distinct. Each claim needs its own boundary, period, method and assurance form; a validated forecast is not an achieved reduction.
Programme overview
Scope first.
Evidence throughout.
Keep environmental capability, historical statement verification and prospective plan validation distinct. Each claim needs its own boundary, period, method and assurance form; a validated forecast is not an achieved reduction.
Technical scope
Subjects within this family.
The profile retains 6 technical subjects. Inclusion here describes the framework; an individual grant covers only the specifically assessed and approved scope.
- F08-C01Inventory and data
- F08-C02Reduction and transition
- F08-C03Energy and circular resources
- F08-C04Local environmental performance
- F08-C05Climate resilience
- F08-C06Low-carbon energy and supply claims
Evidence & assessment
Connect the claim to actual capability.
Read the family profile with the common ASTRA standard. Application-specific criteria, local authority and real evidence must be established for the particular case.
Define the object
Identify the legal holder, actual performer, subject or configuration, site, operating conditions and requested outcome.
Demonstrate implementation
Connect applicable requirements to current personnel, methods, resources and traceable original records. Confirm that reused evidence is relevant to this scope.
Resolve the conclusion
Every applicable mandatory condition must pass, exclusions must be independently justified and in-scope nonconformities verified closed before a positive decision.
Outcome boundaries
Use the conclusion actually reached.
Historical statement verification and prospective plan validation are separate. A validated plan does not prove an achieved reduction; an inventory does not establish the footprint of every flight or customer.
Membership, commercial relationships and a completed application do not determine the technical decision. Separate legal and competent-authority requirements continue to apply.
Controlled references
Programme documents.
Read the common core and this family’s profile together. These resources remain in the dedicated ASTRA collection, not the general Documents library.
First Edition / 30 September 2026. This is the publication date, not an individual approval or effective date. Technical adoption, operator authority and scope activation require their own authentic records.
Your next step
Make the requested scope clear.
Describe the programme family and the actual work for initial scope review. Availability and the appropriate outcome are confirmed for the specific request; submission is not approval.