Condition Report The landlord and tenant are required to inspect the residential unit together at the beginning and end of the tenancy and complete a written condition report. If the landlord allows the tenant to have a pet after the start of the tenancy, an inspection report must be done on the day the tenant starts keeping a pet or on another day mutually agreed to by the landlord and tenant, unless the tenancy started on or after January 1, 2004, and a condition inspection report was completed at that time. A report may describe any damage, how clean each room is, and the general condition of the residential unit including: the floors, carpets, appliances, and paint on the walls. The report must be signed and dated by both the landlord and the tenant who made the inspection, and each should keep a copy. Change of Landlord – A new landlord has the same rights and duties as the previous one and must follow all the terms of this agreement unless the tenant and new landlord agree to other terms.
Project Completion Report At the completion of construction and once a Project is placed in service, the Subrecipient must submit a Project Completion Report that includes the total number of units built and leased, affordable units built and leased, DR-MHP units built and leased, an accomplishment narrative, and the tenants names, demographics and income for each DR-MHP unit.
Project Reports; Completion Report 1. The Recipient shall monitor and evaluate the progress of the Project and prepare Project Reports in accordance with the provisions of Section 2.06 of the Standard Conditions and on the basis of indicators agreed with the World Bank. Each Project Report shall cover the period of one (1) calendar semester, and shall be furnished to the World Bank not later than one (1) month after the end of the period covered by such report.
ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:
Inspection Report The Client and the Company agree that the Company, and its inspector(s), will prepare a written home inspection report which shall:
Final Project Report Prepare a Final Project Report that addresses, to the extent feasible, comments made by the Grant Manager on the Draft Final Project Report. Submit one (1) reproducible master and an electronic copy of the final. Upload an electronic copy of the final report in pdf format to the FAAST system.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
Project Review A. Programmatic Allowances
Evaluation Report 20.5.4.1 The summary evaluation report shall be prepared by the Faculty Evaluation Committee and administrative evaluator(s) and shall include each evaluator’s individual rating. The summary evaluation report shall take into account the results of each of the evaluation components (Section 20.5.3) in order to arrive at an overall rating. When the committee and the administrative evaluator(s) cannot reach an agreement as to the overall rating, the report must include written explanation.
Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
