A preliminary CMO/CDMO project assessment should start with a concise non-confidential fact sheet, not a full formula, dossier, patient information or complete process package. State the dosage form, development stage, target market, requested scope, approximate scale, presentation, timeline, regulatory ownership and the decision sought. Explain whether supporting documents exist without uploading them, then match additional disclosure to the decision stage. An NDA is important but does not replace quality governance, access control or a staged review plan. Public information can support screening; it cannot confirm capacity, project acceptance, approval or suitability for a specific product.
The purpose of a preliminary assessment is to answer one limited question: is there enough strategic, technical and regulatory fit to justify confidential due diligence? That decision can usually be made without sharing product formulas, detailed process parameters, full regulatory dossiers or commercial secrets.
1. Use a one-page non-confidential project fact sheet
A useful first submission should cover the following facts at a level that does not reveal protected know-how:
- Organization and contact. Legal or working company name, country, contact person, role and business email.
- Product category. Dosage form, route of administration and broad therapeutic or use category. A confidential active ingredient can be described by handling class until an NDA is in place.
- Presentation. Vial, ampoule, bottle, blister, tube or other primary pack; broad fill or strength range where it is not sensitive.
- Project stage. Concept, formulation development, process development, clinical, registration, technology transfer, site transfer or commercial supply.
- Target market. Country or market group, proposed applicant or authorization holder, and whether a regulatory pathway has already been discussed locally.
- Requested model. CMO, CDMO, technology transfer, analytical support, registration support or a phased combination.
- Current status. Whether the product has development batches, validated methods, stability data, existing manufacture or an approved dossier—without attaching the files.
- Scale and demand band. Broad development/commercial batch range, indicative annual forecast band and campaign expectations rather than a binding forecast.
- Timing. Desired feasibility decision, transfer start, submission or launch window, plus any genuinely fixed dependency.
- Special characteristics. Sterile or terminally sterilized route, lyophilization, high potency, sensitization, containment, cold chain or controlled-substance considerations at a non-sensitive level.
2. Do not send sensitive information at first contact
The initial inquiry should exclude patient identifiers, prescriptions, complete formulas, exact process parameters, proprietary analytical procedures, unpublished regulator correspondence, complete dossiers, source-code or system credentials, detailed cost structures and other trade secrets. The absence of these materials does not block screening; it protects both parties from uncontrolled disclosure.
3. Match disclosure to the decision stage
| Stage | Purpose | Appropriate information |
|---|---|---|
| Before NDA | Routing and basic fit | The ten-item non-confidential fact sheet, public company information and questions for the first call. |
| After mutual NDA | Structured feasibility | Agreed technical overview, development history, equipment/scale needs, analytical status, known gaps, regulatory context and forecast assumptions. |
| Controlled data room | Due diligence and scope | Indexed documents, named reviewers, access controls, permitted-use rules, Q&A log and a document-by-document request list. |
| Contracted project | Execution | Approved transfer package, protocols, methods, specifications, responsibilities, change control and project records. |
4. Explain document availability without uploading documents
A simple availability matrix is enough for the first stage: “available,” “in preparation,” “not available” or “not applicable” for development report, process description, specifications, method validation, stability, batch history, container-closure information and regulatory correspondence. This helps identify maturity without disclosing content.
4A. Separate electronic-submission context from information sharing
For a cross-border programme that may later involve an electronic submission, a non-confidential brief can identify the intended receiving authority or market and the known submission context without attaching a dossier. ICH states that its eCTD v4.0 Implementation Guide v1.7 and Controlled Vocabulary Package v1.0.3 were endorsed in June 2026. That global reference does not establish that a particular authority has adopted eCTD v4.0, will accept a specific format, or will accept any product application. Applicable local requirements, the dossier lifecycle, identifiers and submission route must be confirmed with the responsible parties and authority before execution. [5]
5. Make the desired decision explicit
State what you want from the preliminary review: a platform-fit decision, a list of critical questions, an indicative scope, an NDA discussion, a site call or a recommendation to stop. A request simply marked “need quotation” is rarely ready because price depends on scope, evidence gaps, market requirements, scale and responsibilities.
6. Use risk-based routing
WHO's technology-transfer guideline expects a planned process supported by due diligence, gap analysis, quality risk management and documented responsibilities. ICH Q9(R1) says the level of formality and effort should be proportionate to uncertainty, importance and complexity. [1] [3] These principles justify a light first screen for a straightforward mature product and a multidisciplinary review for sterile, complex or poorly documented projects.
7. Confirm confidentiality does not replace quality governance
An NDA governs permitted use and protection of information. It does not define manufacturing responsibilities, validation, batch disposition or regulatory communication. Those interfaces belong in the project plan, technical agreement and quality agreement as the project matures. [2] [4]
Frequently asked questions
Must the active ingredient be named before an NDA?
Not always. If identity is sensitive, provide the dosage form, handling class and critical compatibility or containment characteristics needed for routing.
Can a preliminary assessment produce a binding quote?
Usually not. It can establish fit and an indicative scope; a defensible quote normally follows clearer technical, regulatory, quality and supply assumptions.
Is an annual volume forecast required?
A broad range is useful for scale and capacity screening. Mark it as an assumption rather than a commitment unless contractually agreed.
Should the full dossier be uploaded after signing an NDA?
No automatic upload is needed. Agree a focused request list, permitted purpose, access controls and reviewers first.
What happens if critical information is unavailable?
Record the gap and decide whether it requires a development work package, an alternative route or a stop decision.
Authoritative sources
This article is an industry perspective for general business discussion. It is not legal, regulatory or medical advice. Project requirements must be confirmed with the responsible parties and applicable authorities.