> For the complete documentation index, see [llms.txt](https://admin-services.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://admin-services.docs.intersectmbo.org/guides/vendor-guides/1-contracting-and-onboarding.md). # 1 - Contracting & Onboarding ## Overview Designed for vendors, but useful to all, this hub provides transparency on everything you may need to know about agreeing a contract and delivering a proposal under Intersects administration. ## Key stages in delivering your proposal This page will take you through the key stages in delivering your proposal:
Procurement Due Diligence - Verifying Vendor's information Once your proposal has passed the voting threshold, you will be contacted by the Procurement team to complete your due diligence. This involves: * Background ID Check * KYC / KYB Checks * ID Documentation Authentication Check * Business Documentation Checks * Wallet Checks You can find more information in our [Due Diligence Policy](/governance/policies-and-guidance/due-diligence-policy.md) (*to be updated).*
Procurement - Creating your legal contract #### **Procurement - Creating your legal contract** Intersects Procurement team will lead on any contract agreements for Intersect or where Intersect is selected as an Administrator on behalf of the Cardano Development Holdings (CDH). The first part of the process is to agree a traditional legal contract with Intersect as the administrator for your proposal. **Contract Finalization** * Usually following successful on-chain voting, we will invite you to complete your contract. * Hopefully at this point you have already been in contact and a draft contract is in progress, this will now be subject to the necessary final reviews. * This is your last chance to make any amendments prior to it being signed. Remember your delivery will become public information and milestones will be immutably recorded on-chain. **Contract Signing** * It is a constitutional requirement to have a contract in place between the vendor and administrator. * Before delivery begins or any funds can be released the contract must be signed by all parties. Once the final draft has been completed this contract will be sent for signature by the Procurement team. **Additional details** More details on our contracting, associated policies, KYC and KYB can be found here on our knowledge base. [How To - Write Milestones Within Your Statement of Work](/guides/vendor-guides/1-contracting-and-onboarding/how-to-write-milestones-within-your-statement-of-work.md) [Milestones Example Download](https://drive.google.com/file/d/18Yfv9rwKgayv1cVPzSj3QNOJP37UbIxZ/view?usp=drive_link)
Delivery Assurance - Introduction to Delivery Assurance Once Procurement have completed all their legal checks and have a signed legal contract by both the vendor and Intersect, they will hand over the contract to Delivery Assurance to manage. The Delivery Assurance team will be the vendor’s main point of contact within Intersect throughout the management of the contract. **Introduction to Delivery Assurance** * You will be given a Delivery Assurance team member as your main point of contact throughout contract delivery. We will support milestone tracking, milestone sign off, and ensure alignment between the legal contract, smart contract, and what’s being delivered. **Communications Channel Setup** * A communication channel will be created (Slack, Discord or email) to share any updates or ask any questions directly with the Delivery Assurance team at Intersect (Permissions for Intersect to record contact details). **Delivery Familiarization** * We will set up an onboarding call with you to discuss your milestones, acceptance criteria, third-party assurance review, and how the milestone acceptance process works. * We will also share and explain with you how to request any changes to the contract, should you need to do this.
Smart Contracts- Setting up your Smart Contract **Smart Contracts- Setting up your Smart Contract** All deliveries under Intersects administration will be managed through a smart contract, if you have not already done so you should familiarize yourself with this framework [*smart contracts*](/governance/smart-contracts.md)*.* **Funding a Vendor Contract** * The Delivery Assurance team will submit an on-chain action to fund a specific vendor smart contract instance, this will contain your payment schedule from your agreed written contract. * This smart contract has to be witnessed by Intersect’s independent oversight and the process for this, due to how timing works on-chain, this could take up to 36 hrs. * Vendors also have to verify and sign this transaction. This will also validate that the wallet address you have provided is correct. * This creates a transparent version of your contract on-chain, witnessed by yourself, Intersect and Intersect’s independent oversight committee. That's it! From this point onward your delivery is immutably confirmed on-chain and delivery can begin. [The Oversight Committee](/governance/the-oversight-committee.md) [Smart Contracts](/governance/smart-contracts.md)
*** **Go to Step 2 – Delivery and Milestone Management** Navigate to the next stage of the process to learn how to manage your milestones, submit evidence, and stay aligned with delivery requirements. Go To Delivery and Milestone Management *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://admin-services.docs.intersectmbo.org/guides/vendor-guides/1-contracting-and-onboarding.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.