Before an FDA Inspection: What Does Your FSVP File Really Look Like?

There is a difference between having an FSVP file and being able to confidently hand that file to someone who has never seen it before.

That difference matters.

Because when an FDA inspection, inquiry, or records request happens, the question isn't simply:

“Do you have an FSVP?”

The harder question is:

“Can your records demonstrate what you did, why you did it, and whether your current FSVP still reflects the foods and suppliers you actually use?”

For many importers, that is when uncertainty begins.

They open the folder.

They start searching.

They find documents.

Then they notice something.

A certificate is old.

A supplier isn't on the current list.

A product was added last year.

An audit report is there, but nobody documented how it supported the verification decision.

A corrective action was handled by email.

The employee who knew the history left months ago.

Suddenly, the question becomes:

“What does our FSVP file really look like?”

The importer who thought the file was ready

The company had an FSVP folder.

It had been maintained for years.

There were plenty of documents inside.

The team wasn't worried about an FDA inspection.

They believed they could produce what was needed.

Then management decided to conduct a readiness review.

The first request was simple:

“Show us the current FSVP for your active imported foods.”

The team opened the folder.

It looked substantial.

Then someone started comparing the records against actual imports.

That was the turning point.

The folder contained history, not necessarily the current program

The FSVP file had information from several years.

Some of it was still relevant.

Some of it wasn't.

There were old:

• Supplier records
• Certifications
• Product specifications
• Audit reports
• Questionnaires
• Contact information
• Verification records

The problem wasn't that the documents existed.

The problem was determining:

Which information represents the current state of the business?

That distinction can become critical during an inspection.

An FDA inspection isn't the time to discover your filing system

Imagine receiving a request for FSVP records.

Then the internal discussion begins:

“I think Sarah has that.”

“Maybe it's in the supplier folder.”

“Check the old SharePoint.”

“It might be in purchasing.”

“The supplier sent it by email.”

“I know we reviewed it, but I don't remember where the record is.”

That creates unnecessary pressure.

A well-managed compliance system should make record retrieval deliberate rather than dependent on memory.

What should your file tell someone?

At a basic level, your FSVP records should allow a reviewer to understand the applicable FSVP activities and decisions.

That includes the relationship between:

The importer

The foreign supplier

The food

The hazards

The supplier evaluation

The verification activities

Corrective actions, where applicable

Reevaluation

Recordkeeping

The exact records needed depend on the circumstances and applicable FSVP requirements.

But the overall story should make sense.

Start with the importer

Before reviewing the supplier file, confirm the basic question:

Who is the FSVP importer?

This can become complicated when an importing operation involves:

• A U.S. owner or consignee
• Foreign suppliers
• Distributors
• Customs brokers
• Freight forwarders
• Amazon or other marketplaces
• FSVP Agents

The FSVP importer has a specific regulatory role.

An outside reviewer should be able to understand who that entity is and how the responsibility is being managed.

Then look at the actual imported foods

Don't begin by looking only at the FSVP folder.

Begin with reality.

Pull recent import records.

Ask:

What foods are we actually importing?

Then compare those foods with the FSVP.

This simple exercise can uncover one of the most common problems:

The business changed, but the FSVP didn't.

New products can create old problems

Suppose the importer had an FSVP for three products.

Then the company added five more.

The new products were commercially successful.

Nobody thought of them as a compliance event.

But if they are imported foods subject to FSVP, they need to be appropriately addressed within the importer's compliance process.

A readiness review should identify whether they are.

The supplier list should also match reality

Now compare:

Current suppliers

with:

Suppliers represented in the FSVP.

Look for:

• New suppliers
• Inactive suppliers
• Changed supplier names
• Different manufacturing facilities
• Contract manufacturers
• Distributors versus actual foreign suppliers

This can reveal whether the FSVP still reflects the actual supply chain.

The supplier name isn't the whole story

An importer may say:

“We've worked with this company for years.”

But who is actually manufacturing the food?

That question matters.

A supplier may use:

Multiple facilities

Contract manufacturers

Different production locations

Different entities within a corporate group

The FSVP records should accurately represent the applicable supplier relationship.

Then look at the hazard evaluation

One of the most important questions is:

How did the importer evaluate the food and applicable hazards?

The answer should be supported by appropriate records.

An importer may have a supplier HACCP plan or other food safety documentation.

That's useful information.

But the existence of a supplier document doesn't automatically explain the importer's FSVP determination.

Don't confuse the supplier's documents with the importer's responsibility

This is an important distinction.

A foreign supplier may provide:

HACCP plan

Audit

Certificate

Testing

Specifications

Food safety records

These documents can support the importer's evaluation.

