V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryTMDA (Tanzania)
Compliance · The complete guide

Tanzania TMDA: Medicines and Medical Devices Authority, Registration and GMP

In short

Understand TMDA terminology, product-route selection, registration evidence and the records that connect manufacturers, applicants and importers.

4,052 words · ~19 min read
Tanzania TMDA: a regulatory affairs specialist reviews a medicines registration dossier on a tablet
Tanzania TMDA regulates medicines and medical devices and assesses marketing authorization dossiers.
On this page
  1. 01What Tanzania TMDA is—and what registration means
  2. 02Map jurisdiction, product type and legal authority
  3. 03Select the medicinal-product route and establish the baseline
  4. 04Devices and IVDs: keep the evidence model product-specific
  5. 05Good review practice, reliance and cross-border decisions
  6. 06Assess changes against the authorized product
  7. 07Records that connect manufacturer, applicant and importer
  8. 08Run the lifecycle across systems and recover exceptions
  9. 09Failure modes and two worked reconciliation cases
  10. 10A practical implementation and periodic-review checklist
  11. 11Where V5 Ultimate helps—and where humans decide
On this page · 11 sections
  1. 1What Tanzania TMDA is—and what registration means
  2. 2Map jurisdiction, product type and legal authority
  3. 3Select the medicinal-product route and establish the baseline
  4. 4Devices and IVDs: keep the evidence model product-specific
  5. 5Good review practice, reliance and cross-border decisions
  6. 6Assess changes against the authorized product
  7. 7Records that connect manufacturer, applicant and importer
  8. 8Run the lifecycle across systems and recover exceptions
  9. 9Failure modes and two worked reconciliation cases
  10. 10A practical implementation and periodic-review checklist
  11. 11Where V5 Ultimate helps—and where humans decide
AI · Explain it for MY operation

How does TMDA (Tanzania) apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What Tanzania TMDA is—and what registration means

Tanzania TMDA is the Tanzania Medicines and Medical Devices Authority, an executive agency under Tanzania’s Ministry of Health. This institutional description comes from GRevP section 1, Introduction, which describes its responsibility for regulating the quality, safety and effectiveness of medicines, medical devices, diagnostics, biocidal and tobacco products. That stated remit should not be read as covering every manufactured product.

For medicinal products, the GRevP glossary’s marketing authorization definition means approval to market a medicinal product in Tanzania. Use “marketing authorization” for that product-level approval rather than calling every submission, licence or certificate “registration.”

The following is an operational terminology comparison, not a statement of Tanzanian legal requirements. Each row points to a different object and a different record to examine.

TermObjectRecord to examine
TMDARegulatory authorityOfficial authority communication or decision
Medicinal-product marketing authorizationProductProduct-specific authorization and approved particulars
GMPManufacturing arrangementsSite-specific manufacturing and quality-system evidence
Business licensingBusiness activityOperator licence and its activity scope
Batch releaseIndividual batchBatch record and documented disposition decision

These records are not interchangeable. When someone asks whether a product is “TMDA registered,” identify the exact product approval they mean, then keep manufacturing evidence, operator permissions and batch decisions distinct. For the manufacturing concept, see current good manufacturing practice; it addresses a different operational question from product authorization.

02Map jurisdiction, product type and legal authority

The GRevP glossary, “Act” entry names the Tanzania Medicines and Medical Devices Act, Cap 219. Check the Act’s current text for territorial scope and binding duties; the glossary definition is guidance, not a substitute for operative legislation.

Use four authority labels throughout: binding law for applicable legislation; official guidance for agency instructions and interpretations; recommended practice for operational controls; and software support for technical functionality. A checklist or application feature should never be mistaken for a legal requirement.

Build a jurisdiction-and-product matrix before selecting a route. These are recommended review assignments, not determinations of jurisdiction or classification; every proposed market needs its own current-scope check.

MarketProduct or presentationScope questionGoverning instrument to checkReview owner
Mainland TanzaniaMedicinal productsWhich product and activity provisions apply?Current Cap 219 and applicable implementing instrumentsMedicines regulatory lead
Mainland TanzaniaDevices and diagnosticsWhich classification and activity provisions apply?Current Cap 219 and applicable device instrumentsDevice regulatory lead
Proposed Zanzibar distributionEach proposed productWhat territorial framework applies?Current Zanzibar-applicable legislationLocal regulatory/legal reviewer
Other destination countriesEach export productWhat destination requirements apply?Current destination legislation and guidanceDestination regulatory lead
Each proposed marketBorderline supplement, food, cosmetic or chemicalHow is this presentation classified?Current local classification and sector instrumentsClassification lead

