Data cleaning
AuraScore 83/100

Credit Risk Loan Portfolio Attribute Remediation Matrix

Remediate missing, out-of-bounds, and conflicting loan exposure variables for capital adequacy stress testing pipelines.

Use this template when loan tape data from retail, commercial, or syndication books contains structural anomalies, invalid collateral values, or broken rate benchmarks prior to IFRS 9 / CECL calculations.

Template

Role: Senior Risk Data Governance Specialist and Quantitative Credit Risk Analyst specializing in BCBS 239 regulatory data aggregation and Basel model dataset hygiene.

Context

  • Credit portfolio class: {{portfolio_class}}
  • Loan origination feeds: {{origination_systems}}
  • Key dirty fields: {{critical_fields_at_risk}}
  • Target accounting & risk models: {{target_credit_models}}
  • Benchmark replacement standards: {{benchmark_standards}}
  • Capital adequacy framework: {{regulatory_framework}}

Task

Develop a comprehensive credit risk attribute remediation matrix that systematically addresses anomalous loan balances, broken interest rate indices, and missing collateral attributes across {{origination_systems}} to prepare reliable modeling inputs for {{target_credit_models}}.

Method

  1. Define numerical clamping and outlier detection boundaries for debt-to-income (DTI), loan-to-value (LTV), and credit scores.
  2. Standardize corrupted or non-standard amortization schedules and payment frequency codes across {{portfolio_class}}.
  3. Construct replacement logic for legacy floating benchmark rates transition based on {{benchmark_standards}}.
  4. Design multivariate imputation rules for missing property valuations, factoring in regional index movement and property vintage.
  5. Reconcile contradictory delinquency status codes against actual transactional payment histories and days-past-due counters.
  6. Standardize collateral lien prioritization fields, resolving conflicts between multiple originating servicing platforms.
  7. Establish strict boundary validation rules ensuring clean datasets satisfy {{regulatory_framework}} risk data aggregation standards.

Constraints

  • MUST explicitly categorize whether each remediation is an Imputation, Normalization, Replacement, or Capping action.
  • MUST NOT extrapolate values for primary exposure amounts without a deterministic loan ledger reference.
  • Imputed variables must be tagged with unambiguous statistical lineage metadata.
  • Matrix must specify risk-model impact ratings (High/Medium/Low) for every altered parameter.

Output format

A rigorous Markdown document structured as: 1) Executive Remediation Summary (max 120 words); 2) Credit Portfolio Data Sanitization Matrix (table with columns: Field Name, Input Issue / Anomaly, Detection Boundary, Remediation Method, Model Impact Rating, Fallback Handling, Audit Evidence Code); 3) Model Ingestion Assertions (exactly 4 mathematical assertions).

Self-review

  • Verify that all attributes listed in {{critical_fields_at_risk}} have concrete detection boundaries specified.
  • Check that legacy benchmark adjustments fully follow {{benchmark_standards}}.
  • Confirm that no remediation technique obscures default classification required under {{regulatory_framework}}.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

data-analytics
data-cleaning
financial-services
data cleaning
credit risk
bcbs 239