The ISEAL Code came into effect on 1 March 2024. Organisations that had adhered to the previous Codes of Good Practice were granted an 18-month transition period to align their system(s) with the ISEAL Code. For further information, visit: What is ISEAL Code Compliant.

From October 2025, independent evaluations against the ISEAL Code will commence in accordance with the Independent Evaluation Procedure. ISEAL Code Compliant organisations are required to successfully close an evaluation across the full scope of the ISEAL Code. This can be done through a single, full-scope evaluation or through phased specific-scope evaluations. Evaluations must be completed within four years of the end of the transition period, no later than October 2029, to maintain ISEAL Code Compliant status.

Details on the evaluation schedule will be made publicly available.

As a result of this independent evaluation, AWS made the following improvements to how they set their standards:

• Published their Standards Development and Revision Procedure V2.0 on their website.
• Developed and begun implementing a Standards Development and Revision Record Keeping Protocol.
• The organisational affiliations of the AWS Technical Committee Members were disclosed on their website.
• Public summary of their Standard revision process was published on their website.
• Created a Standards Log to document all input received on standards in between review and revision cycles.
• The revised Terms of References for the AWS Standard V3.0 was finalised

As a result of this independent evaluation, AWS made the following improvements to their assurance system:

• Revised and published their Oversight Procedure.
• Finalised their Trading Agreement with their conformity assessment body.
• Established a process to evaluate risk at regular intervals.
• Completed a reconstruction of their website.
• Published their Claims Policy.
• Updated their AWS Certification Requirements document.
• Created an AWS Document Control Policy includes requirements on how Assurance Documents are stored and managed.

As a result of this independent evaluation, AWS agreed the following improvements to their M&E system: 

• Update their stakeholder mapping narrative document and infographic to reflect the changes in the scheme's organizational structure.
• Consult stakeholders to identify any possible unintended effects of the AWS System.
• Implement a new approach to M&E data collection and increase the number of indicators to be monitored.
• Develop an Indicator Protocol to support the AWS M&E Indicator Framework.
• Develop an Outcome and Impact Evaluation Framework that provides a systematic approach to guide AWS in conducting, commissioning and undergoing regular outcome and impact evaluations on an annual basis.