> 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-3-evaluation/providing-clarifications-to-officer-in-charge.md).
# Providing Clarifications to Officer-in-Charge
1. After you have made your submission, the officer-in-charge will provide a list of clarifications and/or items to change.
2. You need to address every point mentioned as incomplete changes will result in longer processing time or rejection.
The clarifications may be from these areas:
* Your Company Profile
* Supporting Documents
* application
3. Make all the changes by the deadline given by the officer-in-charge
{% hint style="info" %}
**Q: How to communicate that you have completed all the clarifications/changes requested?**
**A:** In Vendor Management Portal, go to the application dashboard, select the application ID with status "Revisions required" and make the relevant changes required. After the changes are done, type a message in the Comments and Clarifications box and press "Submit".
Take note that once you pressed "Submit", you will not be able to make any changes to the submission until the officer-in-charge "sends back" the submission.
***
**Q: How do I know who is the officer-in-charge of my annual review, application or Change Request?**
**A:** You may find out by expanding the Comments and Clarifications section of your submission, where the officer-in-charge will be reflected if they have previously evaluated or communicated with you. You may also leave a note in the Comments and Clarifications field and wait for a response. If neither of these options work, please reach out to us via the Contact Us \[] form and we will assist you accordingly.
***
**Q: I need to urgently contact the officer-in-charge as I have missed out some documents in my submission. What should I do? Or I need to route back the submission for some changes or I have uploaded wrong files and needed to correct the submission.**
**A:** Please leave a note immediately in the Comments and Clarifications field of your submission, clearly stating what documents are missing and requesting the officer-in-charge to route the submission back to you for resubmission. If you do not receive a timely response, please contact us via the Contact Us \[] form with your submission details so that we can assist you accordingly.
***
**Q: I would like to arrange a phone call or Teams meeting to discuss the clarifications in my submission. Can I have the officer-in-charge's phone number or mobile number?**
**A:** We are unable to provide the direct contact number of the officer-in-charge. All clarifications and discussions regarding your submission should be conducted through the Comments and Clarifications field, which ensures that all communication is properly documented. Please leave your queries there and the officer-in-charge will respond accordingly.
***
**Q: I would like to raise an escalation to upper management due to an incident involving the officer-in-charge. What is the process?**
**A:** While we are unable to provide the direct contact details of our management team, you may submit your escalation request via the Contact Us \[] form. Please provide a clear account of the incident along with any relevant justifications or supporting information, and we will facilitate the escalation on your behalf.
{% 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 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://preapproval-guide.imda.gov.sg/pre-approval-guide/stage-3-evaluation/providing-clarifications-to-officer-in-charge.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.