Your voice, learned from your edits. You approve every rule.

The Desk learns your voice in four steps. First, it reads your own published writing and proposes a voice profile. Second, you edit and approve that profile, and nothing is written in it until you do. Third and fourth, as you work, it suggests general rules from the edits you make and from the pieces you turn down. Each rule waits for an owner or approver to apply or dismiss it. That's how writing in your voice works on the Desk: it learns from you, and nothing is added to the voice by itself.

Hynca Media Desk sets out the process in its guide "Writing in your voice: how the Desk learns from your words and your edits", published on 4 October 2026. This piece covers each step, what you control at each one, and how to give the Desk clearer signals so the rules it suggests are worth applying.

Where does the Desk's sense of your voice come from?

It starts with what you've already written. The Desk reads your site's own published writing and proposes a voice profile from it. The profile covers your tone, who your readers are, the areas you cover, words to use and avoid, and how your pieces open and close.

Not every organisation has a website full of articles. If you have a newsletter or a social account but no website, you paste in samples instead, and the Desk proposes a profile from those.

Each site can be written in UK or US English. For a British business, trade body or member organisation, that means British spelling and idiom in every piece: organise, colour, programme, licence. Your readers see the language they expect, and nobody on your team has to change "color" to "colour" by hand before a piece goes out.

At this stage the profile is a proposal. It's the Desk's reading of your writing, set out so you can check it.

Who signs off the voice before anything is written?

The owner does. In step two, the owner edits and approves the voice. Nothing is written in it until they do.

That approval isn't a one-off. If the voice is changed, it needs approving again. This is the first point of control, and it means the profile the Desk writes from is always one a person has read and accepted.

It's worth taking time over the proposed profile. Read it as you'd read guidance written for a new member of staff who'll be writing for you. If the tone is more formal than you'd like, change it. If the list of areas misses one your members care about, add it. If there's a word you never use, put it on the avoid list. Every piece the Desk drafts starts from this profile, so a few minutes here saves edits on every piece that follows.

What does the Desk learn from your edits?

Anyone on the team can edit a piece on the Desk before it goes out.

The Desk compares versions in two cases. The first is when an edited piece is approved on the Desk. The second is when a piece is changed in WordPress before it's published. In both cases it looks at what it wrote and what you ended up with, and suggests general rules from the difference.

The guide gives two examples of the kind of rule it means: cutting a kind of opener, or using shorter paragraphs. These describe habits in how you edit. If your team keeps splitting long paragraphs into shorter ones, that habit is something the Desk can name and put to you as a rule.

Small typo fixes aren't learned from. Correcting a slip won't turn into a rule about your voice, so you can tidy a piece without worrying that you're teaching the Desk something you didn't mean.

Where do suggested rules go, and who decides?

Suggested rules appear on your site's page under "Learned from your edits and rejections". An owner or approver applies or dismisses each one. Nothing is added to the voice by itself.

Here's how that plays out. Say the Desk tends to open pieces with a line of background before the news, and your editor keeps cutting that line. Each time an edited piece is approved, the Desk compares the versions. Once it sees the pattern, it suggests a rule: drop that kind of opener. The rule appears in the list on your site's page. Then it's your call. Apply it, and it becomes part of the voice the Desk writes in. Dismiss it, and the voice stays as it was.

Dismissing is a normal choice. An edit can be right for one story and wrong as a general rule. "Use shorter paragraphs" might suit your quick news items and not suit a longer guide for members. If a suggested rule wouldn't fit everything you publish, dismiss it. The Desk suggests; you decide.

What happens when you turn a piece down?

Turning a piece down asks what was wrong and why. There are seven reasons to choose from:

• the wrong story for the site
• already covered
• the wrong angle
• doesn't sound like us
• length or structure
• a fact is wrong
• something else

The Desk takes recent rejections into account when choosing the next stories. It may also suggest a rule, and that rule can be one of two kinds. A writing rule goes into the voice. A story rule goes into the site's "What to cover and avoid" notes. Either way, an owner applies or dismisses it.

So a rejection can shape two different things: how the Desk writes for you, and which stories it picks for you in the first place.

How to give the Desk clearer signals

Our view is simple. The Desk can only learn from what you show it, and it can only change the voice when an owner or approver says yes. The most useful thing you can do is make your signals clear: edit before you approve, and say exactly why when you turn a piece down. In practice, that comes down to three habits.

1. Make your changes where the Desk can see them. Edit on the Desk, or in WordPress before you publish. Those are the two places the guide says the Desk compares versions. Approving a piece you'd rather have changed, meaning to fix it later, gives the Desk nothing to compare. The guide doesn't describe what happens with edits made in WordPress after publication, so if you want an edit to count, make it before the piece goes live.
2. Pick the specific rejection reason. "Something else" is there for cases that genuinely don't fit. Where one of the other six fits, choose it.
3. Review the list of learned rules. Check "Learned from your edits and rejections" on your site's page and apply or dismiss each rule. A suggestion that sits there unread changes nothing, because nothing is added to the voice until someone decides. If you manage several client sites, each site has its own page and its own list, so it's worth building a regular look at each one into your routine.

One more common mistake is treating every edit as a lesson. Some edits are about one story: a local name spelled the way a client prefers, a sentence reworded because a member asked. When the Desk turns one of those into a suggested rule, dismiss it. Your rules should describe how you always write, and a one-off fix doesn't.

The voice is proposed by the Desk and approved by a person. Every rule after that is suggested by the Desk and applied by a person. Nothing about how it writes for your readers changes without you.

To see the whole process from setting up your voice to approval, read how the Desk works.