Retention answers one question: of the people you already had, how many are still with you? It is the number that tells you whether your programme is building something lasting or quietly replacing the same people every year. Vome measures it two different ways, and the first job is knowing which of the two you are asking for.
This article explains how to think about retention, then how to build it with trackers and KPIs. It is written for administrators setting up the Analytics module.

Two questions, and they are not interchangeable.
Rolling retention compares two stretches of time that sit next to each other. Of the people active in the earlier stretch, how many were active again in the later one? It is fast, it updates every month, and it tells you about right now.
Cohort retention takes a group who arrived at the same time and follows that same group forward. Of the people who started in March, how many were still active six months later? It is slower, because a programme four months old cannot have a twelve month figure, but it is the one that tells you whether people stay.
Most organisations want both. Rolling retention belongs on the dashboard you check weekly. Cohort retention is what you take to a board meeting.
You decide, and everything else follows from it. When you create a Retention and churn tracker you choose one of three definitions:
Pick this deliberately and write it down somewhere. Two people reading the same retention figure while holding different ideas of what active means will disagree forever.
Volunteering is not a monthly subscription. Somebody who helps in January and again in June has not left in March, they are simply someone who helps every few months. The activity window is how you tell Vome that.
On the tracker you set it to one of:
Six months is a sensible starting point for most volunteer programmes. Choose a window that matches how often your people actually turn up, not how often you would like them to.

Build one tracker rather than several. A tracker is a definition, and every KPI you hang off it inherits that definition, which is what keeps your numbers reconcilable.
A KPI built on the tracker can read any one of these:
If you only ever show one, show gross retention next to net retention. Gross alone cannot tell the difference between a programme that is holding on to people and one that is losing them but recruiting fast enough to hide it.
Three ways, depending on what you want to show.
One thing to know when you use Compare to on a retention KPI: retention is already a comparison between two windows, so the delta you are adding compares two rates. That is a legitimate thing to want, and the card says so underneath itself, but it is worth saying out loud before someone asks.
This is cohort retention, and it is one measure: Still active N periods after they came in, found under the Cohort retention group when you pick what a KPI measures.
Read the same KPI as a Trend graph instead and you get the whole retention curve on one card, every month from arrival onward, which shows the shape rather than three points on it.
Three readings, and they disagree about the same person, so this is a real choice rather than a display preference. The control is What counts as still here?
Unless you have a specific reason, leave it on the first one. It is the reading most people mean when they say somebody is still around.
Only people who have had time to reach the mark. A nine month figure is worked out across the groups that arrived at least nine months ago. Somebody who joined last month is not quietly counted as having failed to reach nine months, because they have not had the chance yet.
Cells that have not had time to happen are left empty rather than counted as zero. If a card reads blank, that is the system refusing to show you a misleading figure, not an error.
You can also narrow which arrivals are included, using Which joiners?:

Open the tracker and look at its Overview. Five controls shape what you see: Cohort starts at, Counts as retained, Grouped by, Follow for and Cohorts shown.
The Retention curve is the average across every group old enough to have reached each point. The shape is the useful part. A steep drop that then flattens points at the first experience, because the people who get past the early weeks tend to stay. A steady decline all the way along points at re-engagement instead.
The Cohort by cohort table puts one arrival month on each row and the months since arrival across the top. Reading a row left to right follows one group through time. Reading a column downward shows the history of a single checkpoint, so the three month column read down the page is your three month retention for every month in turn.
If a checkpoint you want is blank, raise Cohorts shown. It controls how far back the table reaches, and a twelve month figure needs groups that arrived at least twelve months ago.
Set the definition of active on the tracker to In the database (start date to archived date). Retention is then worked out from your roster: someone counts as retained for as long as they were on your books, from their start date to the date they were archived.
Two things follow automatically. Groups are built from the date people joined rather than a first shift, and the question of what counts as still here stops mattering, because membership runs in one unbroken stretch. The screen locks both controls and explains why.
One caveat worth checking first: profiles archived without an archive date are left out rather than guessed at. The screen reports how many that is, and if your data was imported it can be a large number.
Retention is a slow measure. The first reading tells you where you are, not whether you are improving. The second one, a quarter later, is the one worth acting on.
If you would like help choosing the definitions for your programme, submit a ticket or email support@vomevolunteer.zohodesk.com.