How do I set up sample tracking software for cosmetic lab samples, approvals, and audit-ready change history?

To set up sample tracking software for a cosmetic lab, aim for a workflow that links sample identity, test/approval status, versioned changes, and a complete audit trail. Here’s a practical setup approach.

1) Define the core workflow

Typical cosmetic sample flow:

1. Sample received / created
2. Formula or batch version assigned
3. Lab testing
4. Review and approval
5. Release / reject / rework
6. Archived with full history

Your software should support each step with timestamps, users, and status changes.

2) Track the right data fields

For each sample, capture:

• Sample ID: unique, immutable identifier
• Product name / project name
• Formula version or batch version
• Sample type: stability, microbiology, sensory, packaging compatibility, etc.
• Created by / received from
• Date created / received
• Current status: in testing, pending approval, approved, rejected, on hold
• Assigned tester / reviewer
• Spec limits / test plan
• Results: pH, viscosity, appearance, odor, stability notes, etc.
• Attachments: COA, test sheets, photos, approvals
• Linked change request: why the sample changed
• Disposition: approved, rejected, needs reformulation

3) Use version control for formulations and documents

For audit-ready history, avoid overwriting records.

• Store each formula revision as a new version
• Keep the previous version read-only
• Record:
  • what changed
  • who changed it
  • when it changed
  • why it changed
• Version all related documents too:
  • test methods
  • labels
  • specifications
  • approval forms

4) Build an approval workflow

Use configurable approval states such as:

• Draft
• In review
• QA review
• Regulatory review
• Approved
• Rejected
• Superseded

Best practice:

• Require named approvers
• Capture electronic signature / approval timestamp
• Prevent approvals without required test results
• Allow comments and required rejection reasons

5) Make the audit trail immutable

To be audit-ready, the system should log:

• record creation
• edits to fields
• status changes
• approvals/rejections
• attachment uploads/deletions
• user login/access if needed

Each log entry should include:

• user
• date/time
• action
• before/after values
• reason for change
• record/version affected

Avoid systems that let users edit or delete history. Audit logs should be append-only.

6) Set permissions and roles

Define roles like:

• Lab technician: create samples, enter results
• Reviewer/QA: approve or reject
• Formulator: create revisions
• Regulatory: review compliance-related changes
• Admin: manage settings, not alter history

Use role-based access control so users only see/edit what they need.

7) Standardize naming and identifiers

Use a consistent ID format, for example:

• COS-2026-00123
• PROJ-PRM-015-V3
• STAB-LOT-042-A

This helps with traceability across samples, formulas, test results, and change requests.

8) Add required checks before approval

Configure validation rules such as:

• all required tests completed
• mandatory attachments present
• reviewer assigned
• specification fields populated
• no unresolved deviations
• latest formula version used

This reduces mistakes and makes approval defensible during audits.

9) Create dashboards and reports

Useful reports include:

• samples by status
• samples awaiting approval
• version history by formula
• rejected samples and reasons
• overdue tests
• audit log by date/user
• change history for a sample or formula

10) Ensure compliance-friendly features

If you need regulated or audit-heavy operations, look for:

• electronic signatures
• time-stamped audit trails
• data retention controls
• record locking after approval
• exportable audit reports
• backup and restore
• validation documentation for the software itself

Depending on your region and quality system, you may need alignment with ISO 22716, 21 CFR Part 11-like controls, or internal GMP requirements.

11) Recommended system structure

A simple structure:

• Samples table
• Formulations table
• Test results table
• Approvals table
• Change requests table
• Audit log table
• Attachments/document library

Link records by sample ID and version number.

12) Implementation approach

You can implement this in:

• a LIMS
• a QMS
• a custom database app
• a no-code workflow tool with audit logging

Choose a platform that supports:

• versioning
• workflows
• permissions
• immutable logs
• attachments
• reporting

13) Minimum viable setup

If you want the simplest audit-ready version, start with:

• unique sample IDs
• status workflow
• versioned formula records
• required approval fields
• immutable audit log
• role-based access
• attachment storage
• exportable reports

14) Example workflow

1. Formulator creates Sample COS-2026-00123-V1
2. Lab logs tests and uploads results
3. QA reviews results and comments
4. Approver signs off electronically
5. Status changes to Approved
6. Any later formula change creates V2, not an overwrite
7. Audit log captures all actions

If you want, I can also help you with:

• a database schema
• a sample workflow diagram
• a SOP checklist
• or a software requirements spec for this system.