> For the complete documentation index, see [llms.txt](https://preapproval-guide.imda.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://preapproval-guide.imda.gov.sg/pre-approval-guide/stage-2-vendor-application/preparing-submission/create-new-draft-submission/solution-category-requirements.md).
# Solution Category Requirements
This section contains specific requirements that your solution must meet based on your selected solution category. Please review each requirement carefully and provide accurate responses.
#### Important Guidelines
**Mandatory Requirements:**
* All mandatory requirements must be answered with "Yes" to proceed with your application
* If your solution does not fully meet a mandatory requirement, you cannot continue with the application
**Preferred Requirements:**
* All preferred requirements must be answered with either "Yes" or "No"
* These requirements are not mandatory but help demonstrate your solution's capabilities
**Response Guidelines:**
* Only select "Yes" if your solution fully meets the requirement
* If your solution only partially meets or does not meet the requirement, please select "No"
* Be honest and accurate in your responses as these may be verified during the evaluation process
#### What You Need to Do
Review each requirement listed below and select the appropriate response. Ensure you have answered all questions before proceeding to the next section of your application.
Your responses will be used to assess whether your solution meets the programme standards and requirements for your selected category.
There are 4 questions that may appear in the requirements. Please visit the sub-sections to understand how to answer these questions.
[Data Analytics (DA) and Personal Data Protection (PDP) Requirements](/pre-approval-guide/stage-2-vendor-application/preparing-submission/create-new-draft-submission/solution-category-requirements/data-analytics-da-and-personal-data-protection-pdp-requirements.md)
[Cyber Essential Mark](/pre-approval-guide/stage-2-vendor-application/preparing-submission/create-new-draft-submission/solution-category-requirements/cyber-essential-mark.md)
[Vulnerability Assessment](/pre-approval-guide/stage-2-vendor-application/preparing-submission/create-new-draft-submission/solution-category-requirements/vulnerability-assessment.md)
[InvoiceNow-Ready Solution Provider Accreditation](/pre-approval-guide/stage-2-vendor-application/preparing-submission/create-new-draft-submission/solution-category-requirements/invoicenow-ready-solution-provider-accreditation.md)
{% hint style="warning" %}
**Important Reminder**
Press Save Draft periodically. Information is not saved automatically.
{% endhint %}
---
# 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://preapproval-guide.imda.gov.sg/pre-approval-guide/stage-2-vendor-application/preparing-submission/create-new-draft-submission/solution-category-requirements.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.
