> For the complete documentation index, see [llms.txt](https://community.theiofoundation.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.theiofoundation.org/about-techup/stakeholders/organizations/organization-lifecycle.md). # Lifecycle This page describes the itinerary for an Organization Partner across its participation in TechUp. {% hint style="info" %} **ShortURL | Playbook | Assistant** {% endhint %} {% hint style="warning" %} **NOTICE** This documentation page is under construction.\ Should you want to be notified once it's published, [**let us know**](https://TIOF.Click/TIOFTarianUpdatesService). {% endhint %} Timeline Participating in TechUp is very easy! This simple list of steps will guide you through all the steps. Rest assured, the TechUp team will be with you to support you all the way. Get familiar with the benefits and commitments of participating in TechUp Make sure you fulfil our requirements Register your Organization Get approved (we will be quick!) Prepare your participation Get familiar with the platform (Airmeet) (Optional) Plan for activities you would want to run Attend the orientation session Dress up your booth Promote your participation across your networks & Invite your organization members Attend TechUp Get your post-event stats ## Submit your Organization Participating in TechUp as a Organization Partner is very simple. Just follow the steps below and you’ll be set and ready in no time. How to propose your Organization: Check the requirements Submit your proposal through our submission platform Our team will review your submission promptly and we will be in touch with you for next steps. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community.theiofoundation.org/about-techup/stakeholders/organizations/organization-lifecycle.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.