Adverse Cosmetic Event Report Form: Complete Checklist

What an adverse cosmetic event report form should capture

An adverse cosmetic event report form should preserve the original report, identify the person and product as far as the available evidence allows, capture the event without adding a diagnosis, link the relevant lot and label, record awareness time, and route the case to a qualified reviewer. It is an intake and evidence tool—not a substitute for an official regulatory form or a final reportability decision.

For US mandatory reporting, FDA currently provides Form FDA 3500A and mandatory-reporting resources. FDA's current 3500A instructions include cosmetic-specific direction. Verify the current edition and submission route before using a real case.

This checklist supports workflow design. It is not legal or medical advice.

Keep two records distinct

The internal intake record captures what the organization received and manages review. It can include routing, ownership, product lookup, label provenance, internal dates, and audit history.

The official submission uses the current fields, terminology, and instructions required by the applicable authority. Data may flow from the internal record, but an authorized person must review the mapping and final submission.

Trying to make one form serve both purposes can create gaps. An official form may not contain every internal workflow field. An internal form may use operational labels that do not equal the authority's definitions.

Section 1: Case identity and intake provenance

Include:

• internal case identifier;
• intake channel;
• original receipt date and time;
• person or system that received it;
• source message, call note, or attachment reference;
• date entered into the case system;
• duplicate or related-case check;
• current owner and status.

The original receipt time and data-entry time are separate facts. Preserve both. If a marketplace message was opened later, record the actual available evidence and send the clock question to qualified review rather than silently choosing the later time.

Section 2: Reporter and affected person

Capture only what the approved process needs:

• reporter name or identifier;
• reporter relationship to the affected person;
• safe contact method;
• permission and preference for follow-up;
• affected person's age or age group when relevant and supplied;
• sex or other relevant demographic information when required and supplied;
• country or jurisdiction relevant to routing;
• privacy or consent notes.

Do not place names or medical details into free-text fields merely because they are available. FDA's form instructions distinguish patient information from reporter information and include privacy directions. Follow the current instruction set and internal privacy controls.

Provide explicit states such as not supplied, unknown, declined, and not applicable. A blank field is ambiguous.

Section 3: Event narrative

Preserve:

• the reporter's own description;
• onset date or best estimate;
• status at the time of contact;
• body area involved;
• amount, frequency, start date, and stop date of product use when supplied;
• medical attention or intervention described by the reporter;
• hospitalization, infection, disability, disfigurement, or other outcome facts as reported;
• tests or documents supplied;
• follow-up questions and responses.

FDA's instructions for completing voluntary Form 3500 identify useful cosmetic details such as brand, professional-use status, amount and frequency of use, dates of use, and body part where applied. A responsible person's mandatory workflow must still follow the current mandatory instructions.

Do not convert “my scalp felt painful” into a medical diagnosis. If a reviewer adds terminology or an assessment, keep it separate from the original narrative and identify the reviewer.

Section 4: Cosmetic product identity

Capture:

• brand and exact product name;
• variant, shade, size, or format;
• product identifier or SKU;
• professional-use or retail-use category where relevant;
• lot or batch;
• best-by or use-by information if available;
• purchase source and date if supplied;
• order or shipment reference;
• start and stop dates of use;
• other products used at the same time.

The form should allow uncertain matches. A photo showing a similar package is not proof of the exact batch. Record how the product match was made.

Section 5: Label and packaging evidence

Link:

• photographs of the package and label supplied by the reporter;
• archived approved label artwork;
• label version and effective dates;
• ingredient and warning version;
• source and reviewer for the match;
• content hash or other immutable version reference;
• a note if the actual retail label is unavailable.

For US serious cosmetic adverse events, FDA states that the responsible person must include a copy of the label on or within the retail packaging. The internal checklist should make this a visible evidence item without assuming that the latest marketing image is sufficient.

Section 6: Review and reporting control

