Subcontractor Documentation Sample Clauses

Subcontractor Documentation. Contractor shall require its subcontractors that are not licensed or certified by DHCS to complete and submit non-drug Medi-Cal organizational forms within 30 days of the execution of an initial subcontract, within 90 days of the renewal or continuation of an existing subcontract or when there has been a change in subcontractor name or ownership. Non-Drug Medi-Cal Organizational forms shall be submitted through xxxx://xxx.xxxx.xx.xxx/provgovpart/Pages/Master-Provider-File-Database-Resources.aspx. Organizational documents shall include the subcontractor’s Articles of Incorporation or Partnership Agreements (as applicable), business licenses, fictitious name permits, and such other information and documentation as may be requested by DHCS.
AutoNDA by SimpleDocs
Subcontractor Documentation. Contractor shall require its Subcontractors that are not licensed or certified by the State to submit organizational documents to the State within thirty (30) days of its execution of an initial subcontract, within ninety (90) days of the renewal or continuation of an existing subcontract or when there has been a change in Subcontractor name or ownership. Organizational documents shall include the Subcontractor’s Articles of Incorporation or Partnership Agreements (as applicable), and business licenses, fictitious name permits, and such other information and documentation as may be requested by the State.
Subcontractor Documentation. Subcontractor shall submit all documentation reasonably requested by Owner to substantiate their right to payment, including lien waivers on the forms attached hereto.

Related to Subcontractor Documentation

  • 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.

  • 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.

  • 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.

  • Service Documentation The “Service Documentation” includes;

  • 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

  • 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.

  • Options for Documentation 6.1. We shall document and, upon request, provide such documentation of Our compliance with the obligations agreed upon in this DPA by appropriate measures.

  • 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.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

Time is Money Join Law Insider Premium to draft better contracts faster.