Headquarters:
regenold GmbH
Zöllinplatz 4
79410 Badenweiler
Germany
Phone: +49 7632 82 26-0
Email:
info@regenold.com
We author and contribute to clinical, regulatory, and scientific documents for medicines and medical devices. From protocols and Investigator's Brochures through CTD Modules, CERs, ODDs and PIPs to authority response packages, we produce submission-ready content from your source data, and do not just review existing drafts. Our writing team combines hands-on clinical development experience with regulatory and scientific writing expertise, to make sure the documents reflect the underlying strategy, not just the data.
These are just a few examples to illustrate the kind of work we commonly support.
Your clinical program is moving fast and your team does not have the writing bandwidth. Synopses, protocols, and Investigator's Brochures need to be regulator-ready, consistent, and delivered following a strict timeline.
You are preparing a marketing authorisation application and need the clinical story to hold together. CTD Modules 2.5, 2.7, Module 5, SmPC, and RMP need to be compiled from multiple data sources into a coherent package.
Your CER or performance evaluation report needs an update that will stand up under MDR or IVDR review. Systematic literature searches, PMS data, and clinical evidence need to be integrated into a document that satisfies notified body expectations.
You've received assessment questions from an authority or notified body. You need structured response documents and updated sections across the file, turned around within a tight deadline.
You're evaluating an asset for in-licensing or due diligence and need a gap assessment of the existing clinical and scientific documentation, with a clear view of what's missing and what it will take to close.
“Medical writing” and “scientific writing” are used loosely in the industry. Medical writing usually refers to regulated clinical and regulatory documentation (protocols, CTD modules, clinical evaluation reports, ODDs, PIPs). Scientific writing often refers to publications and scientific communications (manuscripts, posters, abstracts).
We cover both. This page addresses all document types that support regulatory submissions, ethics committee filings, and post-market obligations, as well as publication outputs aligned with the underlying evidence.
We author, compile, and finalise documents across the full development lifecycle for both pharma and device programs:
Writing is part of almost every development activity. To make the scope clear, we structure our support by document domain.
Synopses and protocols, Investigator's Brochures, clinical study reports, and updates of ethics and authority submission packages.
Modules 2.5 and 2.7, Module 5, RMP strategy/compilation, narrative consistency across the clinical files.
CER/PER aligned with MEDDEV 2.7/1 rev.4 and current MDCG guidance (including MDCG 2020-5 on equivalence, MDCG 2020-6 on legacy devices), SSCP/SSP per MDCG 2019-9, PMS plans, PSURs, and PMCF/PMPF documentation under MDR/IVDR.
PK-based argumentation, Biowaiver and reclassification rationales, position papers, structured literature reviews and gap assessments.
Manuscripts, abstracts, posters and scientific articles, aligned with source data and author review.
Writing outputs change as a program moves through development. This overview shows where medical and scientific writing typically contributes at each stage.
Development planning support through structured literature research and feasibility assessments that inform early decisions and the Target Product Profile.
Draft early clinical and scientific strategies for FIH planning, such as selection of starting dose and PD/Biomarker monitoring to allow drafting of initial Investigator's Brochure content and key justifications.
Work with regulatory leads to prepare materials that shape the development strategy, including gap analysis, outline the clinical development plan, scientific advice briefing books and supporting documents.
Synopses, protocols, Investigator's Brochure authoring and maintenance, clinical study reports, and Scientific Advice Briefing Books.
CTD clinical content (Modules 2.5/2.7, Module 5 and RMP) and structured responses to authority assessment questions and clock-stops.
Product-facing clinical/scientific texts where needed (e.g., SmPC/PIL or equivalent), aligned with the dossier and labelling discussions.
Maintenance and updates of clinical/performance and post-market documentation where applicable (e.g., CER/PER, SSCP/SSP, PMS, PSUR, PMCF/PMPF), and response packages for notified body/authority questions.
The type of product shapes both the document set and the regulatory expectations our writers work to.
CTD structure, greater emphasis on mechanism-of-action narratives, comparability arguments, and complex risk discussions (e.g. immunogenicity).
CER/PER under MDR/IVDR, SSCP/SSP, PMS/PMCF documentation. Writing must align with MEDDEV 2.7/1 rev.4, MDR/IVDR, and notified body expectations. Increasing emphasis on integration of real-world data and post-market surveillance findings into clinical evaluations.
Integration of device usability, human factors, and device-specific risk analyses into CTD and clinical evaluation reports. Article 117 documentation requirements.
CTD structure, but often requires specific justification work (PK argumentation, biowaivers, reclassification rationales).
Documentation must address SaMD classification, MDR/IVDR alignment and EU AI Act expectations.

