Getting Full Material Disclosure (FMD) data from suppliers should not depend on sending the same follow-up email five times.

For many manufacturers, the problem is not knowing that FMD data is required. The problem is getting complete, usable and traceable information from suppliers before compliance deadlines arrive.

Supplier responses may be incomplete. Different suppliers may use different formats. Some may not understand what level of material information is required. Others may provide test reports, PDFs or other supporting documents instead of a structured material declaration.

The result is familiar:

Request → Follow up → Follow up again → Receive incomplete data → Clarify → Follow up again

A better approach is to build FMD collection into the sourcing and supplier management process from the beginning.

The goal is not simply to collect more declarations.

It is to collect usable FMD data, validate it, connect it to the right products and keep it current.

Why Is FMD Data So Difficult to Collect From Suppliers?

The biggest problem is usually a reactive workflow.

FMD requirements are often introduced after a component has already been sourced or when a compliance review is already underway. By then, the compliance team has limited leverage over the supplier.

The supplier may also have its own challenges:

• It may not have an existing FMD process.
• The right compliance contact may not be known.
• Material information may exist in different formats.
• The supplier may not understand the required disclosure level.
• Supporting information may be held in test reports or technical documents.
• Different customers may request different declaration formats.
• Internal supplier teams may need to gather information from their own upstream suppliers.

This means a supplier may be willing to respond but still unable to provide the information in the format or level of detail required.

The solution is to make the request clear, give suppliers a practical way to respond and establish a process for handling incomplete information.

For a broader explanation of what FMD contains and how material data fits into product compliance, see the complete guide to Full Material Disclosure.

Why to Set FMD Requirements Before You Need the Data

One of the simplest ways to reduce supplier chasing is to introduce FMD requirements before the supplier becomes part of the compliance backlog.

FMD requirements can be incorporated into:

• RFQs
• Supplier onboarding
• Sourcing templates
• Purchase requirements
• Supplier quality agreements
• Product change processes
• Compliance specifications

The requirement should make clear:

• What information is required
• Which format is accepted
• Which standards apply
• When the information is due
• Which products or components are in scope
• What supporting evidence may be required
• How updates will be handled

The earlier the requirement is established, the less likely the compliance team is to start from scratch after the component has already entered production.

Make the requirement specific

"Provide material information" is too vague.

A supplier should understand what is expected from them.

For example, the request may specify the applicable FMD format, required material and substance information, relevant regulatory lists and the deadline for submission.

The objective is to remove ambiguity before the request reaches the supplier.

What inforamtion Should We Give Suppliers a Clear Way to Respond

Supplier knowledge of FMD can vary significantly.

Some suppliers may already have structured material declarations. Others may have information in spreadsheets, PDFs, laboratory reports, technical drawings or internal material records.

The response process should therefore be designed around the information the supplier can reasonably provide.

Useful support can include:

• FMD templates
• Submission instructions
• Examples of acceptable data
• Supplier onboarding guides
• Validation checks
• Upload forms
• Supplier portals
• Training material
• Clear escalation contacts

The easier the process is to understand, the less time the compliance team spends explaining the same requirement repeatedly.

A supplier should be able to answer three basic questions:

What do you need from me?

How should I provide it?

When do you need it?

Why to Accept Different Source Documents, Then Validate the Data

Not every supplier will have a ready-made FMD in the exact format you want.

Material information may exist in:

• Existing material declarations
• Test reports
• Laboratory reports
• Safety Data Sheets
• Technical documentation
• Material specifications
• Drawings
• Supplier databases
• Structured declaration files

The important point is to distinguish between source evidence and validated FMD data.

A document may contain useful information without being a complete material declaration.

For example, a test report may provide evidence about a particular substance or material characteristic, but it may not provide a complete product composition.

The workflow should therefore be:

Supplier information → Extract → Validate → Structure → Connect to component/product

This avoids treating every supplier document as automatically complete.

Why Should We Segment Suppliers Instead of Treating Everyone the Same

Not every supplier presents the same level of compliance risk or data-collection difficulty.

A practical supplier segmentation approach can consider:

• Number of components supplied
• Product criticality
• Material complexity
• Regulatory exposure
• Customer requirements
• Historical response rate
• Data quality
• Strategic importance
• Risk associated with missing information

For example:

This prevents the compliance team from spending the same amount of time on every supplier.