For borderline products, record intended use, composition, presentation and claims before selecting a route; the sterile or aseptic supplement boundary illustrates why presentation deserves attention. Give the scope map an owner and date_checked field so a historic conclusion is not silently treated as current.

Separately, the compendium’s process introduction states that local manufacturers, wholesalers, distributors and importers of pharmaceutical products must be licensed before conducting business. Treat this as the compendium’s guidance statement, distinct from the operative statutory wording.

03Select the medicinal-product route and establish the baseline

Start with the application family and product family, rather than a generic dossier checklist. The compendium’s process guideline expressly covers new applications, renewals and variations of registered pharmaceutical products in section 2, Scope. These are families covered by official guidance, not a basis for assuming identical documentation across products.

Next, identify the relevant product-specific guidance. TMDA’s medicines-guidelines index lists separate marketing-authorization documentation guidance for human vaccines and biotherapeutic products. That separation makes product-family selection a sensible first planning step. A document title identifies a reference to consult; it does not establish eligibility or supply the technical requirements for a particular submission.

Keep submission status distinct from decision status. The Good Review Practice glossary defines an application as information provided for evidence-based evaluation and a marketing-authorization decision. Operationally, establish an indexed dossier baseline, named applicant contact, submission identifier, correspondence log and response owner. Record each submitted version and its associated questions and responses, so an assessor’s query can be traced to the exact information under review—not merely the latest working file.

Manufacturing evidence belongs alongside that submission history. The compendium’s section 1, Introduction connects marketing authorization with manufacture in facilities meeting TMDA Good Manufacturing Practice guidance. As a document-control practice, reconcile the manufacturing-site name, address and assigned activities across dossier references and supporting GMP records. Keep GMP evidence linked to the relevant site and product; do not treat a GMP document alone as the product-authorization decision.

After a decision, distinguish the submitted baseline from the authorized baseline. The Good Review Practice glossary’s marketing-authorization definition includes packaging, labelling, storage conditions, shelf-life and approved conditions of use. As an operating practice, index those attributes to the decision and associated approved documents, rather than assuming every proposal in the original dossier was accepted unchanged.

Those indexed attributes then provide reference points for later change assessment. Preserve superseded versions and make unresolved differences visible to the responsible reviewer. A focused data-integrity risk assessment can help prioritize controls where mismatched identifiers or overwritten files could obscure what was submitted, what was decided and which baseline operations should follow.

04Devices and IVDs: keep the evidence model product-specific

Building on the scope map above, check current TMDA device- and diagnostic-specific instruments for classification, application route and ongoing obligations. Keep medicinal-product guidance within its stated scope; do not treat it as a universal registration procedure. Resolve questions about risk classes, IVD assessment, certificate recognition and local representation against the current product-specific text.

For operational intake, use the following identification fields. These are useful documentation controls, not a TMDA-mandated schema:

  • Device: intended_use, product_family, model_number, catalogue_number, configuration, manufacturer_site and labelling_version.
  • In vitro diagnostic (IVD): add analyte, specimen_type and intended_user where relevant.
  • Link labelling_version to the applicable label and instructions for use, rather than recording only a document filename.

The identifying questions differ by product: a medicine presentation might be distinguished by strength, dosage form and pack size; a device configuration might instead depend on model, accessories and software version. Use identifiers that distinguish what is actually supplied. Apply production context tagging to connect that identity to manufacturing records without treating the tag as regulatory authorization.

Grouping several models under one commercial name can disconnect regulatory correspondence, technical evidence and the shipped configuration. Maintain an explicit model-to-evidence mapping showing which documents cover each configuration and where coverage remains unresolved. Assign a named regulatory owner to resolve ambiguous scope before the affected evidence is used for a submission or shipment decision. This mapping is a traceability recommendation, not an assumption that TMDA accepts any particular registration grouping.

05Good review practice, reliance and cross-border decisions

The TMDA GRevP glossary defines good review practices as documented best practices concerning the process, format, content and management of medicinal-product evaluation and registration. This is official guidance, not a separate authorization route.

Section 1.1, Objective of this document, presents high-level guidance on principles and processes for application submission and medicinal-product evaluation. For applicants, the practical task is to make the submission and subsequent exchanges easy to follow.

Prepare for a traceable review

