Customer story · Product

Plover ships releases two days sooner by drafting the writing from merged pull requests.

Education220 peopleAmsterdam, Netherlands

faster from code freeze to release
2 days
languages updated on release day
7
of release notes approved on the first draft
90%

Plover makes a learning platform used by 1,800 schools across Europe. Teachers use it to plan lessons, set work and track progress, and the product team ships a release every two weeks. Each release reaches teachers in seven languages.

The challenge

For Plover, a release is not finished when the code is merged. Teachers need release notes they can understand, the help center needs updating, and school administrators need a short summary of anything that changes how their staff work. All of it has to be translated before it goes live.

The writing came last and took longest. After code freeze, product managers spent a day turning merged pull requests into customer-facing notes. The support team then worked out which help articles were affected and rewrote them. Translation followed, and translators often had questions that went back to the product team.

“The code was routinely ready two or three days before the words were,” says Clara Novak, Director of Product. “We’d hold a finished release because the German help articles weren’t done. It was frustrating for everyone, especially engineering.”

The writing also varied. Each product manager had their own style, and teachers read release notes from five different people in a single month.

How they use Pilot

Plover connected GitHub, Linear and its help center content in Notion to Library, so Pilot can read every merged pull request, its linked issue and the help articles that describe the same feature.

At code freeze, an Autopilot agent reads the pull requests merged since the last release. It groups them by feature, ignores internal changes, and drafts three documents:

  • Release notes for teachers, in plain language and in Plover’s voice.
  • A short summary for school administrators that flags anything needing action.
  • A list of help articles that mention changed features, with suggested edits for each.

Product managers review the drafts in Write. Plover’s brand voice is set for an audience of busy teachers: short sentences, no jargon, and every change described in terms of what a teacher will see in class. When a product manager edits a draft, they use the suggestions as tracked changes, so the support lead can see exactly what changed in each help article.

Once the English versions are approved, Write translates them into the six other languages, keeping Plover’s glossary of education terms. Native-speaking colleagues in each market check the translations rather than writing them from scratch.

“Our product managers now edit release notes instead of writing them. Most weeks they change a sentence or two.”

The results

The time from code freeze to release has dropped by two days. Releases now go out on the planned day in all seven languages, and engineering no longer waits on documentation.

About 90% of release notes are approved on the first draft with only small edits. The help center is also more accurate: the agent catches articles that mention changed features, including ones the team would have missed. Support reports fewer tickets from teachers following outdated instructions after a release.

Teachers have noticed the change in tone. Plover’s in-app survey shows more teachers saying they read the release notes, and fewer asking support what a change means.

The product team uses Library well beyond releases. Product managers ask what teachers said about a feature in past interviews, or why a design decision was made, and get answers with links to the Linear issue or research note behind them.

“Shipping faster was the goal,” Novak says. “What we got as well was one consistent voice for every teacher, in every language, every two weeks.”

“The code used to be ready days before the words were. Now release notes, help updates and translations are drafted the moment we freeze, and the release goes out when the code is ready.”
Clara NovakDirector of Product, Plover
Clara Novak, Director of Product at Plover
All customer stories

Your next draft is already started

Join 14,000 teams that research, write and ship with Pilot.