(EU/UK) or releasing unit sits. Third, it sets up inspection logistics: time zones, addresses, and responsible contacts are pulled from the same master data you place in M1. For global programs built on external manufacturing, the administrative story of who does what is as important as your CMC comparability narrative. If you can’t reconcile a packager’s D-U-N-S in M1 with the site named in your carton proofs, questions arrive before scientific review even starts.

This article gives pharma teams a repeatable way to populate Module 1 with establishment data that stands up to audits. We’ll define FEI vs. D-U-N-S and when each matters; show how US, EU/UK, and Japan position facility facts in M1; outline a master-data workflow that prevents “parallel truths”; and provide checklists to link sites to Pre-Approval Inspections (PAIs) and post-approval surveillance. The goal: a crisp administrative backbone where every site has a verified identity, a declared role, and a clear line of sight from dossier to shop floor.

Key Concepts & Regulatory Definitions: FEI, D-U-N-S, Site Roles, and “Who Owns What”

FEI (Facility Establishment Identifier). Used by the US FDA to identify manufacturing and testing establishments, FEI is the anchor the Agency uses to reconcile inspections, compliance actions, and site classifications. You’ll reference FEI in Module 1 when naming US-relevant sites (or sites supplying the US). FEI differs from registration/listing numbers; it’s the durable key that lets reviewers tie your dossier to inspection history and scheduling. Keep a verified FEI catalogue for your network—including contractors and critical suppliers—and treat it as a controlled attribute in Regulatory Information Management (RIM).

D-U-N-S (Data Universal Numbering System). The nine-digit D-U-N-S is a global business identifier widely used in supplier qualification, portal onboarding, and national submissions. It complements FEI by resolving legal entities and physical sites worldwide. In Module 1, D-U-N-S helps unambiguously identify the company that owns the building and the specific operating unit, which is crucial when a corporate group runs multiple licenses at the same campus.

Site roles. Every establishment in M1 should declare its function relative to the product: API manufacture, drug product manufacture, release & stability testing, packaging/labeling, sterilization, cold chain logistics, etc. For EU/UK, include Manufacturer/Importer Authorization (MIA) and name the Qualified Person (QP) responsibility. For US, specify Quality Unit accountability for release. In Japan, align roles with PMDA conventions (e.g., drug substance manufacturer, final bulk, final product, testing site).

PAI linkage. A Pre-Approval Inspection targets sites that perform critical operations. In practice, PAI targeting emerges from three inputs: (1) the establishment list and roles in Module 1; (2) the Module 3 control strategy and batch records (who did PPQ and where); and (3) risk history (inspection outcomes for those FEIs). Your administrative packet should make this linkage obvious. If your PPQ was run at Site A (FEI X) and commercial lots will run at Site B (FEI Y), state that clearly and be ready with evidence that B is ready (qualification, comparability data, line readiness).

Master vs. local identity. A common source of error is “friendly naming” (e.g., “Springfield DP plant”) creeping into controlled forms. Lock your M1 to master data: legal name, registered address, FEI, D-U-N-S, and national codes should resolve back to governed records, not editable text boxes. When corporate restructures or site renumbering occur, update the master first, then regenerate M1 artifacts—never hand-edit one country and hope to remember the others.

Applicable Guidelines & Global Frameworks: Where the Rules Live—and Why They Matter

For the United States, facility identification and inspection history integrate with FDA’s data systems. FEI is the cross-reference for inspections and compliance actions. Your Module 1 should align with FDA’s electronic standards and administrative expectations and, when labeling is included, with Structured Product Labeling (SPL). Keep the FDA’s electronic standards and SPL hub handy via the Agency’s resources on Structured Product Labeling to ensure identifiers and site metadata appear where reviewers expect.

For the EU/UK, authorities maintain EudraGMDP, the public database of manufacturing/ GMP certificates, inspection outcomes, and authorizations. Your Module 1 should reference the authorized manufacturer/importer status and keep names/addresses consistent with the entries in that database. Use the EMA’s eSubmission guidance as your primary anchor for what belongs in Module 1 and how product-information and site facts interlock; see the EMA eCTD & eSubmission pages. UK specifics are published by the MHRA and follow similar principles for manufacturer/importer status and QP oversight.

For Japan, PMDA/MHLW govern administrative forms, establishment naming, and Japanese-language requirements for site documentation and authorizations. Many sponsors operate via affiliates to align national codes and seals. Keep PMDA’s English portal bookmarked to align the administrative packet with national conventions and submission tools; refer to PMDA (English) for procedural anchors.

Across regions, link establishment identity to the inspection ecosystem and to PQS governance (ICH Q10). Your RIM should map sites to products, procedures, and inspection outcomes so Module 1 mirrors reality. When you encode those links, reviewers spend less time reconciling who does what and more time assessing your science.