Recommended applicant-side controls—not individual TMDA filing requirements—include:

  • Use consistent dossier references and stable document identifiers under document control.
  • Structure each response around the question, answer, supporting reference and any revised document.
  • Assign an accountable communication owner and retain the correspondence history.
  • Keep unanswered questions explicit, with an owner, the information still needed and a planned response; do not silently mark them closed.

Keep external assessments distinct

In regulatory-affairs usage, review practice concerns how an assessment is managed; reliance discussions concern using another authority’s work. A well-organized review record therefore does not, by itself, establish a reliance pathway or the effect of a foreign decision.

When proposing external material, prepare a comparison recording the authority and decision, assessed product and manufacturing site, assessment document version, permission to share, and differences from the proposed Tanzania product. Identify unresolved differences rather than treating a shared brand name as proof of equivalence.

Check the applicable TMDA procedure before assigning procedural effect to that material. Treat the comparison as preparation for regulatory discussion, not a promise of eligibility, recognition, reduced review or faster authorization.

06Assess changes against the authorized product

The TMDA medicines-guidelines index lists dedicated guidance on variations to registered medicinal products. Check the current variation text for product-specific classification, documentation and implementation conditions. Do not assign a category from a commercial description such as “artwork refresh” or “supplier optimization.”

Keep assessment and implementation separate

As recommended change-control practice, create one change record containing proposed_change, baseline_version, affected_products, affected_sites, evidence_needed, regulatory_assessment_owner, submission_reference, decision_reference and implementation_status. Where a reference is not yet assigned or is considered inapplicable, record the reason rather than leaving an ambiguous blank.

  • Proposal: describe the intended change and identify the authorized baseline.
  • Internal assessment: assign evidence owners and document the regulatory assessment and its rationale.
  • Regulatory correspondence: link submissions, questions, responses and decisions without treating correspondence alone as permission to implement.
  • Operational implementation: record the assessed implementation conditions, responsible approvers and actual transition.

These are recommended workflow statuses, not TMDA variation categories or statutory permission to implement. Keep their dates and supporting records distinct so an internal approval cannot be mistaken for a regulatory decision.

Worked case: presentation impact

Assume three strengths and two pack sizes per strength: 3 × 2 = 6 controlled presentation combinations. An artwork change affects one strength in both pack sizes: 1 × 2 = 2 affected combinations, leaving 6 − 2 = 4 unchanged. List all six combinations, mark the two affected entries and assign owners for artwork comparison, specification assessment and implementation evidence. This arithmetic defines an impact list; it does not determine application count, fees or variation classification.

Use one change identifier to connect the two proposed artworks, associated specifications and implementation records. Preserve the authorized baseline separately from proposed and superseded versions; the newest upload must not overwrite it. Maintain an audit trail linking version identifiers, assessment decisions and the batches or packaging orders using each implemented version. This makes the before-and-after position reconstructable without relying on filenames or upload dates.

07Records that connect manufacturer, applicant and importer

For medicinal-product supply chains, organize evidence around the questions each party must answer. The following is a recommended operating model, not a universal statutory record inventory or retention schedule.

Record groupBusiness question and useful evidence
Product and site identityWhich product and operations are involved? Connect product identifiers, strength, dosage form, pack presentation, site addresses and manufacturing roles.
Authorization and submission historyWhat was requested, decided and subsequently updated? Link dossier versions, submission references, correspondence and authorization decisions.
Manufacturing and testing evidenceWhat supports this batch’s quality assessment? Connect the batch record, testing records, deviations and review decisions.
Shipment and receipt traceabilityWhere did the batch move, and what arrived? Connect dispatch and receipt references, quantities, batch identifiers and transport-condition records for recall readiness.
Changes and investigationsWhat changed or failed, and which records were affected? Link change assessments, investigation conclusions, affected batches and action decisions.
Complaint or safety correspondenceWhat concern was raised, and how was it handled? Preserve correspondence, case identifiers, follow-up and decision references.

Separate custody from access

An importer need not originate manufacturing evidence to maintain useful traceability. It can hold references, agreed retrieval arrangements and its own receipt records while the manufacturer retains source records. For each evidence group, name the record owner, controlled location, access contact and escalation route. Agree how restricted records can be retrieved for an investigation without confusing access permission with ownership.

Recommended logical model

