Format and Content of Invoices. 3.1. Architect acknowledges that the District requires Architect’s invoices for Basic Services must include explanations of the Services performed.
Format and Content of Invoices. Architect acknowledges that the District requires Architect’s invoices to include detailed explanations of the Services performed. For example, a six-hour charge for “RFIs and CORs” is unacceptable and will not be payable. A more detailed explanation, with specificity, is required. For example, the following descriptions, in addition to complying with all other terms of this Agreement, would be payable.
Format and Content of Invoices. Architect acknowledges that the District requires Architect’s invoices to include detailed explanations of the Services performed. For example, a six hour charge for “RFIs and CORs” is unacceptable and will not be payable. A more detailed explanation, with specificity, is required. This includes a separate entry for each RFI, PCO, CCD and change order. For example, the following descriptions, in addition to complying with all other terms of this Agreement, would be payable. The times indicated below are just placeholders: Review RFI 23; review plans and specifications for response to same; prepare responses to same and forward to contractor, district, construction manager, and project inspector. .8 hours Review COR 8; review scope of same and plans and specifications for appropriateness of same; prepare draft change order and language for same. .7 hours Review COR 11; review scope of same and plans and specifications for appropriateness of same; prepare rejection of COR 11 for review by district, CM, IOR. 1.2 hours
Format and Content of Invoices. Architect shall submit invoices in a format that is mutually acceptable with the District and shall follow the framework of the Compensation section.
Format and Content of Invoices. 3.1. Architect acknowledges that Architect’s invoices for Basic Services must include detailed descriptions of the Services performed.
Format and Content of Invoices. 3.1. Bridging Architect acknowledges that the District requires Bridging Architect’s invoices for Basic Services must include explanations of the Services performed.
Format and Content of Invoices. 1. Xxxx Program Manager acknowledges that the District requires Bond Program Manager’s invoices to include detailed explanations of the Services performed. Bond Program Manager will develop a format that is acceptable to the District that will include sufficient detail to document tasks and scope. Bond Program Manager will keep timecards of employees for purposes of an audit at the District’s request, but those timecards are not required to be submitted with invoices. Hourly Rates for Extra Services
Format and Content of Invoices. 2.5.1. Architect acknowledges that the Judicial Council requires Architect’s invoices for Basic Services must include explanations of the Services performed.
Format and Content of Invoices. 3.1. Architect acknowledges that Architect’s invoices for Basic Services must include detailed descriptions of the Services performed. EXHIBIT E INSURANCE REQUIREMENTS Architect shall procure prior to commencement of the Services and maintain for the duration of this Agreement insurance against claims for injuries to persons or damages to property which may arise from or in connection with the performance of the Services by Architect, Architect’s agents, representatives, employees and Consultant(s). Architect’s liabilities, including but not limited to Architect’s indemnity obligations, under this Agreement, shall not be deemed limited in any way to the insurance coverage required herein. Maintenance of specified insurance coverage is a material element of this Agreement and Architect’s failure to maintain or renew coverage or to provide evidence of renewal during the term of this Agreement, as required or when requested, may be treated as a material breach of contract.
Format and Content of Invoices. Architect acknowledges that the District requires Architect’s invoices to include detailed explanations of the Services performed. For example, a six hour charge for “Architectural Programming” is unacceptable and will not be payable. A more detailed explanation, with specificity, is required. For example each invoice should provide separate entries for each meeting held (date, length, etc.), deliverables related to invoice, etc.
