Isn't master data already controlled by our ERP's permission model?

Permissions control who can edit a record; they don't control how a change is requested, justified, approved by downstream consumers, or rolled back. DAMA-DMBOK 2 and COBIT 2019 BAI06 both treat the change-management workflow as separate from system permissions.

What's the difference between master data and reference data?

DAMA-DMBOK 2 defines reference data as sets of values used to characterise other data (e.g., country codes, currency codes), and master data as the data describing core business entities (customers, products, suppliers, etc.). Both benefit from controlled change processes; the controls overlap but are not identical.

Does this apply to small organisations without a dedicated data team?

The principles scale down. Even a small team benefits from a single intake form, a named approver, and a change history — the same four elements DAMA-DMBOK 2 recommends. The tooling can be lightweight; the structure is what matters.

What a Controlled Master Data Change Process Actually Needs

An insight on what a controlled master data change process actually needs from CodeCraft Enterprise.