But the importer still needs to understand its own FSVP obligations and maintain the applicable records supporting its decisions.

Then examine supplier evaluation

Ask:

“Why did we determine this supplier was acceptable for the food being imported?”

A good file should make the basis of the decision understandable.

That doesn't necessarily mean one particular form must exist for every situation.

It means the records should support the applicable determination.

Then look at verification

This is where an inspection-readiness review becomes particularly valuable.

Ask:

“What verification activities were performed?”

Then:

“When?”

“By whom?”

“What did they cover?”

“What did they find?”

“What conclusion did the importer reach?”

The answer shouldn't simply be:

“There's an audit in the folder.”

The reviewer needs to understand how the evidence relates to the FSVP.

A certification is evidence, not a magic shield

A supplier certification may be valuable.

But the importer shouldn't assume:

“They're certified, therefore no further thinking is required.”

The importer needs to understand the applicable FSVP framework and determine what information and verification activities are appropriate for the specific circumstances.

That distinction can become important during an inspection.

The date on the document matters

Consider a supplier certification dated:

June 2023

Current date:

August 2026

The certificate isn't necessarily worthless.

But an inspector—or internal reviewer—could reasonably ask:

“Why is this the evidence you're relying on today?”

The importer should be able to explain the current status and whether additional or updated information is appropriate.

Expired documents aren't always the biggest problem

The deeper problem can be:

Nobody knows whether the document is current.

That's a system problem.

A strong process should identify:

Expiration dates

Review dates

Renewal needs

Document owners

Follow-up responsibilities

Without that, the importer may discover expired records only when someone asks for them.

Then look for supplier changes

A readiness review should ask:

“What has changed since the last FSVP review?”

Look for:

• Facility changes
• Formulation changes
• Process changes
• Ownership changes
• Certification changes
• Significant audit findings
• Regulatory events
• New information about the supplier or food

FDA's FSVP requirements include reevaluation in circumstances involving applicable new information or significant changes that could affect the adequacy of the FSVP.

The important issue isn't simply whether something changed.

It's whether the importer appropriately evaluated what the change meant.

What if the team says, “We handled it”?

That's good.

Now ask:

“Where is the record?”

Suppose a supplier changed its manufacturing facility.

The compliance manager reviewed the change and decided the existing supplier verification remained appropriate.

Excellent.

But if that decision exists only in an email conversation or someone's memory, the FSVP record may not clearly communicate what happened.

Documentation creates the trail.

Corrective actions deserve attention

Suppose a supplier audit identified a finding.

The supplier responded.

The importer accepted the corrective action.

What happened next?

The readiness review should consider whether the issue was appropriately addressed and whether it affected the supplier evaluation or verification process.

A corrective action shouldn't simply disappear into an email folder.

The inspector doesn't know your intentions

This is a crucial mindset shift.

Your employees may know:

“We took care of it.”

But an external reviewer sees the records.

They can't rely on:

Good intentions

Institutional memory

Verbal explanations

“We've always done it this way.”

They need to understand what the records demonstrate.

That's why documentation matters.

The file should tell a coherent story

Imagine an inspector opens a supplier record.

They should be able to follow the logic:

Who is the supplier?

↓

What food is being imported?

↓

What hazards are relevant?

↓

How was the supplier evaluated?

↓

What verification activities were performed?

↓

Were findings identified?

↓

How were issues addressed?

↓

Was reevaluation needed?

↓

What is the current status?

That's a much stronger file than a folder containing unrelated PDFs.

A pile of documents is not the same as a compliance system

This is one of the biggest misconceptions.

An importer may have:

100 documents

and still have a weak FSVP system.

Another importer may have:

30 well-organized records

and have a much clearer program.

The number of documents isn't the objective.

Relevance, completeness, currency, traceability, and appropriate documentation matter.

The file should be understandable to someone new

Here's a powerful test.

Give the FSVP file to someone who wasn't involved in creating it.

Ask:

“Can you explain how this importer manages FSVP?”

If the answer is yes, that's encouraging.

If the person responds:

“I need to ask the compliance manager.”

you've found a dependency.

What happens when the compliance manager leaves?

This is not hypothetical.

People change jobs.

They retire.

They transfer.

They take leave.

Companies reorganize.

If one employee is the only person who understands:

Why suppliers were approved

Which documents are current

Why certain verification activities were selected

What happened during previous reviews

then the organization has a knowledge-management vulnerability.

Inspection readiness is also business continuity

A well-maintained FSVP doesn't only help during regulatory interactions.

It helps when:

Employees change

Suppliers change

Products change

Customers change

The business grows

New compliance staff join

The same records become institutional knowledge.

What if you find gaps before an inspection?