Companion data-model diagram: Product → Authorization; Authorization → Submission and Change; Product → Batch; Evidence → the relevant Product, Authorization, Submission, Change or Batch. These links represent a recommended logical model, not an official TMDA database specification. Use stable identifiers; retain document version, source record and decision reference as separate fields rather than combining them into one filename.

Testing evidence should identify the sample or batch, method or specification version, result and reviewer reference. Link complaint and safety correspondence to the relevant product and batch where known. Check applicable reporting and retention instruments for exact duties; do not infer a reporting destination, deadline or retention period from this model.

Recommended Product and Evidence Model

Product

Identifies the controlled product presentation.

  • product_id
  • product_type
  • presentation
  • manufacturer_site_id

Authorization

References the applicable market decision.

  • authorization_id
  • product_id
  • jurisdiction
  • approved_version

Submission

Preserves the application and correspondence.

  • submission_id
  • product_id
  • dossier_version
  • decision_reference

Change

Connects assessed changes with implementation.

  • change_id
  • affected_product_ids
  • baseline_version
  • implementation_status

Batch

Links manufacture with shipment identity.

  • batch_id
  • product_id
  • site_id
  • shipment_reference

Evidence

Locates a versioned supporting record.

  • evidence_id
  • source_system
  • source_record_id
  • document_version
Stable identifiers connect product identity, authorization, submissions, changes, batches and supporting evidence.

08Run the lifecycle across systems and recover exceptions

Use this seven-step workflow as a recommended operating model for registration-related work, not a statutory TMDA sequence. Adapt the handoffs to the applicable product route.

  1. Scope the product and market: record the intended category, territory and route.
  2. Assign responsibilities: name the applicant, manufacturer and importer contacts and internal decision owners.
  3. Establish the evidence baseline: identify controlled documents and their source records.
  4. Submit and track: retain the submitted version, submission reference and correspondence.
  5. Resolve questions: assign each question, approve responses and link supporting evidence.
  6. Reconcile the decision: compare the decision with the submitted baseline and update affected records.
  7. Monitor subsequent changes: route proposed changes back to the responsible regulatory reviewer.

Connect systems without losing provenance

Link regulatory tracking to document control for dossier versions, manufacturing records for batch context, laboratory records for results and inventory systems for stock identity. Use stable product and batch keys, controlled version references and a source_record_id identifying the originating record. Assign explicit ownership of each authoritative field so conflicting values have a defined resolution owner. Check identifiers and versions at transfer and record acceptance or rejection. These are data-integrity design controls, not claims about V5 interfaces.

Recover exceptions visibly

For a missing attachment, duplicate submission reference, mismatched product identifier or superseded evidence file, preserve the original event and route the exception to its owner. Investigate the source, authorize correction under internal procedures, then reconcile dependent records rather than silently overwriting them. Keep an exception log with detected_at, affected_record_ids, owner, resolution_reference and reconciliation_status. Use audit trail review to check that the correction and downstream reconciliation remain traceable.

From scope check to controlled change
  1. 1
    Confirm scopeRecord intended use, destination market and unresolved classification questions.
  2. 2
    Assign responsibilitiesName applicant, manufacturer, importer, evidence owners and review contacts.
  3. 3
    Establish baselineIndex product, site, specification and controlled-document references.
  4. 4
    Track submissionPreserve the submitted version and correspondence identifiers.
  5. 5
    Resolve questionsAssign responses, reconcile attachments and record outstanding issues.
  6. 6
    Reconcile decisionConnect the decision reference to affected operational records.
  7. 7
    Monitor changesAssess proposed changes against the applicable product baseline.
Recommended operational handoffs; check the applicable product-specific procedure before acting on each regulatory decision.

09Failure modes and two worked reconciliation cases

The controls below are recommended operational practice, not claims about TMDA rejection frequencies. Reconcile identifiers, document versions and response status separately: a complete register can still point to the wrong product or unsupported answer.

FailureConsequencePreventive controlRecovery record
Mismatched product identifiersEvidence is assigned to the wrong product.Match application reference, strength, dosage form and pack against a controlled product crosswalk.Corrected crosswalk, affected-document list and reviewer sign-off.
An unresolved question marked closedMissing data disappear from the active workload.Reconcile each question ID to its response, supporting data and closure basis; distinguish internal readiness from authority correspondence.Reopened question, corrected status history, owner and outstanding action.
Wrong evidence versionA response relies on superseded information.Match each attachment’s document ID and revision to the approved submission manifest.Replacement manifest, version comparison and assessment of affected responses.
Shipment with uncertain lot identityCartons cannot be reliably assigned to a lot.Match carton labels and packing-list entries to manufacturer lot references and the relevant batch record.Segregation record, carton-level reconciliation and documented disposition.

