Supplier Master Data

Build Supplier Master Data That Procurement, Finance and Risk Can Trust

Establish authoritative supplier identities, controlled create-and-change workflows, duplicate prevention, critical-attribute quality rules and traceable distribution across sourcing, ERP, accounts payable, risk and analytics environments.

Define supplier identity, authority and ownership

Detect duplicates without unsafe automatic merges

Govern onboarding, changes, exceptions and disablement

Improve downstream procurement, payment and reporting data

Discuss Your Supplier Master Requirement Review Service Scope

Scope may cover assessment, design, remediation, implementation support or ongoing stewardship. Final responsibilities, timeline and commercial terms are confirmed after discovery.

Supplier Master Control ViewIllustrative operating model

An illustrative source-to-trusted-supplier-record workflow showing sourcing, ERP and accounts payable data entering identity matching, governance and quality controls before trusted supplier data is distributed to procurement, payment and analytics.

Sourcing & onboardingRequests, declarations, classifications

ERP & business unitsLocal supplier and vendor records

AP & risk inputsPayment, status, due-diligence context

Governed Supplier Master

Controlled identity + stewardship

Identity & matchingStandardise identifiers, names, addresses and relationships.

Ownership & workflowAssign create, change, approve, review and exception decisions.

Quality & controlsValidate critical attributes, evidence, status and completeness.

Trusted supplier record

Legal identityTax & payment refsClassificationStatus & hierarchySource lineage

ProcureSourcing, contracts, purchasing

Pay & controlAP, approvals, change evidence

AnalyseSpend, risk, performance, planning

Clear Decision Rights

Make supplier create, change, approve and exception ownership explicit.

Controlled Identity

Separate true duplicates from legitimate supplier relationships and variations.

Critical-Attribute Quality

Define rules for identifiers, status, classification and other business-critical fields.

Traceable Distribution

Understand how trusted supplier data moves to consuming systems and processes.

Business need

When Supplier Records Become an Operational and Control Problem

Supplier master issues often surface as payment, procurement, reporting or audit problems. The underlying cause is usually a combination of fragmented records, unclear ownership, weak validation and inconsistent change processes.

Duplicate supplier identities

One legal supplier appears under multiple names, codes, addresses or local records, weakening spend visibility and increasing reconciliation effort.

Service response: profile identity attributes, design match rules and route ambiguous candidates through controlled review.

Inconsistent identifiers and classifications

Legal names, registration identifiers, category codes, payment terms or supplier statuses are represented differently across systems and business units.

Service response: define canonical standards, reference mappings and source-authority rules.

High-risk change activity

Bank, payment, address, ownership or status changes do not follow consistent evidence, approval, segregation or exception rules.

Service response: design risk-based change controls and decision rights appropriate to the data and process.

Fragmented onboarding

Sourcing, procurement, finance and local teams collect the same information separately, creating incomplete records and repeated manual checks.

Service response: map the onboarding lifecycle and define accountable capture, validation and approval points.

Stale and inactive suppliers

Records remain active without a clear review, status, reactivation or deactivation process, complicating operational control and reporting.

Service response: define lifecycle states, review criteria, stewardship and evidence expectations.

Unreliable spend and supplier analytics

Different supplier keys and hierarchies prevent reliable aggregation by legal entity, group, category, geography or business relationship.

Service response: design supplier relationships, hierarchies and trusted keys for downstream use.

Need to Separate Supplier Symptoms from the Root Master-Data Problem?

Start with your priority processes, source systems, duplicate concerns, change risks and decision owners so the first scope focuses on evidence rather than assumptions.

Request a Supplier Master Review See the Control Framework

Direct answer

What Supplier Master Data Consulting Actually Covers

The service is not just a cleansing exercise. It connects supplier identity, data quality, ownership, workflow, control design and system distribution so the trusted record can be operated after the project ends.

A governed supplier record, not another duplicate database

Supplier master data defines how an organisation identifies a supplier, which attributes matter, which sources can be trusted, how conflicting values are resolved, who may create or change records, how evidence is retained and how approved data is distributed to consuming systems.

Supplier-domain definition and critical attributes
Source authority, survivorship and record relationships
Standardisation, duplicate detection and exception handling
Ownership, stewardship, create-change-disable workflow
Quality rules, monitoring and issue management
Migration, reconciliation and controlled syndication where scoped

