When the RBI issues a new circular affecting collections conduct, the change does not just need to be acknowledged — it needs to be deployed. Scripts updated, agent training completed, IVR flows modified, WhatsApp templates approved, compliance logs configured. Each of these is a task with an owner, a dependency, and a deadline derived from the circular's effective date. The Ops Programme Manager AI converts the regulatory change into a project plan and tracks every task to completion before the effective date.
The gap between knowing about a regulation and complying with it
The Regulatory Change Monitor AI reads the RBI circular and produces the impact assessment — which processes are affected, what must change, and what the effective date is. The Ops Programme Manager AI takes that assessment and converts it into an operational rollout plan: the specific tasks, the specific owners, the specific dependencies between tasks, and the specific timeline that works backward from the effective date to ensure every change is implemented before compliance is required.
This conversion — from impact assessment to rollout plan — is where regulatory change management most commonly fails. Institutions that know what needs to change frequently fail to manage the implementation as a coordinated programme. Technology changes wait for process changes to be finalised. Process changes wait for training materials that have not yet been drafted. Training cannot begin until the script change has been approved by legal. Each dependency creates a delay — and the delays accumulate until the effective date arrives with implementation still in progress.
The Ops Programme Manager AI tracks the critical path from the moment the impact assessment is received. When any task on the critical path is at risk of delay, it escalates immediately — not to the task owner, but to the function head responsible for that dependency, with the specific downstream impact stated.
A live rollout plan: RBI FPC amendment — effective December 1, 2025
Phase 1 — Policy and Script Drafting
Days 1–5 · Owner: CCO + Collections Head · Deadline: Nov 19New disclosure language drafted for all collection channels (voice, IVR, WhatsApp). Legal review of disclosure text completed. Collections head sign-off on updated script. Policy document updated and version-controlled.
Phase 2 — Technology Implementation
Days 3–10 · Owner: CTO · Deadline: Nov 22 (tech change request)IVR platform updated with mandatory disclosure at call commencement. Auto-dialler script parameterised. WhatsApp Business API templates updated and submitted to Meta for approval (24–48 hour approval turnaround). Call recording system configured for 3-year retention.
Phase 3 — Agent Training
Days 8–17 · Owner: HR Head + Collections Head · Deadline: Nov 28All collections agents (internal and agency) trained on the new disclosure requirement. Training cannot begin until the script is finalised (Phase 1 dependency). Recovery agency partners notified and given the updated conduct brief. Training completion recorded in compliance log.
Phase 4 — Compliance Verification and Go-Live
Days 17–24 · Owner: CCO · Go-live: December 1UAT of IVR disclosure, WhatsApp template, and auto-dialler. Call sampling — 20 calls reviewed by compliance officer to verify disclosure is being made. Compliance log configured to capture disclosure confirmation per call. Board compliance report updated to include new FPC amendment.
How the Ops PM AI tracks the critical path
The critical path through this rollout runs: legal review → script finalisation → training material → agent training → call sampling → compliance sign-off. Any delay in this chain delays go-live readiness. The WhatsApp template's Meta approval creates the only external dependency — a 24–48 hour turnaround the institution cannot control, which is why it was submitted on Day 8 (November 18) despite the script only being finalised on Day 6 (November 17). The Ops PM AI identified this external dependency and triggered the submission as soon as the script was available, rather than waiting for Phase 2 to be formally started.
When the Meta approval has not arrived by Day 10, the Ops PM AI generates an escalation: the WhatsApp template cannot be UAT-tested unless the approval arrives by November 23 — and flags an alternative scenario (phone call-only disclosure from December 1 until Meta approval, then full channel rollout) so that the CCO has a contingency plan available without needing to improvise one at go-live.
The process change map: what each team's workflow looks like before and after
Agent identifies account, initiates call
IVR or agent call opens with collections purpose statement. No mandatory disclosure of borrower rights at call commencement. Disclosure made only if borrower asks.
Mandatory borrower rights disclosure at commencement — every call, every channel
IVR: automated disclosure plays before the collections message. Voice: agent reads disclosure script (30 seconds). WhatsApp: disclosure text included in every collection message template. Auto-dialler: disclosure parameterised as mandatory first segment. Call log records disclosure confirmation.
Borrower right to account statement must be actionable on request
If a borrower requests an account statement during the collection interaction, a specific process must now produce it within 48 hours. Previously: ad hoc. Now: logged request, automated fulfilment workflow, 48-hour SLA tracked.
Call recordings stored for 3 years — configurable on telephony platform
Previously: 1-year retention policy. New requirement: 3 years from call date. Storage configuration update required by Nov 22. Older recordings retained under prior policy; all calls from Dec 1 onward retained for 3 years.
Grievance redressal mechanism disclosure — already in collections scripts
The institution's existing collections scripts already include grievance redressal mechanism disclosure. No change required — existing process satisfies the new requirement. Compliance confirmed and logged.
The regulation does not wait for the rollout plan to be finished
The effective date of an RBI circular is not a target — it is a deadline. Institutions that approach regulatory change as a sequential process — read, assess, plan, implement, train — run out of time because the dependencies between those stages are not managed as a critical path. The Ops Programme Manager AI converts the regulatory change into a managed programme the day the impact assessment is received: tasks assigned, dependencies mapped, external submissions triggered immediately, and escalation paths defined before the first task is late. The December 1 deadline is a programme milestone, not a surprise.