Templates turn governance from concept into daily habit. They give every step a defined owner, a defined input, a defined output. The instruments below are what make Q-Lana data discipline operational every day, plus a preview of the Q-Lana Master Data Dictionary that anchors the whole framework.
These instruments are not theory. They are refined every quarter through client work. Banks, funds, impact investors. Emerging and developed markets. The previews below show structure and intent. The full versions are scoped and tailored to each institution as part of a Q-Lana engagement.
Each template carries a clear purpose, named ownership, and a defined integration point with the rest of the data architecture. Below: the purpose of each, plus a small structural excerpt to show the format. The full templates are configured and shipped as part of a Q-Lana implementation.
Captures every key data field for a domain: definition, ownership, system of record, allowed formats, validation rules, SLAs. The single reference for data accountability inside that domain.
Defines essential business and risk terms (RAF metrics, RAROC, portfolio limits, default events, IFRS 9 stages) so all teams speak the same language. Critical for aligning business and analytics output.
Lists rule identifiers, definitions, owners, and remediation steps. Powers automated DQ scorecards. The institutional record of what "clean" actually means for each domain.
Standardizes how Relationship Managers record client interactions. Separates facts from opinions, highlights triggers, risks, and agreed actions. Builds the qualitative knowledge base over time.
Tracks client consent, purpose of data use, lawful basis, retention period, and anonymization plan. The audit-ready record of how the institution handles personal and sensitive data.
Defines behavioral and contextual early-warning indicators (DPD streaks, covenant breaches, negative sentiment, sector stress). Links signals to escalation workflows.
The Master Data Dictionary is the canonical definition of every field that can appear in the lending lifecycle on the Q-Lana platform. It exists for three reasons: to give every Q-Lana customer a consistent, defensible data model from day one without forcing them to invent one; to give Q-Lana a single source of truth that downstream code, ETL pipelines, dashboards, and customer documentation are generated from; and to give institutional buyers (CIOs, Chief Data Officers, internal auditors, regulators) a verifiable artifact that demonstrates how the platform handles data. The dictionary is a product. It is built, versioned, and shipped with the same discipline as the platform itself.
| Field | Definition | Type | Owner | Regulatory anchor |
|---|---|---|---|---|
| individual.date_of_birth | Date of birth of the natural person; used for age, KYC, and beneficiary checks. | date | Onboarding | KYC / AML |
| company.legal_name | Registered legal name of the entity as recorded in the relevant business registry. | string(255) | Counterparty mgmt | ISO 20022 |
| facility.principal_outstanding | Drawn principal owed by the borrower at the reporting reference date, gross of provisions. | decimal(18,2) | Credit operations | Basel III · IFRS 9 |
| collateral.market_value | Most recent market valuation of the pledged asset, in the currency of the collateral instrument. | decimal(18,2) | Collateral mgmt | Basel III |
| covenant_breach.cure_period_days | Number of days the borrower has to cure a covenant breach before formal escalation. | integer | Risk management | Internal RAF |
# Sample field definition from the Q-Lana Master Data Dictionary entity: facility field_name: principal_outstanding type: decimal(18,2) unit: currency_amount required: true owner: credit_operations steward: facility_data_steward sensitivity: internal regulatory_mapping: basel_iii: "EAD component" ifrs_9: "gross carrying amount" bcbs_239: "P3.5 lineage required" validation: - rule: non_negative - rule: less_than_or_equal_to.original_principal # ... full record contains 17 additional metadata fields ...
Governance used to be a policy nobody read. Once the templates and the Master Data Dictionary became the single source of truth, every team spoke the same language and the audit trail wrote itself. Discipline finally lived in the tools, not in memos.
Head of Data, regional bank
Three places the Governance Toolkit shows up next.
The full template library, with usage notes, integration patterns, and the template-evolution story across Q-Lana client engagements.
Talk to us about scoping a Q-Lana Master Data Dictionary deployment for your institution. Modular adoption, regulatory mapping, and the tailored implementation playbook.
The precondition for everything. Where the architecture, the journey, and the toolkit come together as the foundation that makes the rest of the institution scale.
Strategy decks describe data governance. Templates run it. The six instruments above and the Master Data Dictionary that anchors them turn principles into daily habits. What gets captured. Who owns it. Where it lives. When it expires. The institutions that win are not the ones with the best slides. They are the ones with the best templates.
No pitch deck. A working session on where data fragmentation is costing the lending business, and the foundation that has to land before anything else moves.
Curated news with practitioner commentary. One Deep Dive in rotation. One applied tool. Read in fifteen minutes. Used the same week.