Establishing secure connection…Loading editor…Preparing document…

Legal RDC ANVISA Letter

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

LEGAL RDC ANVISA LETTER

This Letter of Declaration (the Letter) is made effective as of by and between Company Name: , a legal entity with registered address at , registration/holder number (hereinafter referred to as Applicant), and Regulatory Representative Name: , with principal place of business at (hereinafter referred to as Representative).

Recitals

WHEREAS, Applicant is the holder, manufacturer, or authorized distributor of the product identified as Product Name: , intended for regulatory review under RDC No. ;

WHEREAS, Applicant seeks to furnish to Agência Nacional de Vigilância Sanitária (ANVISA) documentary and attestative information required by applicable RDC provisions in connection with the product, including but not limited to manufacturing site data, quality control documentation and declarations of compliance;

WHEREAS, Representative is retained to prepare and submit regulatory documentation on behalf of Applicant and to certify factual and documentary matters described herein.

NOW, THEREFORE

In consideration of the foregoing recitals and the mutual covenants contained herein, the parties agree as follows:

1. Definitions

For the purposes of this Letter, the following terms shall have the meanings assigned below: (a) "RDC Requirements" means the regulatory obligations set forth in the RDC referenced above and any implementing administrative guidance; (b) "Documentation" means records, certificates, batch release information, technical dossiers and other materials submitted to ANVISA in support of the product; and (c) "Confidential Information" means non-public information exchanged between the parties but does not include information required by law or regulatory authorities to be disclosed.

2. Declaration of Compliance

Applicant hereby declares, under penalty of law and to the best of its knowledge and belief, that the product identified above complies with the applicable RDC Requirements as of the effective date and that the Documentation submitted or to be submitted to ANVISA is true, complete and accurate in all material respects.

3. Representations and Warranties

Applicant represents and warrants that: (a) it is duly organized and validly existing under applicable law and has authority to execute this Letter; (b) it has obtained all necessary consents and authorizations to make the declarations herein; (c) Documentation provided to Representative for submission is genuine and derives from records maintained in the ordinary course of business; and (d) it will promptly notify Representative and ANVISA of any material change in the facts or data contained in the Documentation.

4. Obligations of Representative

Representative shall prepare and deliver the Documentation to ANVISA in a timely and professional manner, shall act only at the direction of Applicant with respect to substantive regulatory decisions, and shall maintain records evidencing submission and any correspondence with ANVISA for a period consistent with applicable regulatory retention obligations.

5. Attachments and Evidence

6. Confidentiality and Regulatory Disclosure

The parties acknowledge that information submitted to regulatory authorities may be subject to public disclosure under applicable law. Notwithstanding any confidentiality obligations between the parties, each party consents to disclosure of Documentation as required by law, regulation, or by instruction of ANVISA. For all other information exchanged between the parties, each party shall use reasonable measures to protect Confidential Information from unauthorized disclosure.

7. Notices

All notices, requests, consents and other communications required or permitted under this Letter shall be in writing and delivered to the addresses set forth below or to such other address as a party may designate in writing.

8. Recordkeeping; Audits

Each party shall maintain complete and accurate records supporting the representations made in this Letter. Upon reasonable notice, Applicant shall permit Representative or a regulatory authority to inspect records relevant to the Documentation and compliance with RDC Requirements, subject to applicable confidentiality protections.

9. Amendments; Waiver

No amendment, modification or waiver of any provision of this Letter shall be effective unless in writing and signed by both parties. No failure or delay by either party in exercising any right shall operate as a waiver of that right.

10. Governing Law; Dispute Resolution

This Letter shall be governed by and construed in accordance with the laws of the Federative Republic of Brazil without regard to principles of conflict of laws. Any dispute arising out of or relating to this Letter shall be resolved through good faith negotiations between the parties and, if unresolved, by the competent courts in the forum agreed by the parties.

11. Entire Agreement; Severability

This Letter constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior oral or written agreements and understandings. If any provision of this Letter is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect.

Certification

The undersigned certify, under penalty of administrative and criminal sanctions applicable under Brazilian law for false statements, that the information and Documentation provided in connection with this Letter are true, complete and accurate to the best of their knowledge and belief.

Applicant (Company) Printed Name:

By:

Date:

Representative Printed Name:

By:

Date:

