Laserfiche WebLink
Section No 4 <br /> Revision No 0 <br /> Date September 5, 1991 <br /> Page 5 of 6 <br /> changes For emergency situations, verbal authorization of the scope changes <br /> by the Project Manager is a suitable basis for scope change implementation <br /> In these cases, it is the responsibility of the Project Manager to provide <br /> written follow-up authorization of any verbally approved scope changes, both <br /> to field personnel, the PIC, and the client <br /> 4 4 2 Review and Approval of Methods <br /> Scope changes may involve an extension of the work elements and <br /> procedures previously authorized, the addition of new work elements or <br /> procedures, or changes to the procedures originally envisioned to accomplish <br /> a particular task Scope changes involving new procedures and/or protocols <br /> not incorporated into the QAPP or Sampling and Analysis Plan (GAAP) must be <br /> accompanied by a detailed description of the procedures/protocols to be <br /> followed Prior to implementation, the new procedures/protocols must be <br /> approved by the Quality Control officer, the Principal-in-Charge, the Project <br /> Manager and the client Following required approvals, the new procedures <br /> will be incorporated into applicable sections of the QAPP and/or SAAP <br /> 4 4 3 Implementation <br /> Implementation of all project scope changes is the responsibility of the <br /> Project Manager Project scope change implementation includes the following <br /> elements <br /> ■ Discussion and concurrence of proposed change with Principal-in- <br /> Charge, appropriate Task Leader, and client, <br /> o Documentation of client approval of scope change and associated <br /> • budget via a contract amendment, change order letter, or memo to <br /> file, <br /> 4-5 <br />