How to Use the TTB Wine Label Copy Writer Prompt Before Your Next COLA Application

Wine labels have two jobs that pull in different directions. The front and back need to sell the bottle, and every word also has to hold up when TTB reviews the label for a Certificate of Label Approval. Small wineries often write the story first and bolt the mandatory statements on later, which is how a lovely back label ends up with an appellation it cannot use or a bottler phrase the winery did not earn. The TTB Wine Label Copy Writer: Front and Back Label Text with Mandatory Statements Checked Before COLA Submission prompt flips that order. It checks what the facts allow, writes the required text, and only then writes the story.

What the prompt produces

1. An eligibility check that decides whether you can use a varietal name, which appellation fits, and whether a vintage date is allowed, based on the percentages you give it.
2. Front label copy with brand name, class or type, appellation, vintage, and alcohol content.
3. A bottler statement that matches what the winery actually did with the wine.
4. A back label with your story inside a word budget, followed by net contents, the sulfite declaration, and the Government Warning in its exact wording.
5. A claims review that lists words a reviewer could treat as claims, such as organic or reserve.
6. A pre-COLA checklist with type size items, placement checks, and the documents to keep on file.

How to fill the inputs

BrandName is the brand on the label plus any fanciful name. GrapeSources is the most important input: list each grape by percent and where it was grown, down to county, state, or AVA. The prompt uses this to test the varietal and appellation thresholds, so guesses here produce wrong labels.

Vintage is the year and the share of the wine from that year. AbvAndSize is the lab alcohol number and the container size. BottlerFacts says whether the winery grew, crushed, fermented, or only bottled the wine, which decides between phrases like Produced and Bottled by and Bottled by.

Additives covers the sulfite test result and any fining agents. StoryFacts is the raw material for the back label: site, farming, cellar choices, and pairing, plus a word limit that fits your label size.

Reading the example output

The example is a Washington Syrah with 82 percent of the fruit from one AVA and 18 percent from a county outside it. A few lessons stand out:

• The AVA does not qualify. Eighty two percent is under the 85 percent AVA minimum, so the label falls back to the state appellation, which covers all of the fruit.
• The varietal still works. Syrah is above the 75 percent minimum.
• Alcohol is stated as a number. At 14.6 percent the wine is above 14 percent, so Table Wine is not an option, and the stated figure cannot cross the 14 percent line under the tolerance rules.
• The AVA stays out of the story too. Naming it in the back label text could read as an appellation claim, so the story talks about the cobblestone block instead.
• Estate Bottled is refused. Part of the fruit was not grown by the winery inside the appellation.
• The Government Warning is verbatim, with only the words GOVERNMENT WARNING in bold capitals.

Tips for better results

Give exact percentages. A blend at 74 percent and one at 76 percent get different labels. If your numbers are close to a threshold, ask your winemaker to confirm them before drafting.

Keep the story factual. Night harvest, barrel time, and site details are easy to support with records. Words like sustainable, organic, or old vine need proof, and the claims review will flag them.

Check the printer proof, not the screen. Type size minimums are physical measurements, and a design that looks fine on a monitor can shrink below them in print.

Treat it as a drafting aid. The prompt says so in its own output. Regulations change, and TTB makes the approval decision, so read the current regulation text or ask your compliance consultant before you submit.

Mistakes to avoid

• Writing the back label first and squeezing mandatory text into what is left.
• Using a county or AVA name in the story when it is not the label appellation.
• Choosing a bottler phrase because it sounds better rather than because it is true.
• Leaving the sulfite declaration off because the wine had low added sulfites without checking the test result.

Who it is for

This prompt fits winery owners, winemakers who handle their own compliance, label designers working with small producers, and compliance consultants who want a faster first draft. It also works for importers who need a clean label brief for a foreign producer, as long as you add the importer details and country of origin.

Related PromptDig links

• Prompt: TTB Wine Label Copy Writer: Front and Back Label Text with Mandatory Statements Checked Before COLA Submission
• More writing prompts: Browse more prompts
• Have a compliance writing prompt that works? Share a prompt