Worked case 2: reconcile shipment quantities

Assume a shipment contains 120 cartons with 10 packs per carton: 120 × 10 = 1,200 packs. Three cartons have uncertain lot identity, representing 3 × 10 = 30 packs. Segregate those cartons under the applicable internal procedure while investigating; the other 117 cartons represent 117 × 10 = 1,170 packs.

The reconciliation is 1,170 + 30 = 1,200 packs. Record which carton identifiers account for each subtotal. Restoring the carton-to-lot link supports recall readiness; a reconciled count is not itself a release decision for either group.

Worked case 3: measure response readiness

Assume eight reviewer questions are tracked in mutually exclusive statuses: five responses internally approved, two awaiting data and one requiring clarification. Reconcile 5 + 2 + 1 = 8. Internally ready responses are 5 ÷ 8 × 100 = 62.5%.

This measures applicant-side readiness by question count, not scientific importance or remaining effort. It is neither an approval probability nor a measure of the authority’s assessment progress: internal approval does not establish that TMDA has assessed or accepted a response.

10A practical implementation and periodic-review checklist

Use this checklist as recommended implementation practice, not a prescribed TMDA inspection checklist. Keep completion evidence and open actions in a shared governance register.

  • Name a scope-map owner with authority to resolve questions across functions.
  • Maintain a product-route decision record, including its rationale and unresolved classification questions.
  • Allocate manufacturer–applicant–importer responsibilities explicitly; obtain acknowledgement from each party.
  • Identify the controlled product baseline, its version and the person responsible for maintaining it.
  • Assign correspondence ownership, including response coordination and filing of final communications.
  • Agree evidence-access arrangements with external parties; test permissions and nominate backup contacts.
  • Maintain a retention-rule register showing each rule’s basis, affected records and responsible custodian.
  • Train staff on their assigned tasks, escalation points and locating current records.
  • Schedule reassessment and document event-driven review triggers.

Test retrieval

Select one product and one associated batch. Starting with its batch record, reconstruct the applicable product baseline, relevant change history, shipment identity and supporting evidence. Record missing links and assign corrective actions, owners and due dates. Choose acceptance criteria locally rather than assuming a mandatory retrieval time or pass score; use a follow-up effectiveness check to confirm repaired links remain usable.

Keep reassessment visible

Trigger review for a proposed new market, changed product presentation, manufacturing-site change, altered supplier responsibilities or changed governing documents. Keep review_frequency, next_review_date, owner and unresolved_scope_questions visible in the register; record decisions and follow-up actions after each review.

11Where V5 Ultimate helps—and where humans decide

Batch Evidence Assembly

V5 Ultimate assembles its batch record from the work order, steps and step executions, dispensed bags and dispense variances, lab samples, QC check results, equipment used, checklists, electronic signatures and deviations.

For a TMDA-related review, the recommended handoff is to relate the assembled batch record to the correct product baseline and relevant investigation or submission reference. Responsible reviewers then assess whether that evidence is relevant and complete for the question being addressed.

  • Record completeness: check that expected records are present, identifiable and linked to the correct batch. Presence alone does not establish that a result is acceptable.
  • Technical interpretation: have appropriate specialists evaluate results, discrepancies and deviations against the applicable specifications and investigation conclusions.
  • Decision authority: document who may approve the assessment, authorize follow-up actions and make the batch-release decision, with the rationale and unresolved issues visible.

Software support does not establish site compliance or confer regulatory authorization. Humans approve and release. Treat this separation as a governance recommendation: an assembled record supports a decision, but neither replaces technical judgment nor grants decision-making authority.

Frequently asked questions

Q.How should an applicant assess whether a foreign authorization or assessment report is relevant to a Tanzania application?+

Build a comparison against the product proposed for Tanzania: formulation, strength, dosage form, indications, manufacturing sites, process, specifications and packaging. Record the foreign decision’s date, conditions, outstanding commitments and subsequent changes. Check whether the assessment report covers those same particulars and can legitimately be shared. Use document control to identify versions and a data integrity assessment to examine provenance. Present differences explicitly and ask TMDA whether the proposed submission route can use that evidence.

Q.What should a company check before treating a mainland Tanzania registration as covering distribution in Zanzibar?+