A European pharmaceutical company was preparing an MAA for a small molecule and needed CTD Modules 2.5, 2.7, and Module 5 authored from multiple clinical study reports and nonclinical data. We wrote the Clinical Overview and Clinical Summary, compiled and quality-checked the CSRs, ensured narrative consistency across all clinical modules, and prepared structured responses to the day-120 assessment questions. The application received a positive opinion without a second assessment round on clinical.

A device manufacturer needed to update the clinical evaluation report for a Class IIb active device ahead of a Notified Body audit. The existing CER had been authored under MEDDEV 2.7/1 rev.3 and did not meet current expectations. We conducted a new systematic literature search, integrated post-market surveillance data, rewrote the equivalence argumentation in line with MDCG 2020-5, and produced a CER aligned with MEDDEV 2.7/1 rev.4 and MDCG guidance. The Notified Body accepted the updated CER without major findings.

A biotech entering clinical development for a first-in-class oncology compound needed an Investigator's Brochure and Phase I/II protocol authored from existing nonclinical and early CMC data. We wrote the IB from source, including a structured nonclinical summary, clinical implications section, and safety monitoring guidance. We then authored the protocol incorporating ICH E6(R3) quality-by-design principles and risk-based monitoring elements. Both documents were accepted by the ethics committee and authority without requests for major revision.
We write the documents and define the clinical strategy; the regulatory team provides regulatory strategy, manages submissions, and handles authority interactions.
Clinical writing supports trial documentation. Clinical development covers overall clinical strategy, trial design, CRO coordination, and operations.
CMC documentation (Module 3, ASMFs/DMFs) is handled by the CMC team. We cover the clinical modules.
PSURs and safety documentation draw on PV data. We author the reports; the PV team manages the safety data and signal detection.
Tell us about your product and timeline, and we’ll outline how we can help.
Speak with an ExpertAs early as possible. Our senior writers bring more than 20 years of clinical development experience each, which means they can contribute to shaping the evidence strategy from the very start. If you have a Target Product Profile, you have enough to start structuring your evidence narrative and aligning early documents (IBs, protocols, Briefing Documents) with the regulatory pathway. Early involvement prevents rework when the submission deadline arrives.
Both, but we are strongest when writing from source data and materials. We take clinical data, study reports, literature search outputs, and regulatory inputs and turn them into submission-ready documents. We also review and restructure existing drafts where that is what's needed.
Yes. We write, review, and finalise CTD modules, CERs, PSURs, ODDs, PIPs and other documents, and coordinate with the regulatory team to publish and submit them. We also prepare response packages for authority and notified body questions.
We create core documents that satisfy both EMA and FDA structures, then adjust formatting and emphasis for regional expectations (e.g. EMA Scientific Advice vs. FDA type A, B, C, and D meetings Briefing Documents). For markets beyond the EU and US, we coordinate with local regulatory experts through regulanet®, our global network, to ensure documents meet local authority requirements while keeping the core content consistent.
We flag gaps early and propose next steps: supplementary studies, bridging justifications, strengthened post-market plans, or revised evidence strategies. We don't just document the gap; the goal is we help you close it.
We follow a structured review cycle: first draft, consolidated comments, revision, final QC. We manage the document through each round and track all changes. For large submissions, we coordinate review across multiple internal and external contributors to keep the timeline on track.
Yes. We author SSCPs for implantable and Class III devices under MDR, and SSPs (Summary of Safety and Performance) for certain IVDs under IVDR, aligned with MDCG 2019-9 guidance. These documents are intended for patients and healthcare professionals and must be written in clear, non-promotional language while accurately reflecting the clinical evidence and risk profile. We prepare them as part of the clinical documentation package and coordinate the manufacturer validation process before upload to EUDAMED.
Yes. Notified Body review cycles for CERs, PERs, and technical documentation generate detailed questions that require structured, evidence-based responses. We prepare the response documents, update the affected sections of the clinical evaluation or technical file, and ensure consistency across the documentation. The process is analogous to responding to health authority assessment questions for pharmaceutical submissions, but the document set and review expectations are different.