Field Documentation Sample Clauses

Field Documentation. Field activities performed during the Study activities will be documented in bound, dedicated logbooks. All entries will be made in ink and no erasures will be allowed. If an incorrect entry is made, the information will be crossed out with a single line and initialed. If pages are left intentionally blank, a diagonal line will be drawn across the page and the field team member will sign the page. The field team will provide a comprehensive description of field activities to allow reconstruction of events, review of data and interpretation. All documents, records, photographs and information relating to field activities will be maintained in the project file via electronic files and/or hard copy. The Study Leader will review all field documentation to verify the activities will meet the intent of the QAPP and SAP. Daily recorded field information will include: ■ Project name; ■ Dates activities were performed; ■ The names of the field team members and/or contractors conducting the activity and any oversight personnel; ■ Climatic Conditions; ■ Description of sample collection points; ■ A map with proposed sampling locations; ■ Equipment/methods used; ■ Sample collection methods (in accordance with the Field SOPs); ■ Deviations from the SSWP and/or the Field SOPs; ■ Equipment calibration results; ■ Field observations; and ■ A description of photographs that may have been taken. Additional field forms may be used as necessary including: ■ Sample Control Logs (includes sample type, date, time, analysis requested, sample depth, number of containers, identification of duplicate samples, MS/MSDs, equipment rinsate blanks and trip blanks.); ■ Borehole / Well Abandonment Field Form; ■ Chain-of-Custody Sheets and Custody Seals; ■ Drilling Log; ■ Soil Vapor Sampling Form; ■ Test Pit Logs; ■ Well Development and Groundwater Sampling Field Form; and ■ Well Installation Log. All forms will include the project name, date and time, sample location and sample number(s), and the name of the field team members completing the forms, with signature.
AutoNDA by SimpleDocs
Field Documentation. 28 7.6.1 Project Remedial Action Plan 28 7.6.2 Field Logbook 28 7.6.3 Photo-Documentation 29 7.6.4 Soil Sampling Locations and Measurements 29 8.0 QUALITY CONTROL 29 8.1 XRF Calibration And Quality Control 30 9.0 PROJECT SAFETY AND TRAINING 31 9.1 Special Training Requirements / Certification 31 9.2 Health and Safety Plan 31 9.3 Utility Clearance 31 9.4 Excavation Area 31 10.0 PROJECT REPORTING 32 11.0 ASSUMPTIONS AND WORK PLAN DEVIATIONS 32 12.0 REFERENCES 32 APPENDIX A – Figures Figure 1 Site Location and Topographic Map Figure 2 Jordan Valley West Meadow’s Survey Map Figure 3 Site #8 Survey Map Figure 4 Previous Sample Location Map Figure 5 Excavation Diagram Figure 5A Site Cross Sections Diagram Figure 6 Soil Placement Location Map Figure 7 Final Grade Plan including Public Improvement Plan APPENDIX B – Site Specific Data Summary Tables and Total vs. TCLP Lead Regression Results Table 1 Analytical Data Summary – Test Pits Table 2 Analytical Data Summary - TCLP Table 3A Regression Analysis Data – Summary Output for Lead including 8-TP- 14-0-3 (TCLP vs. Total) Table 3B Regression Analysis Data – Summary Output for Lead excluding 8- TP-14 (TCLP vs. Total) Table 4A Previous Data Summary - Organics Table 4B Previous Data Summary - Metals APPENDIX C – Missouri Department of Natural Resources Quality Assurance Project Plan for Brownfields/Voluntary Cleanup Program Sites (QAPP) APPENDIX D – Site-Specific Quality Assurance Addendum to MDNR QAPP APPENDIX E – Site-Specific Health and Safety Plan APPENDIX F – frankZdesign Seeding Memorandum PREAMBLE

Related to Field Documentation

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

  • Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits, and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. It is important that you retain and keep safely all documents associated with your policy so that you can refer to them in the event of a claim.

  • Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.

  • Supporting Documentation Upon request, the HSP will provide the LHIN with proof of the matters referred to in this Article.

  • Medical Documentation The teacher must supply a letter from a medical 3 doctor, who treated the patient, stating that in his/her opinion, there is a strong 4 probability that the illness was contracted at school.

  • Source Documentation Accounting records must be supported by such source documentation as canceled checks, bank statements, invoices, paid bills, donor letters, time and attendance records, activity reports, travel reports, contractual and consultant agreements, and subaward documentation. All supporting documentation should be clearly identified with the Award and general ledger accounts which are to be charged or credited.

  • Service Documentation The “Service Documentation” includes;

  • Documentation License Subject to the terms of this Agreement, Flock hereby grants to Customer a non-exclusive, non-transferable right and license to use the Documentation during the Service Term for Customer’s internal purposes in connection with its use of the Flock Services as contemplated herein.

  • Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!