The Most Scrutinized Square Inches in Retail
On an infant formula can, nothing is just design. Every claim is regulated, every ingredient line is checked, every translation is reviewed. In this industry a label error isn't a reprint — it's a regulatory event. Which is why, at one global infant nutrition leader, every label passes legal, regulatory, packaging, and marketing review before anything ships.
The reviews themselves were never the problem. The routing was.
The Shepherding Problem
Before automation, label approval at the company's US operations was a relay race run by email. Marketing initiated a label and then personally shepherded it: send to legal, wait; forward to regulatory, wait; on to packaging, wait; back through marketing. Four reviews that had no dependency on each other ran one after another, because email has no concept of "everyone look at this at once."
And when a reviewer requested changes — which, with regulated labels, is routine — the shepherding started over. The cost wasn't just elapsed weeks per label; it was that nobody could say at any moment where a label actually stood.
Committee Review, As a System
The approval system built on DocQ turns the relay race into a committee. When a label enters review, it fans out to all four functions in parallel — legal, regulatory, packaging, and marketing see it simultaneously, each with their own approval action. An "on deck" staging step queues labels into the committee in order, and a final approval gate sits after it: no label advances until every review clears.
Label types get their own lanes — seven workflows in all. Standard labels, legal-and-packaging fast-tracks, digital variants that skip packaging review, Spanish-language labels with a dedicated Spanish review step, and hospital/medical product labels with their own review path including French. Choosing the lane is the only routing decision a human makes; everything after is the system's job.
Crucially, change requests don't restart the world. A dedicated change path re-runs its own parallel committee on the revision — the label loops through review, not through the entire process.
Keeping the Forms People Knew
The quiet masterstroke of the deployment wasn't a workflow at all. The team had years of process encoded in its label request and change-control forms — documents every stakeholder could fill in from memory. Replacing them with unfamiliar screens would have traded routing friction for adoption friction.
Instead, AI read the legacy forms and rebuilt them as native DocQ forms and document templates: the same fields, the same structure, now driving the automation directly. Day one looked familiar to everyone — except the part where the label routed itself.
Weeks to Days
The result is approval cycles measured in days instead of weeks, with every review, approval, and change logged on the label's record. The committee still makes every decision. The system just makes sure the committee convenes instantly, in parallel, every time — and that the evidence files itself.
