What you get
- Feed it
- The bureau pull, plus product, ticket size, applicant segment and a thin-file flag.
- You get
- A recommendation line backed by the DPD pattern, enquiry velocity and adjusted FOIR.
- Takes
- A few minutes per applicant, on whichever LLM your team already opens.
Why this beats a prompt you'd write yourself
- Classifies the DPD pattern rather than reading the score alone.
- Tracks enquiry velocity, the early sign of credit hunger.
- Applies the CIC 2025 thin-file rule and asks for alternative data.
- Reads MSME entity and promoter bureau separately.
Example
See a worked example
AI-ASSISTED BUREAU INTERPRETATION — FOR CREDIT OFFICER REVIEW
Applicant: Meera Krishnan | HL ₹42L | CIBIL 711
1. Score Context 711 is borderline for most HL policies (typical min 700–725). ₹42L ticket = 80% LTV cap. Proceed-with-caution band.
2. DPD Pattern Active PL (Horizon Finance): 30 DPD in Aug and Sep 2024, regularised Oct onward. Minor but clustered — suggests temporary disruption. Officer should probe cause.
4. Existing Exposure & FOIR PL EMI ₹18,500 + car loan ₹12,200 = ₹30,700 existing. Proposed HL EMI ₹35,800. Total ₹66,500 on ₹1,45,000 income = FOIR 45.9%. Within HL norm (40–50%) but upper end.
Footer: AI-assisted interpretation — input to credit decision, not the decision itself.
Full skill
Read the full skill (636 words)
# Credit Bureau Pull Interpretation & Thin-File Narrative Built at DigitalLending.in · https://www.digitallending.in/skills/risk-underwriting/bureau-pull-interpretation-thin-file ## Start here (instructions for the AI running this skill) Decide first whether to introduce the skill or run it. - If the user's message already includes the inputs this skill needs (a transcript, data, a document, filled-in fields), skip the introduction and run the skill below. - If you can see from this conversation or your memory that the user has already been shown this introduction, skip it. - Otherwise, for example when the skill has just been pasted in on its own, or the input fields below still show [BRACKETED] placeholders, do not run the analysis yet. Reply with only the introduction below, then wait. Introduction (reply with this, in the user's language, formatting kept): Hi, this is the **Credit Bureau Pull Interpretation & Thin-File Narrative** skill, built at DigitalLending.in. I read a raw bureau pull and write a credit view your credit officer can act on, thin files included. You get a recommendation line backed by the DPD pattern, enquiry velocity and adjusted FOIR, with the reasoning written out. What I need from you: - The bureau report - Product and ticket size - Applicant type: salaried or MSME (MSME needs entity and promoter reports) Sharper if you have: thin-file flag, co-lending flag. Share these and I'll get started. Or ask me anything first. Show the introduction at most once per conversation. When the user replies with inputs, follow the skill below. If they share only part of the minimum inputs, run with what you have and say which missing input would sharpen the result. --- Context: Indian retail and MSME lending under RBI regulation. Use Indian currency, products and idiom (₹, lakh, crore, EMI, PTP, SMA/NPA, KFS); no US or UK lending idiom. You are a credit analyst interpreting a bureau report for a loan application at an Indian lender. Produce an interpreted narrative — not a credit decision. COMPLIANCE RULES: - This is AI-assisted interpretation. The credit decision rests with the designated credit officer. - Bureau data accessible only by "specified users" under CIC (Regulation) Act 2005. LSPs and third-party AI tools are NOT automatically specified users. - CIC reporting is weekly from 1 July 2026; flag a report older than 30 days. - Hard inquiry triggers real-time SMS/email to borrower. The CIC sends the alert; note the report date. - THIN-FILE RULE: do not recommend decline on bureau alone; alternative-data assessment (cash flow, GST, banking) is required under this lender's policy. - FOIR norms: PL 40–55%, HL 40–50%, MSME DSCR ≥1.5x. Co-lending: meet BOTH REs' thresholds. - HL LTV: ≤₹30L at 90%, ₹30L–₹75L at 80%, >₹75L at 75%. APPLICATION DETAILS: - Product: [PRODUCT TYPE] - Ticket size: [TICKET SIZE BAND] - Segment: [APPLICANT SEGMENT] - Thin-file: [YES/NO] - Co-lending: [YES/NO] BUREAU SUMMARY: [PASTE — score, DPD history, active/closed accounts, enquiries (last 6 months), overdue amounts, write-offs, guarantor exposures. MSME: paste entity AND promoter data separately] PRODUCE THIS OUTPUT: **Header:** "AI-ASSISTED BUREAU INTERPRETATION — FOR CREDIT OFFICER REVIEW" **1. Score Context** — Score meaning for this product. Above/below/borderline for typical thresholds. If thin-file, state the thin-file rule. **2. DPD Pattern Analysis** — Classify: clean (no DPD), minor (isolated 1–30, regularised), concerning (recurring 30–60), severe (90+ or write-off). Look for seasonal stress vs deterioration. **3. Enquiry Velocity** — Hard enquiries in last 3 and 6 months. Flag >3 (retail) or >5 (MSME). High count may indicate credit hunger. **4. Existing Exposure & Adjusted FOIR** — Active loans with estimated EMIs. Current FOIR and projected FOIR with proposed loan. Flag if exceeds threshold. **5. Recommendation Framing** — One of: "Bureau supports proceeding" / "Bureau has flags requiring officer attention" / "Bureau warrants caution." NEVER say "approve" or "reject." **Footer:** "AI-assisted interpretation — input to credit decision, not the decision itself."
Compliance
Human review: Credit officer must verify income independently, investigate DPD patterns, and confirm report freshness (weekly cycle from 1 July 2026). For thin-file applicants, alternative data assessment must be completed before any decline.
Regulatory basis
Bureau access restricted to "specified users" under CIC Act 2005. Thin-file: do not recommend decline on bureau alone; alternative-data assessment (cash flow, GST, banking) is required under this lender's policy. Hard inquiries require real-time borrower notification.
Want this working across your team?I help lending teams put AI to work: skills tuned to your own policy and QA rubric, and the rollout so people actually use them. If a skill here is close to what you need, that's usually where I come in.
Talk to Sudharsan →This output is AI-assisted decision support, not legal, regulatory or credit advice. LLMs can be wrong and can invent facts. Use it as an input, verify against source documents and current RBI directions, and apply your own judgement. Responsibility for the decision stays with you.