Good fit

Multiple ERP, procurement or AP systems share supplier data.
Duplicate suppliers or fragmented identities affect operations.
Supplier onboarding or change approval is inconsistent.
An ERP, MDM, merger or source-to-pay programme needs clean master data.
Procurement, finance and risk need a common supplier view.

May not be the right fit

A one-time spreadsheet correction is sufficient.
The requirement is only supplier sourcing or commercial negotiation.
A software licence is required but data ownership and rules are already complete.
The need is a statutory audit, legal opinion or fraud investigation.
No accountable business owner can approve supplier-master decisions.

Supplier data model

Define the Supplier Record Around Real Business Decisions

The exact model depends on procurement, finance, risk, legal, operational and system requirements. A practical supplier master distinguishes authoritative attributes, reference values, relationships, evidence and restricted data instead of treating every field as equally important.

Legal identity

Approved name, entity identifiers, addresses, country or jurisdiction context, status and source evidence.

Purpose: know which real-world organisation the record represents.

Procurement classification

Supplier category, purchasing organisation, business-unit relationship, preferred or approved status and relevant reference codes.

Purpose: support sourcing, purchasing and spend views.

Payment-related attributes

Approved payment and remittance attributes, terms and validation metadata governed according to risk and access requirements.

Purpose: control sensitive changes and payment processing dependencies.

Tax and compliance references

Identifiers, declarations, certificates or statuses that the organisation is authorised and required to maintain for its operating context.

Purpose: make requirements explicit without assuming one rule applies everywhere.

Risk and due-diligence context

Risk classifications, review status, screening references and ownership metadata where the relevant process requires them.

Purpose: connect supplier data to accountable risk decisions.

Relationships and hierarchy

Parent-child relationships, legal entities, sites, remit-to relationships and group structures needed for procurement or reporting.

Purpose: aggregate and control suppliers beyond a flat code list.

Lineage and evidence

Source system, creation or change provenance, approval evidence, timestamps, owner and relevant stewardship notes.

Purpose: explain where a trusted value came from and who approved it.

Lifecycle status

Prospective, active, blocked, inactive, archived or other approved states with clear transition and reactivation rules.

Purpose: keep status decisions consistent across processes and systems.

Control framework

From Fragmented Supplier Records to a Governed Master

The work moves from evidence and definitions to controlled mastering and operations. Each stage produces a decision or artefact that can be reviewed, implemented and handed over.

Supplier Master Lifecycle

Illustrative sequence — adapted to the agreed assessment, design or implementation scope

Discover

Inventory supplier sources, processes, interfaces, owners, defects and risk points.

Output: source & issue map

Define

Agree supplier identity, critical attributes, reference values, relationships and lifecycle states.

Output: canonical definition

Standardise

Normalise names, identifiers, addresses, codes and other fields needed for reliable comparison.

Output: rule specification

Match

Identify duplicate and related supplier candidates using approved deterministic and similarity rules.

Output: candidate set

Master

Apply authority, survivorship, relationship and golden-record rules with visible exceptions.

Output: trusted-record logic

Approve

Define create, change, review, segregation and exception workflow with accountable sign-off.

Output: control workflow

Distribute

Map trusted supplier data to ERP, AP, procurement, analytics and other consuming systems.

Output: syndication design

Monitor

Measure completeness, validity, duplicates, stale records, exceptions and stewardship actions.

Output: KPI & operating model

Not every organisation needs a new MDM platform. The target pattern may use existing ERP controls, workflow, data-quality services, integration and stewardship capabilities when those can meet the approved requirements.

Service capabilities

Build the Governance, Data and Workflow Capabilities Needed to Operate Supplier Master Data

Capabilities are selected according to the supplier problem, risk, estate and target operating model. Assessment-only work can stop at findings and design; implementation work can continue into remediation, migration, integration and operational handover.

Profiling and current-state assessment

Measure source completeness, uniqueness, consistency, stale records, conflicting values and process-control gaps before proposing a target state.

Source inventoryQuality baselineRoot cause

Canonical model and standards

Define supplier entities, critical attributes, reference codes, status values, relationships and approved representations for shared use.

DictionaryReference dataCritical attributes

Matching, duplicates and survivorship

Design match logic, candidate scoring, steward review, merge or link rules, source precedence and conflict-resolution decisions.