Before planning Zanzibar distribution, obtain written confirmation from the relevant Zanzibar authority of the applicable product authorization, importer, premises and consignment arrangements. Provide the exact product identity, mainland certificate, proposed local operator and distribution model. Ask whether a separate application or other permission applies; do not base shipment decisions solely on the certificate’s country name. As an operational safeguard, map complaint handling, returns and recall readiness across both destinations, with named contacts and traceable stock records.

Q.How should a borderline supplement, disinfectant or diagnostic product be assigned to a regulatory route?+

Prepare a classification brief rather than choosing a route from the trade name. Describe ingredients, concentrations, intended purpose, claims, mode of action, administration route, users and presentation. For disinfectants, specify the target surface and use setting; for diagnostics, specify the specimen and clinical purpose. Include proposed labels and instructions for use. A sterile supplement presentation deserves particular scrutiny. Seek written classification advice from the relevant authority before committing to a dossier or commercial labeling.

Q.What evidence should an importer arrange to access when manufacturing records remain with the manufacturer?+

Agree a documented access arrangement covering batch identity, certificates of analysis, executed manufacturing and packaging records, deviations, investigations, change history and the manufacturer’s release decision. Specify who retrieves each record, how authenticity is demonstrated, and how confidential material reaches an assessor or investigator. Include batch records and relevant shipment temperature monitoring, not just summary certificates. Test the arrangement with a retrieval exercise. The practical objective is usable evidence during a query, complaint or quality incident, without requiring routine duplication of every archive.

Q.How should an applicant respond when an assessor asks a question addressed in an earlier submission?+

Answer the current question directly, then identify the earlier submission date, dossier version, section and page. Attach or reproduce the relevant explanation where appropriate, and explain whether any underlying information has changed. TMDA’s Good Review Practice guidelines, section 4.3.2 describe first assessment, second assessment and quality assurance of the assessment report. Keep a response matrix and audit trail so another reviewer can reconstruct the exchange. Avoid replying only “already submitted”; check whether the new question concerns a different scope or unresolved inconsistency.

Q.What should a quality team do when an unassessed packaging change is discovered after shipment?+

Open a change-control investigation, identify affected batches and destinations, and establish exactly what changed: contact materials, barrier properties, closure, artwork or pack configuration. As initial containment, consider holding remaining stock and suspending further dispatch while assessing patient risk and authorization impact. Preserve samples and distribution records through distribution deviation management. Have quality and regulatory staff evaluate stability, compatibility, labeling and filing implications, then document decisions on authority contact, market action and disposition rather than treating shipment as acceptance of the change.

Q.What does a passing laboratory result establish, and what questions still need a separate decision?+

A passing result supports conformity of the tested sample with the specified acceptance criterion, subject to the method, sampling and data being suitable. It does not, by itself, resolve batch representativeness, manufacturing deviations, transport exposure, packaging suitability or whether the marketed configuration matches its authorization. Keep the label claim and release limit distinct when interpreting results. Record which question the test answers and route the remaining questions to the responsible quality or regulatory reviewer before deciding the batch’s status.

Q.Who should approve regulatory responses and batch disposition when software assembles the supporting evidence?+

Define approval authority in controlled procedures and the relevant company agreements. Regulatory staff should coordinate submission responses, with technical owners confirming their content and an authorized signatory approving the final response. Assign batch disposition to the designated human quality decision-maker under the applicable arrangements. Software assembly should support these reviews, not replace them or certify compliance. Reviewers should check completeness, unresolved exceptions and consistency with the authorized product, then record the decision, rationale, identity and date.

Primary sources

  • TMDA medicines guidelines index
  • TMDA Compendium of Guidelines for Marketing Authorization of Medicinal Products (July 2020)
  • TMDA Good Review Practice guidelines
Software that covers TMDA (Tanzania)
V5 Ultimate for Veterinary Pharma
For veterinary manufacturers evaluating production and quality records. Compare your requirements for labels, medicated-feed…
Talk to us about TMDA (Tanzania)

Want to see how TMDA (Tanzania) could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
PharmaceuticalMedical Devices
Inside V5
  • → Score your compliance gap — then download the validation pack.
  • → Document control — one version in force, every change signed and explained.
  • → QMS — quality records next to the work they concern.
Related terms
  • → 21 CFR Part 11
  • → EU Annex 11
  • → 21 CFR 211
  • → 21 CFR 820
  • → GAMP 5
  • → CSV
  • → CSA
  • → IQ / OQ / PQ

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC