> For the complete documentation index, see [llms.txt](https://cyberpassion.gitbook.io/internal-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cyberpassion.gitbook.io/internal-docs/data-collection/introduction.md). # Introduction ### Purpose • Collect all required information from the client • Avoid delays in project execution • Ensure all content and documents are available before work starts • Maintain proper project records *** ### Step 1: Contact the Client Contact the client through: • Phone Call • WhatsApp • Email Explain what information is required and why it is needed. *** ### Step 2: Share Data Requirement List Send the client a list of required items such as: • Organization Profile • Logo • Contact Details • Images • Content / Text • Faculty Details • Department Details • Existing Website Details (if applicable) • Any other project-related information *** ### Step 3: Collect Information Receive the information from the client through: • WhatsApp • Email • Google Drive • Documents • Excel Files *** ### Step 4: Verify the Data Check whether: • All information has been received • Images are clear • Content is complete • Documents are correct If anything is missing, inform the client immediately. *** ### Step 5: Organize the Data Save all received data in the proper project folder. Create separate folders for: • Content • Images • Documents • Credentials • Approvals *** ### Step 6: Share with Internal Team After verification, share the data with the concerned team: • Design Team • Development Team • Content Team • Support Team *** ### Step 7: Update Data Status Maintain a simple status record: #### Data Received All required information received. #### Partial Data Received Some information is pending. #### Follow-up Required Client needs to provide more information. #### Ready for Work All required data is available and work can start. #### --- # 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://cyberpassion.gitbook.io/internal-docs/data-collection/introduction.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.