Final Checklist

Pre-requisites

• ☐ Source system inventory documented
• ☐ Table and column list (DDL or schema export) collected
• ☐ Data dictionary / business glossary reviewed
• ☐ Primary and business keys identified for every in-scope table
• ☐ Sample data reviewed (minimum 100 rows per table)
• ☐ Refresh frequency and CDC/delta availability confirmed
• ☐ PII field register received from client

Source Analysis

• ☐ Every in-scope source table classified (Master / Reference / Relationship / Transaction / Event)
• ☐ Table grain documented for every source table
• ☐ Source-to-source joins documented where required

MID Completion

• ☐ All source tables have at least one target entity assigned
• ☐ All mandatory CDM columns mapped (partyid/acct_num/rec_src and other PKs)
• ☐ Transformation logic documented for every non-trivial mapping
• ☐ Code conversion tables completed for all code-set fields
• ☐ Date format conversions documented
• ☐ Default values specified for nullable mandatory fields
• ☐ All relationship data mapped to dedicated relationship entities (not embedded in attribute tables)
• ☐ No source column left in an ambiguous or undecided state
• ☐ attrib_* usage documented with business meaning and approval reference

DQ and PII

• ☐ At least one DQ rule documented per mandatory field
• ☐ Nullability rules confirmed
• ☐ Domain / code checks written for all code-set fields
• ☐ Date range and sequence checks defined
• ☐ Referential integrity checks defined between entities
• ☐ All PII fields flagged (PII=Yes / Quasi / Sensitive)
• ☐ Masking and encryption treatment confirmed for PII fields

• ☐ PII Category populated for every mapped field (Direct Identifier / Quasi-identifier / Sensitive Category / Non-PII)
• ☐ Tokenisation Required (Y/N) set for every field; Tokenisation Method confirmed for all Y fields
• ☐ Allowed in 360 View (Y/N) set for every mapped attribute
• ☐ Allowed for MaxAI / Analytics Exposure (Y/N) confirmed by business steward for every field
• ☐ Aggregation-Only Flag (Y/N) set for every field; Y fields reviewed and approved by Data Architect
• ☐ Column-level Lineage Mapping populated (minimum: source-to-LDZ path for every attribute)
• ☐ Owner / Steward (Implementation Side) named for every mapped attribute

Review and Sign-off

• ☐ Business stakeholder has reviewed and signed off on semantic correctness
• ☐ CDM data architect has reviewed and signed off on canonical fit
• ☐ ETL engineer has reviewed and signed off on implementability
• ☐ Extension requests (if any) approved by Design Authority
• ☐ MID VERSION_HISTORY tab updated with new version number and sign-off details
• ☐ Final MID handed to engineering team for metadata loading