> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/forms/reviewing-submissions.md). # Reviewing submissions Once vendors start filling out your forms, their responses appear in Vendor Space for you to review. You can view individual submissions, browse through all responses, and create vendor records from the data. ## Viewing Submissions 1. Navigate to **Forms** in the sidebar and select the form you want to review. 2. Click the **Submissions** tab. 3. You will see a list of all submissions received for that form, with the most recent at the top. Each entry in the list shows a summary of key fields (such as company name and email) along with the submission date, so you can quickly scan through responses. > **Note:** Submissions from standalone forms (direct links or embeds) are saved as leads without an event association. Submissions from event pages include the event context. Both types appear in the same submissions list. ## Viewing a Single Submission Click on any submission in the list to open its full details. You will see every field the vendor filled out, displayed in the same order as your form. This detailed view makes it easy to review a vendor's complete application at a glance. ## Creating Vendor Records from Submissions When you review a submission and want to move forward with that vendor, you can create a vendor record directly from their application data. 1. Open the submission you want to act on. 2. Click **Create Vendor** (or the equivalent action). 3. Vendor Space will pre-fill a new vendor record using the data from the submission -- name, email, phone, and other relevant details. 4. Review the pre-filled information, make any adjustments, and save. This saves you from manually re-entering information and ensures that the vendor's details are consistent across your records. > **Tip:** Review submissions regularly so vendors aren't left waiting. A prompt response helps build trust and keeps your event planning on track. ## Managing a High Volume of Submissions If you receive a large number of submissions, here are a few strategies to stay organized: * **Review in batches:** Set aside regular time to go through new submissions rather than checking one at a time throughout the day. * **Use the search and filter tools:** Narrow down the list to find specific submissions quickly. * **Create vendor records as you go:** Converting approved submissions into vendor records keeps your pipeline moving forward. > **Tip:** Combine forms with your vendor pipeline to track each applicant's progress from submission through to confirmed participation. --- # 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://vendorspace.gitbook.io/docs/forms/reviewing-submissions.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.