What Information Should a Pharmaceutical Complaint Record Include?
A field-by-field guide to complaint source information, product identification, batch traceability, complaint narratives, evidence, safety cross-checks, follow-up, investigation records, and authorized closure documentation.
A Good Complaint Record Preserves the Source, Supports Traceability, and Makes Missing Information Visible
The exact fields depend on the product, market, company procedure, complaint system, and quality agreement. However, a well-structured record should show what was reported, when it was received, who reported it, which product and batch may be involved, what evidence exists, whether safety information is present, what follow-up was attempted, and how the case progressed through review, investigation, response, and authorized closure.
Complaint intake often begins with partial information. A caller may know the product but not the batch number. An email may include a photograph but no purchase details. A distributor may report multiple affected units without identifying whether any patient used the product.
The complaint record should not create false certainty. It should distinguish between information that was reported, information that was verified, information that is still missing, and conclusions made later by authorized personnel.
Three Principles for Complaint Record Quality
Preserve the Source
Retain the reporter’s original meaning, relevant wording, attachments, and intake-channel information.
Make Timing Traceable
Record receipt, awareness, transfer, follow-up, investigation, response, and closure dates according to the approved process.
Show Ownership and Handoffs
Identify who received, reviewed, transferred, investigated, responded to, and approved each controlled stage.
Master Complaint Record Checklist
The table below provides a practical structure. It is not a universal regulatory template and should be configured around applicable requirements and client-approved procedures.
| Record Section | Information Examples | Why It Matters |
|---|---|---|
| Case Identification | Complaint number, related identifiers, status, owner, source system | Supports unique identification and workflow control |
| Receipt and Awareness | Date and time received, channel, first awareness, country, market | Supports timing, escalation, and traceability |
| Reporter or Complainant | Name, role, organization, contact details, relationship to product or patient | Supports follow-up and source assessment |
| Product Identification | Product name, strength, dosage form, presentation, pack size, market | Helps identify the correct product and presentation |
| Batch and Traceability | Lot or batch, expiry, serial number where applicable, site, distributor, purchase details | Supports manufacturing and distribution review |
| Complaint Narrative | Original wording, defect description, quantity, discovery conditions, product-use context | Preserves what was reported |
| Evidence and Samples | Photographs, video, label images, receipts, product return, sample condition | Supports investigation preparation |
| Safety Cross-Check | Reporter, patient, suspect product, reaction, medication error, exposure, awareness date | Supports authorized Pharmacovigilance handoff |
| Follow-Up | Missing fields, questions, attempts, responses, unsuccessful contact, next action | Shows completeness efforts and status |
| Investigation | Investigation decision, rationale, records reviewed, findings, root cause, actions | Supports Quality review and approved conclusions |
| Response and Communication | Acknowledgement, interim communication, final response, approval, date sent | Maintains communication history |
| Closure and Trending | Closure approval, defect category, root-cause category, CAPA link, trend code, closure date | Supports authorized closure and analysis |
1. Case Identification and Administrative Details
Administrative fields help ensure that the record is unique, searchable, assigned, and traceable throughout its lifecycle. They may include:
Case Identity
- Unique complaint or case number
- Related external or partner identifier
- Source system and intake channel
- Current workflow status
- Assigned owner or queue
- Related Quality, PV, CAPA, or deviation numbers
Timing and Location
- Date and time received
- Date first known to the organization
- Country and market
- Language received
- Time-zone reference where relevant
- Transfer and acknowledgement timestamps
2. Reporter and Complainant Information
The record should capture enough information to identify the source according to the approved procedure and allow appropriate follow-up. Relevant fields may include:
- Name or documented source identifier
- Role, profession, department, or relationship to the product
- Company, pharmacy, distributor, hospital, or other organization
- Telephone, email, postal address, or preferred contact method
- Country and language
- Permission or restrictions affecting follow-up
- Relationship to the patient, if safety information is present
- Whether the reporter can provide the product, sample, photographs, or additional records
Do not invent missing source details
When information is unknown, the record should state that it is unknown, unavailable, not provided, or pending follow-up according to the organization’s approved terminology.
3. Product Identification
Product identification should be sufficiently specific to distinguish the affected medicinal product and presentation. Depending on the product, this may include:
Core Product Fields
- Product or brand name
- Active ingredient where relevant
- Strength or concentration
- Dosage form
- Route or delivery format
- Pack size and presentation
Market and Label Details
- Country or market supplied
- Label language
- Product code or presentation code
- Marketing Authorisation Holder
- Manufacturer or site where relevant
- Photograph or label copy reference
4. Batch, Lot, Expiry, and Distribution Traceability
Batch and distribution details help connect the complaint with manufacturing, testing, release, supply, and related complaint data. Useful information may include:
- Batch or lot number exactly as displayed
- Expiry or use-by date
- Serial number, device identifier, or unit code where applicable
- Manufacturing or packaging site
- Wholesaler, distributor, pharmacy, or customer
- Purchase date, receipt date, invoice, or order details
- Storage and transportation conditions reported by the source
- Quantity purchased, supplied, affected, used, and available
- Location of remaining units
- Availability of a returned product or sample
Record the exact batch text before normalizing it
If the system uses a normalized batch format, preserve the original value or source evidence as well. Small differences in letters, numbers, spacing, or symbols can affect traceability.
5. Complaint Description and Original Narrative
The narrative should describe what the reporter observed, when and how it was discovered, and what happened to the product. Important points may include:
- The reporter’s original wording or an accurate source-preserving transcription
- What appeared incorrect, damaged, missing, changed, or unexpected
- Where the issue was located on the product or package
- How many units were affected or examined
- Whether the issue was visible before opening, during use, or after use
- Whether the product was used or administered
- Whether similar units or packages were checked
- Environmental, storage, handling, or transportation context reported by the source
- Any actions already taken by the reporter or organization
Separate observation from interpretation
“The liquid contained visible particles” is a source observation. “The product was contaminated” is a conclusion that may require authorized investigation and assessment.
6. Evidence, Attachments, and Returned Product
Evidence should be indexed and linked to the complaint record so reviewers can understand what was received and its status. Examples include:
Digital Evidence
- Product and packaging photographs
- Video or audio files
- Scanned labels, receipts, and invoices
- Email threads or portal submissions
- Distributor or partner documentation
- File name, date, source, and attachment index
Physical Product or Sample
- Requested, available, or unavailable status
- Return instructions and authorization
- Shipping and tracking details
- Date received and receiving location
- Condition upon receipt
- Chain-of-custody or transfer history where required
7. Safety Information and Pharmacovigilance Cross-Check
Every complaint record should be reviewed according to an approved process for information that may require Pharmacovigilance handling. In the EU, a valid individual case safety report generally requires four minimum data elements.
Identifiable Reporter
Available information distinguishing the source of the safety report.
Identifiable Patient
Available information distinguishing the patient.
Suspected Product
A medicinal product identified or reasonably described as suspected.
Suspected Reaction
A reaction or event reported in association with the suspected product.
The complaint record may also need to capture medication errors, overdose, misuse, abuse, occupational exposure, pregnancy or breastfeeding exposure, therapeutic failure, product-use concerns, or other safety information according to the organization’s approved process.
8. Follow-Up and Missing-Information Tracking
Missing information should be visible and actionable. A follow-up log may include:
Identify Gap
Prioritize
Contact Source
Record Attempt
Update Record
Escalate or Close Gap
- Specific information requested
- Reason the information is relevant
- Person or organization contacted
- Date, time, channel, and language
- Follow-up attempt number
- Response received or no response
- New attachments or evidence
- Next action and due date
- Escalation status
- Reason follow-up was stopped or deemed unavailable
9. Investigation, Findings, and Action Records
Authorized Quality personnel determine whether an investigation is required and its scope. The complaint record or linked investigation record may include:
- Investigation decision and responsible person
- Reason for investigation or documented reason when no investigation is conducted
- Batch, production, packaging, laboratory, release, and distribution records reviewed
- Reference sample, retention sample, returned product, or evidence reviewed
- Related complaints, products, components, sites, or batches
- Investigation findings and approved conclusions
- Root-cause category or inability to identify root cause
- Correction, corrective action, preventive action, deviation, or nonconformance links
- Risk assessment and market-action references where applicable
- Approvals, completion dates, and effectiveness-check status
10. Response, Closure, and Trending Fields
Complaint closure should show that required activities were completed or appropriately transferred and that the authorized approval was documented. Useful fields may include:
What Does 21 CFR 211.198 Specifically Require?
For drug-product complaint files in the United States, written procedures must describe the handling of written and oral complaints. The regulation requires Quality Control review of complaints involving a possible failure to meet specifications, evaluation of whether an investigation is needed, and review for possible serious and unexpected adverse drug experiences.
The written record includes, where known, the product name and strength, lot number, complainant name, nature of the complaint, and reply to the complainant. Where an investigation is performed, findings and follow-up are included. When no investigation is conducted, the record includes the reason and the name of the responsible person.
Use regulatory minimums as a floor, not the entire data model
An effective complaint record often requires additional product, source, evidence, safety, investigation, communication, and traceability fields to support the complete operational workflow.
Common Complaint Record Quality Gaps
- The original narrative is replaced by a short interpretation
- Product strength, dosage form, presentation, or market is missing
- Batch information is recorded without preserving the source image
- Unknown fields are left blank without a documented status
- Safety information is not transferred or cross-referenced
- Attachments are stored outside the record without an index
- Follow-up attempts do not show dates, channels, or outcomes
- Investigation decisions and responsible personnel are unclear
- Related CAPA, deviation, or trend codes are not linked
- Closure occurs before required approvals and reconciliations are complete
How Operational Support Can Improve Record Completeness
Operational support can help standardize intake templates, validate mandatory fields, identify missing information, coordinate follow-up, index attachments, maintain Quality–PV links, prepare investigation documentation, reconcile statuses, and support reporting or legacy-data remediation.
The service should operate under approved procedures, defined permissions, escalation rules, quality controls, and clear responsibility boundaries. Final scientific, technical, medical, Quality, pharmacovigilance, and regulatory decisions remain with authorized personnel.
Pharmaceutical Complaint Record FAQs
General answers about complaint data fields, missing information, attachments, safety cross-checks, and closure.
Must every complaint field be complete before a record is created?
No. A complaint record should be created according to the approved intake process using the available information. Missing fields should be identified and followed up where appropriate rather than delaying traceable registration.
Should the original complaint narrative be retained?
Yes. The original wording or an accurate source-preserving transcription should be retained according to the approved procedure. A structured summary should not erase or replace essential source information.
What if the batch or lot number is unavailable?
The record should show that the batch information is unknown, unavailable, or pending follow-up. Attempts to obtain it and their outcomes should be documented.
Should photographs be stored inside the complaint record?
Photographs should be securely stored and linked or indexed to the complaint record according to the organization’s system and document-control process. The record should show the source, date, and status of the evidence.
What safety information should complaint intake capture?
Intake should capture available reporter, patient, suspected product, reaction or event, exposure, medication-error, and timing information and route it according to the approved Pharmacovigilance process.
Who decides whether a complaint requires an investigation?
The decision belongs to authorized Quality personnel under applicable procedures. The record should show the decision, responsible person, and documented rationale where required.
What should be completed before complaint closure?
Required follow-up, investigation, communication, Quality–PV reconciliation, related-action links, categorization, and approvals should be completed or appropriately documented according to the approved process.
Can an outsourcing provider maintain complaint records?
Operational record activities may be supported under approved procedures, contracts, access controls, quality oversight, escalation pathways, and clear responsibilities. Final regulated decisions remain with authorized client personnel.
Regulatory Sources Used for General Context
Readers should review current requirements, product-specific obligations, quality agreements, and approved company procedures.