Match rulesExceptionsGolden record

Onboarding and change workflow

Map supplier requests, evidence, validations, approvals, segregation, exception routing, status changes and hand-offs between teams.

CreateChangeDisable

Ownership and stewardship

Clarify executive accountability, domain ownership, procurement and finance roles, steward responsibilities, escalation and governance cadence.

RACIDecision rightsForums

Migration and syndication

Define source-to-target mappings, remediation requirements, reconciliation, cutover controls and downstream distribution specifications.

MappingReconciliationInterfaces

Quality rules and monitoring

Translate supplier expectations into measurable rules, thresholds, exceptions, ownership, dashboards and issue-management routines.

CompletenessValidityUniqueness

Risk and control design

Identify sensitive or higher-risk attributes, approval boundaries, access considerations, evidence needs and control ownership without overstating compliance.

AccessEvidenceSegregation

Operating handover and managed support

Document runbooks, monitoring, exception queues, rule maintenance, governance cadence and knowledge transfer for sustainable operation.

RunbookStewardshipContinuous improvement

Deliverables

Practical Outputs Your Teams Can Use After the Engagement

Deliverables are selected by scope. A focused assessment may emphasise evidence and priorities; an implementation scope can add detailed mappings, rules, workflows, remediation artefacts and operating documentation.

Category	Typical deliverable	Purpose	Client input
Current state	Supplier-source inventory and quality baseline	Show where records originate, how they differ and which issues materially affect the domain.	Representative extracts, schemas, issue logs and source owners.
Definition	Supplier data model, dictionary and critical-attribute register	Establish shared meaning, required fields, reference values, relationships and lifecycle states.	Business definitions, policies, system constraints and domain decisions.
Identity	Standardisation, matching and duplicate-rule specification	Make duplicate identification transparent, testable and appropriate to supplier risk.	Known duplicates, identifiers, labelled examples and acceptable error thresholds.
Mastering	Source-authority and survivorship matrix	Control which source wins, when values may be combined and when steward review is required.	System ownership, verification rules and accountable approvers.
Governance	Supplier ownership, stewardship and RACI model	Clarify who creates, changes, approves, reviews, escalates and monitors supplier data.	Organisation roles, current approvals and governance forums.
Workflow	Create-change-disable process and control design	Translate supplier policy into practical workflow, evidence and exception handling.	Current procedures, approval matrix, risk requirements and workflow platform context.
Remediation	Risk-ranked remediation and duplicate backlog	Sequence correction work based on business impact, certainty, effort and dependencies.	Business validation, change windows and acceptance criteria.
Migration	Source-to-target mapping and reconciliation specification	Support ERP, MDM or source-to-pay migration with controlled transformation and acceptance.	Target model, migration plan, interfaces and test environment.
Operations	KPI set, monitoring design, runbook and handover pack	Sustain quality, stewardship, exception handling and governance after go-live.	Operating-team roles, tooling, reporting and support expectations.

Have a Supplier Master Problem but Not Yet a Defined Work Package?

Share the affected systems, supplier population, duplicate or change issues, migration context and expected decision. We can help distinguish assessment, design, remediation and implementation needs.

Request a Scoped Proposal Review Common Use Cases

Use cases

Common Situations Where Supplier Master Data Needs Focused Intervention

The same master-data principles apply differently depending on whether the immediate driver is payment control, technology transformation, consolidation, analytics or ongoing supplier governance.

ERP consolidation or migration

Multiple supplier masters must be profiled, deduplicated, mapped and accepted before loading into a target environment.

Model: Programme workstream
Primary output: Trusted migration set
Dependency: Target model and business validation

Source-to-pay transformation

Supplier onboarding, approval and master-data hand-offs need one controlled design across sourcing, procurement, ERP and AP.

Model: Operating model + implementation
Primary output: Governed lifecycle workflow
Dependency: Process and platform owners

Duplicate supplier remediation

Regional or business-unit creation has produced repeated suppliers that weaken spend reporting or payment controls.

Model: Assessment + remediation
Primary output: Risk-ranked duplicate backlog
Dependency: Approved match and merge rules

Supplier change-control hardening

Sensitive supplier attributes are changed through inconsistent channels without standard evidence, approvals or traceable exceptions.

Model: Control-design project
Primary output: Change workflow and controls
Dependency: Finance, risk and system ownership