Start with the suppliers and components that create the greatest compliance exposure.

How to Make Supplier Requests Specific

A generic request such as:

"Please provide your FMD."

creates unnecessary back-and-forth.

A stronger request tells the supplier exactly what is required.

For example:

Component: [Component identifier]

Product: [Product identifier]

Required information: Material and substance composition

Required standard: [Applicable standard]

Regulatory scope: [Applicable requirements]

Submission format: [Accepted format]

Supporting evidence: [Required documents]

Due date: [Date]

Contact: [Compliance contact]

The objective is to make the request actionable rather than open-ended.

How to Track the Request as a Workflow

Sending the request is only the beginning.

A useful FMD collection workflow should show where every supplier request stands.

A simple status model could be:

Not Requested

↓

Request Sent

↓

Supplier Acknowledged

↓

Data Received

↓

Validation in Progress

↓

Gaps Identified

↓

Supplier Clarification

↓

Validated

↓

Accepted

This gives the compliance team visibility into the actual state of the campaign.

It also makes follow-up more targeted.

Instead of asking:

"Have you sent the FMD?"

the team can identify exactly what is missing.

How to Follow Up Based on the Missing Data

Not every incomplete response needs the same follow-up.

Consider the difference between:

Missing declaration

and

Declaration received but missing substance information

and

Material data received but component mapping is unclear

and

Supporting evidence is missing

Each requires a different action.

This is where a structured workflow is more effective than repeated generic reminders.

The follow-up should identify:

1. What was received
2. What is missing
3. Why it is required
4. What the supplier needs to provide
5. When the information is required

This reduces unnecessary communication and gives the supplier a clear path to closure.

How to Validate FMD Data Before Marking It Complete

Receiving a supplier file does not mean the FMD requirement is complete.

The data should be checked before it is accepted.

Validation can include:

• Required fields completed
• Correct component identified
• Correct supplier identified
• Material information present
• Substance information present where required
• Substance identifiers correctly formatted
• Concentration or weight information provided where required
• Applicable declaration format followed
• Supporting evidence available
• Data consistent with the product or component record

The objective is to prevent incomplete supplier data from becoming a compliance problem later.

Why should We Keep Supporting Evidence With the FMD

FMD should not exist as an isolated spreadsheet row.

Where supporting evidence exists, it should be associated with the relevant declaration or material record.

Depending on the situation, this may include:

• Supplier declarations
• Test reports
• Laboratory reports
• SDS documents
• Technical specifications
• Material certificates
• Supporting correspondence

This creates a stronger evidence trail.

It also makes future reviews easier because the team does not have to reconstruct why a particular material or substance assessment was accepted.

Why Should We Not Treat FMD as a One-Time Collection Exercise

Products change.

Suppliers change.

Materials change.

Regulatory requirements change.

A declaration collected two years ago may therefore not represent the current product.

FMD collection should include a defined refresh process.

For example:

Initial collection → Validation → Product use → Change monitoring → Refresh → Revalidation

The appropriate refresh frequency depends on the product, supplier, material risk and applicable requirements.

The important point is to define the trigger for updating the data rather than waiting for a compliance deadline.

How to Connect Supplier Data to the Product

Supplier data becomes much more useful when it is connected to the product structure.

The relationship should ideally be traceable:

Supplier

↓

Component

↓

Material

↓

Substance

↓

Product

This allows compliance teams to understand which products may be affected when a supplier updates a material declaration.

It also reduces the need to request the same information again when a material is used across multiple products.

That is one of the biggest differences between a reusable FMD data foundation and a collection of supplier documents.

How to Use FMD Data Across Compliance Requirements

The same underlying material information may support assessments across multiple requirements.

Depending on the product and market, this may include:

• RoHS
• REACH
• PFAS requirements
• California Proposition 65
• TSCA
• POPs
• Customer-specific material restrictions

FMD does not replace the individual compliance assessment for each requirement.

Instead, it provides underlying product material and substance information that can be reused across those assessments.

This is why the quality of the original supplier data matters.

Poor supplier data creates repeated work across multiple compliance processes.

Reliable supplier data creates a reusable compliance asset.

How to Build Supplier Engagement Into the Compliance Process

Supplier engagement should not be limited to sending requests when a deadline is approaching.

A stronger process includes:

Onboarding → Request → Support → Follow-up → Validation → Acceptance → Refresh

