TİTCK Permit Dossier and Party Responsibilities

The product supply of a clinical trial is bounded by the quality of that trial's permit dossier: a product not defined in the file cannot be imported, a version absent from the file cannot ship, and an importer not referenced in the file cannot file a declaration. The TİTCK permit process is therefore not merely the regulatory unit's business; it is accepted as the common ground of the entire supply chain. The dossier is built on two axes: the content axis carries coherent versions of the protocol, the investigator's brochure and the product dossier; the process axis follows the assessment chain that starts with the ethics committee, completes with the agency review and reopens at every substantial change. This article explains the sections of the permit dossier, the owner of each section, the assessment flow and the change management. A single-view responsibility map is offered for sponsors, local representatives, CROs and supply teams.

Who is this for?

This guide is for every role touching the permit dossier or feeding from it. The sponsor's regulatory teams are the file's architects; the clinical supply unit matches the shipment plan with the product definitions in the file. The local representative is the foreign-based sponsor's legal counterpart in Türkiye and is accepted as the single address for communication with the authority. CROs manage the operational flow from application to site activation and keep the file's timings realistic. Manufacturer and quality units build the file's technical backbone with GMP documents, specifications and analysis information. Customs and import owners prepare the document set referencing the acceptance information. Site coordinators and the principal investigator are responsible for keeping protocol and consent versions current in the field. In an audit, every role must be able to show the date and version of its own section; this article provides the frame for that readiness.

Which products does it cover?

The product scope of the dossier extends to every pharmaceutical product to be used in the trial. The investigational product itself: formulation, dose strengths, packaging information and manufacturing site. The comparator: its source, licensing status and, where required, the blinding plan. Placebo: composition and matching rationale. Ancillary medicines: their definitions in the protocol and procurement routes. Alongside these, the product's analytical underpinnings enter the file: specifications, analytical methods, stability data and reference sample arrangements. Label mock-ups are also part of the product scope; they are defined with Turkish information, warning statements and a code system. Product-based version control is mandatory: the protocol has a version, the product dossier a version and the label a version; all three must be coherent at every moment of the trial. The scope also assesses research material that is a medical device; the device passes through its own legislation and sits in this file only in its context of use.

When does it apply?

The permit process applies to every new trial, but certain moments require the file to reopen. When a substantial protocol change is made, for instance in dose, patient population or product source, the assessment chain runs again. When the investigator's brochure is updated, a change in safety information can reflect into the consent text and to the authority. A manufacturing site change, formulation revision or specification update renews the product dossier. A change in label content requires re-approval of the mock-ups. New centres and investigator changes update the file's party section. Extensions and unblinding changes form a separate category and are assessed together with the statistical plan. The practical rule is this: every element in the file has its own trigger; when a change arrives, not only the changed section but every section it affects must be reviewed. No update should be made without a change-management record.

Legal framework and authority

The legal basis of the process is the legislation on clinical trials and the guides published under its authority. The legislation defines the conditions for conducting medicinal product trials, the application contents, the ethics committee and agency assessment procedures, product dossier requirements and traceability rules. The competent authority is TİTCK: applications are received through the agency's systems, assessments run on the calendars foreseen in the legislation, and the outcome forms the basis for the trial's supply chain. Ethics committees are the independent assessment authority; their approvals are an inseparable part of the application file. On the customs side, the competent-authority control of pharmaceutical GTİP codes is met with the document set referencing the acceptance information. Guide documents and templates are published and updated on the agency's official pages, and the application calendar must be kept alive against legislative and guide changes. This article summarises how the process works; the current texts must govern every application.

Step-by-step process

1. Identify the parties and roles in writing: sponsor, local representative, CRO, importer, depot, principal investigator; build the responsibility matrix.
2. Match product definitions with the protocol: let each product's status, source, form and strength become clear.
3. Collect the core file: protocol, consent texts, investigator's brochure, investigator qualifications, insurance and financial arrangements.
4. Build the product dossier with the manufacturer: GMP documents, formulation and specification information, stability data, analytical methods.
5. Prepare label mock-ups: Turkish information, warnings and the code system; check consistency with the consent and protocol language.
6. Plan the application: merge the ethics committee and agency assessment calendar with the product supply calendar.
7. Track the assessment: answer questions through a single point, meet additional requests with versioned submissions.
8. Tie the acceptance information to the supply chain: reference it in the import document set, match the shipment plan to the approval.
9. Set up change management: with a trigger table, impact assessment and the reassessment flow.

Document checklist

• Responsibility matrix and party designations, signed version.
• Current version of the protocol and its amendment summary.
• Informed consent forms, approved Turkish versions.
• Investigator's brochure, the version in the application and its updates.
• IMP dossier: formulation, specification, stability and analysis information.
• GMP documents and certificates of the manufacturing site.
• Label mock-ups and the code system description.
• Investigator qualifications: CV, GCP training, declarations.
• Insurance and financial arrangement documents.
• Acceptance information and agency correspondence, complete and dated.

Parties and responsibilities

The matrix binds every section of the file to a single owner and makes section-based responsibility demonstrable in an audit. When roles change, the matrix must be updated, and the update entered into change management.

Exceptions and edge cases

The edges of file practice are where confusion most often appears. Information updates must be separated from substantial changes: not every update requires reassessment, but a classification error produces either delay or noncompliance. In multinational trials, differences between the global protocol and local implementation must be recorded openly in the local file; silent adaptation is not accepted. Whether an information update reflects into the consent text is assessed by the weight of the new safety information. A product becoming licensed during the trial does not change its status; the trial file continues under its own rules. In emergencies and participant-safety changes, a retrospective notification procedure is defined; outside it, no change is made without prior notification. In single-centre trials the ethics and agency processes run on narrow resources; calendar planning must be built for that narrowness. No product undefined in the file may ship; the rule has no exception.

Common mistakes

The most common mistake is assembling file sections from different versions; protocol, brochure and label mismatch. The second is leaving responsibilities in conversation; when the matrix stays unsigned, gaps open at the moment of crisis. The third is requesting the product dossier at the last moment; GMP and stability information can take weeks from the manufacturer. The fourth is not classifying changes; what seemed minor turns out substantial and notification is late. The fifth is planning operations before the acceptance information arrives; the import and site calendars are built without foundation. The sixth is answering authority questions in a scattered way; contradictory answers damage the file's credibility. The seventh is postponing the archive until the file closes; audit dates give no warning.

Important notice

This article is general information, not legal or customs advice; for clinical trial applications, TİTCK legislation, current content tables and templates must govern. Product examples and GTİP information mentioned here are for orientation; the GTİP examples are not binding. Legislative changes can affect application contents; official sources must be checked before any transaction.