Enter text✕

What the Legal RDC ANVISA Letter Is and When It’s Used

The Legal RDC ANVISA Letter is a formal regulatory communication prepared by manufacturers, importers, or legal representatives to address matters governed by ANVISA's RDC resolutions. It typically accompanies product registration, technical dossiers, clarification requests, or compliance statements for health-related products destined for the Brazilian market. While the letter itself follows Brazilian regulatory requirements, U.S.-based teams preparing or e-signing the document should align internal controls with U.S. electronic signature law (ESIGN and UETA) and ensure translations, notarizations, and supporting exhibits meet both ANVISA expectations and any bilateral legal formalities required for cross-border submissions.

Why a Clear, Compliant Letter Matters

A properly drafted Legal RDC ANVISA Letter reduces processing delays, supports regulatory traceability, and documents corporate intent for product compliance. Clear scope, correct references to the RDC numbers, and authenticated signatures help avoid requests for additional information and potential administrative rejections.

Why a Clear, Compliant Letter Matters

Who Prepares and Signs This Letter

Typical users include regulatory affairs teams, in-house legal counsel, exporters, and authorized local representatives who manage Brazilian regulatory submissions.

  • Regulatory Affairs Teams responsible for dossier assembly and technical accuracy.
  • Legal Counsel or Compliance Officers verifying legal language and declarations.
  • Importers / Local Representatives who submit materials to ANVISA and accept legal responsibility.

Final signers may be company officers, designated agents, or local legal representatives; roles should be documented and match supporting authorization documents.

Essential Elements of a Professional RDC ANVISA Letter

A complete letter follows a predictable structure: clear identification of the RDC reference, product details, regulatory request or declaration, authorized signatory details, and attachments. Each section should be concise, accurate, and cross-referenced to supporting documents.

Header

Include company letterhead, ANVISA unit addressed, submission date, and the specific RDC number(s) referenced in the request or declaration.

Purpose

State the precise intent—registration, clarification, post-market report, or compliance attestation—and reference relevant application identifiers or protocol numbers.

Product Details

Provide product name, model or SKU, active ingredients, presentation, batch or lot numbers if applicable, and any registration codes previously issued.

Legal Declaration

Include the declarative language required by the RDC, naming applicable standards, conformity claims, and citations of the regulatory text relied upon.

Signatory Block

Provide the printed name, title, corporate authority statement, date, and an explicit statement that the signatory is authorized to bind the entity.

Attachments

List accompanying documents (technical dossier, translations, notarized powers of attorney) with filenames and exhibit references for easy cross-checking.

Stepwise Guide to Complete and Approve the Letter

Follow these sequential steps to prepare, review, sign, and submit a compliant RDC ANVISA Letter.

  • 01
    Draft: Populate core fields and cite the specific RDC provision being addressed.
  • 02
    Internal Review: Legal and regulatory teams verify language and supporting exhibits for consistency.
  • 03
    Authenticate: Obtain required notarizations, translations, or powers of attorney as applicable.
  • 04
    Submit: Send to ANVISA via the prescribed channel and retain proof of delivery and confirmation.

Typical Preparation and Submission Flow

This high-level flow shows the common path from drafting to regulatory receipt for cross-border regulatory letters.

  • Document Drafting: Create the letter and attach technical dossiers and certificates.
  • Translation & Notarization: Translate to Portuguese and notarize documents if ANVISA requires notarized copies.
  • Signature Collection: Collect authorized signatures using accepted authentication or in-person notarization.
  • Filing to ANVISA: Submit through ANVISA's portal or official channel and record acknowledgment.

Configuring an Online Workflow for the Letter

When using an e-signature platform, configure fields and authentication options to reflect legal and ANVISA requirements.

Field Configuration
Document Format Upload as PDF/A or PDF; retain originals in DOCX for edits
Authentication Use email + SMS code or stronger methods for signer attribution
Attachments Include translated documents and notarized exhibits as separate files
Retention Enable platform retention and export signed PDF with audit trail

Technical Formats and Integration Considerations

Ensure your signing platform supports PDF/A export, multi-file attachments, official audit trails, and optional advanced signer authentication for regulatory records.

  • File Formats: PDF, PDF/A, DOCX, and supporting image files.
  • Integrations: Connectors with Google Workspace, Microsoft 365, and NetSuite streamline records.
  • Authentication: Email, SMS codes, two-factor, and enterprise SSO options.

Choose a platform that produces a tamper-evident signed PDF with an attached certificate of completion and preserves metadata like timestamps, IP addresses, and signer attribution for audit purposes.

Timing Considerations and Typical Processing Windows

Timelines for drafting, translation, and regulatory review vary; plan internal lead time and track official ANVISA acknowledgments closely.

Internal Drafting:

Typically 3–10 business days depending on complexity and available exhibits.

Translation & Notarization:

Allow 3–14 business days for certified translations and any notary steps.

ANVISA Review:

Review duration varies widely; expect several weeks to months for substantive reviews.

Corrections & Replies:

Respond promptly; delays in replies commonly extend total processing time.

Recordkeeping:

Retain submission proof and signed letter indefinitely per company retention policy.

Key Milestones from Draft to Acknowledgment

Track these numbered milestones to monitor progress and compliance throughout the submission lifecycle.

01

Milestone 1 — Draft Complete

Document finalized with product and RDC references; attachments listed.

02

Milestone 2 — Internal Approval

Legal and regulatory sign-off obtained and recorded.

03

Milestone 3 — Signatures & Notary

Authorized signature collected, and notarization completed if required.

04

Milestone 4 — Submission Acknowledged

ANVISA receipt or portal acknowledgment captured and archived.

Security and Compliance Features to Preserve Record Integrity

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
Certifications: SOC 2 Type II, ISO 27001, PCI DSS
Healthcare Support: HIPAA-compliant with BAA available
Regulatory: 21 CFR Part 11 capability supported
Accessibility: WCAG 2.0 Level AA compliant
Audit Trail: Tamper-evident audit logs and certificates

Risks and Consequences of Errors in the Letter

Processing Delays: Submission may be deferred or rejected
Application Rejection: Incomplete references can cause outright refusal
Administrative Fines: Regulatory fines or corrective orders possible
Import Holds: Products may be detained at entry
Contractual Exposure: Breach of distribution agreements risk
Reputational Harm: Stakeholder trust and market access affected

Common Pitfalls to Avoid When Preparing the Letter

  • Using inconsistent product identifiers between the letter and technical dossier leads to classification and review errors.
  • Failing to provide certified translations causes processing delays and may require re-submission with corrected documents.
  • Omitting notarized powers of attorney for local representatives can invalidate the signatory's authority.
  • Relying solely on scanned handwritten signatures without an audit trail complicates attribution and may be insufficient for compliance.

Practical Examples of Letter Use

Realistic scenarios illustrate how different organizations prepare and route an RDC ANVISA Letter to meet regulatory needs.

Case Study: Manufacturer Clarification

A U.S. medical device firm submits a clarification letter to correct product nomenclature in its dossier.

  • The point: correct identification avoids misclassification.
  • Outcome: the company attached a notarized translation and recorded the submission receipt, reducing follow-up questions and preventing a resubmission.

Case Study: Local Rep Authorization

An importer files a registration update with a power of attorney and signed RDC letter.

  • The point: authorized local representation is essential.
  • Outcome: proper notarization and an explicit authorization clause enabled acceptance on first review and preserved import continuity.

Practical Tips for Accurate and Efficient Completion

Apply these practical measures to reduce errors and streamline regulatory acceptance.

Use a Standard Template
Maintain a vetted template that contains required sections and preformatted references to RDC provisions to minimize drafting errors.
Confirm Signatory Authority
Attach current corporate documents or notarized powers of attorney showing the signer's authority to act for the company.
Bundle Supporting Evidence
Attach a concise exhibit index and label each file consistently so reviewers can cross-reference claims without searching.
Preserve the Audit Trail
If signing electronically, ensure the platform provides a tamper-evident PDF with timestamps, IP logs, and a completion certificate.

Comparing eSignature Providers for Letter Preparation and Signing

Select an eSignature provider that supports required formats, audit trails, notarization workflows, and applicable compliance frameworks; pricing models and feature sets vary by vendor.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes Yes
Audit Trail Yes Yes Yes Yes Yes
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

Frequently Asked Questions and Troubleshooting

Answers to common questions about preparing, authenticating, and submitting an RDC ANVISA Letter from U.S.-based teams.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users