MITC Template and Format for Research Analysts (2026)
You know you have to share the MITC. The questions that actually slow you down are the practical ones: what does each clause say, what format do you send it in, and how do you avoid retyping the whole thing for every new client. This is the hands-on companion to the explainers: the standard MITC structure clause by clause, the format SEBI expects, and how to generate it per client without doing it by hand.
Note: General information, not legal or compliance advice. Always use the current RAASB or industry-standard MITC wording and verify it against the latest SEBI circulars before you rely on it.
What the MITC is, in one paragraph
MITC is the Most Important Terms and Conditions: a SEBI-standardised set of terms every Research Analyst has to share with clients before, or at the start of, the service. It pulls the headline points of the analyst-client relationship into one short document so they are read rather than buried. The wording and format are standardised through the RA industry standards issued via RAASB, so you are not meant to write your own version. If you want the full background on what it is and where it came from, the MITC explainer and the MITC, KYC and reporting piece cover it. This post is the practical one: the actual structure and how to handle it.
The clauses, one by one
The standard MITC walks through the same set of clauses for every analyst. Here is what each one is doing. Use the current RAASB-issued standard text verbatim for the wording; the descriptions below are the plain-English version of what each clause covers, not a substitute for it.
Standard clause set, described in plain terms. The clauses and their exact wording are standardised; confirm the current RAASB-issued text and the latest SEBI circular before you share it.
The format SEBI expects
Two things matter about format. First, the wording: use the standardised RAASB text for the clauses, do not paraphrase them into your own language. The whole point of the MITC is that it reads the same everywhere, so a client can recognise the terms. The only parts you change are your own details: your name, your SEBI registration number, your fees, your contact. Second, the presentation: it should be a clear, standalone document, not a paragraph tucked into page nine of the agreement. A short PDF carrying the standard clauses with your details filled in is the format most analysts settle on. The MITC sits on top of your full client agreement, it does not replace it.
When and how to share it
Share the MITC before the client starts paying, or right at the start of service, and again whenever the terms change. Both new and existing clients are in scope. The how is as important as the when: send it over a channel that records delivery, get the client to acknowledge it, and capture that acknowledgement. This usually slots straight into digital KYC and onboarding, so the MITC goes out in the same flow that verifies the client, and nothing gets skipped. Keep the fee line honest with the SEBI cap; the fees guide has the numbers.
Keeping proof you shared it (Regulation 25)
The MITC only protects you if you can show the client received and acknowledged it. Under Regulation 25 you keep that proof for five years. In practice that means a timestamped record of the send and the acknowledgement, stored somewhere retrievable and tamper-evident, not a loose email you might lose. When a client later claims they were never told you do not guarantee returns, the retained, timestamped MITC acknowledgement ends the argument. The same record-keeping discipline applies to your complaints handling, so it is worth building once and reusing.
Generating the MITC per client without retyping
Here is the slow part, and the only part worth automating. The clauses are fixed and standardised, so the only things that change between one client and the next are your own details and the client name. Retyping the whole document each time, then chasing the acknowledgement by hand, is wasted effort. The fix is simple: generate the standard MITC pre-filled with your registration and fee details once, send it to each new client, and log the acknowledgement on send automatically. The wording stays exactly as standardised; only the delivery and the proof are automated. That is what tools handle. Aktai keeps a timestamped delivery record for everything you send a client, so the acknowledgement and the five-year proof come for free rather than as a separate chore.
FAQ
Is there a standard MITC template for Research Analysts?
Yes. The MITC text and format are standardised through the RA industry standards issued via RAASB, so the clauses and their wording are meant to be uniform across every analyst. You fill in your own details, your SEBI registration number, your fees, your contact, but you do not rewrite the standardised clauses themselves. Always use the current RAASB-issued wording and check it against the latest SEBI circular before you rely on it.
What format should I share the MITC in?
In the prescribed standard wording, as a clear standalone document, not buried inside a long agreement. Share it over a channel that records delivery, such as email or WhatsApp, get the client to acknowledge it, and keep that acknowledgement. A PDF that the client receives and accepts, with a timestamp on the send, is the practical format most analysts use.
How long do I have to keep proof that I shared the MITC?
Five years, alongside your other records under Regulation 25. The proof is the timestamped record that the client received and acknowledged the MITC. If a client later disputes what they were told, that retained record is what settles it, so store it in a form that is retrievable and tamper-evident, not a folder you might lose.
Can I automate sending the MITC to each client?
Yes, and that is the part worth automating. The clauses are fixed, so only your own details and the client name change between sends. A tool can pre-fill the standard MITC with your registration and fee details, send it to each new client, and log the acknowledgement automatically, which removes the retyping and the chasing. The wording stays standardised; only the delivery and the proof are automated.