For DSPs
Craft & growing distilled spirits plants

Workflows, deadlines, and 27 CFR citations, organized around how your distillery actually runs.

What paperwork is required, when, and how do you actually complete it? That is the question every DSP keeps answering on paper, in spreadsheets, and across tabs at 11 p.m. Mashscript turns federal and state recordkeeping into a guided daily workflow — instead of a stack of PDFs.

TTB forms covered
9
Citations anchored
27 CFR
Pricing
SMB-ready
Today’s entries
Ledger

What happened in the distillery, in plain English

  • Fill27 CFR §19.292
    120 barrels entered at 110.0 proof, 53 gal. net
  • Loss27 CFR §19.291
    2.4 gal. — barrel #41, attributed to evaporation
  • Submit27 CFR §5
    COLA batch 0142 — class & appellation review

Plain-English intake, anchored to TTB forms and the underlying regulation.

Where it sitsDaily floor work, before month-end
What it replacesPDFs + spreadsheets + 11 p.m. tabs
What it never isA regulator, or a guess at the law
How it works

From spoken shift to record-ready in three moves.

Mashscript keeps a single source of truth per operation. The same intake feeds records, the records feed the form, the form feeds the deadline.

Ask about onboarding
  1. 01

    Build the plant profile

    DSP type, capacity, distillation & bottling lines, rickhouses, tanks, stills, contract production, distribution, exports, on-site sales. Twelve minutes, not twelve pages.

  2. 02

    Type what you did today

    "We filled 120 barrels." "A label was rejected." "We lost 2.4 gallons." Plain language. The system returns the exact records to update, in the order the regulation requires.

  3. 03

    Sign and retain

    Records, proof-gallon calculations, losses, label approvals and sign-offs keep a retention-ready archive with audit trail, anchored to TTB forms.

Records covered

Every TTB form relied on is anchored, version-controlled, and explained.

Each record ships with a plain-English explainer, a step-by-step completion path, a common-mistake checklist, and a citation that points back to the underlying regulation. The app stays a guide — never the regulator.

27 CFR §19.292Record

TTB monthly operations report

Compiles each month from the same intake — proof gallons, bottling, losses, transfers — without re-keying.

27 CFR §19.142Record

Formula & recipe filings

Versioned recipes with the ingredients, process, and class/type a TTB reviewer actually expects.

27 CFR §5 / §7Record

COLA label approvals

From intent to submission to approval — government fact, allergen line, appellation, mandatory.

27 CFR §19.351Record

Barrel & proof-gallon ledger

Fill, proof, dump, loss. Each line linked to the citation that requires it.

27 CFR §19.402Record

Transfers & bond data

In-bond removals, exports, and the bonded-wholesale and retail-trace rules at the receiving side.

27 CFR §19.291Record

Losses, samples & sign-offs

Evaporation, theft, samples for analysis. Employee initials where the regulation attaches.

DSP type
Production capacity
Distillation lines
Bottling lines
Rickhouses
Tanks
Stills
Contract production
Distribution
Exports
On-site sales
Bond data

What regulations apply to a bonded DSP at our size?

Filtered to the subset required by your capacity, state, and sales channels.

When are we on the hook for the operations report?

A deadline calendar informed by your bond type and reporting frequency.

What does the regulator actually want to see?

Per-field guidance with common-mistake checklists and source citations.

How long do we have to keep all of this?

Retention rules per record class, surfaced on the archive view.

Onboard with the operator, not a sales rep

Ship your first month of records with Mashscript on the line.

We onboard one DSP at a time. Write to mashscript@polsia.app and a founder will walk you through the plant profile, the deadlines, and the form path.