Trade Lifecycle Management for SEBI Research Analysts (2026)
A recommendation is not a single message. It has a life: you open it, you update it as things change, and at some point you close it. SEBI's record-keeping rules, and the annual audit that tests them, expect you to be able to show that whole arc, with timestamps, five years later. Here is how to manage the lifecycle of a call so it stands up to scrutiny, without it living in your head or buried in a WhatsApp thread.
Note: general guidance for SEBI-registered Research Analysts, not legal advice. Aktai is research and compliance tooling, not an execution or advisory service; you remain the registered analyst who makes the call.
Why the lifecycle, not just the call
Most Research Analysts record the entry well enough. You have the report, the rationale, the date. Where records fall apart is everything after: the update you sent when the thesis shifted, and the exit you never quite wrote down. Six months later, when a client disputes a loss or an auditor asks for the file on a particular stock, you are reconstructing the story from memory and a scroll-back through chats. That is the gap that turns into a finding.
Treating each recommendation as a lifecycle, one connected record from open to close, fixes that. It is also simply better research practice. A call you have to close out forces honesty about how it actually went, which is the raw material for the past-performance reporting SEBI now expects you to publish.
The three stages
The call, with its reasoning attached
The moment you form a view is the moment to record it: the security, the date and time, the rationale, your holding and conflict disclosures, and who the note went to. A view recorded after the fact, or reconstructed from memory, is the weakest evidence there is. Recorded at entry, with a timestamp you did not set yourself, it is the strongest.
Every revision, in order
Calls move. New filings land, a thesis weakens, a target is revised. Each update is part of the same record, not a fresh unconnected message. An ordered chain of updates shows you managed the call actively and kept clients informed, which is both good practice and exactly what the record-keeping rule is reaching for.
The close, and why
A call that just goes quiet is the one that looks bad in an audit and worse in a performance review. Record the exit: the date, the outcome, and a line on why you closed it. A clean exit completes the record and feeds honest past-performance reporting instead of a book of calls that were silently abandoned.
The record has to be tamper-evident, not just present
An auditor is not only asking whether a record exists. They are asking whether it can be trusted. An editable file with a recent modified date does not prove when a recommendation was first made, because anything in it could have been changed yesterday. That is the core weakness of running a recommendation book in a spreadsheet or a chat history, and it is covered in depth in our piece on why a spreadsheet fails Regulation 25.
A tamper-evident record solves it. When each note is hashed and timestamped at the moment you send it, the hash is proof the content was not altered afterwards. The entry note, every update, and the exit note all carry their own timestamp, so the lifecycle is not just stored, it is verifiable. That is the difference between a pile of records and an audit-ready one.
How this works on a research desk
On Aktai, the lifecycle record is a by-product of doing the work, not a second job. You draft and send the entry note, and it is hashed and locked into the audit trail with its timestamp, recipients and content. The same happens for each update and for the exit note. Because every send lands in one ordered, exportable trail rather than scattered across client chats, the full history of any call is one click away, and the audit log exports as a CSV when the annual audit or an inspection asks for it.
Aktai does not place trades, set stop-losses in a broker account, or auto-execute. It is a research desk, so the lifecycle it manages is the lifecycle of your recommendation and its record, not order routing. For many independent Research Analysts that is exactly the part that was missing, because the execution always happened in the client's own broker account anyway; what was hard was proving, cleanly, what you said and when.
FAQ
What is trade lifecycle management for a Research Analyst?
It is the practice of recording every stage of a recommendation as one connected record: the entry view and rationale when you first make the call, every update or revision while the call is live, and the exit when you close it. Instead of an idea that lives in your head and a few scattered WhatsApp messages, the call has a single time-stamped history a client and an auditor can both follow.
Does SEBI require Research Analysts to track the lifecycle of a recommendation?
SEBI requires you to keep records of your research reports, the rationale behind each recommendation, and your client communications for five years, and the annual compliance audit tests those records. While the regulations do not use the phrase "trade lifecycle", the obligation to show what you recommended, when, why, and how it was updated or closed is exactly what a lifecycle record provides. Keeping it as a connected, time-stamped log is the cleanest way to meet the record-keeping rule.
Why is a WhatsApp thread not enough to record a recommendation lifecycle?
A chat thread is editable, deletable, hard to export in a usable form, and scattered across many client conversations. It cannot prove when an entry call was first made versus edited later, it mixes the call with unrelated chatter, and reconstructing the full history of one recommendation across months of messages is painful. An auditor wants a clean, ordered, tamper-evident record of each call, which a chat history is not designed to give.
What should a recommendation record contain?
At entry: the security, the date and time, your view, the rationale, your conflict and holding disclosures, and the clients it went to. During the call: every material update with its own timestamp. At exit: the close date, the outcome, and a short note on why you exited. Keeping these as one linked record, rather than three disconnected messages, is what makes it audit-ready and what lets you publish honest past-performance numbers later.
How does Aktai help with the record side of the lifecycle?
Aktai is a research desk, not an execution platform: it does not place orders or track stop-losses in a broker account. What it does is make the record side automatic. Every note you mark as sent is SHA-256 hashed and stored with its timestamp, recipient and content, retained five years, and exportable as a CSV for the annual audit or an inspection. So the entry note, the update notes and the exit note all land in one tamper-evident trail rather than a chat thread, and the recommendation-performance record builds itself from the notes you actually sent.