Merger or multi-business consolidation

Supplier identities and relationships must be reconciled across legal entities, regions, category structures and operating models.

Model: Domain consolidation
Primary output: Cross-system supplier map
Dependency: Hierarchy and authority decisions

Spend, risk and AI readiness

Analytics or AI initiatives need a stable supplier key, explainable relationships and trusted attributes before outputs can be relied on.

Model: Data readiness workstream
Primary output: Governed supplier dimension
Dependency: Defined analytical use cases

Engagement approach

Move from Evidence to Controlled Supplier-Master Operation

Delivery is phased around the decisions required. The engagement can stop after assessment and design or continue into remediation, implementation, migration and operational support.

Frame the business problem and control boundary

Confirm the processes affected, supplier population, source systems, business impact, decision owners, target outcomes and what is outside scope.

Profile data and map the supplier lifecycle

Review representative records, duplicates, missing fields, conflicting values, onboarding, change, disablement, interfaces, issues and current controls.

Design the target supplier master and governance model

Agree canonical attributes, reference data, source authority, matching, survivorship, ownership, stewardship, workflow and critical controls.

Validate rules against representative scenarios

Test duplicate logic, source precedence, exceptions, lifecycle decisions and approval paths with procurement, finance, data and technology stakeholders.

Implement, remediate or prepare migration

Where scoped, configure controls, develop rules, create remediation backlogs, support steward review, map target data and validate source-to-target outcomes.

Handover monitoring and continuous improvement

Document operating procedures, KPI ownership, exception handling, governance cadence, backlog management, change control and knowledge transfer.

Need the Supplier Master to Work Across Procurement, Finance and Technology?

Bring the data owners and process owners together around one operating model, one set of critical rules and explicit system responsibilities.

Discuss the Operating Model Review Control Considerations

Governance, privacy and control

Protect Higher-Risk Supplier Attributes Without Making Every Field a Bottleneck

Supplier data can include sensitive business information, personal contact data, payment-related details and due-diligence evidence. Controls should reflect actual risk, legal obligations, client policies and system capabilities rather than applying one blanket workflow to every attribute.

Change-risk controls

Differentiate routine profile maintenance from higher-risk changes and define appropriate evidence, review and approval requirements.

Segregation and decision rights

Clarify request, verification, approval, execution and review responsibilities to reduce ambiguous ownership.

Evidence and auditability

Define what evidence should be retained for key supplier decisions, where it belongs and who can review it.

Privacy-aware handling

Identify personal or restricted supplier-contact data, limit unnecessary collection and align access, retention and sharing with applicable requirements.

Quality and exception governance

Assign rule owners, thresholds, steward queues, accepted exceptions, remediation evidence and escalation paths.

Third-party and system boundaries

Document which checks are performed by internal teams, external providers, source systems or target platforms so responsibility is not assumed.

Important scope boundary: Supplier master data consulting can support governance, control design and evidence readiness, but it does not by itself provide legal advice, statutory audit, fraud certification, banking verification guarantees, sanctions-screening assurance or regulatory certification. Specialist activities can be coordinated only when explicitly scoped with appropriately qualified parties.

Technology and architecture

Use the Existing Estate Where It Can Meet the Supplier-Master Requirements

Supplier master data may span multiple platforms. The target design should establish responsibility for capture, validation, mastering, workflow, integration, monitoring and consumption before deciding whether new software is necessary.

Source & onboardingSourcing, portals, forms, ERP, local systems and approved external inputs.

Validation & standardisationMandatory fields, formats, identifiers, reference values and risk-based checks.

MasteringIdentity match, golden-record rules, relationships, survivorship and exceptions.

Workflow & stewardshipCreate, change, approve, review, exception and lifecycle decisions.

ConsumptionProcurement, AP, finance, risk, data platforms, reporting and analytics.

Cross-cutting capabilities: metadata and lineage · data quality · access and security · policy and standards · monitoring and issue management · testing and reconciliation

Commercial model

Supplier Master Data Pricing Is Confirmed After Scope and Evidence Review

DataConsultant does not publish a fixed fee for this exact service. Public market prices for narrow vendor diagnostics, software support or freelance tasks are not sufficiently comparable to a governed enterprise supplier-master engagement, so no numeric market range is presented here.

