Controlled Changes
Route additions, updates, deprecations and mappings through defined ownership and approval.
Managed Data Operations
Managed Reference Data That Keeps Enterprise Codes, Classifications and Mappings Controlled in Production
Operate shared code sets, hierarchies, mappings and allowed values through a governed service model with controlled change intake, validation, approval, versioning, publication, exception handling and operational reporting.
Controlled change intake and approval routing
Version, effective-date and mapping traceability
Publication, distribution and exception monitoring
Service reporting and prioritised improvement backlog
Service boundaries, operating windows, roles, controls, acceptance criteria and any service levels are confirmed during scoping and mobilisation.
Reference Data Operations Console
Illustrative operating view
Illustrative service visual; actual workflows and controls are configured to the client environment and agreed scope.
Consistent Mappings
Maintain governed crosswalks between shared values, source systems and downstream consumers.
Traceable Versions
Keep source, rationale, approval, version and effective-date evidence visible for operational review.
Observable Operations
Track exceptions, publication checks, backlog and improvement actions without inventing service targets.
01 · Operational Problem
When Small Code Lists Become Enterprise-Wide Operational Dependencies
Reference data often looks simple until the same value is copied into applications, integrations, reports, controls and regulatory processes. Uncontrolled changes then create inconsistent classifications, broken mappings, delayed releases and hard-to-explain downstream differences.
Unowned Code Changes
Teams add or retire values without a clear business owner, approval route, rationale or effective date.
Conflicting Mappings
Crosswalks between source and target systems drift, leaving duplicate, unmapped or obsolete values in production.
Delayed External Updates
Standards-based or third-party code changes arrive, but impact analysis and controlled adoption are inconsistent.
Spreadsheet-Centred Control
Critical lists and mappings live in local files, making ownership, version history and distribution difficult to govern.
Hidden Downstream Drift
Published changes are not consistently checked across consumers, so systems silently operate on different versions.
Recurring Exception Backlog
Invalid values, failed publications and unresolved mappings become repeat incidents instead of managed improvement work.
02 · Service Definition
A Managed Operating Layer for the Shared Values Your Systems Depend On
The service is designed for ongoing operation, not just a one-time data clean-up. It combines a clear service boundary with governed change control, platform-aware execution, operational evidence and continual improvement.
What Managed Reference Data means in practice
DataConsultant can operate agreed reference-data processes across code sets, classifications, hierarchies and mappings: receive change requests, validate against defined rules and authoritative sources, route approvals, record versions and effective dates, publish through the agreed mechanism, verify distribution, manage exceptions and report on operational health.
- Service procedures are documented so day-to-day work is repeatable and traceable.
- Business ownership and approval rights are made explicit rather than implied.
- Operational monitoring focuses on agreed controls, exceptions, queues and distribution checks.
- Recurring issues are moved into a prioritised improvement backlog instead of remaining permanent manual workarounds.
Reference Data Current service
Controlled values and classifications used by other data: status codes, categories, units, country/currency codes, reason codes, taxonomies and mappings.
Master Data Adjacent discipline
Core business entities such as customer, product, supplier or location records. Entity matching and golden-record management are separately scoped unless explicitly included.
Data Quality Supporting control
Rules, monitoring and issue management can be part of the service, but enterprise-wide data-quality transformation is a broader engagement.
Replace Ad-Hoc Code-List Changes with a Governed Operating Flow
Bring the current request channels, owners, mappings, publication steps and recurring exceptions into one reviewable service model.
03 · Managed Scope
What the Managed Reference Data Service Can Operate
The operating scope can be configured around selected domains and platforms. The intent is to make responsibilities, controls and evidence explicit from request intake through publication, verification and service review.
Reference-Set Inventory & Ownership
Maintain a controlled inventory of in-scope datasets, authoritative sources, owners, approvers, consumers and operational contacts.
Change Intake & Approval Routing
Standardise requests for additions, modifications, deprecations and mappings with rationale, evidence and accountable approval.
Validation & Control Checks
Apply agreed format, uniqueness, source, mapping, effective-date and policy checks before a change is released.
Crosswalk & Mapping Maintenance
Operate mappings between internal, external and platform-specific values with controlled exceptions and version history.
Version & Effective-Date Control
Record the approved state of a reference set so consumers can distinguish current, future, superseded and retired values.
Publication & Distribution
Execute or coordinate agreed publication mechanisms and verify that required downstream consumers receive the intended release.
Exception & Reconciliation Monitoring
Review unmapped values, failed checks, stale versions, rejected changes and distribution issues through an operational queue.
Service Reporting & Improvement
Provide agreed operational reporting, review recurring causes and maintain a prioritised backlog for control and process improvement.
Reference Data Change Lifecycle
A controlled service separates request, decision and release activities so operational evidence can follow the change end to end.
01
ReceiveCapture requester, source, rationale, affected set and requested effective date.
02
ValidateCheck format, source authority, duplicates, mappings, dependencies and defined controls.
03
ApproveRoute the decision to the accountable owner or steward according to the agreed workflow.
04
VersionRecord the approved state, effective date, superseded values and change evidence.
05
PublishRelease through the agreed platform, API, file, integration or controlled distribution mechanism.
06
Verify & ImproveCheck distribution, manage exceptions, report outcomes and prioritise recurring improvement needs.
04 · Service Boundary
Clear Operating Boundaries Before Steady-State Service Begins
A managed service works best when the operating team, client owners and separately commissioned activities are easy to distinguish. The final responsibility model is agreed during mobilisation.
| Activity | Typical treatment | What this means |
|---|---|---|
| Change intake, validation and workflow administration | Managed scope | Operate the agreed request flow, apply defined checks, route decisions and maintain operational evidence. |
| Mapping, version and publication administration | Managed scope | Maintain approved crosswalks and release metadata, then execute or coordinate the agreed publication process. |
| Business meaning and final approval | Client decision right | Accountable owners or stewards normally retain the business decision unless another arrangement is explicitly agreed. |
| Authoritative-source selection and legal interpretation | Client decision right | The organisation remains responsible for policy, legal and regulatory interpretation and for approving authoritative sources. |
| New platform implementation or major integration build | Separately scoped | Can be commissioned where needed, but is not assumed to be part of day-to-day managed operations. |
| Full master-data matching and golden-record implementation | Separately scoped | Reference data can support master data, but entity resolution and full MDM implementation require their own scope. |
| Formal audit, certification or specialist security testing | Separately scoped | Operational evidence can support assurance activities, but the managed service is not represented as a statutory audit or certification service. |
05 · Tangible Outputs
Operational Deliverables That Make the Service Governable and Transferable
The output is more than completed tickets. The service should leave a coherent operational record of what is in scope, how decisions are made, how changes are released and where improvement is needed.
Service Model & RACI
Scope, roles, decision rights, interfaces, governance cadence and escalation paths.
Reference-Set Register
In-scope datasets, owners, authoritative sources, consumers and operational dependencies.
Operating Procedures
Documented intake, validation, approval, versioning, publication and exception procedures.
Mapping & Crosswalk Register
Controlled mappings with source, target, version, exception and ownership context where applicable.
Change & Release Evidence
Approved change history, rationale, effective dates and publication evidence for the agreed service scope.
Exception Backlog
Tracked unmapped values, rejected changes, failed checks and recurring operational causes.
Operational Reporting Pack
Agreed visibility into queues, exceptions, control checks, release activity and improvement actions.
Improvement Roadmap
Prioritised actions to reduce recurring manual work, strengthen controls and improve service reliability.
Define the Operating Model, Not Just the Data Dictionary
Scope ownership, workflow, release evidence, monitoring, reporting and transition so the service can be run consistently over time.
06 · Delivery Approach
From Transition and Stabilisation to Ongoing Reference-Data Operations
The sequence is adapted to current maturity and evidence. No transition duration, staffing model, response time or uptime commitment is assumed before the environment and required operating model are understood.
Mobilise
Confirm scope, stakeholders, access, decision rights, operating window, controls and transition responsibilities.
Inventory
Identify reference sets, owners, sources, mappings, consumers, workflows, known issues and current documentation.
Stabilise
Address critical handover gaps, clarify procedures, baseline backlog and make operational evidence usable.
Operate
Run intake, validation, approval coordination, versioning, publication, mapping and exception processes.
Monitor
Observe agreed control checks, queue health, mappings, distribution outcomes and recurring failure patterns.
Report
Provide operational visibility, decision requests, recurring causes, dependencies and agreed governance inputs.
Improve
Prioritise automation, control, process, documentation and platform improvements through a governed backlog.
07 · Governance & Operational Control
Keep Business Decisions, Service Execution and Platform Responsibilities Distinct
The managed service should make accountability visible. The matrix below is illustrative; the final responsibility assignment depends on client policy, platform ownership and the agreed service boundary.
| Responsibility | Client business owner | Client platform owner | DataConsultant managed service |
|---|---|---|---|
| Approve business meaning and policy-sensitive changes | Accountable / Responsible | Consulted | Coordinates & records |
| Operate intake and validation workflow | Consulted | Consulted | Responsible within scope |
| Maintain mappings and release metadata | Approves material rules | Consulted | Responsible within scope |
| Platform access and technical change approval | Informed | Accountable / Responsible | Executes authorised actions |
| Monitor exceptions and report recurring causes | Reviews decisions | Reviews platform causes | Responsible within scope |
| Prioritise improvement backlog | Business priority input | Technology priority input | Evidence & recommendations |
08 · Sources, Standards & Client Inputs
Operate Against Agreed Authoritative Sources, Not Informal Copies
Reference data may be internally owned or based on external code sets. The service needs a clear source of truth, ownership model and impact path before changes can be managed reliably.
Internal reference sets
Organisation-specific status values, reason codes, product or service classifications, organisational codes and controlled taxonomies.
Standards-based code sets
Where adopted by the client, examples can include ISO 3166 country codes and ISO 4217 currency codes. Updates still require agreed source monitoring, impact assessment and controlled adoption.
Third-party and industry lists
Vendor, market, industry or partner-maintained classifications can be included when source rights, update mechanisms and ownership are clear.
Cross-system mappings
Source-to-target crosswalks can be operated as governed assets with owner decisions, exception handling and release evidence.
Bring Queues, Mappings and Ownership Gaps into One Governed Service
Use current evidence to decide what should be operated, what should stay with business owners and what needs separate platform or governance work.
09 · Buyer Fit
When Managed Reference Data Is the Right Next Step — and When Another Service Comes First
A managed operating service is most useful when the organisation has recurring reference-data work that needs sustained control. If the core problem is still strategy, governance design or platform implementation, that dependency should be addressed rather than hidden inside operations.
Good fit for managed operations
- Shared code sets or mappings affect multiple systems or business processes.
- Reference-data changes recur and require repeatable intake, approval and release.
- Ownership exists but operational administration is inconsistent or burdensome.
- Mappings, versions, effective dates or publication evidence need stronger control.
- Recurring exceptions and manual work need a governed improvement backlog.
- Operational reporting is needed across reference-data requests and controls.
Another engagement may come first
- Reference-data policy, ownership and decision rights have not yet been designed.
- The main need is full master-data matching, entity resolution or golden-record implementation.
- A new RDM or MDM platform must be selected, designed or implemented before operations can stabilise.
- The problem is a one-off data cleanse rather than an ongoing service requirement.
- The primary requirement is legal advice, statutory audit, certification or specialist security testing.
- Required service levels, support windows or staffing commitments have not yet been scoped.
10 · Commercial Clarity
Managed Reference Data Pricing Is Built from the Actual Operating Scope
A reliable fixed price cannot be presented without knowing the number of datasets, change volume, control model, mappings, platform footprint and operating requirements. Comparable public pricing is not sufficiently like-for-like to provide a responsible INR benchmark for a managed enterprise reference-data service.
Custom enterprise scope
Request a Quote
DataConsultant can prepare a commercial proposal after the required service boundary, transition needs, operating model, controls, integrations and reporting expectations are understood.
Published fixed fee on this page Not listedReference sets & domainsNumber, complexity, ownership model and business criticality.
Change volume & frequencyRequest patterns, release cadence, peaks and backlog.
Mappings & consumersCrosswalk volume, downstream systems and distribution endpoints.
Workflow & controlsValidation, approvals, segregation of duties, evidence and exception routing.
Platforms & integrationsExisting RDM/MDM, catalogue, database, API, workflow and integration tooling.
Operating windowRequired coverage, release constraints, escalation paths and service coordination.
Reporting & governanceOperational reporting, review cadence, decision forums and documentation.
Transition & improvementDocumentation gaps, open exceptions, stabilisation effort and improvement backlog.
Security & privacyAccess model, classification, audit evidence, retention and control requirements.
Delivery arrangementRemote, onsite or hybrid needs and dependencies on client or third-party teams.
Commercial note: no SLA, response time, uptime, staffing level, discount, licence fee or delivery duration is implied by this page. Any such commitment is documented only after scope and service design are agreed.
Get a Scope Built Around Your Change Volume, Control Model and Integration Footprint
Share the current reference sets, change channels, mappings, consumers and operational pain points so the right service boundary can be defined.
11 · Why DataConsultant
Operate Reference Data with Governance, Platform and Data-Quality Context Connected
The service is positioned within wider enterprise data management rather than as isolated ticket handling. That makes it easier to identify when a recurring operational issue needs a governance, quality, architecture or platform response.
Governance by Design
Ownership, approval, evidence and service cadence are built into the operating model instead of treated as afterthoughts.
Platform-Aware Operations
Processes can align to existing databases, MDM/RDM tools, catalogues, APIs, workflows and integration patterns where supported.
Evidence-Led Improvement
Recurring exceptions and manual effort can be converted into a prioritised improvement backlog with owners and decisions.
Documented Service Boundaries
Runbooks, responsibilities and dependencies support continuity, handover and transition-out rather than hidden operational knowledge.
Connected Data Disciplines
Reference-data issues can be considered alongside data quality, metadata, lineage, governance, architecture and managed operations.
Transition & Knowledge Retention
Mobilisation and operating documentation are designed to preserve context and support a controlled future change of operating model.
13 · Frequently Asked Questions
Managed Reference Data Questions Enterprise Buyers Commonly Need Answered
Scope, ownership, platforms, controls, transition and commercials should be clear before managed operations begin.
What is Managed Reference Data?
Managed Reference Data is an ongoing operational service for controlled code sets, classifications, mappings, hierarchies and allowed-value lists used across enterprise systems. The service can manage intake, validation, approval workflow, versioning, publication, distribution checks, exception handling, reporting and continual improvement within an agreed operating model.
What types of reference data can be included?
Scope can include internally governed status codes, classifications, organisational codes, product or service categories, units, reason codes, taxonomies, cross-system mappings and externally maintained code sets such as country or currency codes when those sources are adopted by the organisation. The actual datasets, authoritative sources and ownership model are confirmed during scoping.
How is reference data different from master data?
Reference data usually defines controlled values or classifications used to describe, constrain or map other data, while master data represents core business entities such as customers, products, suppliers or locations. They are related but operationally different. A reference-data service should not be assumed to include entity matching, golden-record creation or full master-data management unless those activities are explicitly scoped.
What is included in the managed service?
A typical scope can include service mobilisation, dataset inventory, ownership and approval routing, change intake, validation rules, mapping maintenance, version and effective-date control, publication and distribution checks, issue and exception handling, operational reporting, runbooks, governance cadence, backlog management and an improvement roadmap. Final inclusions depend on the agreed service boundary.
Who retains approval and business ownership?
Business ownership and decision rights should be explicitly defined rather than assumed. DataConsultant can operate agreed workflows and controls, while designated client owners or stewards can retain approval authority for business-sensitive changes. The final RACI, escalation path and acceptance criteria are agreed during mobilisation.
How are reference-data changes controlled?
A controlled flow normally records the request, source and rationale; validates the proposed value or mapping; routes it to the right approver; records version and effective-date information; publishes through the agreed mechanism; verifies downstream distribution; and retains evidence for reporting and review. The exact controls depend on risk, platform capability and client policy.
Can you work with our existing MDM, catalogue, database or integration tools?
Yes, where the required access and interfaces are available. The service can be designed around existing reference-data or MDM platforms, metadata catalogues, databases, APIs, integration tooling, workflow tools and cloud services. Recommendations remain requirements-led and platform-aware rather than assuming a specific vendor stack.
How are quality issues and unmapped values handled?
The operating model can include validation rules, duplicate or invalid-code checks, mapping completeness checks, reconciliation, failed-publication checks, exception queues, root-cause categorisation and controlled remediation. Thresholds, priorities and acceptance criteria are agreed for the service rather than invented in advance.
How can external standards or code-list changes be managed?
Where external code sets are in scope, the service can track approved source changes, assess affected mappings and consumers, route updates for approval, maintain versions and effective dates, publish controlled changes and verify downstream adoption. DataConsultant does not replace the authoritative standards body or the client’s legal and regulatory interpretation.
How are privacy, security and auditability addressed?
Controls can cover role-based access, change evidence, segregation of duties, source traceability, approval history, platform permissions, data classification and retention of operational records. Reference data is not automatically low risk; internal identifiers, business-sensitive classifications, access logs and workflow evidence should be handled according to the client’s security and privacy requirements.
How long does transition into managed operations take?
A reliable transition timeline is confirmed after scoping. It depends on the number of reference sets and domains, current documentation, source quality, approval design, integrations, downstream consumers, open backlog, platform access, control requirements and the amount of stabilisation needed before steady-state operation.
How is Managed Reference Data pricing determined?
Pricing is scope-led and confirmed through a Request a Quote process. Key factors include the number and complexity of reference datasets, change volume, source and approval workflows, mapping volume, distribution endpoints, platform and integration complexity, operating window, reporting and governance requirements, transition backlog, security controls and the amount of continual-improvement work requested.
Can we start with one domain and expand later?
Yes, a phased service can be appropriate when one reference-data domain is the immediate priority. Expansion should use the same agreed control model where practical, while confirming additional owners, sources, mappings, consumers, platform needs and commercial scope before each new domain is onboarded.
What is not automatically included?
Unless explicitly scoped, the service does not automatically include legal advice, statutory audit, certification, penetration testing, source-system replacement, full master-data implementation, large-scale data remediation, 24-hour support commitments, guaranteed response times or guaranteed uptime. Any such requirement must be separately assessed and agreed.
Managed Reference Data Enquiry
Request a Managed Reference Data Scope Review
Share your contact details and requirement. DataConsultant can review the likely service boundary, transition inputs, operating controls and commercial next step.