Bulk-editing events
Select multiple events at once to update shared fields, reschedule dates, trim a range, or extend a series — all previewed before anything commits.
When a season changes — different venue, courts bumped from 4 to 6, series extended by three weeks — editing events one at a time gets old fast. Bulk editing lets you select up to 100 events, apply the same changes across all of them, and review a full plan before anything is saved.
Selecting events
On the scheduler calendar or list view, tick the events you want to edit. You can select across different dates and times — the bulk tool works on whatever you pick. The limit is 100 events per operation. If you have more than that, run the operation in two passes.
What you can change in one pass
Shared field updates — pick any combination: location, courts, capacity (max players), duration, description, waitlist mode, auto-invite, and the allow-player-score-entry toggle. Every selected event gets the same value. Leave a field blank and it's untouched — only the fields you fill in are merged.
Rescheduling — these are independent of the field updates and can be combined with them:
| Option | What it does |
|---|---|
| Set time of day | Moves every selected event to that start time |
| Snap to weekday | Shifts each event to the next occurrence of that day of the week |
| Trim range (new start / new end) | Events outside the range are deleted, not updated |
| Extend range (new start / new end) | Dates before the earliest or after the latest selected event get new occurrences auto-filled |
Preview before you commit
Every bulk operation is a two-step flow: Preview, then Confirm. The preview shows exactly what will happen — how many events will be updated, which dates will be deleted (if you trimmed the range), and which new dates will be generated (if you extended). No changes are written until you confirm. The preview and the commit run the same planning code, so what you see is what executes.
Warnings appear in the preview when something needs attention, like a selection that mixes different start times while auto-fill is active. The operation can still proceed; the warning tells you which time was used for the generated events.
Capacity bumps and waitlists
When you increase capacity on an event that has a waitlist, PickleFriend automatically promotes players off the waitlist to fill the new slots. A promotion email goes out per player, per event — queued during the commit for every event in the batch where the new capacity exceeds the old.
If a single event fails during the batch (a row that disappeared mid-request, for example), the others continue. The confirmation screen shows the count of updates, deletes, generated events, promotions, and any per-row errors.
Auto-fill for extended date ranges
When you set a new start or end date beyond the current selection, new events are generated to fill the gap. Each is cloned from the most recent non-trimmed event in your selection (after any field updates you applied), with chat messages, notices, and waitlist runtime state cleared so each new event starts fresh. Booking jobs carry over with empty volunteer slots.
The weekday pattern for generated events is inferred from the selection. If your selected events fall on Tuesdays and Thursdays, the generated events land on Tuesdays and Thursdays. The time of day comes from any explicit "set time" you chose, or from the template event if you didn't.
Auto-fill stops at 100 new events and warns you if it had to cut short. Extending a long season may require a second pass.
Ladder divisions
If your active group is a single ladder division, the bulk tool automatically applies the operation to the ladder's events as a whole. You don't need to switch divisions manually.
What's next
- Setting up a recurring series from scratch: Recurring leagues
- Waitlist modes and grace period options: Waitlists
- Adding events one at a time: Creating an event