That's exactly when you want to find them.

You can:

Request updated documents

Review supplier information

Update product coverage

Evaluate changes

Document decisions

Address verification gaps

Improve recordkeeping

Train employees

Implement monitoring

You have time.

What if you discover the gaps during an inspection?

Now the pressure is different.

The organization is responding to an external request.

Employees are searching.

Management is involved.

The supplier may need to respond quickly.

The issue can become much more stressful than it needed to be.

That's why readiness matters.

A readiness assessment doesn't mean an inspection is coming

Some importers hesitate to conduct a gap assessment because they think:

“If we review ourselves, it means we're expecting an inspection.”

Not at all.

An internal review is simply preventive management.

You don't need to wait for a warning sign.

The “inspection tomorrow” test

Try this exercise.

Imagine you received a request tomorrow for your FSVP records.

Now ask:

Can we identify the FSVP importer?

Can we identify all current foreign suppliers?

Can we identify the foods being imported?

Can we retrieve the applicable FSVP records?

Can we explain the supplier evaluations?

Can we show applicable verification activities?

Can we demonstrate how significant changes were handled?

Can we locate corrective-action records?

Can we explain the current status of each supplier?

Can someone other than one employee navigate the files?

If several answers are uncertain, that's useful information.

The biggest weakness may be organization

Sometimes the underlying compliance work is actually strong.

The problem is that records are scattered.

For example:

Purchasing has supplier documents.

Quality has audit reports.

Regulatory has FSVP evaluations.

Operations has shipment information.

Accounting has supplier records.

No one has the complete picture.

An inspection request can expose this immediately.

The solution isn't always “more documents”

This is important.

If the file is disorganized, adding another form may make things worse.

The better solution may be:

Clear ownership

Centralized records

Document control

Supplier mapping

Product mapping

Review schedules

Defined workflows

A strong system reduces unnecessary complexity.

The importer should know what is current

One of the easiest inspection-readiness improvements is current-status control.

For each supplier, you should be able to determine:

Current supplier information

Current products

Current verification status

Current documents

Open actions

Next review

This makes the file much easier to manage.

The importer should also know what is not current

Transparency is better than false confidence.

If a document is pending renewal, the system should show that.

If a supplier review is overdue, it should be visible.

If an issue is open, it should be tracked.

A managed open issue is better than an invisible one.

Don't hide the gaps from yourself

Some companies avoid internal assessments because they don't want to discover problems.

But the problem already exists if the gap exists.

The assessment didn't create it.

It simply revealed it.

And once visible, it can be managed.

What does an inspection-ready FSVP feel like?

It feels different.

Instead of:

“Where is that document?”

you hear:

“It's in the supplier record.”

Instead of:

“I think we reviewed that.”

you can say:

“Here is the review record.”

Instead of:

“The supplier changed something last year.”

you can say:

“Here is the change, our evaluation, and the resulting action.”

Instead of:

“I believe this product is covered.”

you can say:

“Here is where the product is addressed.”

That's confidence.

The goal isn't to predict every FDA question

You can't.

The goal is to make your program understandable enough that you can respond to reasonable requests without reconstructing your compliance history under pressure.

That's a much more realistic objective.

The best time to inspect your own FSVP is before someone else does

A readiness assessment gives you the opportunity to step back.

Look at the entire system.

Test it against current imports.

Identify weaknesses.

Prioritize corrections.

Then maintain it.

That is preventive compliance.

Your FSVP file should represent your business today

Not:

The business you had in 2022.

Not:

The supplier list from 2023.

Not:

The product lineup from 2024.

Not:

The documents someone happened to save in 2025.

Your compliance records should be managed so they accurately support your current importing operation and applicable FSVP responsibilities.

A simple inspection-readiness checklist

Before an FDA inspection or records request, consider reviewing:

Importer

• Correct FSVP importer identified
• Responsibility clearly understood
• Current contact information

Foreign suppliers

• Current supplier list
• Current facility information
• Supplier changes identified
• Supplier evaluations documented

Foods

• Current product list
• Current product coverage
• Relevant food safety information
• Changes evaluated

Verification

• Applicable verification activities identified
• Current supporting records
• Findings reviewed
• Corrective actions documented where applicable

Reevaluation

• Significant changes tracked
• New information evaluated
• Reevaluations documented when required

Records

• Current records identifiable
• Historical records controlled
• Documents easy to retrieve
• Ownership defined

Management

• Open actions tracked
• Review dates established
• Responsibilities assigned
• Ongoing maintenance process in place

Don't wait until the inspector asks

The most uncomfortable moment is often not:

“We have a gap.”

It's:

“We don't know whether we have a gap.”

That is why proactive review is so valuable.