# Submitting Request to Tech team

To handle program owners request better in a more systematic way, we introduced '[Tech Software Request Form](https://docs.google.com/document/d/147kl-tehu3Z3rVUBiNRcJlyVuVGqYcPXulRXyEPkxQE/)'. Please feel free to duplicate this template and fill it up to submit to Tech through JIRA (preferred) or Email.

This is also part of our SOP process and requirements from '[SOP Event & Program Management'](https://drive.google.com/file/d/11iDCfN-OZ_CGii43_-A23t8tZQ5axcDI/view?usp=sharing) & '[SOP System Development](https://drive.google.com/file/d/1i34sAP5hJLr5dIL5E__cXeXOI3qFK4bJ/view?usp=sharing)'. (we are refining these SOP)

![SOP Event & Program Management](/files/-MV-BeVGVvf8MRAkJCWP)

![](/files/-MV-CUOlblIOVqE_hbyY)

{% hint style="info" %}
Program Owners are expected to submit this at earlier of the year as soon as possible when their project execution memo is approved.
{% endhint %}

Take Notes:

* Memo must be approved by CEO and attached as a copy here
* All projects must appoint a person in charge. Tech team appointed project manager will liaise with this personnel only. 
* All project must have gone through UAT test (where program owner is involve) before it can be publish onto the Internet. 
* All project must be renewed yearly, else allocated resources will automatically be discontinued (e.g. domain name etc)
* All SLA duration is 6 months with an additional 6 months extension with a total budget not more than MYR 100k.


---

# Agent Instructions: 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:

```
GET https://central-docs.mymagic.my/for-program-owner/submitting-request-to-tech-team.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.