Newsletter ideas for fishing guides

A newsletter earns its place when it tells a reader something about your water they could not have learned without you. That is a high bar and it is also the only one, because the alternative, a round-up any business could send, is the reason most guiding newsletters stop after four issues. The good news is that the raw material is public and almost nobody uses it. The fisheries service runs a searchable database of recreational fishing statistics, the environmental agency publishes water quality by watershed, and the wildlife service runs a hatchery system whose work directly affects what swims past you. All free. Everything around the sending sits under the getting-booked hub.

Why do guiding newsletters die?

Because they were never about anything.

The first issue is enthusiasm, the second is a photograph, the third is an apology for the gap, and there is no fourth.

What is missing is a subject: a recurring thing the newsletter is for, which survives a month when nothing exciting happened.

The operations that keep going have one, and it is almost always the water rather than the business.

A newsletter about what the water is doing has content in February, in a blown-out week, and in a season when the fishing was poor.

A newsletter about the business has content only when something happens, which is rarely.

Pick the subject first and the schedule becomes possible, rather than picking the schedule and hunting for content.

Which list receives it is worked out in the segmenting piece.

Big Outdoor, LA

What data exists about your fishery?

More than most guides have ever looked at.

The fisheries service maintains a searchable database of recreational fisheries statistics through its recreational information programme, allowing users to filter data by time series, geographic area, species, mode and other characteristics.

Public-use datasets and statistical analysis programs are published separately, and where the tool cannot answer a question, a custom data request may be submitted under a published data request policy.

It also publishes a target schedule for estimate releases, and states plainly that preliminary statistics will be revised before being posted as final, and that the direction and magnitude of revisions cannot be predicted.

That caveat is worth carrying into anything you write from it, because a number quoted as final when it was preliminary is the kind of error a knowledgeable reader notices.

Note also that the tool itself can be unavailable: it was down for maintenance when read for this piece, which is a reminder to check rather than to assume.

Used carefully, it gives a guide something no competitor is saying, which is the whole point of a newsletter.

The tool is published by NOAA Fisheries.

What about water quality?

Published by watershed, and readable by anybody.

The environmental agency runs a public tool covering water quality at community, state and national level.

At community level it reports water quality in a local watershed, information on swimming, eating fish and aquatic life, restoration and protection efforts, permitted discharger information, identified issues including impairments and discharge violations, local drinking water information and water monitoring information.

At state level it covers the state's water programme, summaries of specific assessments, a statewide survey of water quality where available, and state drinking water metrics.

The agency attaches an honest caveat: more recent or more detailed water information may exist that is not yet available through its databases or other sources.

For a newsletter that is a genuinely interesting subject, because most clients have never considered the water they are standing in as something anybody measures.

Write it plainly, quote what the tool says, and add what you have seen yourself, keeping the two visibly separate.

The tool is published by the Environmental Protection Agency.

Texoma Striper Kings, TX

Is there anything worth saying about hatcheries?

Often, and clients find it fascinating.

The wildlife service runs a national fish hatchery system alongside its refuges, and its own summary describes a network of 570 national wildlife refuges, 70 fish hatcheries and 20 million acres of wilderness.

Where a hatchery feeds your water, what it does and when is a story with dates in it, which is exactly what a newsletter needs.

Clients who have never thought about where fish come from will read that further than anything you write about your boat.

It also positions the operation as connected to the fishery rather than merely extracting from it, which matters to a growing share of people booking.

Get the specifics from the hatchery itself rather than from memory or from another guide, since stocking schedules change.

And avoid implying that a stocking event settles what will happen on a particular day, because it does not.

The system is described by the US Fish and Wildlife Service.

What should a regular issue actually contain?

Three things, in the same order every time.

What the water has been doing, in two or three sentences, with any number attributed.

What that means for somebody thinking about a trip in the next six weeks, which is your judgement and should be labelled as such.

And one thing to look at, whether a photograph, a short clip or a link worth the click.

That structure is short enough to write in half an hour and repeatable enough to survive a bad month.

Add a single line about availability at the end rather than building the issue around it.

Resist adding sections, since every section you add is one you must fill next time.

What that availability line should say is covered in the winter campaign piece.

Should you write about mistakes?

Yes, and it is the most-read issue you will send.

An issue about something you got wrong, a day you misread, a decision that cost a fish, is more interesting than any success and considerably harder to write.

It also does something no promotional writing can, which is to make the reader trust the rest of what you say.

Keep it about your own judgement rather than about a client, a condition or another operation.

And do not resolve it into a lesson too neatly, since the honest version usually ends with something you still are not sure about.

One of those a year is plenty, and it should not be manufactured.

Where nothing went wrong, do not invent something, because a reader can tell.

The same honesty governs what a page claims, as covered in the testimonials piece.

How do you handle rule changes?

Carefully, and with the date on the page.

Regulations are the subject clients most want explained and the one where being wrong costs the most.

Write from the managing agency's own current page rather than from a forum, another guide, or last year's issue.

Name the rule, name where you read it, put the reading date beside it, and send the reader to the agency to confirm before they act.

Do not summarise a rule you have not read in full, and do not carry a summary forward from a previous issue without re-reading.

Before publishing anything of this kind, pull the exact current requirements straight from whichever agency manages your fishery.

Where a rule is genuinely unclear, say that it is unclear, which is more useful than a confident wrong answer.

How this discipline applies elsewhere is covered in the blogging piece.

How long should an issue be?

One screen, unless it is the annual explainer.

