Webinar

MDSAP in Practice: What It Really Takes to Stay Audit-Ready Across Global Markets

Kartika Puri

November 18, 2026

Marc Goedecke, Product Manager for MDSAP at DQS, and Apurva Kushare, PhD, Regulatory Affairs Specialist Lead at RegDesk, joined us for a practical discussion of MDSAP audit readiness, global registration management, and the work required to maintain regulatory compliance across markets.

Watch the webinar replay

MDSAP Is About How Processes Work Together

MDSAP audit readiness involves more than having documented procedures. Auditors examine how processes connect, how information moves between them, and whether organizations can demonstrate effective oversight.

As Marc Goedecke explained:

“Many significant MDSAP findings arise where processes exist, but are not effectively connected to one another.”

This is an important distinction for regulatory and quality leaders. A complaint investigation, for example, may have implications for risk management, corrective and preventive action (CAPA), and post-market surveillance. If those processes operate independently, important information and follow-up actions can be missed.

Marc emphasized that MDSAP auditors follow audit trails and place particular attention on investigations and risk assessment activities. Organizations need to demonstrate traceability and objective evidence across process interfaces, not simply show that individual procedures are in place.

MDSAP in Practice: What It Really Takes to Stay Audit-Ready Across Global Markets

MDSAP Does Not Replace Regulatory Intelligence

One of the most important points from Marc’s presentation was the difference between the MDSAP audit approach and the broader regulatory requirements manufacturers must meet.

The MDSAP audit approach reflects requirements incorporated into the program at the time a revision is published. However, regulatory requirements become legally applicable according to the timelines established by the relevant authorities, whether or not those changes have been incorporated into MDSAP.

Marc illustrated this with the example of FDA cybersecurity requirements, which he noted were implemented in 2023 but incorporated into the MDSAP audit approach in 2026. That timing can create a gap for manufacturers that rely on the audit approach as their primary source of regulatory updates.

His conclusion was clear:

“MDSAP should be viewed as an important component of a regulatory strategy, but not as a substitute for an effective regulatory intelligence and regulatory change management process.”

For regulatory leaders, this means maintaining visibility into changing requirements across every applicable market, assessing their impact, and implementing changes within the required timelines. Audit readiness must be supported by continuous regulatory monitoring and change management.

Global Registration Management Requires Connected Information

Apurva Kushare addressed the operational challenges that emerge as manufacturers expand across markets. Each country can have different registration pathways, documentation requirements, approval timelines, renewal periods, and local obligations.

As the number of products and markets grows, regulatory information often becomes fragmented across spreadsheets, shared folders, emails, and internal systems and there may be a time to replace these spreadsheets with a Regulatory Information Management system. Registration details may be maintained in one place, while certificates, technical documentation, and correspondence are stored elsewhere.

Apurva highlighted the consequences:

“The challenge is not that these systems cannot store regulatory information. They actually can, but the real issue is that they often operate independently, without a single consistent view of how all the information is related.”

This fragmentation affects more than administrative efficiency. Teams may struggle to confirm current registration status, identify outdated documents, determine which markets are affected by a product change, or keep track of upcoming renewals and obligations.

Apurva described the opportunity as a shift from:

“Managing individual spreadsheets and documents to managing connected regulatory information.”

Using a centralized approach like RegDesk can connect product information, country-specific requirements, regulatory intelligence, registration tracking and reporting, and compliance activities. This gives teams better visibility into where products are registered, which requirements apply, and which registrations are active, pending, or approaching expiration.

Regulatory Change Must Lead to Documented Action

Both presentations reinforced that regulatory compliance requires an ongoing process. Identifying a new or revised requirement is only the starting point. Organizations must determine applicability, assess potential impact, identify affected products and quality processes, implement necessary changes, and retain evidence of their decisions.

During the Q&A, Apurva addressed what happens when requirements change after a compliance assessment has been completed:

“A compliance assessment, in my opinion, should not be treated as one-time activity.”

She explained that organizations should reassess applicability, update risk assessments, identify affected products and quality management processes, and retain previous assessments for traceability.

For regulatory and quality leaders, this highlights the importance of maintaining a documented connection between regulatory changes, impact assessments, assigned responsibilities, and resulting actions. Without that connection, it becomes difficult to demonstrate how the organization identified and addressed evolving requirements.

Bringing Audit Readiness and Ongoing Compliance Together

MDSAP provides a common audit framework, but maintaining compliance across global markets requires continuous coordination between quality systems, regulatory intelligence, registration management, and change assessment.

The webinar highlighted three priorities for manufacturers:

  • Connect quality processes: Ensure information, investigations, risk assessments, and corrective actions are linked and traceable.
  • Monitor requirements beyond MDSAP: Track regulatory changes across applicable markets and assess them according to each authority’s effective dates.
  • Maintain connected regulatory information: Keep product data, registrations, supporting documentation, responsibilities, and compliance activities visible and current.

For organizations managing expanding product portfolios and global market access, audit readiness is an ongoing operational discipline. Regulatory change managment depends on the ability to connect information, understand regulatory impact, and demonstrate that required actions have been taken.

# #