LendingIQ logo
← Agent catalogue

AI Agent Profile · LendingIQ · Agent #77 · POA

Policy & Ops Manual Agent AI

Function: Policy Documentation ExecutiveInvoked via: RBI circular · policy change request · staff policy queryRuntime: AWS Bedrock · ap-south-1Model: Claude Sonnet 4Context window: 200K tokens

DivisionLending Operations

Resume

What this agent does

The Policy & Ops Manual Agent AI keeps LendingIQ's lending policies and operations manuals current, consistent, and accessible — drafting policy updates when RBI issues a new circular, managing the version control and sign-off workflow, and answering staff queries against the approved policy corpus through an embedded Q&A interface on the policy portal. It replaces the manual policy documentation executive with a continuous documentation capability that ensures staff are never operating against outdated policy and that every policy change is traceable to its regulatory source.

Primary functions

Policy Drafting

Per RBI circular or policy change request · 5-day draft turnaround

Invoked when: a new RBI circular is received, or a policy change request is submitted by the CCO or credit head

  • Analyses the new circular against the current policy repository — identifying every section of every policy document that is affected by the circular's requirements, and producing a gap analysis that maps the circular's specific obligations to the current policy language. The gap analysis distinguishes between three types of change: mandatory changes (the circular requires a different policy position than the current one), clarifying changes (the circular provides explicit guidance on an area where the current policy was ambiguous), and recommended changes (the circular does not mandate a change but the current policy is inconsistent with the circular's evident intent). The CCO reviews the gap analysis before the drafting begins — mandatory changes proceed immediately; clarifying and recommended changes are reviewed for priority and scope.
  • Produces a redlined draft of the affected policy sections — the current text with tracked additions, deletions, and modifications, with a marginal note on each change explaining the specific circular provision that requires or supports it. The redline format allows the CCO and board to see exactly what is changing, why, and how it relates to the regulatory source. Undocumented policy changes — where the text is different but the reason for the change is not recorded — are a persistent inspection finding; every change in the draft has an explicit source reference.
  • Identifies implementation implications of the policy changes — changes to the LOS configuration, changes to staff procedures, training requirements, and any downstream effects on related policies that are not themselves being updated but that reference the changed sections. The implementation implications are included in the sign-off pack so that the CCO and board approve not just the text change but the full implementation plan required to make the change operationally effective.
Output: Gap analysis report — circular obligations mapped to current policy, change type classification. Redlined policy draft — tracked changes with circular source references and marginal notes. Implementation implications summary. All three submitted to CCO within 5 business days of circular receipt.

Version Control

Continuous · all policy documents

Invoked at every draft, review, sign-off, and publication event for any policy document

  • Maintains a complete version history for every policy document — the full text of every version, the date it was effective, the date it was superseded, the CCO and board resolution that approved it, and the circular or internal decision that triggered the change. The version history is the audit trail that enables an inspector to reconstruct what policy was in effect on any given date — a question that arises when an exception or complaint involves an event that occurred under a prior policy version.
  • Manages the sign-off workflow — routing the draft to the CCO for review, incorporating CCO comments and re-routing for approval, and then routing to the board for resolution. The workflow tracks the status of each draft (submitted to CCO, under CCO review, submitted to board, awaiting board resolution, approved, published) and escalates to the CCO where a review milestone is approaching without a recorded review action. A policy draft that stalls in the sign-off workflow creates a gap between the regulatory obligation (effective from the circular date) and the internal policy update (effective from the board resolution date); tracking the workflow prevents unnoticed gaps from accumulating.
  • Archives superseded policy versions in the policy repository in a form that is retrievable but clearly distinguished from the current version — preventing staff from inadvertently operating against an outdated policy while ensuring that the prior version is available for audit and dispute resolution purposes. The current version is the only version visible in the default policy portal view; prior versions require an explicit archive access request.
Output: Version control log — complete version history per policy document with dates, approvals, and triggers. Sign-off workflow status dashboard — current drafts by stage. Superseded versions archived with clear version labels. Current published version always the single accessible version in the policy portal default view.

Staff Q&A Bot

Continuous · embedded in the policy portal

Invoked when: a staff member submits a policy query through the Q&A interface on the policy portal

  • Answers staff policy queries against the current approved policy corpus — providing the specific policy section, the applicable rule, and the relevant conditions or exceptions in plain language. The Q&A bot is the alternative to calling the compliance team — staff who would previously have emailed the CCO's office with a policy question receive a response within 2 minutes, with the specific policy section cited so they can verify the answer themselves. The bot reduces the compliance team's handling of routine policy queries, freeing compliance capacity for substantive regulatory work.
  • Distinguishes between what the policy says and what it means where these are genuinely ambiguous — flagging queries where the policy text does not clearly answer the question and routing them to the CCO for a formal interpretation rather than providing a confident answer that may be wrong. A bot that provides confident answers to ambiguous queries is more dangerous than one that acknowledges ambiguity; staff who act on a wrong Q&A answer in good faith create a compliance failure that the CCO then has to manage.
  • Logs every Q&A query and the response provided — building a dataset that reveals the areas of the policy where staff have the most queries. A policy section that generates a high volume of staff queries is either insufficiently clear (a drafting problem) or covers an area where staff are regularly encountering new situations the policy did not anticipate (a coverage problem). The Q&A log is a diagnostic tool for the next policy review cycle.
Output: Staff Q&A response — specific policy section cited, applicable rule stated in plain language, conditions noted. Ambiguous queries flagged and routed to CCO for formal interpretation. Q&A log with query categories and volume by policy section — delivered to CCO monthly for policy clarity review.

Knowledge base

Policy Repository — Current and Archived Versions

The full corpus of LendingIQ lending policies and operations manuals — current approved versions and the complete version history. The primary source for both policy drafting and staff Q&A.

RBI Circular Archive

All RBI circulars received since the policy repository was established — linked to the policy sections they affected and the policy drafts they triggered. The regulatory source record for every policy change.

CCO and Board Sign-Off Records

The resolution records for every policy approval — date, approving body, and the draft version that was approved. The audit trail that demonstrates that no policy was published without the required sign-off.

Q&A Log — Staff Query History

All staff policy queries and responses — the diagnostic dataset for policy clarity review and the record of formal CCO interpretations for queries where the policy was ambiguous.

Compliance Calendar Agent AI — Implementation Deadlines

Circular implementation deadlines used to prioritise the policy drafting queue — circulars with short implementation windows are escalated above those with longer timelines.

Pre-Training — NBFC Policy Documentation Knowledge

RBI NBFC regulatory framework, lending policy documentation standards, and policy drafting best practices up to knowledge cutoff.

Hard guardrails

Will notPublish a policy update to staff without CCO and board sign-off. The publication gate is absolute — a draft, however well-prepared, is not an approved policy until it has passed the sign-off workflow. A policy published without sign-off is not a valid policy under LendingIQ's governance framework.
Will notProvide a definitive Q&A answer to a query where the policy is genuinely ambiguous. Ambiguous queries are flagged and routed to the CCO for formal interpretation. A confident wrong answer to an ambiguous question creates a compliance failure that is harder to manage than an acknowledged gap.
Will notInterpret regulatory intent beyond what the RBI circular explicitly states. Where a circular is unclear on its intent, the agent notes the ambiguity in the gap analysis and escalates to the CCO and legal counsel for interpretation. Regulatory intent is a legal judgment; the agent documents the question, not the answer.
Will notDelete or overwrite superseded policy versions. Every prior version is retained in the archive in its original form — the version history is permanent and uneditable. Policy version manipulation would compromise the audit trail and could constitute a regulatory offence.

Known limitations

The agent's ability to identify all affected policy sections from a new circular depends on the clarity and specificity of the circular. Where a circular introduces a new concept or requirement that does not map directly to existing policy language, the gap analysis may miss affected sections that a subject-matter expert would identify through professional judgment. The CCO review of the gap analysis is the check on this limitation.Treat the agent's gap analysis as a comprehensive first pass, not as a complete identification of all regulatory implications. CCO review should specifically focus on areas where the circular introduces genuinely new requirements rather than variations of existing ones — these are the areas most likely to have cross-policy implications that the agent's text-matching approach may miss.
The staff Q&A bot answers queries against the approved policy text — it cannot account for informal guidance, past practice, or verbal CCO interpretations that have not been incorporated into the policy. Staff who have been following an informal interpretation that differs from the policy text may receive a Q&A answer that contradicts their established practice.Use the Q&A log to identify areas where staff queries frequently reflect an informal interpretation that differs from the policy text — these are candidates for the next policy update cycle, where the informal interpretation is either codified in the policy or formally reversed.
Agent Profile · Policy & Ops Manual Agent AI · LendingIQ · Agent #77Last updated April 2026 · For internal use

Important Reads

Learn more about how to deploy Policy & Ops Manual Agent AI to your lending workflow.