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.
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. Claims can arise, under certain types of insurance contract, long after the expiry of the policy. It is therefore important that you retain and keep safely all documents associated with your policy.
Course Curriculum, Instruction, and Grading X. Xxxx College courses offered as dual credit, regardless of where they are taught, follow the same syllabus, course outline, textbook, grading method, and other academic policies as the courses outlined in the Hill College catalog. B. Approved courses being taught for dual credit must follow the approved master syllabus of the discipline and of Hill College. C. Textbooks should be identical to those approved for use by Hill College. Should an instructor propose an alternative textbook, the textbook must be approved in advance by the appropriate instructional department of Hill College and the Vice President of Instruction. Other instructional materials for dual credit/concurrent courses must be identical or at an equivalent level to materials used by Hill College. D. Courses which result in college‐level credit will follow the standard grading practices of Hill College, as identified by college policy and as identified in the appropriately approved course syllabus. The grades used in college records are A (excellent), B (above average), C (average), D (below average), F (failure), I (incomplete), W (withdrawn), WC (withdrawn COVID). The lowest passing grade is D. Grade point averages are computed by assigning values to each grade as follows: A = 4 points, B = 3 points, C = 2 points, D = 1 point, and F = 0 points. Grading criteria may be devised by Hill College and the ISD to allow faculty the opportunity to award high school credit only or high school and college credit depending upon student performance. E. Faculty, who are responsible for teaching dual credit/concurrent classes, are responsible for keeping appropriate records, certifying census date rosters, providing interim grade reports, certifying final grade reports at the end of the semester, certifying attendance, and providing other reports and information as may be required by Hill College and/or the School District.
Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.
Documentation and compliance (a) The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses. (b) The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter. (c) The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
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
Responsibility for documentation None of the Security Agent, any Receiver nor any Delegate is responsible or liable for: (a) the adequacy, accuracy or completeness of any information (whether oral or written) supplied by the Security Agent, an Obligor or any other person in or in connection with any Finance Document or the transactions contemplated in the Finance Documents or any other agreement, arrangement or document entered into, made or executed in anticipation of, under or in connection with any Finance Document; (b) the legality, validity, effectiveness, adequacy or enforceability of any Finance Document, the Transaction Security or any other agreement, arrangement or document entered into, made or executed in anticipation of, under or in connection with any Finance Document or the Transaction Security; or (c) any determination as to whether any information provided or to be provided to any Secured Party is non-public information the use of which may be regulated or prohibited by applicable law or regulation relating to insider dealing or otherwise.
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.
ENVIRONMENTAL DOCUMENTATION Each environmental service provided by the Engineer shall have a deliverable. Deliverables shall summarize the methods used for the environmental services, and shall summarize the results achieved. The summary of results shall be sufficiently detailed to provide satisfactory basis for thorough review by the State, The Federal Highway Administration (FHWA), and (where applicable) agencies with regulatory oversight. All deliverables shall meet regulatory requirements for legal sufficiency, and shall adhere to the requirements for reports enumerated in the State’s NEPA MOU. a. Quality Assurance/Quality Control Review For each deliverable, the Engineer shall perform quality assurance quality control (QA/QC) reviews of environmental documents and on other supporting environmental documentation to determine whether documents conform with: 1) Current Environmental Compliance Toolkit guidance published by the State’s Environmental Affairs Division and in effect as of the date of receipt of the documents or documentation to be reviewed; 2) Current state and federal laws, regulations, policies, guidance, agreements, and memoranda of understanding between the State and other state or federal agencies; and 3) FHWA and American Association of State Highway and Transportation Officials (AASHTO) guidelines contained in “Improving the Quality of Environmental Documents, A Report of the Joint AASHTO and American Council of Engineering Companies (ACEC) Committee in Cooperation with the Federal Highway Administration” (May 2006) for: DocuSign Envelope ID: F9E4AA24-4672-4529-8EFA-00D1CA218520 a) Readability, and b) Use of evidence and data in documents to support conclusions. Upon request by the State, the Engineer shall provide documentation that the QA/QC reviews were performed by qualified staff. b. Deliverables shall contain all data acquired during the environmental service. All deliverables shall be written to be understood by the public and must be in accordance with the State’s Environmental Toolkit guidance, documentation standards, current guidelines, policies and procedures. c. Electronic versions of each deliverable must be written in software which is compatible to the State and must be provided in a changeable format for future use by the State. The Engineer shall supplement all hard copy deliverables with electronic copies in searchable Adobe Acrobat™ (.pdf) format, unless another format is specified. Each deliverable shall be a single, searchable .pdf file that mirrors the layout and appearance of the physical deliverable. The Engineer shall deliver the electronic files on CD-R, CD-RW media in Microsoft Windows format, or through the ftp site. d. When the environmental service is to apply for a permit (e.g., United States Coast Guard (USCG) or United States Army Corps of Engineers (USACE), the permit and all supporting documentation shall be the deliverable. e. Submission of Deliverables 1) Deliverables shall consist of reports of environmental services performed in addition to a Categorical Exclusion (CE) determination form and supporting documentation including the required form or Environmental Assessment (EA) document, when applicable. 2) All deliverables must comply with all applicable state and federal environmental laws, regulations and procedures and include all items listed in the Environmental Document Review Checklist and the Administrative Completeness Review Checklist. 3) On the cover page of each environmental assessment (EA), finding of no significant impact (XXXXX), environmental impact statement (EIS), and record of decision (ROD) prepared under the authority granted by this MOU, and for any memorandum corresponding to any CE determination it makes, the Engineer shall insert the following language in a way that is conspicuous to the reader or include it in a CE project record: "The environmental review, consultation, and other actions required by applicable DocuSign Envelope ID: F9E4AA24-4672-4529-8EFA-00D1CA218520 Federal environmental laws for this project are being, or have been, carried-out by TxDOT pursuant to 23 U.S.C. 327 and a Memorandum of Understanding dated December 16, 2014, and executed by FHWA and TxDOT." f. The State shall provide the State’s and other agency comments on draft deliverables to the Engineer. The Engineer shall revise the deliverable: 1) to include any State commitments, findings, agreements, or determinations (e.g., wetlands, endangered species consultation, Section 106, or Section 4(f)), required for the Transportation Activity as specified by the State; 2) to incorporate the results of public involvement and agency coordination; 3) to reflect mitigation measures resulting from comments received or changes in the Transportation Activity; and 4) include with the revised document a comment response form (matrix) in the format provided by the State. g. All photographs shall be 3.5” x 5” color presentation printed on matte finish photographic paper or 3.5” x 5” color presentation printed on matte white, premium or photo quality laser or inkjet paper. All photographs shall be well focused and clearly depict details relevant to an evaluation of the project area. Provision of photographs shall be one original print of each image or electronic presentations of comparable quality. Comparable quality electronic photograph presentations shall be at least 1200 x 1600 pixel resolution. Photographs shall be attached to separately labeled pages that clearly identify project name, project identification (ID) number, address or Universal Transverse Mercator (UTM) of resource, description of the picture and direction of the photographic view. In addition to the hard-copy prints, an electronic version of each will be submitted with the same identification information as the hard-copy.