Country-Specific & Regional Variations: How US, EU/UK, and Japan Expect Site Facts in M1

United States (FDA). US submissions expect a clear list of all establishments engaged in manufacture, processing, packing, or testing, with roles and FEI numbers. Contract manufacturers and testing labs are not optional: if they touch the product or release decision, list them. If a site is new to the product post-approval, use the supplement route with the appropriate category and ensure Module 1 declares the site, FEI, role, and readiness. For PAIs, narrate the PPQ/ commercial split in your cover letter and ensure quality agreements and supplier qualifications are “audit-ready.” If your network includes a sterile sterilization contractor or a complex packager, call them out—these are high-leverage PAI targets.

European Union/United Kingdom. Module 1 must align with MIA scope and any listed Manufacturing and Importation Authorizations in EudraGMDP. Name the QP release site and any importation testing facilities. If your product is centrally authorized, list sites consistent with the application form; for national/MRP/DCP routes, follow NCA specifics for how many lines of text, which authorizations to cite, and whether to include recent GMP certificate references. Translation of site names is not free-form; use the form’s conventions to avoid national queries. When worksharing/grouping moves changes across licenses, keep site identity consistent in every member state’s M1 packet.

Japan (PMDA). Establishment naming follows Japanese conventions and may require Japanese-language forms, seals, and proof of manufacturing/marketing authorization relationships. Indicate drug substance vs. drug product production sites, final bulk sites where applicable, and testing/packaging locations. Consistency between Japanese M1 and the English master (e.g., CCDS for labeling, Module 3 for CMC) is critical; keep a bilingual cross-walk that pairs each Japanese entry with its master data attributes (FEI/D-U-N-S where appropriate) to avoid translation drift and site misidentification.

External manufacturing networks. For sponsors relying on CMOs/ CDMOs, regulators will expect clean governance lines: who owns batch disposition, who investigates deviations, and how supplier changes flow into regulatory change control. Module 1 should make these lines obvious by naming the release testing establishment and the holder of responsibility (MAH/QP). If multiple CMOs share a campus, disambiguate with building identifiers and floor/line where relevant to sterile flows.

Processes, Workflow & Submissions: A Master-Data Conveyor That Prevents Parallel Truths

1) Curate a governed site registry. In your RIM, maintain a single source of truth for every establishment: legal name, registered address, FEI, D-U-N-S, national authorizations (MIA, site licenses), contact roles, and inspection history. Each attribute has an Owner of Record (RA CMC for identifiers; QA for GMP status). New CMOs are onboarded through a site creation workflow with documentary evidence (licenses, certificates) attached.

2) Map product–site roles early. At change control/ program kickoff, run a Site Role Matrix: API, DP, packaging, testing, sterilization, importation, release. For each site, record the commercial intent (PPQ now/ commercial later) and whether a PAI is likely. Use the matrix to populate Module 1 placeholders and to brief Supply/QA on inspection readiness.

3) Lock identifiers before drafting M1. Do not author forms until FEI and D-U-N-S are verified against the registry and addresses match exactly. If your CMO’s legal entity changed, update the registry and regenerate forms. For EU/UK, cross-check MIA scope; for US, confirm FEI ties to the exact building/operation that will run PPQ.

4) Build the cover-letter narrative. The cover letter is the administrative “map”: it lists establishments by role, cites prior sequences for any replaced site entries, and calls out PAI-relevant sites with a one-line rationale. If PPQ and commercial use differ, say so and state how readiness is demonstrated (qualification, comparability, line clearance). This is where reviewers decide who to call on Day 7.

5) Validate and reconcile. Run eCTD validators that check node/leaf naming and detect orphan administrative leaves (old site lists not replaced). Compare the M1 site list against Module 3 (3.2.P.3, 3.2.S.2, analytical labs) to catch omissions. Where labeling mentions a manufacturer (carton/ container proofs), ensure the legal name matches the registry.

6) Submit and monitor PAI signals. After filing, track inspection scheduling correspondence and store it against each site’s record. If an alternate site is activated via supplement/variation, link the sequence to the site record so your inspection history stays product-aware.

Tools, Software & Templates: Make Identity & Inspection Linkage a System Property

RIM as the cockpit. Use RIM to own product–site relationships, identifiers, and procedural status. The system should expose tiles such as “Sites in Scope,” “FEI Verified,” “MIA scope aligned,” and “PAI candidate” with owners and dates. When a submission is built, the Envelope Builder should pull identifiers directly from RIM to eliminate typos.