This makes supplier engagement part of the compliance operating model.

For organizations building a more structured supplier engagement process, see how to build a supplier engagement program for FMD.

The objective is not simply to increase the number of supplier responses.

It is to improve the quality, completeness and usability of the information received.

What Should You Do When a Supplier Does Not Respond?

Supplier non-response is common, but repeated manual chasing should not be the entire strategy.

A defined escalation process can include:

First request

Send the requirement with clear instructions and deadline.

Reminder

Follow up with the outstanding requirement clearly identified.

Second escalation

Contact the appropriate supplier or account owner.

Procurement escalation

Use the relevant commercial or procurement relationship where appropriate.

Risk prioritization

Identify whether the missing data affects a high-risk component or product.

Exception management

Record the unresolved gap and determine the appropriate compliance action.

This creates accountability without turning the compliance team into a permanent follow-up function.

What If the Supplier Says the Information Is Confidential?

Suppliers may be reluctant to disclose certain material information because of proprietary concerns.

The response should be based on the actual information requirement and applicable disclosure framework.

Instead of simply accepting an incomplete declaration, document:

• What information was withheld
• Why it was withheld
• Which component or material is affected
• What supporting evidence is available
• Whether the available information is sufficient for the required assessment
• Whether additional testing or documentation is needed

Confidentiality should therefore become a documented exception to manage, not an automatic reason to mark the product compliant.

When Should FMD Collection Be Automated?

Manual collection becomes increasingly difficult when the organization manages:

• Large supplier networks
• Thousands of components
• Multiple product families
• Multiple regulatory requirements
• Repeated supplier requests
• Frequent material changes
• Large volumes of declarations

At that point, automation can help manage repetitive workflow steps such as:

• Supplier invitations
• Reminder emails
• Escalations
• Submission tracking
• Document collection
• Data extraction
• Validation checks
• Missing-data identification
• Status reporting
• Change alerts

The compliance team can then focus on exceptions and decisions rather than manually tracking every supplier.

For a closer look at the technology side, see FMD software for supplier compliance.

A Practical FMD Supplier Collection Workflow

A scalable process can be summarized as:

1. Identify

Determine which products, components and suppliers require FMD.

2. Define

Specify the required disclosure level, format, standards and regulatory scope.

3. Request

Send a structured supplier request with clear instructions and deadlines.

4. Support

Give suppliers templates, guidance and a practical submission method.

5. Track

Monitor requests, responses, incomplete submissions and escalations.

6. Validate

Check the submitted data and supporting evidence.

7. Resolve

Identify gaps and request only the information that is missing.

8. Connect

Link validated information to the relevant component and product.

9. Assess

Use the material data for applicable compliance assessments.

10. Refresh

Update the information when supplier, product, material or regulatory changes require it.

This creates a repeatable process instead of a cycle of one-off supplier requests.

FMD Supplier Data Collection Checklist

Use this checklist when reviewing your supplier FMD process:

☐ Supplier contacts are identified and maintained

☐ FMD requirements are defined before supplier outreach

☐ Suppliers understand exactly what information is required

☐ Multiple acceptable source formats can be handled

☐ Supplier submissions can be tracked by status

☐ Missing information can be identified

☐ Material and substance information is validated

☐ Component, material, and substance relationships are maintained

☐ Supporting evidence is retained

☐ Supplier follow-ups are based on missing information

☐ FMD data is connected to the relevant products

☐ Material information can be reused across compliance requirements

☐ Data can be reviewed and updated when supplier information changes

The Goal Is Not More Supplier Emails

The goal is better supplier data.

A mature FMD process moves from:

Reactive requests

to

Structured supplier requirements

then to

Validated material data

and finally to

Reusable product compliance information.

When FMD is embedded into sourcing, supplier onboarding and product compliance workflows, the compliance team spends less time asking suppliers for information and more time using that information to manage risk.

That is the difference between chasing FMD data and managing FMD data.

How Regilient Can Support FMD Collection

Regilient supports the supplier side of the FMD workflow by bringing collection, supplier engagement, validation and product compliance data into a connected process.

The objective is to help teams manage:

• Supplier requests
• Supplier responses
• Supporting documents
• FMD information
• Validation
• Material and substance data
• Compliance assessments
• Evidence
• Ongoing updates

Learn more about managing Full Material Disclosure data across the product compliance process.