Why quote-based? The same supplier-master label can mean a five-system assessment, a duplicate remediation workstream, a workflow redesign, an ERP migration or an ongoing stewardship service. Commercial terms need to match the actual decision, data volume and delivery responsibility.

Assess

Supplier Master Diagnostic

Evidence-led review of supplier sources, quality, duplicates, ownership, workflows, risk points and practical next steps.

Commercial treatmentRequest a Quote

Defined source and stakeholder scope
Quality and duplicate baseline
Control-gap findings
Prioritised remediation roadmap

Request Diagnostic Pricing

Design

Target Supplier Master & Controls

Design the canonical supplier model, decision rights, matching, survivorship, workflow, quality controls and operating model.

Commercial treatmentRequest a Quote

Supplier data model and standards
RACI and stewardship model
Matching and survivorship rules
Create-change control design

Request Design Pricing

Implement

Remediation or Migration Workstream

Implement approved rules, steward remediation, source-to-target mapping, reconciliation, controls and deployment support.

Commercial treatmentRequest a Quote

Rule implementation and testing
Duplicate or quality remediation
Migration and reconciliation support
Operational handover

Request Implementation Pricing

Operate

Managed Supplier Data Support

Ongoing stewardship, monitoring, exception triage, rule maintenance, reporting and continuous improvement under agreed responsibilities.

Commercial treatmentRequest a Quote

Monitoring and exception queues
Stewardship and issue support
Rule tuning and backlog management
Governance reporting and handover

Request Managed Support Pricing

Supplier populationRecord volume, active suppliers, sites, relationships and change frequency.

Source complexityERP, sourcing, AP, local systems, interfaces, data models and jurisdictions.

Data conditionCompleteness, duplicates, conflicting identifiers, stale data and remediation depth.

Control scopeOwnership, sensitive changes, evidence, approvals, exceptions and auditability.

Matching difficultyIdentifier availability, name/address variation, hierarchy and false-merge risk.

Technology scopeAdvisory only versus workflow, MDM, data-quality, integration or platform implementation.

Migration & rolloutTarget systems, mapping, reconciliation, testing, cutover waves and business units.

Operating supportStewardship workload, monitoring, reporting, documentation, training and managed coverage.

Want Pricing That Reflects the Supplier Population and Delivery Responsibility?

Send the source count, approximate supplier volume, priority issues, target platforms, required deliverables and whether you need assessment, design, remediation, migration or ongoing support.

Request a Supplier Master Quote Review FAQs

Why DataConsultant

Keep Supplier Master Decisions Connected to Governance, Architecture and Daily Operations

Supplier data problems sit between business processes and technology. A useful engagement therefore needs clear decision rights, defensible data rules, practical implementation detail and an operating handover rather than a generic cleansing recommendation.

Business-owned decisions

Procurement, finance, risk, data and technology responsibilities are made explicit rather than hidden inside tooling.

Evidence before remediation

Profiling, rules and exceptions are documented so correction priorities can be reviewed and accepted.

Platform-aware, requirements-led

Use existing ERP, MDM, workflow and data-quality capabilities where they can meet the approved control needs.

Operate after go-live

Monitoring, stewardship, issue handling, rule maintenance and knowledge transfer are considered from the design stage.

Frequently asked questions

Supplier Master Data Consulting FAQs

Answers to common enterprise buyer questions about scope, deliverables, duplicate matching, controls, platforms, migration, duration, pricing and ongoing support.

What is supplier master data?

Supplier master data is the governed set of relatively stable information used to identify, classify, onboard, transact with and monitor suppliers across procurement, finance, risk and enterprise systems. It can include legal identity, addresses, identifiers, tax references, payment-related attributes, purchasing classifications, status, relationships, ownership and source lineage.

How is supplier master data different from vendor master data?

The terms are often used interchangeably, but organisations may define them differently. Supplier commonly describes the business relationship used by sourcing and procurement, while vendor may be the term used in an ERP or accounts-payable system. The engagement establishes the organisation’s approved definition, identifiers, relationships and system mappings rather than assuming the terms are identical.

When should an organisation improve its supplier master data?

Common triggers include duplicate supplier records, inconsistent legal names or identifiers, repeated onboarding effort, uncontrolled bank or payment-detail changes, fragmented supplier status, ERP or source-to-pay transformation, weak spend visibility, audit findings, merger integration, supplier-risk initiatives or recurring manual reconciliation.