DMS & eCTD publishing. The DMS should generate PDF/A with bound signatures for site lists, letters of authorization, and agent appointments. Your publishing suite must enforce leaf-title libraries (e.g., “1.2.1 Manufacturer Information – Finished Product”) and lifecycle rules (replace by default for site lists). Add a pre-flight rule that blocks dispatch if the site registry shows an identifier mismatch.

Inspection integration. Maintain a lightweight inspection ledger per site (dates, scope, outcomes) and link it to FEI and MIA. For EU/UK, store links to EudraGMDP entries; for US, track last FDA classification. Use the ledger to auto-flag PAI candidates during planning (e.g., “no recent sterile inspection”).

Templates that force clarity. Ship three templates with every program: (1) a Site Role Matrix (site → role → identifier → authorization → PAI likelihood → owner); (2) a Cover-Letter macro that lists sites by role and cites sequences replaced; and (3) a Vendor Onboarding pack that captures FEI, D-U-N-S, licenses, and contacts with documentary proof. Train authors to populate templates from RIM, not from spreadsheets parked on desktops.

Master-data governance. Create SLAs: new site requests answered in 5 business days; identifier changes within 2 days; post-inspection status updates within 3 days. Run a monthly site hygiene sweep to find duplicates, stale addresses, or orphaned site records that no longer tie to products.

Common Challenges & Best Practices: How Establishment Data Fails—and How to Keep It Clean

Parallel truths. Different teams keep their own site lists (quality, supply, RA). Result: the FEI in Module 1 doesn’t match QA’s inspection tracker. Fix: appoint RIM as the only source; block submission assembly if a site isn’t in the registry; give QA write access for inspection outcomes and authorization evidence.

Role ambiguity. A CMO runs both packaging and release testing, but Module 1 lists only packaging. Reviewers ask who is accountable for release; the query burns a week. Fix: the Site Role Matrix must include release testing and disposition responsibility. In the EU/UK, always name the QP release site and importation testing location.

Identifier drift. Corporate mergers change legal names; authors copy an old form; national queries ensue. Fix: lock forms to RIM export; require identifier verification as a pre-validation gate; run delta alerts when a site’s legal name changes so draft submissions refetch data.

PPQ vs. commercial site mismatch. PPQ at Site A, commercial at Site B, but Module 1 doesn’t explain the split. Fix: make the cover letter state PPQ site(s), commercial site(s), and readiness evidence; link to Module 3 comparability. Expect PAI attention on Site B and prepare accordingly.

Orphan administrative leaves. Teams “add” a new site list as new instead of replace, creating parallel histories. Fix: enforce lifecycle validators; run quarterly consolidation sequences that retire duplicates with a clear narrative of keeper vs. legacy.

External network opacity. Contract sterilizers or secondary packagers are omitted because “they’re not core.” Fix: if a site touches the GMP flow or labeling, it belongs in Module 1 with identifiers and role. Hidden nodes create inspection surprises and label control risk.

Latest Updates & Strategic Insights: IDMP, Structured Content, and Inspection Forecasting

IDMP & master data alignment. As agencies advance IDMP and related master-data initiatives, product and organization identifiers will bind more tightly to manufacturing sites. Forward-looking sponsors are mapping sites to standardized dictionaries now, so RIM can autofill M1 and reconcile envelopes with ERP/quality data. This ends the “copy-paste era” and makes impact analysis (e.g., a site authorization change) automatic across submissions and labels.

Structured content & object-level governance. Treat “site identity” as an object—legal name, address, FEI, D-U-N-S, authorizations, roles, contacts—with version history. When a field changes (new address line, updated MIA), your system regenerates every place that object appears: Module 1 forms, cover letters, site lists, even label mock-ups where a manufacturer is named. Pair this with language packs (JP/EU) so translations update without drift.

Inspection forecasting. With a year of telemetry, you can predict likely PAI targets: sterile lines, new CMOs, sites with long gaps since last inspection, or FEIs with complex change histories. RIM dashboards can flag “PAI-likely within 60 days” when a submission includes those characteristics. That in turn drives readiness sprints—mock interviews, batch record dry-runs, data-integrity checks—before the call arrives.

Portfolio waves & reliance. As teams run global maintenance waves, a clean site registry is the difference between synchronized approvals and month-long slips. When your M1 pulls the same identifiers and roles into US/EU/JP packets, reliance/worksharing strategies land cleaner because agencies are reconciling the same facts. Keep authoritative anchors one click away in templates and dashboards—the FDA’s SPL/electronic standards page, the EMA eSubmission hub (including EudraGMDP linkages), and PMDA—so new staff cite rules, not lore.

Bottom line. Establishment data is not clerical; it’s how regulators decide who to trust, who to visit, and when to start your clock. When you turn site identity into governed objects, tie them to inspection history, and make Module 1 a faithful mirror of manufacturing reality, inspections become confirmations—not investigations.