AWS Standards Development Procedure

AWSStandardDevelopmentProcedureDraft1-2

AWSStandardsDevelopmentProcedure

Version1.0

Nov2016

ALLIANCEFORWATERSTEWARDSHIP(SCIO)

EdinburghCentreforCarbonInnovation(ECCI),HighSchoolYards,InfirmaryStreet,EdinburghEHI1LZ,ScotlandTEL:+44(0)1316514690|EMAIL:[email protected]

AWSisregisteredasaScottishCharitableIncorporatedOrganisation(SC045894

AWSStandardSystemDevelopmentProcedure

AWSStandardSystemDevelopmentProcedure

Contents Purpose ....................................................................................................................... 4

Responsibility for these Requirements ........................................................................ 4

AWS Standard System ................................................................................................ 5

AWS Standard Framework .......................................................................................... 5

A Introduction ........................................................................................................... 7

B Scope .................................................................................................................... 9

C Normative References .......................................................................................... 9

D Associated Guidance ............................................................................................ 9

E Terms and Definitions ........................................................................................... 9

1 GENERALPROVISIONS........................................................................................................10

2 STANDARDSDEVELOPMENT...............................................................................................10

3 STRUCTUREANDCONTENT................................................................................................17

ALLIANCE FOR WATER STEWARDSHIP (SCIO)

Edinburgh Centre for Carbon Innovation (ECCI), High School Yards, Infirmary Street, Edinburgh EHI 1LZ, Scotland TEL: +44 (0)131 651 4690 | EMAIL: [email protected]

AWS is registered as a Scottish Charitable Incorporated Organisation (SC045894)

PURPOSE

Thisdocumentsetsouttheprocedurefordevelopment,reviewandrevisionoftheAWSStandardandtheassociatedCertificationandInterimAccreditationRequirements.Itincludesthestructureandcontentofthestandardalongwiththerationaleforthresholdsofcompliance.

ThisdocumentisanormativereferencewhichwillbeusedalongsideothernormativeAWSdocumentstoassignresponsibilities,manageprocessesandsetdeadlinesforthetimelyandeffectivedevelopment,reviewandrevisionoftheAWsStandardSystem.Thisprocedureisintendedtoinformtheprocessofdevelopment,reviewandrevision,ratherthansetoutindetailhere.SuchprocesseswillbeformulatedandagreedbytheAWSTechnicalCommittee.

RESPONSIBILITYFORTHESEREQUIREMENTS

TheAWSTechnicalCommitteeisthebodyresponsiblefortheAWSStandardsDevelopmentProcedure.TheTechnicalCommitteewillreviewthecontentsofthisdocumentonanongoingbasis.Arecordofamendmentsisshownbelow.

AmendmentRecordVersionNo. DateofPublication DescriptionofAmendmentDraft1.3 Sept2016 PostTCComments

Draft1.4 Oct2016 BoardCommentsintegratedVersion1.0 Nov2016 Approved




AWSSTANDARDSYSTEM

AWSisthestandardssystemownerandkeeperofTheAWSInternationalWaterStewardshipStandard(“theAWSStandard”).Assuch,AWSisresponsibleforimplementationoftheAWSStandard,includingstandardsdevelopment,capacitybuilding,assurance,labellingandmonitoring.Toachievethesegoals,AWShasstructureditsstandardssystemintothreeprograms:verificationprogram,training&capacity-buildingprogram,andmembershipprogram(Figure1).Thesethreeprogramsarecomplementary.TheyservetoreinforceoneanothertoensurethattheAWSStandardSystemprovidesacredibleandrobustimplementationoftheAWSStandard.

Figure1.DiagramoftheAWSStandardSystem.

AWSStandardSystem

VerificationProgram

Training&CapacityBuildingProgram

MembershipProgram

AWSSTANDARDFRAMEWORK

TheAWSStandardSystemisrootedinfournormativedocumentswhich,together,comprisetheAWS‘StandardFramework’.ThescopeandinterrelationshipofthesenormativedocumentsisshowninTable1.

Table1.InterrelationofthefournormativedocumentsoftheAWSstandardsframework.

NormativeDocument Purpose ProgramPrimaryTarget

Audience

AWSStandard SetstheStandardAWSVerification

ProgramImplementers

CABs

AWSSelf-VerificationRequirements

Setstheprocessfor

self-verification

AWSVerificationProgram Implementers

AWSCertificationRequirements

Setstheprocessforcertification

AWSVerificationProgram

CABs

AWSorAB




AWSInterimAccreditationRequirements

Setsthecriteriaandtheprocessforaccreditation

AWSInterimAccreditationProgram

AWSVerificationProgram

&

AWSTraining&CapacityBuildingProgram

CABs

Trainers

Consultants

FirstandforemostisTheAWSInternationalWaterStewardshipStandardwhichlaysthefoundationoftheAWSStandardSystembyestablishingtheactions,criteriaandindicatorsforhowsitesshouldmanagewateratthesitelevelandhowwatershouldbestewardedbeyondtheboundariesofthesite.Thisisanormativedocumentwhichisapplicable,onavoluntarybasis,toanysitewishingtodemonstrateitsconformitywiththeAWSStandard.

ThesecondnormativedocumentoftheAWSstandardframeworkistheAWSSelf-VerificationRequirements.Thisdocumentdescribesthemandatoryrequirementsfortheprocessesofself-verificationwhicharetobefollowedbyimplementers.

ThethirdnormativedocumentoftheAWSstandardframeworkistheAWSCertificationRequirements(i.e.thisdocument).ItdescribesthemandatoryrequirementsforcertificationwhicharetobefollowedbyCABs.

TheAWSInterimAccreditationRequirementsisthefourthnormativedocumentoftheAWSstandardframework.ItsetsoutthemandatorycriteriathatAWS(oraccreditationbody)willusetoevaluatethecompetencyofAWSserviceproviders(CABs,trainersandconsultants).Scopeisthereforeapplicableattwoprogramlevels-verificationandtraining&capacity-building.

AWSmayproduceadditionalnormativedocumentsinsupportofprogram-levelobjectives.Suchobjectivesmayincludeestablishingrulesandrequirementsformembership,brandingandclaims,training,capacity-building,andrelatedtopics.

Inadditiontonormativedocuments,AWSmayalsoproduceguidancedocumentsfromtimetotime.Thepurposeofguidanceistohelpimplementers,serviceproviders,andstakeholderstobetterunderstandAWSrequirementsandhowtoimplementthemeffectively.Forexample,AWSintendstoproduceaguidancedocumententitledAWSVerificationSystemwhichprovidesanoverviewofhowallthedifferentelementsoftheAWSVerificationPrograminteracttodeliveracredibleassurancetostakeholdersonAWSclaims.




Fig.2LifeCycleoftheStandard

A INTRODUCTION

TheAllianceforWaterStewardship(AWS)isaglobal,non-profitorganizationdedicatedtoadvancingwaterstewardshiparoundtheworld.Aspartofthismission,AWSdevelopedTheAWSInternationalWaterStewardshipStandard.TheAWSStandardwastheresultofaninternational,four-year,ISEALcompliant,multi-stakeholderprocesswhichrespondedtothegrowingneedforevidenceofrobustwaterriskandimpactmitigationefforts.Itisbuiltaroundthenotionofimplementingwaterstewardshipatthesitelevelinawaythatunderstandsandengageswiththebroadercatchmenttoworkwithotherwaterstakeholderstoaddresssharedwater-relatedchallengesandopportunities.

TCProposaltoDevelopStandard

TCDevelop1stDraft

1stPublicConsultation

TCDevelop2ndDraft

2ndPublicConsultation

TCDevelopFinalDraft.

MemberApproval

AWSStandard

TCReview

ReviewConsultation




AWShasdevelopedaverificationsystemforimplementingtheAWSStandardwhichisconsistentwiththeISEALAssuranceCode,providingconsistency,rigour,competence,impartiality,transparency,andaccessibility.AcentralfeatureoftheAWSStandardSystemistheroleofindependentcertificationbythird-partyConformityAssessmentBodies(CABs).

AWSwillimplementtheAWSStandardSystemintwophases:aninitialphasewillbeusedworkoutanykinksandensurecapacityissufficienttomeetsystemneeds.Forthesecondphase(Phase2:2017+),AWSwillupdatetheAWSStandardSystemandaddimprovedfunctionalitypendingAWSmemberinput.ThroughoutPhase1,AWSwillitselfruntheaccreditationprogram.Thistimewillbeusedtogainexperiencewiththesystemandexaminethepotentialoftransferringtheaccreditationfunctiontoanindependentaccreditationbody.Therefore,thepresentdocumentreferstotheAWSaccreditationfunctionasan‘interim’arrangement.

AsanISEALmember,AWSiscommittedtoanequitable,openandtransparentapproachtodevelopingitsstandard.Accordingly,theAWSStandardSystemfollowsISEAL’sStandardSetting,Assurance,andImpactsCodes.TheAWSStandardisalsointendedtobecomplementarytoexistingsystemssuchasISO14001.AndAWS’sapproach–utilizingthecompetenciesofindependentthird-partyentitiestoassesscompliancewiththestandard-drawsheavilyonexistinginternationalnormswhichapplytoconformityassessmentbodies(e.g.ISO17065).




B SCOPE

ThisprocedureappliestoTheAllianceforWaterStewardship(AWS).ItdescribeshowAWSwilldevelop,reviewandreviseitsStandardsSystem.ThisappliesnotonlytotheAWSStandard,butalsototheassociatedSelfVerification,CertificationandInterimAccreditationRequirements.

InaccordancewiththeISEALStandard-SettingCode,AWSStandardsSystemDevelopmentProcedureseekstoincludeallinterestsandensurethatnooneinterestcandominateintheprocessofstandardsdevelopment,reviewandrevision.

C NORMATIVEREFERENCES

AWSCertificationRequirements,Version1.0,July2015

AWSSelf-VerificationRequirements,Version1.0,July2015

AWSInterimAccreditationRequirements,Version1.0,July2015

AWSGlossaryofTerms,Version1.0,July2015

AWSTheoryofChange,

TheAWSInternationalWaterStewardshipStandard,Version1.0,April2014

ISEALAllianceCodeofGoodPractice:SettingSocialandEnvironmentalStandardsv5.0,June2010(“ISEALStandard-SettingCode”)

ISEALAllianceCodeofGoodPractice:AssuringCompliancewithSocialandEnvironmentStandardsv1.0(“ISEALAssuranceCode”)

ISO17011:2004Conformityassessment—Generalrequirementsforaccreditationbodiesaccreditingconformityassessmentbodies(§5.9,Complaints)

D ASSOCIATEDGUIDANCE

None

E TERMSANDDEFINITIONS

AlltermsaredefinedintheAWSGlossaryofTerms.




1 GENERALPROVISIONS1.1 StandardDevelopmentProcedures

Aim:AWSfollowstransparentproceduresthatareimprovedovertime.

1.1.1 ThisProcedureformsthebasisofthestandarddevelopmentprocessunderwhichtheAWSStandardsSystemisdevelopedandrevised.

1.1.2 ThisProcedureshallbemadeavailabletostakeholders,ontheAWSwebsite.1.1.3 ThisProcedureshallbereviewedpriortoareviewoftheAWSStandardorwithinfiveyearsof

approval,whicheverissooner,andshalltakecommentsfromstakeholdersaboutthisProcedureintoaccount.

1.2 ConsistencyBetweenStandards,wateruseprotocolsandtools.

Aim:AWSseekstoavoidduplicationandtobeconsistentwithstandardsthathaveoverlappingscopes,andtoincorporatewateruseprotocolsandtools,whilenotlimitinginnovationandimprovement.

1.2.1 Attheoutsetofastandardsdevelopmentprocess,AWSshall:1.2.1.1 Identifyandinformorganisationsthathavedevelopedinternationalstandardsthatincludewater

stewardshipprovisions,aswellaswateruseprotocolsandtools,ofitsintentiontodeveloporrevisethestandard;

1.2.1.2 Seek input from them on the review, process and terms of reference for the revision of thestandard;and

1.2.1.3 EncouragetheirparticipationintheStandardssubsequentdevelopment.1.2.1.4 Actively explore possibilities for unilateral ormutual recognition for parts or all of the system

requirements.

1.2.2 InordertofacilitatestakeholderengagementintheAWSStandardsdevelopmentAWSshallprepareanannualworkprogrammethatincludes:

1.2.2.1 Contactinformation,1.2.2.2 Anycurrentstandardsdevelopmentwork,1.2.2.3 Anystandardsadoptedintheprecedingperiod;and1.2.2.4 PublishtheannualworkprogrammeforthenextyearontheAWSwebsiteattheendofeachyear.

Guidance:Theworkprogrammedoesnotneedtobeaseparatedocument,e.g.itcanappearasapageonthewebsite.

2 STANDARDSDEVELOPMENT2.1 TermsofReferenceforthestandard

Aim:ForAWStoclearlyarticulatewhatthestandardaimstoachieveandwhythestandardcontinuestobeneeded.




2.1.1 AWSshalldeveloporupdatethetermsofreference(TOR)forthestandard.Theseshallbeincludedintheintroductorypagesofthestandard.

2.1.2 TheTORshallincludethefollowingelements:2.1.2.1 Theapplicability,includingsectoralscopeofthestandardandtheintendedgeographicapplication;2.1.2.2 Ajustificationoftheneedforthestandard,including:anassessmentofwaterrelatedsustainability

issues;anexplanationofwhetherthestandardwillmeettheexpressedneed;anddocumentationofotherstandardsoperatingorindevelopmentthatmeetallorpartoftheexpressedneed;

2.1.2.3 Clearsocial,environmentalandeconomicOutcomesthatthestandardseekstoachieveandhowthosearelinkedtotheorganization’sintendedchange

2.1.2.4 AWSTheoryofChange;and2.1.2.5 An assessment of risks in implementing the standard and how to mitigate these, including:

identificationoffactorsthatcouldhaveanegativeimpactontheabilityofthestandardtoachieveitsoutcomes;unintended consequences that couldarise from its implementation; andpossiblecorrectiveactionsthatcouldbetakentoaddressthesepotentialrisks.

2.2 StakeholderIdentification

Aim:ForAWStohaveanunderstandingofwhoitsstakeholdersare.2.2.1 Attheoutsetofastandardsdevelopmentprocess,theAWSshallupdatelistsofsectorsthathave

an interest inthestandardanddefinekeystakeholdergroupswithinthosesectors,basedonthestandard’sscopeanditssocial,environmentalandeconomicoutcomes.

2.2.2 Stakeholdersshallbeidentifiedonbothaninternationalandregionalbasis,inordertodeterminethatallregionsarerepresented,whilstmaintainingtheinternationalfocusofthestandard.

2.2.3 AWS shall: 2.2.3.1 seek to achieve representative participation in its standards development

activities, as evidenced by records of stakeholder input; and 2.2.3.2 to this end, set participation goals for interest sector engagement that can be evaluated and

updatedovertime.

Guidance: Key stakeholder groups includedirectly affected stakeholders (thosewhowill be impactedbyimplementationofthestandard)andmayincludeindirectlyaffectedstakeholderswhohaveaninterestintheapplicationofthestandard.Scopeincludesthesectorandgeographiestowhichthestandardapplies.As AWS has an international standard, it is important to maintain this focus, whilst reflecting regionalperspectives.

2.3 ReviewprocessAim:ForAWStoidentifythescopeoftherevisioninordertoallocatesufficienttimeandresourcestothenextroundofstandarddevelopment.




2.3.1 AWSshallconductareviewofthestandardanditsassociatedimplementingdocuments,priortoinitiatingarevisionprocess.

2.3.2 Thereviewshallinclude:2.3.2.1 aminimumthirty-dayconsultationofkeystakeholdergroupstoidentifyareasofthestandard

thatneedreviewandpotentialrevision;and2.3.2.2 ananalysisofallcommentsreceivedfromthisconsultationandduringthetimethatthestandard

hasbeeninoperation.

2.4 PublicSummaryoftheStandardsDevelopmentProcess

Aim:Stakeholdershavetheinformationtheyneedtodeterminewhetherandhowtoparticipate.

2.4.1 A minimum of thirty days prior to the outset of a process for development of the standard, asummaryoftheprocessshallbemadepublicallyavailablethatshallinclude:

2.4.1.1 summary of the TOR for the standard (2.1), including the proposed scope, objectives andjustificationoftheneedforthestandard;

2.4.1.2 theareasidentifiedforrevisionduringthereviewprocess;2.4.1.3 stepsinthestandarddevelopmentprocess,includingtimelinesandclearlyidentifiedopportunities

forandmeansbywhichstakeholderscancontribute;and2.4.1.4 decision-makingprocedures, includinghowdecisionsaremadeandwhomakes them. Thiswill

generallyfollowthedecision-makingprocessdescribedintheAWSTechnicalCommitteeTermsofReference,asthisisthebodythatwillimplementtheStandardsDevelopmentProcess.

2.4.1.5 Duringthisperiodandindeedoncetherevisionprocesshascommenced,stakeholdersmaysuggestwaystoimprovetheprocess.TheseshallbedulyconsideredbytheTechnicalCommittee.

Guidance:ThePublicSummaryisaconciseoverviewforstakeholderstounderstandwhetherandhowtoengage.IftheTOR(2.1)includealloftheinformationoutlinedinthisrequirement,andiftheTORaremadepubliclyavailable,thentheycanserveasthePublicSummary.However,careshouldbetakentoensuretheTORsareaccessibletostakeholders.

2.5 PublicConsultation

Aim:Stakeholdershavesufficienttimeandopportunitytoprovideinputonthestandardandcanseehowtheirinputhasbeentakenintoaccount.

2.5.1 Thepublicconsultationphaseforstandardsdevelopmentorrevisionshallinclude:2.5.1.1 Atleastoneroundof60daysforcommentsubmissionsbystakeholders.2.5.1.2 Asecondroundofconsultationofatleast30daysforstakeholderstogivefeedbackonwhether

their comments were understood and taken into account and to gain input on substantive,unresolvedissues.




2.5.1.3 Additional rounds of consultation, where substantive, unresolved issues persist after theconsultationround(s),orwhereinsufficientfeedbackwasreceived.

2.5.1.4 Tworoundsofpublicconsultationshouldbeincludedinplanningforanystandardsdevelopmentprocess.

2.5.2 Participationintheconsultationprocessisopentoallstakeholders;and2.5.3 AWSproactivelyseekstheparticipationofkeystakeholdergroups.

Guidance: Participation of all key stakeholder groups cannot be ensured but AWS shallmake efforts toengageallthosekeystakeholdergroupsidentifiedinthestakeholderidentificationprocess(see2.2).

2.5.4 Submissionsfromconsultationperiods.2.5.4.1 AWSshall:2.5.4.2 Compileallcommentsreceivedduringaconsultationperiodinordertoidentifymaterialissues;2.5.4.3 Documenthoweachmaterialissuehasbeenaddressedinthestandardsdevelopment;2.5.4.4 MakethisdocumentpubliclyavailableontheAWSwebsite;andsendittoallpartiesthatsubmitted

comments.2.5.4.5 MakeoriginalcommentsreceivedduringtheconsultationperiodpubliclyavailableontheAWS

website,withattributiontostakeholdergroups,butwithholdingtheidentityofstakeholder.

2.6 FeasibilityAssessment

Aim: Enterprises can implement the standard and assessors can efficiently and effectively evaluatecompliancewithit.

2.6.1 AspartoftheAWSStandardsdevelopment,AWSshallassess:2.6.1.1 TheabilityofenterprisestoimplementtherequirementsoftheAWSStandard;2.6.1.2 Theauditabilityoftherequirementsinthestandardand;2.6.1.3 The effectiveness of associatedAWSCertification andAccreditation Requirements in assessing

conformancewiththeAWSStandard.

Guidance:ThisassessmentcanincludeconsultationwithCABsandenterprisesapplyingthestandard,fieldtrialsoraudits,orimpactorriskassessmentsasappropriate.

2.7 Decision-Making

Aim:Stakeholdersseethattheirviewsarereflectedindecision-making

2.7.1 AnyStandardsDevelopmentprocessshallbeledbytheAWSTechnicalCommittee.2.7.2 MembershipoftheAWSTechnicalCommitteeis:2.7.2.1 opentoallstakeholders;and




2.7.2.2 shallbeconstitutedbyareasonablebalanceofthosestakeholders,includingthosethataredirectlyaffected.

2.7.3 membershipcriteriaandapplicationproceduresforbecomingamemberaretransparentandnon-discriminatory.TheseareavailableontheAWSwebsite.

2.7.4 TheTermsofReferencefortheTechnicalCommitteeinclude:2.7.4.1 consensus-baseddecisionmaking;2.7.4.2 defined criteria to determine when alternative decision-making procedures should come into

effect,intheeventthatconsensuscannotbeachieved;and2.7.4.3 Whatthedecision-makingthresholdswillbe,whilstensuringthatnoonestakeholdergrouportype

cancontroldecision-making.

NOTE:AWSiscurrentlyundergoingareviewofitsmembershipmodel.Thiswillincludethedecisionmakingstructure,aimingtobeinclusiveofallstakeholdergroups,whilstnotallowinganyonegrouptodominateinthedecisionmakingprocess.

Guidance:Consensusisdefinedasgeneralagreement,characterisedbytheabsenceofsustainedoppositiontosubstantialissuesbyanyimportantstakeholdergroup.

2.8 Standards’Availability

Aim:Thestandardandassociatedrequirementsareaccessibletointerestedstakeholders.

2.8.1 Allapprovedstandardsandrequirementsshall:2.8.1.1 bepublishedpromptly;and2.8.1.2 bemadeavailableforfree,inelectronicformatontheAWSwebsite;2.8.1.3 containasummaryofmajorchangesfromthepreviousversion.

2.8.2 AWSshallmakehardcopiesofpublicsummaries,standardsandotherrelatedmaterialsavailable

uponrequestataslowacostaspossible,andcoveringonlyreasonableadministrativecosts.2.8.3 Standardsandsupportingdocumentsshalleachinclude:2.8.3.1 contactinformationforAWS;2.8.3.2 theformalstatusofthedocument;2.8.3.3 thattheofficiallanguageisEnglish;and2.8.3.4 thatinthecaseofinconsistencybetweenversions,referenceshalldefaulttotheofficiallanguage

version.

2.8.4 AWS shall seek to ensure that translations of the standard are available in additional languageswherethissupportstheuseofthestandard.

2.8.5 WhereAWSauthorizesadditionaltranslations, itshallhaveoversightandresponsibilityforthesetranslations.




2.9 ReviewandRevisionofStandards

Aim:TheAWSStandardremainsrelevantovertimeandreflectscurrentstakeholderunderstandingofgoodsustainabilitypractices.

2.9.1 AWSTechnicalCommittee,withthesupportoftheAWSTechnicalProgramme,shall:2.9.1.1 review the AWS Standard including the Guidance Section and associated Certification and

Accreditation Requirements at least once every five years for continued relevance and foreffectivenessinmeetingitsstatedobjectives;and

2.9.1.2 ifnecessary,revisetheAWSStandard,GuidanceandassociatedRequirementswithinthefive-yearcycle,inlinewiththerequirementsinthissection.

2.9.2 Inordertomaintainthestakeholderconsensusachievedandsupportforthestandard,aswellasnottocauseunnecessarydisruptiontothoseimplementingthestandard,suggestionsforrevisionwillneedtobepresentedalongwithacompellingcaseforrevision.

Guidance: A standard’s review considers information gathered from stakeholder input, auditingresultsandorganizationalmonitoringandevaluation,aswellasnewknowledgeorpractices thatmightrequirethestandardtobeupdated.Ifthereviewconcludesthatchangestothestandardarerequired,thenastandardsrevisioniscarriedoutaccordingtotheprocessoutlinedinthisProcedure.TheGuidancethataccompaniestheAWSStandardisalivingdocumentandmaybeupdatedasandwhenneworrevisedguidancebecomesavailable.

2.9.3 AWSTechnicalProgrammeshall:2.9.3.1 makepubliclyavailabletheplannedtimingofthesubsequentreview;and2.9.3.2 includethisinformationinthestandard.

2.9.4 AWSacceptsproposalsatanytimeforrevisionsorclarificationstothestandard.

NOTE:PleaserefertotheAWSComments,ComplaintsandAppealsProcedure:2.2ConcernsRegardingAWS.

2.9.5 Inthecaseofnon-substantivechangestothestandard(e.g.tocorrecttypographicerrorsoroutdated

references),AWSdoesnotneedtoconductaformalrevisionprocessbutshallincludenotificationofanychangesintheAWSnewsletterandmarkeachnewversionwithaversionnumbere.g.V2.1.

2.9.6 In the caseof substantive changes to the standard, these shall be considered in the subsequentreviewandrevisionprocess.

2.9.7 Urgentsubstantiverevisionstothestandard(in-betweenregularrevisions),shall:2.9.7.1 Occurifsubstantiveomissionsareidentified.2.9.7.2 FollowtheprocessforaregularReviewandRevisionprocess.




2.9.8 ReviewandRevisionoftheAWSInterimAccreditationandCertificationRequirementsmaytakeplaceatanypointinthelifeoftheStandard.Suchchangesmayoccurwithouttriggeringafullrevisionofthestandard,solongasthechangedoesnotmateriallyimpactontheintentoftheStandard.

Guidance:SubstantiveomissionsincludechangestotheStandardthatwouldrequireachangeinpracticebycertifiedenterprises.SubstantiveomissionsmaybeconsideredcriticalandtriggerarevisionprocessiftheTechnicalCommitteeassesstheretobeamajorrisktotheintegrityofthesystem.InthiscasearecommendationwillbemadetotheAWSBoardfordecision.

2.10 TransitionPeriod

Aim:Certificateholders,CABsandAccreditationBodieshaveadequatetimeandnoticetocomplywithanynewrequirements.

2.10.1 AWSshallnoteinthestandard:2.10.1.1 thedateofarevisionorreaffirmationofthestandard;and2.10.1.2 thetransitionperiodbywhichtherevisedstandardwillcomeintoeffect.2.10.1.3 revisedstandardsshallgenerallybecomeeffectiveasof1stJanuaryeachyear.2.10.1.4 Noticethatarevisedstandard isbeing introducedshallbegiventoCABsandanyAccreditation

BodyassociatedwithAWSatleast3monthspriortothisdate.2.10.1.5 In the first year, extended timelinesmay be given to existing certificate holders to come into

compliancewithchangestothestandardi.e.MajorNonConformitiesmaybegivenoneyearforcompliance,ratherthantheusualthreemonths.

2.10.2 AWS shall promptly inform its stakeholders of the revised standard and transition period, inparticularConformityAssessmentBodies,andwillrequirethemtoinformcertifiedenterprisesandthosewhoareintheprocessofcertification.

2.11 Records

Aim: Stakeholders can refer to previous consultations to understand the basis for the standard’srequirements.

2.11.1 AWSshallkeeponfileforatleastfiveyears,oratleasttworevisioncycles,whicheveristhelongerperiod,thefollowingrecordsrelatedtoeachstandardsdevelopmentorrevisionprocess:

2.11.1.1.1 policiesandproceduresguidingthestandarddevelopmentactivity;2.11.1.1.2 listsofstakeholderscontacted;2.11.1.1.3 stakeholdersinvolvedateachstageoftheprocess;2.11.1.1.4 commentsreceivedandasynopsisofhowthosecommentsweretakenintoaccount;




2.11.1.1.5 alldraftandfinalversionsofthestandard;and2.11.1.1.6 maketheseavailabletostakeholdersuponrequest.

2.12 ResolvingComplaints

Aim: Stakeholders have access to a transparentmechanism for raising concerns about the standarddevelopmentprocessandhavingthoseconcernsconsidered.

2.12.1 AWS shall make impartial and documented efforts to resolve procedural complaints related tostandardsdevelopment,throughtheAWSComments,ComplaintsandAppealsProcedure.

Guidance:Proceduralcomplaintsarecomplaintsaboutthestandarddevelopmentprocedure(howthestandardwasset),asopposedtosubstantivecomplaints,whichrelatetothecontentofthestandardandwhichshouldbetakenintoaccountthroughtheregularstandards’reviewandrevisionprocess.RefertotheAWSComments,ComplaintsandAppealsProcedureformoreinformation.

2.12.2 AWSshalldisclosedecisionstakenonproceduralcomplaints.

3 STRUCTUREANDCONTENT3.1 SustainabilityOutcomes

Aim:Thestandardonlycontainsrequirementsthatsupportachievementofthedefinedsustainabilityoutcomes.

3.1.1 AWSshallstatethedefinedsocial,environmentalandeconomicoutcomesclearlyandexplicitlyinthestandard.(seeISEALImpactsCode)

3.1.2 AWSshallensureinitsstandardthat:3.1.2.1 criteriaareincludedtoaddressallofthedefinedsocial,environmentalandeconomicoutcomes;

and3.1.2.2 onlycriteriathatarerelevanttomeetingtheseoutcomesareincluded.

Guidance:Makingtheselinkscanbeaccomplishedbyincludingintroductorylanguageineachsectionofthestandardindicatingtowhichoutcomesthecriteriarelate,orbynotingthiscorrelationbesideeachcriterion.TheAWSStandardV1-0describessuchoutcomesintheIntroduction,page9.

3.1.2.3 AWSshallensurethatanyclaimsmadeaboutthestandardoraboutcompliancewiththestandardareconsistentwiththedefinedsocial,environmentalandeconomicoutcomes.(seeISEALImpactsCode6.5andISEALClaimsGoodPracticeGuide).

Guidance:Claimsmadeaboutthestandardareatypeofmarketingclaimthat isusedtopromoteanaspectof,orrelationshipwithastandardssystem.Anexamplewouldbeanadvertisementpromoting




association with a standard or standards system. Claimsmade about compliance with the standardusuallyresultfromaconformityassessmentprocess.

Examplesofassuredclaimsincludeuseoflogos/labels/trustmarksandclaimsofcertificationagainstastandard.NOTE:AdescriptionoftheclaimsthatcanbemadeisgivenintheAWSSelfVerificationRequirementsandAWSCertificationRequirements.

3.2 PerformanceLevel

Aim: Requirements in the standard are set at a performance level that results in significant positivesustainabilityimpacts.

3.2.1 TheAWSStandardshall:3.2.1.1 meetorexceedexistingregulatoryrequirements;and3.2.1.2 clearlyreferencerelevant,existingnationaland/orinternationallawsandregulations. 3.2.1.3 Addressstakeholderconcernswhichexceedexistingregulatoryrequirements,inordertoaddress

theAWSmission.

3.3 ConsistentInterpretation

Aim:Thestandardisconsistentlyinterpretedandappliedacrossitsfullgeographicscope.

3.3.1 TheAWSStandardshallbeconsistentwiththefollowingrequirements:3.3.1.1 onlyincludelanguagethatisclear,specific,objectiveandverifiable;3.3.1.2 beexpressed in termsofprocess,managementandperformancecriteria, rather thandesignor

descriptivecharacteristics;3.3.1.3 notfavouraparticulartechnologyorpatenteditem;3.3.1.4 includedefinitionofthescopetowhichthestandardapplies;3.3.1.5 attributeorcitealloriginalintellectualsourcesofcontent;and3.3.1.6 not present administrative requirements related to assurance, claims or labels or other non-

technicalissuesintegratedwithtechnicaland/orperformancerequirements. Guidance: ‘Assurance’ requirements can include scoring mechanisms for evaluating compliance,definitionofmandatoryandimprovementrequirements,policiesonderogationsfromthestandard,etc.‘Othernon-technicalissues’areissuessuchasrequirementsforparticipationinthescheme.

3.3.2 AWSshallpreparesufficientguidanceonthestandardtosupportconsistent interpretationof itsrequirements.

Guidance: In cases where there is a detailed normative standard, additional guidance may not benecessary.




3.3.3 TheAWSStandardshallbeusedwithoutnationalorregionaladaptations. 3.3.4 NationalorregionalguidancefortheAWSStandardshallbeasconsistentaspossiblewithstandard’s

guidanceandatleastasstringent.3.3.5 Disputesthatarisefrominconsistenciesbetweenthestandard’sguidanceandlocalguidanceshall

alwaysdefertotheAWSStandard,includinganyassociatedinterpretation.

3.4 LocalApplicability

Aim:Thestandardisrelevantinthelocalcontextswhereitisapplied,basedinpartoninputfromlocalstakeholders.

3.4.1 Theprocess to take intoaccount localeconomic, social,environmentalandregulatoryconditionsshall reflect the process at an international level, including stakeholder identification andengagementandinputtotheinternationalstandardsdevelopment,inorderthattheinternationalstandardtakesaccountoflocalconditions.

3.4.2 The national or regional level may augment the Guidance associated with the Standard at theinternationallevelinordertofacilitatelocalimplementation.

Date post:	02-Feb-2022
Category:	Documents
Upload:	others
View:	6 times
Download:	0 times

AWS Standards Development Procedure

Documents