# Nothing ships unchecked.

> FCOS review and approval workflow: Admin, Editor and Reviewer roles, submit-for-review, the exact change a reviewer saw, approval-gated PDF export and a full activity log for nutrition labels and production SOPs.

Canonical: https://fcos.cloud/features/label-approval-workflow

Editors prepare labels, reviewers approve or send them back, and export unlocks only for the version that passed review.

## What is a label approval workflow?

A label approval workflow is the controlled path a label takes from draft to approved: someone prepares it, a separate reviewer checks it and approves or requests changes, and only the approved version can be exported or printed. Each decision is recorded with who made it and when.

## Why approvals live in FCOS

- **Four eyes on every label**: The person who edits is not the person who approves.
- **Reviewers see the change**: Re-reviews show what changed since the last approval.
- **An audit trail by default**: Every edit, submission and decision is attributed and timestamped.

## How a label moves

1. **Draft**: Editors prepare the product, ingredients and nutrition.
2. **Review**: Reviewers approve, or send it back with a comment.
3. **Export**: The approved version unlocks PDF export.

## What the workflow includes

- **Roles**: Admin, Editor and Reviewer, with permissions you can adjust.
- **Re-review on change**: Ingredient changes send approved labels back for review.
- **Approval-gated export**: PDF export only for the approved version.
- **Activity log**: Who changed what, and when, across the workspace.
- **Notifications**: Reviewers hear about submissions; editors hear about decisions.
- **SOP approvals**: Production SOPs use the same review, with versioned PDFs.

## Workspace role defaults

Admins can change what each role may do.

- Admin: everything, including team and costing
- Editor: edit products and nutrition, submit for review
- Reviewer: approve or reject labels and SOPs

### Can the same person edit and approve a label?

By default editors cannot approve. Reviewers and Admins approve, so a second person checks every label.

### What happens when an ingredient changes after approval?

The affected labels are flagged for re-review, and any production SOP built on them is flagged for a revision.

## Put approvals where your labels live.

Start free, invite an editor and a reviewer, and ship your next label through review.

- [Start free](https://fcos.cloud/register)
- [Talk to sales](https://fcos.cloud/contact)

## Related

- [Features](https://fcos.cloud/features)
- [Nutrition label maker](https://fcos.cloud/features/nutrition-label-software)
- [Production SOPs (New)](https://fcos.cloud/features/production-sop)
- [Compliance filings](https://fcos.cloud/features/compliance-filings)