> 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/maintaining-your-contract-status/how-to-keep-my-status-as-a-pre-approved-vendor/withdrawal-process.md).

# Withdrawal Process

If you decide to withdraw from the SMEs Go Digital Pre-Approval process, you must provide a written notification with 30 days notice that it is withdrawing from the application via <smes_go_digital@imda.gov.sg>.

You may re-apply for SMEs Go Digital Pre-Approval status at a later date, and such re-application shall be treated as a new application.&#x20;

You shall be required to undergo the entire SMEs Go Digital Pre-Approval 4-stage process, the submission of a full set of documents and information required for SMEs Go Digital Pre-Approval. &#x20;

{% hint style="warning" %}
**Q: I have decided to close down or cease operations for my pre-approved solution business line. What should I do?**

**A:** Please initiate the withdrawal process by writing to us at <smes_go_digital@imda.gov.sg> with the relevant justification for your withdrawal.
{% 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/maintaining-your-contract-status/how-to-keep-my-status-as-a-pre-approved-vendor/withdrawal-process.md?ask=<question>&goal=<user_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.
