Writing a brief for a brewery consultant that gets results

Why a brief matters

Many brewery owners call a consultant with a single sentence: the beer is not right, or we need help with the brewery. The consultant then spends the first visit discovering what the owner could have written in an hour. Worse, the work can drift towards whatever the consultant notices first instead of what the owner needs most.

A brief does not need to be long. Two pages is usually enough. It needs to be clear about the problem, the context and what success looks like.

Describe the business and the brewery

Start with a short description: brewpub or production brewery, city, years open, brewhouse size, number of fermenters and bright tanks, packaging format and approximate monthly volume. List the core beers. Say who brews, how experienced they are and who makes decisions. Include anything unusual, such as a borewell water supply, a recent equipment change or a new owner.

State the problem plainly

Describe what is wrong in specific terms. "Our wheat beer has tasted sour in three of the last six batches" is far more useful than "quality issues". Say when the problem started, how often it happens, what has already been tried and what happened when it was tried. If you have more than one problem, rank them. A consultant who knows your top priority can plan the work around it.

If you are not sure what the problem is, say so. Our guide to what a brewery health check covers describes a structured way to find out.

Be honest about what has gone wrong before, including any earlier consultant. If a previous engagement failed, say why you think it did. That helps the next consultant avoid repeating it and shows them which approaches your team has already tried and rejected.

Describe the team too. A consultant planning training needs to know who will be trained, how experienced they are and how much time they can give. A plan that assumes a full-time assistant brewer will not work if your assistant also runs the bar.

List the data you have

Tell the consultant what records exist: brew logs, fermentation records, recipe sheets, SOPs, lab results, sales data by beer, utility bills and maintenance records. Say honestly where records are missing. A consultant can plan around missing data, but only if they know about it in advance. Sending records before the first visit is one of the simplest ways to get more out of the engagement.

Define success

Write down what you want to be different when the work is done. Examples include:

• No sour batches of the wheat beer for three months.
• Brewhouse efficiency consistently within a target range.
• A packaging line running with oxygen pickup at an agreed level.
• Written SOPs for every core task.
• A head brewer who can run fermentation troubleshooting alone.

Measurable goals make it possible to judge the work afterwards. They also stop the engagement from drifting.

Add one success measure for the team as well as for the beer. For example, the assistant brewer can carry out the new yeast count and viability check without help. That keeps the engagement honest about leaving skills behind.

Avoid goals that depend on things outside the brewery's control, such as a sales figure that depends on the weather or a competitor closing.

Constraints, budget and access

Say what limits the work: budget range, deadlines such as a launch date or a licence inspection, equipment you cannot replace, staff who are only available on certain days and areas where you do not want changes. Give a realistic budget range if you can. It lets the consultant propose work that fits rather than a plan you cannot afford.

Explain access: when the consultant can visit, who will be available on site and how they can reach the decision maker. A consultant who cannot reach anyone with authority will struggle to get changes made.

Read the reply carefully

A good consultant reads your brief, asks questions and proposes a scope that responds to it. Be wary of a reply that ignores the brief and offers a standard package. Our guides on when to hire a consultant brewmaster and choosing between a consultant or full-time head brewer cover the wider decision. The brief is your first test of whether the consultant actually listens.

Common questions

How long should a consultancy brief be?

Usually one or two pages. It should cover the business, the problem, the data available, what success looks like, constraints and access.

Should I include a budget in the brief?

A realistic range helps. It lets the consultant propose work that fits instead of a plan you cannot afford.

What if I do not know exactly what the problem is?

Say so in the brief and describe the symptoms. A health check is a structured way to find the underlying problem before deeper work starts.