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 cosmetic lab samples, approvals, and audit-ready change history, design the system around traceability, controlled workflows, and immutable records. Here’s a practical setup approach.

1) Define the core workflow

Map the lifecycle of a cosmetic sample from start to finish:

1. Request created
2. Sample assigned / formulated
3. Testing / evaluation
4. Reviewer approval or rejection
5. Revision loop if needed
6. Final approval
7. Archive with full history

For each step, decide:

• who can act,
• what fields are required,
• what status changes are allowed,
• what evidence must be attached.

---

2) Set up the data model

At minimum, track these records:

Sample record

Include:

• Sample ID
• Product name / project name
• Formula version
• Batch or lot number
• Date created
• Created by
• Owner / department
• Current status
• Linked attachments
• Linked approval record
• Linked test results

Approval record

Include:

• Approver name
• Role
• Decision: approved / rejected / needs changes
• Timestamp
• Comments
• Signature or e-signature identifier
• Version approved

Change history / audit log

Capture every change:

• field changed
• old value
• new value
• who changed it
• when it changed
• reason for change
• record version
• IP/device metadata if needed

This history should be append-only so edits don’t overwrite prior values.

---

3) Use role-based permissions

Typical roles:

• Lab Technician: create and update sample data
• Formulator: edit formula details, upload revisions
• Reviewer / QA: approve or reject
• Manager: oversee workflows and exceptions
• Admin: configure system, but not necessarily approve content

Best practice:

• separate “create/edit” permissions from “approve” permissions,
• prevent one user from approving their own work if compliance requires independence.

---

4) Build status controls

Create fixed statuses such as:

• Draft
• In Preparation
• Submitted for Review
• Under Testing
• Changes Requested
• Approved
• Rejected
• Archived

Only allow valid transitions. Example:

• Draft → In Preparation
• In Preparation → Submitted for Review
• Submitted for Review → Approved / Changes Requested / Rejected
• Changes Requested → In Preparation
• Approved → Archived

This prevents unauthorized or confusing changes.

---

5) Make change history audit-ready

For audit readiness, your system should log:

• every create, edit, delete, and approval action
• before/after values for each changed field
• timestamp in a consistent timezone
• user identity
• reason for change
• version number
• electronic signature events if used

Important:
Avoid allowing hard deletes. Instead, use soft delete or status-based archiving so records remain reviewable.

If your industry or customers care about regulated recordkeeping, consider:

• immutable audit log tables,
• electronic signatures,
• record retention policies,
• time-stamped approvals,
• access logs.

---

6) Attach supporting documents

For cosmetic samples, attach:

• formula sheets
• lab notes
• stability test results
• sensory evaluation forms
• safety assessments
• batch manufacturing records
• images of sample packaging
• emails or review notes if needed

Store these with version control so reviewers see the exact document set tied to the approved sample.

---

7) Add version control for formulas and samples

Cosmetic samples often iterate. Use versioning like:

• Formula A v1.0
• Formula A v1.1
• Formula A v2.0

Each revision should link back to the previous version and preserve the approval trail.
Never overwrite a previously approved formula—create a new version.

---

8) Configure notifications and task routing

Set alerts for:

• sample submitted for approval
• approval overdue
• changes requested
• testing completed
• final approval granted

Route tasks automatically to the right team based on:

• product type
• region
• ingredient category
• required reviewer group

---

9) Add search and traceability features

Make sure users can find records by:

• sample ID
• formula name
• batch/lot number
• approver
• date range
• status
• ingredient
• project

For traceability, support “forward” and “backward” lookup:

• from sample to approvals/tests/versions
• from ingredient or batch to all affected samples

---

10) Prepare for audits

To be audit-ready, your system should support:

• exportable audit trails
• read-only archived records
• timestamped approval history
• user access reports
• retention schedules
• complete record reconstruction by sample ID

Auditors often want to see:

• who changed what,
• why it changed,
• when it changed,
• who approved it,
• what version was approved.

---

11) Choose build vs buy

Buy if you need speed

Look for software with:

• configurable workflows
• e-signatures
• audit trail
• role-based access
• document management
• version control
• reporting

Build if you need customization

If building custom software, use:

• relational database for core records
• append-only audit tables
• workflow engine
• document storage with versioning
• authentication/authorization layer
• reporting/dashboard layer

---

12) Recommended implementation checklist

Use this checklist to launch:

• Define sample lifecycle statuses
• Define user roles and permissions
• Create sample, approval, and audit log tables
• Add version control for formulas and documents
• Enforce status transition rules
• Enable timestamped approvals and signatures
• Set up notifications and task routing
• Restrict deletes and preserve history
• Add search and export capabilities
• Test with a real sample workflow
• Train users on approved process
• Validate audit trails and reports

---

Simple recommended structure

A good minimum structure is:

• Samples
• Sample Versions
• Test Results
• Approvals
• Audit Logs
• Attachments
• Users/Roles
• Workflow Statuses

---

If you want, I can also give you:

1. a database schema for this setup,
2. a workflow diagram, or
3. a list of software features to ask vendors for.