A regular issue that requires scrolling gets saved for later, which is the same as deleted.

Three short paragraphs and one image is a complete issue, and the discipline of that length is what makes it sustainable.

Once a year, write something long: a proper explanation of a fishery, a season, a technique or a decision.

That issue is the one people forward, and it earns its length because it is genuinely a reference rather than an update.

Put it on your site as a page too, since it will be the most useful thing you publish that year.

Everything else stays short.

The subject line that gets it opened is covered in the subject lines piece.

What about the off-season issue?

The most valuable one, and the hardest to fill.

Winter is when past clients are deciding about next year and when a guiding operation has least to report, which is an awkward pairing.

What works is shifting from reporting to explaining: the fishery's calendar, why a particular month behaves as it does, what a beginner should expect in each season.

None of that depends on anything happening, and all of it is more useful to a reader planning than any conditions report would be.

It is also the material that keeps working, since an explanation of a season is as true next winter as this one.

Write two of those in December, publish them across the off-season, and the quiet months stop being a problem.

Keep them on the site as well, because somebody searching for exactly that question will find them years later.

Where the seasonal calendar itself comes from is described in the piece on place pages.

Should clients be able to reply?

Yes, and the replies are the point.

A newsletter sent from an address nobody monitors is a broadcast, and readers treat broadcasts accordingly.

Sending from an address you actually read turns each issue into a conversation, and the replies are where the bookings come from.

End with a genuine question rather than a call to action: what do you want to know about the spring run, which month worked best for you, what would you like explained.

Answer every reply personally, which at this scale is a handful of messages and takes twenty minutes.

Keep a note of what people ask, since that list is next year's issues written for you.

An operation with a year of those questions never has to invent a subject again.

And where somebody replies about a date, treat it as an enquiry rather than as correspondence.

How those enquiries should be handled is set out in the welcome sequence piece.

Should photographs carry the issue?

One, and it should be doing a job.

An issue built around a gallery is a gallery, and readers treat it as one, which is to say they scroll past it.

One photograph illustrating the thing the issue is about does more than six good ones illustrating nothing in particular.

Caption it with what it shows and when, since a picture without a date is decoration and a picture with one is evidence.

Where the issue is about conditions, the useful photograph is of the water rather than of a fish, which is the opposite of the instinct.

Keep the file small enough not to slow the message, because a heavy newsletter loads badly on a phone at a launch.

And never use a photograph of a client without their agreement, however incidental it looks.

Which photographs are worth keeping is covered in the trip photos piece.

What tone should it take?

The one you use on the phone, written down.

Guiding newsletters fail in two directions: too corporate, which reads as a company nobody wants to hear from, or too casual, which reads as somebody with nothing to say.

The reliable middle is the way you actually explain something to a client on the phone: specific, unhurried, willing to say you are not sure.

That voice is hard to fake and easy to use, because you already have it.

Read a draft aloud before sending, which catches almost every sentence that has drifted into marketing.

Cut any sentence that could have appeared in another operation's newsletter unchanged, since that sentence is doing no work.

And sign it with your own name rather than the business name, because a newsletter from a person gets read and a newsletter from a company does not.

Why the sender name matters as much as the words is covered in the naming piece.

How do you know it is working?

Replies and bookings, not opens.

Open rates for a small list are noisy and increasingly reflect mail software rather than readers, which makes them a poor instrument for a decision.

What means something is whether anybody replies, whether the questions get better, and whether people mention the newsletter when they book.

Count those three by hand across a season, since at this scale a hand count is more accurate than any dashboard.

If an issue produced three replies and a booking, it worked, whatever a percentage says.

And if six months produce nothing at all, the subject is wrong rather than the frequency, which is worth fixing before sending more.

Give it a full year before judging, because a newsletter's effect is slow and cumulative by nature.

Why open rates mislead is explained in the spam and bounce piece.

Which habits kill a newsletter?

Seven, and the first is having no subject.

Starting without deciding what the newsletter is about, so every issue is invented from nothing.

Committing to monthly when your water produces six things a year worth saying.

Making it about the business rather than about the water.

Adding sections that then have to be filled forever.

Quoting a preliminary statistic as though it were final.

Carrying a rule summary forward without re-reading the source.

And apologising for the gap in every issue, which draws attention to the gap.

Where those messages land is determined by the deliverability piece.

What surprises operators here?

How much of it is already published.

A federal database lets you filter recreational fishing statistics by time series, area, species and mode, and almost nobody in this trade has opened it.

The second surprise is that water quality is reported at watershed level, with impairments and discharge violations included.

The third is the scale of the hatchery and refuge system sitting behind many fisheries, at seventy hatcheries and five hundred and seventy refuges.

The fourth is that the fisheries data comes with an explicit warning that preliminary figures will be revised unpredictably.

The fifth is that six good issues a year beats twelve padded ones, which nobody wants to hear and everybody finds true.

Taken together, the newsletter problem is a reading problem rather than a writing one.

How the writing itself should read is covered in the content calendar piece.

The newsletter, in order

Pick a subject, then a realistic rhythm.

Decide what the newsletter is about, and make it the water rather than the business.

Count what genuinely changes in a year and set the frequency from that count, not from a convention.

Use the same three-part structure every issue: what happened, what it means, one thing to look at.

Attribute every number and say when you read it, marking your own judgement as judgement.

Write one long explainer a year and publish it on your site as well.

Write one honest account of something you got wrong, and do not manufacture it.

Keep regular issues to one screen and add no new sections.

And stop apologising for gaps, since nobody was counting.