> 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-4-approval.md).
# Stage 4: Approval
This stage help you understand the Appointment letter and vendor responsibilities.
## 1. Appointment Letter
Upon successful application, you will be offered an Appointment Letter.
* Appointments commence upon receipt of the Appointment Letter and continue until terminated
* Vendors may only sell the specific solution version that was evaluated and pre-approved
* Pre-approval status does not guarantee or endorse the solution's quality or fitness for purpose, and must not be marketed as such
**Appointment Structure**
A review year runs for 12 months from the appointment date. For example, if appointed on 1st April 2025, the review year is 1st April 2025 to 31st March 2026.
You can check your contract information in VMP at "[Approved Solutions](/pre-approval-guide/stage-4-approval/approved-solutions.md)" section.
Annual reviews occur in the 9th month of each review year. Passing vendors continue their appointment, while failed reviews may lead to suspension or termination and non-submission leads to termination.
## 2. Responsibilities as a [new pre-approved vendor](/pre-approval-guide/stage-4-approval/welcome-to-the-pre-approved-vendor-programme.md)
In the next section, learn the first steps as a new vendor.
{% hint style="warning" %}
FAQ
Q: As a pre-approved vendor, how do I notify changes to my company's ACRA details (company name, UEN, address, shareholding, etc.)?
A: Submit this [form ](https://form.gov.sg/68117f6fa667a54847523fd2)and select "Question about onboarding that is not found in FAQ"
{% 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-4-approval.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.
