Modeling a Committee, Not a Chain
Most approval workflows are chains: A, then B, then C. Regulated label review is a different shape — a committee. Legal, regulatory, packaging, and marketing must all approve, none depends on another's output, and the label advances only when the slowest reviewer finishes. Modeling that as a chain wastes exactly as much time as the chain is long.
The architecture that serves this infant nutrition leader's US label operations models the committee directly, using DocQ's parallel workflow steps as the core primitive.
Anatomy of a Lane
Each of the seven workflows follows the same skeleton, tuned per label type:
- Initiation — marketing submits the label through the request form, with a brand-sponsor action step confirming ownership.
- On deck — a staging step that queues labels into review in order, so the committee always works from a clean plate.
- Committee review (parallel) — a parallel step fanning out to four simultaneous review branches: legal, regulatory, packaging, and marketing. Each branch carries its own approval action; the step completes only when all branches approve.
- Final approval gate — a department-level sign-off after the committee, the last line before a label is official.
- Change loop — rejection at any branch routes into a dedicated change path with its own parallel committee step, so revisions re-run review without re-entering initiation.
The lanes differ where the label types differ. The Spanish lanes add a dedicated Spanish review step; the hospital lanes add their review path including French; the without-packaging variants omit the packaging branch entirely rather than making packaging reviewers rubber-stamp digital labels.
Why Seven Workflows Instead of One
A single workflow with conditional routing could, in principle, express all of this. The deployment deliberately didn't do that. Seven explicit lanes mean the submitter makes exactly one decision — which lane — and each lane stays simple enough to read on one screen. In a regulated environment, a workflow a compliance officer can read end to end is worth more than a clever one.
The AI Forms Import
The most unusual part of the build touched no workflow at all. The team's institutional process lived in legacy label request and change-control forms — and the deployment carried them forward by having AI read the originals and regenerate them as native DocQ artifacts: form definitions with the same fields and structure, and document templates wired to the workflows.
Technically, this collapsed what is usually the slowest part of a forms migration — manual field-by-field recreation — into a review-and-adjust exercise. Operationally, it meant the system launched speaking the organization's existing language.
The Audit Property
Because every step is a DocQ workflow step, every review action — who approved, who requested changes, what changed, when — accrues to the label's record as a by-product of processing. Regulatory evidence for any label, across any number of revision loops, is a lookup.
That's the architecture in one sentence: a committee that convenes in parallel, lanes that match the label, a change loop that respects everyone's time, and a paper trail that writes itself.