What is included in a Supplier Master Data engagement?

Scope can include source inventory, supplier-domain definition, data profiling, critical-attribute design, standardisation rules, matching and duplicate analysis, source-authority and survivorship decisions, ownership and stewardship, create-change-disable workflows, quality controls, remediation planning, migration mapping, syndication design, monitoring and operating handover. Final scope is agreed during discovery.

What deliverables can we expect?

Typical outputs can include a supplier data model and dictionary, source and lineage map, data-quality baseline, duplicate findings, matching rules, survivorship matrix, ownership and RACI model, workflow and control design, remediation backlog, migration or distribution specifications, KPI definitions, operating procedures and a prioritised implementation roadmap.

How are duplicate suppliers identified safely?

Duplicate analysis combines standardisation, deterministic identifiers, domain-specific similarity signals, risk thresholds and business review. High-confidence candidates may be handled differently from ambiguous records. Merge, link, suppress or retain decisions should follow approved survivorship rules, evidence requirements and rollback or exception procedures where technically applicable.

Can the service address supplier bank and payment-detail changes?

Yes, where included in scope. The work can define which payment-related attributes are controlled, who may request and approve changes, what validation evidence is required, how segregation of duties is applied, how exceptions are escalated and what audit trail should be retained. It does not replace banking, fraud-investigation, legal or statutory assurance services.

Which systems and platforms can be included?

The engagement can cover ERP, procure-to-pay, sourcing, accounts-payable, supplier-portal, master-data, data-quality, workflow, integration, data-platform, catalogue and reporting environments. Recommendations remain requirements-led and vendor-neutral unless a specific platform implementation or selection is explicitly in scope.

Can Supplier Master Data support ERP, MDM or source-to-pay migration?

Yes. Supplier master work can profile source data, define target attributes and code mappings, identify duplicates, establish migration acceptance rules, create remediation backlogs, define source-to-target reconciliation and support cutover readiness. Migration execution, platform configuration and production support are included only when separately scoped.

What information does DataConsultant need from us?

Useful inputs include representative supplier extracts, data dictionaries, source-system inventory, onboarding and change procedures, approval matrices, known issue logs, duplicate reports, reference data, integration maps, audit or risk findings, data-retention requirements and access to procurement, finance, data, risk and technology stakeholders.

How long does a Supplier Master Data engagement take?

A reliable timeline is confirmed after scoping. Duration depends on the number of supplier records and source systems, data quality, countries and business units, matching complexity, stakeholder availability, workflow design, remediation volume, platform configuration, migration scope, review cycles and required deliverables.

How is Supplier Master Data pricing calculated?

DataConsultant does not publish a fixed fee for this exact service. Pricing is confirmed after scoping because effort depends on supplier volume, source count, data sensitivity, profiling depth, duplicate complexity, workflow and control requirements, target platforms, remediation or migration scope, stakeholder participation, documentation and any ongoing operational support.

Can DataConsultant work with our procurement, finance and technology teams?

Yes. Supplier master data normally requires coordinated decisions across procurement, accounts payable, finance, data governance, enterprise applications, risk, compliance, security and business units. Roles, evidence access, decision rights, dependencies and sign-off points are clarified during mobilisation.

Can ongoing supplier-master monitoring or stewardship be supported?

Yes, where required. Ongoing support can be scoped for quality monitoring, exception triage, duplicate review, stewardship workflows, rule tuning, reporting, backlog management and knowledge transfer. Service levels, staffing, support windows and commercial terms are defined in the agreed proposal rather than assumed on this page.

Scope your requirement

Discuss Your Supplier Master Data Requirement

Share enough context for the team to understand the supplier problem, affected systems, required decision and likely delivery model. Avoid sending highly sensitive data in the first enquiry.

Business problemDuplicates, onboarding, payment-change risk, reporting, migration, merger or another supplier-data issue.
Supplier and system scopeApproximate record population, ERP or source-to-pay landscape, business units and countries.
Required outputsAssessment, rules, workflow, remediation, migration, implementation, operating model or managed support.
Constraints and target decisionsRisk, audit, privacy, architecture, programme milestones, stakeholder availability and approval needs.

Request a scoped discussion

DataConsultant can review the likely scope, evidence required, stakeholder involvement, responsibility boundaries and appropriate next step.