A policy document without a version number is a document without a history. A policy document with a version number but no record of who approved each version, what changed between versions, and when each version was distributed to staff is a document with the appearance of governance rather than the substance of it. The RBI's expectations on policy governance — particularly for credit policy, collections policy, and fair practices code — require that institutions maintain complete version histories, demonstrable sign-off trails, and evidence that updated policies were communicated to and acknowledged by relevant staff. The Policy & Ops Manual Agent AI manages the entire version control and sign-off workflow — from draft to review to approval to distribution — and maintains the complete history of every policy document in the institution's library.
What governance-grade version control actually requires
Version control at most institutions means saving a new file with "_v2" in the filename. Governance-grade version control means something structurally different: every version has a unique identifier and a locked record of what changed from the previous version; every version has a documented approval by an identified individual with the authority to approve that document; every version has a distribution record showing which staff members received it, in what form, and when; and every version is immutable once approved — changes require creating a new version, not overwriting the current one. The institution that can produce all four of these records for any version of any policy document, on demand, in response to an RBI examination request, has governance-grade version control. The institution that can only produce the current version of the document does not.
The version history: Credit Policy document
| Version | Date | Triggered by | Sections changed | Approver and authority | Distribution |
|---|---|---|---|---|---|
| v4.2 | Aug 12, 2025 | Board quarterly review + RBI/DOR/2025-26/42 (FOIR guidelines update) | Section 7.2.4 (employer list exception) · Section 6.8 (new business) · Section 11.1 (FOIR table revised) | Board of Directors — Resolution BOD/2025-Q2/14 · MD signature · Aug 12, 2025 | All staff (August 14) · Acknowledgement: 98.4% within 72h |
| v4.1 | Apr 8, 2025 | RBI/DOR/2024-25/112 (digital lending amendment) | Section 8.1–8.4 (digital lending chapter — full rewrite) · Section 2.3 (KFS fields) | Board of Directors — Resolution BOD/2025-Q1/07 · MD signature · Apr 8, 2025 | All staff + DSA partners (April 10) · Acknowledgement: 96.1% |
| v4.0 | Jan 15, 2025 | Annual policy review — comprehensive | All 12 chapters reviewed · Material changes to Sections 5, 6, 9, 11 · Minor updates elsewhere | Board of Directors — Resolution BOD/FY26-Q3/02 · MD + Board Risk Committee Chair · Jan 15, 2025 | All staff (January 17) · Branch heads: physical confirmation · Acknowledgement: 99.2% |
| v3.8 | Sep 22, 2024 | RBI inspection finding — exceptions to collections policy require documentation | Section 10.4 (exception documentation) · Section 10.5 (authority matrix for collections waivers) | MD — emergency amendment authority under Board Policy Governance Framework · MD signature · Sep 22, 2024 | Collections team and branch managers only (Sep 23) · Acknowledgement: 100% — mandatory within 24h |
| v3.7 | Jun 4, 2024 | Quarterly Board Risk Committee review | Section 7.4 (NRI borrower guidelines) · Section 9.2 (LTV table — LAP revised) | Board Risk Committee — Resolution BRC/2024-Q1/11 · BRC Chair signature · Jun 4, 2024 | All staff (June 6) · Acknowledgement: 97.8% |
The sign-off workflow: RBI/DOR/2025-26/84 amendments in progress
Circular analysis completed · Draft amendments prepared · Reviewers notified
All 6 sections identified, all 5 non-Board drafts prepared, Board flag raised for Section 11.2(b), review deadline of November 22 set, Compliance Officer (CO) and Legal notified by email and portal task.
Completed: Nov 8, 2025 · 4:28 PM COMPLETESection-by-section review of all 5 non-Board amendments · One minor revision requested
CO reviewed all drafts. One revision: the FLDG disclosure paragraph (Section 8.3(d)) — CO revised the phrase "clearly labelled section" to "clearly demarcated box with a visible heading" per the institution's preferred KFS formatting standard. Revision incorporated. CO signed off on all 5 non-Board amendments.
Completed: Nov 14, 2025 · 3:14 PM COMPLETELegal review of KFS template amendments and Collections Manual cross-reference · In progress
KFS Field 13–14 additions require Legal to confirm the recovery agent contact language is consistent with the institution's debt collection agreement templates. Legal review in progress — expected completion November 18. Deadline: November 22.
Assigned: Nov 8 · In progress · Due: Nov 22 IN PROGRESS · Due Nov 22MD signature on Digital Lending Policy v4.3, KFS template, Collections Manual, FPC, LSP Policy
MD signature on the 5 completed non-Board amendments, scheduled after Legal review completes. Target: November 22–25. MD sign-off page pre-populated with amendment summaries for each document — MD reviews summaries and signs rather than reading all 5 full documents.
Scheduled: After Legal review · Target Nov 22–25 PENDING LEGAL COMPLETIONBoard agenda item for December 5 meeting · Draft resolution pre-prepared by Policy AI
Credit Policy Section 11.2(b) (FLDG cap and disclosure in Board-approved credit policy) requires Board resolution. Board agenda item prepared, draft resolution language prepared, Board papers pack includes: (a) RBI circular summary, (b) proposed new section 11.2(b), (c) compliance implications of non-adoption. Board pack to be circulated December 1. Decision expected December 5.
Board meeting: Dec 5 · Board pack: Dec 1 SCHEDULED · Dec 5 BoardAmended documents published to policy portal · Staff acknowledgement tracking begins
Upon MD sign-off (Steps 1–4): documents published to the policy portal, email notification sent to all relevant staff groups, acknowledgement required within 72 hours. December 1 effective date: all staff will have received and acknowledged the 5 non-Board amendments by November 27 (72 hours after MD sign-off target of November 24). Board amendment (Section 11.2(b)) distributed after December 5 Board meeting.
Target: Nov 24 (distribution) · Nov 27 (acknowledgement deadline) SCHEDULEDThe version history table is not administrative housekeeping — it is the institution's proof that its policies were current, approved, and communicated at every moment an examiner might ask about
When the RBI examination team asks what the collections policy said in September 2024, the answer is in the version table: v3.8, approved by MD under emergency amendment authority on September 22, distributed to collections team and branch managers September 23, 100% acknowledgement within 24 hours. The examiner can see the trigger (RBI inspection finding), the approver (MD), the distribution (targeted to relevant staff), and the acknowledgement rate (100%). This is the governance record that demonstrates the institution takes policy maintenance seriously — not as a compliance exercise but as an operational reality. The Policy & Ops Manual Agent AI's version control and sign-off workflow produces this record continuously, for every document, without anyone in the institution having to think about maintaining it. The governance record is a byproduct of the process, not a task that is added to the process.