An RBI circular is published on a Thursday afternoon. By the following Monday, the institution's lending teams are expected to operate in compliance with it. In between, someone must read the 14-page circular, identify every section of the credit policy, collections manual, KYC SOP, and fair practices code that the circular affects, draft the necessary amendments, route them for review and sign-off, and ensure that the updated policy reaches every person whose work it governs — in time, in writing, and with evidence of receipt. At most institutions, this process takes 3 to 6 weeks and produces policy documents that lag their regulatory obligations by the width of a compliance team's backlog. The Policy & Ops Manual Agent AI compresses this to 72 hours, from circular publication to drafted amendments, reviewed, signed, and distributed.
An RBI circular is published on a Thursday afternoon. By the following Monday, the institution's lending teams are expected to operate in compliance with it. In between, someone must read the 14-page circular, identify every section of the credit policy, collections manual, KYC SOP, and fair practices code that the circular affects, draft the necessary amendments, route them for review and sign-off, and ensure that the updated policy reaches every person whose work it governs — in time, in writing, and with evidence of receipt. At most institutions, this process takes 3 to 6 weeks and produces policy documents that lag their regulatory obligations by the width of a compliance team's backlog. The Policy & Ops Manual Agent AI compresses this to 72 hours, from circular publication to drafted amendments, reviewed, signed, and distributed.
The circular-to-policy pipeline: what has to happen and why it takes so long without automation
The process begins with circular interpretation — reading a regulatory document and identifying what it changes. This requires regulatory expertise, knowledge of what the current policy says, and the ability to see the delta between "what we do now" and "what we must do after this circular." Most compliance teams do this well but slowly, because each person on the team is simultaneously managing several other regulatory obligations and the reading, interpretation, and policy-mapping for a complex circular can take a full day for a qualified compliance officer.
The second step is policy section identification — finding every section of every document in the institution's policy library that the circular affects. A single RBI circular on digital lending guidelines may affect the digital lending policy, the KYC SOP, the collections manual, the fair practices code, the board-approved credit policy, the customer grievance policy, and the privacy and data management policy simultaneously. A compliance officer manually mapping a circular to the policy library may miss sections — not because they are careless but because the policy library is large, the connections are non-obvious, and the mapping is cognitively demanding at the scale of a real institution. The Policy AI maintains a tagged, indexed policy library and can identify every section affected by a given regulatory theme in seconds.
The third step is drafting the amendments — writing the specific changes to policy language that the circular requires. This is where policy quality degrades most in manual processes: the amendment is drafted under time pressure, by whoever is available, in language that may not be consistent with the rest of the document's style and terminology. The Policy AI drafts amendments in the document's existing style, using consistent terminology, with explicit citations to both the RBI circular section that mandates the change and the pre-existing policy section being amended.
"A lending policy that does not reflect the current regulatory framework is a policy that will produce compliance findings. The only question is whether the institution discovers this first or the examiner does."
The circular analysis: RBI/DOR/2025-26/84 — Digital Lending Framework Amendment
Circular Analysis — RBI/DOR/2025-26/84 · Received Nov 8, 2025 · Analysis completed Nov 8 · 4:28 PM
Digital Lending Framework Amendment — Effective: Dec 1, 2025 · Policy impact: 6 sections across 4 documents · Review deadline set: Nov 22
Circular summary — what changed
The RBI has issued amendments to the Digital Lending Framework (August 2022) covering three primary areas: (1) First Loss Default Guarantee (FLDG) arrangements — enhanced disclosure and cap requirements for co-lending arrangements; (2) Key Fact Statement — mandatory inclusion of recovery agent information and grievance contact for digital loans; and (3) Loan Service Provider (LSP) due diligence — updated minimum standards for LSP vetting, including mandatory quarterly performance reviews.
Reference: RBI/DOR/2025-26/84 · Para 3.2, 4.1, and 5.4 · Effective December 1, 2025 · Non-compliance: supervisory action
Policy sections requiring amendment — 6 sections across 4 documents
Digital Lending Policy · Section 8.3
MANDATORY · Dec 1 deadline
FLDG disclosure: Section 8.3 currently does not require borrower disclosure of FLDG arrangements in co-lending. Circular Para 3.2 mandates explicit disclosure to borrower at KFS stage. Amendment required: new sub-section 8.3(d) — "FLDG Disclosure Obligation." Language drafted by Policy AI and appended to this analysis.
→ Draft amendment: 4 paragraphs · Prepared · Awaiting Compliance Officer review
KFS Template · Fields 12–14
MANDATORY · Dec 1 deadline
Key Fact Statement template currently does not include a dedicated field for recovery agent contact details and escalation grievance contact. Circular Para 4.1 requires both as mandatory KFS fields for all digital loans. Policy AI has drafted the two new fields with RBI-compliant language and formatting, to be inserted between current Fields 12 and 13.
→ Draft amendment: 2 new KFS fields · Template redline prepared · Requires Legal and Compliance sign-off
LSP Governance Policy · Section 4.1
UPDATE · Dec 1 deadline
Current LSP due diligence requires annual performance review. Circular Para 5.4 upgrades this to quarterly. Amendment: Section 4.1 to be updated — "annual" replaced with "quarterly" in 3 locations. Performance review template to be updated with additional metrics specified in Annex II of the circular.
→ Draft amendment: Word substitution (3 instances) + new Annex II metrics table · Prepared
Collections Manual · Section 6.2 (Recovery Agents)
UPDATE · Dec 1 deadline
Recovery agent contact disclosure (required in KFS per Para 4.1) must be consistent with what is stated in Section 6.2 of the Collections Manual. Current 6.2 does not specify a borrower-accessible escalation contact. Policy AI recommends aligning both documents — a single defined escalation contact per product, consistent across KFS and Collections Manual.
→ Draft amendment: new sub-section 6.2(c) · Consistent with KFS Field 13 draft · Cross-reference added
Fair Practices Code · Section 2.4
UPDATE · Dec 1 deadline
Fair Practices Code Section 2.4 (Transparency) should be updated to reflect the enhanced FLDG disclosure obligation. Not a mandatory new section — but alignment with the Digital Lending Policy amendment (Section 8.3) is necessary for consistency. Policy AI recommends updating the FPC cross-reference in Section 2.4 from "Digital Lending Policy Section 8.3" to "Digital Lending Policy Sections 8.3 and 8.3(d)."
→ Draft amendment: 1-line cross-reference update · Minor but necessary for document consistency
Board-Approved Credit Policy · Section 11.2
NEW SECTION
Circular Para 3.2 requires that co-lending FLDG caps be reflected in the Board-approved credit policy, not only in operational documents. A new Section 11.2(b) is required, specifying the maximum FLDG percentage per co-lending partner type and the disclosure obligations. This section requires Board approval (since it amends the Board-approved credit policy) — flagged as requiring December Board agenda item.
→ Requires Board approval · Flag raised for December Board agenda · Cannot be effective Dec 1 without Board sign-off
Amendments requiring Board approval
1 — Credit Policy 11.2(b)
December Board agenda flag raised · Other 5 amendments: Compliance + Legal sign-off sufficient
Review deadline set
Nov 22 · 5 reviewers notified · Board item: Dec 5 meeting
Compliance implementation deadline: Dec 1
The redline amendment: what the Policy AI produces for review
Redline Draft — Digital Lending Policy · Section 8.3 · New Sub-Section 8.3(d)
Prepared by Policy AI · Nov 8, 2025 · Awaiting Compliance Officer review · Version 1.0-DRAFT
8.3 FLDG Arrangements in Co-Lending
8.3(a) The institution may enter into First Loss Default Guarantee (FLDG) arrangements with co-lending partners, subject to the RBI Master Direction on Co-Lending Model and the limits specified in Section 11.2 of the Board-Approved Credit Policy.
8.3(b) FLDG arrangements must be documented in the co-lending agreement, reviewed by the Legal function, and approved by the Board Risk Committee prior to operationalisation.
8.3(c) All FLDG arrangements are subject to quarterly reporting to the Board Risk Committee.
[NEW — Policy AI draft · RBI/DOR/2025-26/84 Para 3.2 · Mandatory by Dec 1, 2025]
8.3(d) FLDG Disclosure Obligation: Where a digital loan is originated under an FLDG arrangement with a co-lending partner, the institution shall disclose the existence of the FLDG arrangement to the borrower at the Key Fact Statement stage, prior to loan acceptance. The disclosure shall state: (i) that an FLDG arrangement is in place; (ii) the identity of the co-lending partner; and (iii) that the arrangement does not alter the borrower's rights, obligations, or the terms of the loan as stated in the KFS. The disclosure shall appear as a separate, clearly labelled section of the KFS immediately before the borrower's acceptance signature.
Note: This sub-section is effective from December 1, 2025, per RBI/DOR/2025-26/84. All digital loan disbursements from December 1 must include the FLDG disclosure in the KFS where an FLDG arrangement applies. The KFS template update (Fields 13–14) required to implement this provision is detailed in the KFS Amendment dated November 8, 2025.
4h 12mCircular to drafted amendments — vs 3–5 days manual process · 6 sections identified · All 5 non-Board drafts prepared
6Policy sections affected — across 4 documents · 2 mandatory (KFS + Digital Lending) · 3 updates · 1 new Board section flagged
Dec 1Implementation deadline — Nov 22 review deadline set automatically · Board item flagged for Dec 5 Board meeting · No deadline missed
1Board flag raised — Section 11.2(b) requires Board approval · Cannot be delegated to Compliance · December agenda item created
The institution that reads a circular and updates its policy library in 72 hours does not spend December explaining to its branches why they received a circular compliance notice for something the compliance team was "still working on"
The Policy & Ops Manual Agent AI does not replace the compliance officer's judgement — it replaces the compliance officer's reading, mapping, drafting, and document management workload. The compliance officer who previously spent 3 to 5 days on circular response now spends 2 to 4 hours reviewing well-prepared drafts, confirming the AI's section identification is complete, and approving language that is already consistent with the document's style. The remaining time is spent on the judgement work that only a qualified compliance officer can do: assessing edge cases, advising the business, and attending the Board Risk Committee. The Policy AI turns circular compliance from a reactive scramble into a structured, timestamped, always-on process — and the compliance officer from a document assembler into a policy decision-maker.
