Date range or series? Two ways to create recurring shifts

The short answer: if the work is ongoing, use a series. A date range gives you a pile of unrelated shifts that you will have to maintain one by one for as long as the program runs.

Overview

When you create shifts, Vome offers two ways to make more than one at a time: a date range and a series. They are mutually exclusive, you pick one at creation, and the choice is easy to make casually because both appear to do the same thing. Both fill your calendar with the same-looking shifts.

The difference shows up later, and by then it is expensive. This article is for administrators deciding which to use.

1. What a date range actually creates

Vome's own description is exact: a date range "creates a finite batch of standalone shifts between the start and end dates you pick. Each shift is independent. Edits and attendee changes do not carry over to the others."

Two words are doing the work there.

Finite. You name an end date and the generator stops. There is no ongoing thing left behind.

Standalone. Once generated, the shifts have no relationship to each other. Vome does not remember that they came from one pattern. They are simply forty shifts that happen to look alike.

2. What a series creates

A series is a rule plus a template, and it stays alive. Each dated shift is generated from that rule, much like a recurring event in a calendar app.

Because the rule persists:

Editing at the series level flows to every future shift.
Leaving the end date off keeps the schedule extending indefinitely. Vome generates roughly six months ahead and keeps going.
People can join the whole recurring schedule in one action instead of booking each occurrence.
Adding somebody from the series view puts them on every upcoming shift, from a start date you choose.

3. The difference in one line

A date range is an event that already happened to your calendar. A series is a rule that is still running.

Everything else follows from that.

4. What choosing a date range costs you later

None of these are bugs. They are what "standalone" means, and they are worth seeing before you commit.

A time change becomes N edits. The Tuesday slot moves from 9:00 to 9:30, and there is no "this and future" to apply it with. You open every remaining shift.
A regular becomes N reservations. Somebody commits to every Tuesday for the year, and there is nothing to enrol them in. You add them shift by shift, and again for every shift you create later.
Somebody leaving becomes N removals, with the same problem in reverse.
It stops silently. The range runs out, the shifts stop appearing, and nothing warns you. Usually this is noticed by the people who came to volunteer.
There is no commitment to report on. You have attendance at forty separate shifts rather than a person enrolled in a schedule.

5. Why a series stays manageable

This is the part worth knowing before you decide, because it is more capable than "it repeats" suggests.

Every change asks how far it reaches. Edit, cancel, assign, or remove, and you choose: this shift only, this and future shifts, or all shifts. The same scope applies to attendee changes, so ending one person's commitment from a date forward is one action.

One-off changes survive bulk edits. If you customised a single shift, a later series-wide edit skips the fields you changed by hand, so your exception is not quietly overwritten. When you do want the series value to win, a "Force every shift to match the series" checkbox appears and names the fields it will clear.

You can act on shifts that do not exist yet. Cancel or edit a date beyond the generation window and Vome records the instruction, then applies it when it creates that date.

Joining and leaving are real concepts. With series settings enabled on the opportunity, people join the recurring schedule, optionally choosing a start date and a commitment length within limits you set. Leaving offers its own scopes, including scheduling a last day.

6. Attention: each day and time pairing becomes its own series

If you set up a batch with more than one weekday or more than one time slot, you do not get one series. Every day-of-week and time-slot combination becomes a separate series.

So Monday 9:00 to 12:00 plus Wednesday 13:00 to 16:00 produces two series, managed independently. That is usually what you want, since somebody who commits to Mondays has not committed to Wednesdays. It does mean a series-level edit reaches one of them, not both, so plan your patterns deliberately rather than selecting every box in one pass.

7. When a date range is the right choice

It is not a trap, it is a different tool. Use it when the run of shifts is genuinely finite and genuinely unrelated:

A one-off event across several days. A three-day festival is three days of staffing, not an ongoing commitment.
A campaign with a hard end. A six-week seasonal drive that will not simply continue.
Shifts that differ from each other anyway. If you expect to customise most of them, the shared template earns you nothing.
Nobody is committing to the pattern. If people book one date at a time and never think of it as "their Tuesday", you do not need a schedule for them to join.

8. Can I convert a date range batch into a series?

No. There is no convert action. Shifts generated from a date range stay standalone for their whole life.

Changing your mind means cancelling the remaining shifts and creating a series in their place, which also means re-enrolling anybody already booked. That asymmetry is the reason to think about it at creation: choosing a series when you did not need one costs you almost nothing, while choosing a date range when you needed a series costs you a rebuild.

Summary

A date range creates a finite batch of standalone shifts. A series creates a living rule with a shared template.
With a date range, edits, additions and removals are per shift, forever.
A date range stops silently when it runs out. An open-ended series keeps extending itself.
A series scopes every change: this shift, this and future, or all.
One-off customisations survive series-wide edits unless you force them to match.
People join and leave a series as a commitment, rather than booking each date.
Each weekday and time-slot pairing becomes its own series.
Date range still wins for one-off events, fixed campaigns, and shifts nobody commits to as a pattern.
You cannot convert one into the other, so pick deliberately at creation.

Date range or shift series: which to use for recurring shifts