This section belongs to authorized reviewers, not initial customer support. Include:

• jurisdiction and rule set;
• configured responsible person;
• validated awareness time;
• seriousness assessment and basis;
• reportability decision and basis;
• internal review date;
• external due date;
• business-day calendar version;
• required submission materials;
• approver;
• submission status and reference;
• reason for a no-file or deferred decision.

The workflow can calculate a date after the rule and trigger are approved. It should not decide seriousness or reportability from a keyword in the narrative.

Section 7: Follow-up

Include:

• follow-up attempt date and method;
• questions asked;
• new information received;
• receipt date for each new item;
• updated reviewer assessment;
• whether a follow-up submission is required;
• follow-up due date;
• submission reference;
• case closure criteria.

Never overwrite the original event description. Use an ordered history so a reviewer can see what changed.

Worked synthetic form outline

Assume the following invented report:

• intake: customer-service email received 20 July 2026;
• product: SERUM-30;
• batch: LOT-26-071;
• order: ORDER-1049;
• use: once daily for three days, as reported;
• event: reporter describes a persistent rash and says they visited a clinic;
• label image: supplied;
• discharge or clinic record: not supplied;
• follow-up permission: yes.

The form should produce:

1. an immutable link to the original email;
2. a product match with batch and order evidence;
3. a label item marked supplied, awaiting version verification;
4. the rash and clinic visit in the reporter narrative;
5. medical documentation marked not supplied;
6. an immediate qualified-review task;
7. no automatic causality or seriousness conclusion;
8. a follow-up request recorded separately.

If a reviewer later confirms the applicable US serious-event workflow, that decision, rule version, due date, and submission preparation are added to the review section. The intake fields remain unchanged except through traceable corrections.

Form quality checklist

Data design

• Use structured fields for dates, status, product IDs, and evidence state.
• Keep narrative where the reporter's words matter.
• Distinguish unknown from not applicable.
• Record field provenance.
• Version material corrections.
• Prevent unsupported users from changing review decisions.

User experience

• Put urgent escalation instructions before long form fields.
• Use plain language for the reporter.
• Avoid asking the reporter to decide legal seriousness.
• Allow attachments through a protected channel.
• Show why sensitive information is requested.
• Save progress without losing the original receipt time.

Review control

• Separate intake permissions from regulatory approval.
• Require named ownership.
• Show missing evidence without blocking urgent escalation.
• Keep internal and external dates distinct.
• Record every transmission and acknowledgement.
• Test follow-up and duplicate-case behavior.

Privacy and security

• Minimize personal and health data.
• Restrict access by role and purpose.
• Encrypt data in transit and at rest under the approved design.
• Define retention and deletion rules.
• Avoid sending case details in ordinary notification messages.
• Test exports and support access.

Common form mistakes

Making every field mandatory

Reporters often do not have a lot number, exact date, or medical record at first contact. Blocking intake can delay escalation. Accept the case, show the gap, and follow up.

Combining supplied and assessed severity

Keep the reporter's statement and the qualified assessment in separate fields with separate provenance.

Using one current label for every historical case

Tie the case to the version actually associated with the unit when evidence permits.

Treating form completion as submission readiness

All configured fields can be populated while the wrong jurisdiction, product, label, or responsible person is selected.

Copying an official form into software and never updating it

FDA form editions and instructions change. Keep a source review date and a controlled mapping rather than a permanent screenshot.

Boundaries

An internal form can support consistent intake, evidence completeness, routing, dates, and audit history. It cannot:

• diagnose or treat an event;
• determine causality;
• replace qualified seriousness and reportability review;
• replace the current official form or instructions;
• guarantee a complete or accepted submission;
• establish compliance;
• authorize disclosure of sensitive information.

To try a synthetic intake and evidence checklist, run the CosmeticLedger sample and use the same page to request a paid form-and-workflow review. The sample does not notify FDA or make a regulatory decision.