October 3, 2026 release

What's new

Forms

Build a form, and ask anything

Admin → Forms is new. Write a form from a set of question types — short and long answers, single and multiple choice, yes/no, numbers, dates and email addresses — and add descriptive text between questions to explain what comes next. Publish a form and it's live at its own link. Set it to Listed and it also answers at a readable web address and appears on your venue's public list of forms. Save any form as a template to start the next one faster, and remove a template once you no longer need it.

The builder is one place, in tabs: Questions, Settings, Share and Responses. Opened from an event, it adds a This event tab for that event's own settings.

Changes save as you make them, and publish when you're ready

There's no Save button. The builder saves every change as you make it and says Saving… then Saved. If a save fails, it retries and offers Retry, and it warns you before you leave with anything unsaved.

Editing a published form doesn't change what respondents see straight away. Your edits wait as Unpublished changes until you select Publish changes in the row pinned to the bottom of the builder. Anything that would affect people who've already answered, like removing an option they chose, is spelled out first, with the choice to email them. Discard changes puts a form back to what's live now, after saying what you'd lose. Preview shows the form exactly as a respondent will see it, unpublished changes included, at phone or desktop width. Nothing you submit in a preview is recorded.

If someone else changes a form while you're editing it, your next save stops rather than overwriting theirs, and offers to reload their version. Duplicating a form, or starting one from a template, keeps each question's answer limits.

Conditional questions, and changing a question's type

A question can be conditional: it appears only when an earlier answer calls for it, so people are asked only what applies to them. Only ask this question when appears as soon as there's an earlier question with a fixed set of answers to depend on, such as a choice or yes/no question — you no longer have to save the form first. Ask "Staying for dinner?" and then "Any dietary needs?" in one sitting. A Descriptive text block can be shown only to people who answered a certain way, too.

Remove now works on a question, or an option, you added in the same sitting. Anything Venvy already refuses to remove — a question another question's condition depends on, or an answer a condition watches for — is still refused, and still says why.

To change a question's type, pick a new one from its Question type menu. Before a question has any answers, every type is on offer. Once it has answers, you can still switch between short and long text, and from single choice to multiple choice. Multiple choice can go back to single choice as long as nobody has picked more than one option. If a change would remove the question's options, its limits on places, or another question's condition on it, Venvy tells you what will go before you confirm.

Put a form on an event, and collect by date

Every event has a Forms area, now a list of its forms; select one to open it in the builder. Add a form walks you through where it comes from, its questions, how it collects, and publishing. A form you add there is that event's own — its answers stay with the event, and editing it changes nothing anywhere else. (If you really do want one form shared across several events, that's offered separately so it's never chosen by accident.)

A form on a repeating event can collect its answers for each date, for each Repeating Set, or once for the whole schedule. Each date gets its own link, and the link reads as the date itself (…/2026-10-26), so the right one can go on the right night's program. When a listed form collects by date, visitors who arrive at the form's general address are asked which date they're answering for before they begin.

Only accept answers for a date is a switch on a form's Settings tab. While it's on, the form's own link doesn't show the questions. It lists the dates still ahead, and each one opens that date's own link, so every answer lands on an event and a date, never under Not from an event. With nothing ahead, the page says there's nothing open to sign up for right now. Forms you add on an event's Forms page start with it on, and so do forms that were already made there; forms made in Admin → Forms start with it off. Answers already under Not from an event stay there. While it's on, the Share tab explains what the form's own links do and where each event's links are.

When a form accepts responses

Accept responses on the Settings tab has a From date and an Until date. Before From, the form tells visitors it isn't open yet; after Until, that it's no longer accepting responses. Until includes that whole day. Leave either blank for no limit.

Under Answering more than once, turn on Accept one response per person. A second response from the same email address is refused, and the person is told plainly that they have already completed the form. Turning it on asks which question is the respondent's email address. Only a required email question, asked of everyone, can be chosen; where exactly one qualifies, Venvy picks it. Naming it matters on a form that asks for more than one address, such as your email and your supervisor's email. If you later delete that question or make it optional, the form says so and keeps accepting responses in the meantime.

Uniqueness follows the grouping the form collects into: once per date, once for the whole Schedule, or once per Repeating Set. A form on two events counts them separately. The address is the one the respondent types and isn't verified, so this stops someone answering twice but not someone determined to use a second address; the setting says so. Turning it on changes nothing already collected.

Places on an answer

In a question's Limits, under its options, put 20 against Steward and the twenty-first person can't choose it — the option stays on screen, marked full. Any question with a fixed set of answers can carry places: single choice, multiple choice and yes/no. An empty box means unlimited; zero means closed from the outset. A limit counts over one set of answers, the same set the form collects into: under each date, twenty stewards means twenty on every date; under the whole Schedule, twenty across the run.

In an event's Forms area, Limits at this event sets that event's own number, with the form's shown underneath. Leave it empty to use the form's; once set, changing the form's number later moves every event that hasn't set its own. It can be 0 or larger than the form's. It needs permission to attach a form to an event, not to build one.

Lowering a number below the people already signed up asks you to confirm, naming the dates and by how many. Nobody is removed. Those dates read as over their number, like 7 of 6, and nobody else can join; raise the number and it goes back to normal.

People filling in the form see how many places are left beside each capped answer. If someone takes the last place while another person is partway through, that person's other answers are kept and they're told circumstances changed, then pick something else. If it was the last place on the form, they're told that instead, with links to other dates. Where a required question has no answers left, the form says so before asking anything, and the date chooser marks which dates are full. A form whose every date is full stays on your public list, marked full.

The results show how many places of each answer are taken per date; across a run, "full on 4 of 6 dates" names the dates with room. The Quick look says Sign-up full when nothing can be signed up for and, for anyone who can read answers, shows how many places each role has taken.

Remove an option and Venvy tells you how many people chose it and across how many sets of dates, then asks you to confirm. Their answers are kept, readable as an answer that is no longer offered. You're also offered the chance to email them, switched off unless you turn it on. Venvy proposes wording and you edit it; the removal happens first and the message goes afterward, so if the removal fails nothing is sent.

Sign-ups, open slots and deleting a response

In the form's Settings under What respondents can see, all off until you turn them on:

Show who's signed up lists the people already signed up above the questions. You choose which short-answer question supplies the names (usually "Your name"). On a form divided by date, each date shows only its own sign-ups. Respondents are told before they send that their name will be shown, and you can let them tick Don't show my name; they're still counted, as "and 1 other".
Show limits at the top of the form lists each limited answer and the places left, for example "Faculty: 2 of 3 places left".
Show open places on the list of dates, on a date-only form, shows each date's Open slots, for example "Student: 3 · Faculty: 2".

The builder's Preview shows the limits section, and a placeholder where the sign-up list goes, never anyone's real name. Each row of the results table also has a Delete button to remove a single response, such as a fake or unwelcome name. Its place opens up again, and the deletion is recorded in the audit log.

Reading the answers

A form's results, and the responses on an event's Forms page, are one table: a row for each person, a column for each question. Select a heading to sort, or its ⋯ to filter. Add filter narrows by any answer, with counts beside each choice. Group by gathers responses under each answer to a choice question, or under each date on an event, and replaces Break down by. On a repeating event, each date or run is also a filter. The table says how many responses it's showing, and the address keeps your view so you can share it. Once a form is published, its responses are the first thing you see on the event; everything else is folded away, each section still showing its current setting, and settings save as you change them with a Saved mark beside the control.

Show in the Quick look on an event's Forms page offers Nothing, Count or Names. For Names, pick the question that holds each person's name; a preview of the Quick look updates beside it. "Show results as a sign-up list" is gone — use Group by. Forms that had it keep every response, and events that showed names in the Quick look still do.

Confirmations, messages and permissions

Turn on Send respondents a copy of their answers (on an event's Forms page, its own Email receipt section) and everyone who completes the form gets their answers by email. On an event, the email includes a calendar file with the dates they signed up for. A form that sends confirmations has to ask for an email address; you're told if it doesn't. Email everyone, or just the people for one date, straight from the responses; you see how many people it will reach before anything sends, and each gets their own copy.

Forms have their own permissions in Settings → Roles: build forms, add them to events, read the answers, and email a form's respondents — never, only on events the person manages, or always. Administrators hold all of them. The in-app help now covers Forms end to end.

Public pages

Your venue's name

Admin → Settings → General has a new Venue name field. It's the name visitors see on your public calendar, volunteer sign-up page and forms, and in their browser tab. Those pages used to show "Venvy" instead of yours, and the public calendar showed our logo too. Enter your name and choose Save name. Changes are recorded in the audit log.

A new Public pages section sits just above Settings. It lists the pages your venue shares with everyone: Public calendar, Volunteer and Public forms, each opening in a new tab. A page appears only while it's turned on in Settings; Public forms appears while at least one listed form is open for responses. When none is on, the section doesn't appear at all.

A way back into Venvy from your public pages

When you're signed in and open one of your public pages, a thin bar says You are currently signed in to Venvy, with a link to Your Venvy home. It never shows who's signed in, and people who aren't signed in don't see it. Where the page is about something you can open in Venvy, a second link appears: Volunteers in Venvy on an event's sign-up page (or Event in Venvy if your role doesn't show volunteer names), and Form in Venvy on a public form. On the public calendar, an event's details show Open in Venvy if you can open that event. The × hides the bar in that browser tab; on a phone the bar shows just its links and the ×.

When your public volunteer page is on, every event it lists also has a page of its own, showing just that event with the sign-up form ready. It's the link to share when you need help on one night, with See all events leading back. On an event's People page a Sign-up page link sits beside the volunteer list, and in the Quick look a link icon sits beside the volunteer count. Both open in a new tab, and appear only when the event is on your public volunteer page: confirmed, upcoming, with at least one volunteer role, and within how far ahead the page looks. In the Quick look, click the count ("3 of 7 volunteers") to go to the event's People page, scrolled to Volunteers.

Repeating Sets and booking

Each Repeating Set can have its own manager

Useful when Tuesdays and Thursdays have different instructors. Each set's card under Schedule shows who manages it, or No manager, and Manager… lets you set, change or remove that person.

From a date. Pick the date the new manager takes over; it starts at the next date still to come. Earlier dates keep their manager, and past dates never change.
Substitutes aren't overwritten quietly. A date handed to someone else on its own is listed with an unticked checkbox and keeps its manager unless you tick it.
Who's told. The previous and new managers each get one Manager changed notice naming the set and how many dates changed, if those notices are on. A date you tick also tells the person it's taken from. Removing a set's manager changes no date and tells nobody.

Add a set has an optional Managing user; empty, new dates get the manager of the run's latest date. In an event's Basics, Managing user is marked Only for the date you opened. Choosing a different managing user is no longer Admin-only: anyone who can edit an event can give it to someone who can manage events. Out of the box a Manager still books new events as themselves, and an Admin can change that on the Roles page. Rebook the series lists each set's manager too.

Adding, extending and editing sets

Add a set under Schedule now asks when the rule begins: a Starts on date above the repeat choices, suggesting today or the run's first night if still to come. It used to count from today, so a January run's "every Tuesday, 6 times" started months early. It also asks where: choose the rule; choose the rooms (the run's next date's rooms are ticked, and you can pick several); then Check these dates, which shows every date before anything is booked — clear, moving a lower-priority booking (admins can choose where it goes), stepping into another free room, or impossible. The confirm button states exactly how many dates will be booked. Before, it quietly used the run's latest room and left out taken dates while still counting them.

Moving a set's end date later works the same way: it asks where the new dates should meet, with the set's upcoming rooms ticked, and Check these dates shows every added date. A date that can't be booked is left out and the set keeps every date it has.

Changing a set's time, length or rule checks every date first, like changing an event's time. A lower-priority booking in the way moves once you've seen it (admins choose where), and a date whose new time is held by an equal-or-higher-priority booking keeps its current time and goes to override approval. If a new rule makes dates the set didn't have, you choose where they meet and see every date checked, as with Add a set. This also fixes Change the clock from…, which used to refuse every rule that added dates.

Edit… on a set that hasn't had any dates yet now includes Starts on, and Review changes says what moving it does. A later start cancels the dates before it, naming each; an earlier start adds the days the rule makes before the current first date, which you place and check like Add a set and which join the same set. Once a set has had a date, its start is history and isn't offered; change its days or time from a date instead. Also fixed: changing only a set's length no longer splits it in two, a change can't apply from a date that has passed, and a set with no dates left says so instead of failing on review.

Add a Repeating Set now opens at the event type's default time instead of 7:30 PM for 2½ hours, and Add another schedule on the reserve form does the same (it used to copy the first schedule's start and last an hour). A type with no default opens at 9:00 AM for 1 hour.

Room checks cover every schedule

When you reserve with more than one schedule (Add another schedule), each room is checked against the dates of all of them, not just one. A room could say Free even though a later schedule's dates were taken, and you weren't shown whose bookings would move until after you reserved. And Before this saves now names each date refused for capacity, with the numbers: "Oct 8 can't take these rooms — they seat 10, and this event is for 30."

Rebook the series

Rebook the series, in an event's Schedule area, now asks only one question: where should this run meet? The event's name, type, manager and schedules are on screen, locked; edit the event itself to change them. It works on dates still to come (spelled out, like "12 dates · Thu 10 Sept → Thu 5 Nov"); past nights are left exactly as they are, rooms included. If the dates don't all meet in the same rooms today, it says so, and rebooking puts every remaining date in the rooms you pick. A run no longer blocks its own move: the rooms it already sits in read as free.

Each room says what it can do across the run: "Free on all 17 dates", "Free on 15 of 17". Adding a second room tells you the cost before you tick it, in terms of what stays:

Adding this room moves 15 of 17 dates — the other 2 keep the rooms they have now

Those dates aren't canceled; they stay in the calendar in the rooms they hold, listed by name with reasons before you confirm. Start from one room or a set; Add another room builds a set. Rooms held together must all be free on a date for the run to take it.

The room you want is usually not empty. A run can now be rebooked into a contested room: "They move on 9 dates · Moving all 17 dates", meaning a lower-priority event moves out on 9 of 17. Whose booking moves and where it lands is named before anything saves. Dates held by something the run doesn't outrank are each asked about, with Keep [room] as the default — a real answer — or a room genuinely free on that date. Only dates you change are written.

For equal- or higher-priority bookings, each contested date offers Take it, showing whose booking would move and where it would land (Venvy suggests the best free room and you can pick another), or that nowhere is free. If it's only that booking's head-count exceeding every free room, Venvy offers to correct it. Dates are decided one at a time. An Admin takes the date and the rebook saves in one go. Anyone else asks: nothing changes until an Admin decides, not the contested dates and not the rest of the run; you can rebook the other dates now and ask separately. While a request waits, the run shows what's outstanding and you can withdraw it; a date that arrives first drops out. In the Approvals queue the Admin answers each date on its own and can send a moved booking elsewhere. Deciding applies the whole rebook at once, checked against the calendar as it is then; if something changed, nothing saves and the Admin is told why. Anyone whose booking moved gets one notice listing every date and where it landed; a date left without a room is called out separately.

Swap rooms

The Swap board puts rooms down the side and dates across the top, with the events that hold them. Drag an event onto another room to swap the two, or onto a free room to move it; from the keyboard, press Enter on an event and choose where it goes. Changes are staged and nothing saves until you Review and apply. An event's Basics page has Swap rooms…, opening the board on its date; a repeating event can open it across its whole run to bring a scattered run back into one room. An event in several rooms keeps its other rooms when one is swapped.

A swap exchanges rooms events already hold, even against the usual booking rules. The review says which rule is being set aside and who it affects, such as an event in a room too small or with no room. Every swap is recorded in the Audit log, and a manager whose event moved against a rule is told. Swap rooms between events is off for every role except Admin; enable it in Admin → Roles. The board shows only the rooms and events your calendar shows.

Events needing a room

When a higher-priority booking takes an event's room and nowhere else is free, the event shows on Home under Events needing a room. It used to open a dead-end page still listing the room it had lost. Now it opens ready to fix: pick a room under Schedule and save, and it's back on the calendar with its forms, teams and history. Anyone who can edit the event can do this, or delete it instead.

Private events you're allowed to edit

If your role hides an event from you but you're allowed to edit it, the calendar now shows it as Private event · Yours to edit, in every view and in the Quick look. Selecting it opens the full edit screen.

Where some dates of a repeating event are hidden from you, this and following and all are grayed out when you delete, with a sentence saying why: delete the date on its own instead, or ask an admin.

Teams and people

Request to join a team

Open a team's page and click Request to join, with an optional note; withdraw it any time while it waits. Being on a team means its events show on your calendar and it can ask whether you're coming; it doesn't give you any say over the group. Managers get the request in the bell menu under a new Requests tab and by email; both offer Approve and Deny and open Venvy to finish (the email buttons never approve on their own). Open requests also appear on the team page above Members.

Approve adds the person as a member.
Deny asks for a reason, which the person sees. They can ask again after 15 days.
A team with no managers sends requests to your administrators.
Managers get one reminder after a week; the request expires after 30 days, the person is told, and can ask again right away.

See who's coming on a full-roster team

If your team shares its Full roster, open an event's People: the new Availability section lists everyone on the team with their answer and when they gave it. The Quick look still shows totals, with a Full roster link under them to the names. It appears only when you're allowed to see them; on a counts-only team, only the team's managers get it.

Audit and history

Explain an event's history

On the Audit log, filter by Target and choose Explain this event's history for a short, plain-English account of how the event reached its current state — why it moved rooms, why it holds two, who approved what. For a repeating event you pick the date first, each listed with its rooms. The explanation is written by Anthropic's AI and labeled so. Every statement ends in a numbered citation; choose one and the entry it rests on opens beneath it. Where the log doesn't explain something, it says so. Email addresses, sign-in and account activity, and event descriptions and memos are never sent. An explanation is kept and shown instantly to anyone with audit-log access until something new happens to the event.

Explanations are off until an admin turns them on in Settings → AI explanations. They use your venue's own Anthropic API key, so Anthropic bills your venue directly; the key is checked before saving, stored encrypted and never shown again. You also set a monthly spending cap ($25 unless changed) and how many explanations one person can ask for in an hour. A typical one costs about a cent.

A quieter filter bar, and names instead of IDs

The Audit log no longer shows seven filter fields on every visit. The Target search stays; everything else comes in through + Add filter: Action, Entity type, Actor email, Name or email, or Date. Each filter shows as a pill (choose it to change it, or its × to remove it), and Clear all starts over. Filters apply as soon as you set them, so there's no Apply button. Date replaces From and To, with Today, Last 7 days and Last 30 days.

The Target column now shows a name instead of a string of letters and numbers for repeating events, sets of dates, forms, override requests, tags and more — a repeating event shows its title even after it was deleted. Every action can be filtered too; some, such as creating a repeating event, couldn't be picked in Action before.

Improvements

Tags in your own order. In Settings → Tags, a new tag now goes to the end of the list rather than into alphabetical place (existing tags keep their order). Choose Reorder, then drag a tag or use the arrows on each row, and Save order or Cancel. The tag nearest the top speaks for a thing that carries several tags but can show only one. If a colleague adds or removes a tag while you arrange, saving is refused and Venvy offers to reload the list.
People area, in panels. On an event's People, Teams and participants, Volunteers and Availability each sit in their own panel; you still save everything with the Save bar. Once volunteer roles are saved they fold into one Volunteer setup line, such as "2 roles · 5 volunteers needed", with the list of who has signed up first. Click Volunteer setup to change the roles.
Upcoming events look like the List view. On a team's or a room's page, each upcoming event shows its event type's icon on a square in its room's color, then the room, the time and the event type, as the calendar's List view shows them.
Reserving on a phone. Picking an event type scrolls the time and the Repeat this event switch into view, and turning Repeat on scrolls its options into view.
One icon in the Quick look. If you can change the event you see just Edit event; if not, Full details. Either closes the Quick look as the event opens.
When something can't load, we say so. Adding a tag: if the list can't load, the menu says Couldn't load tags with Retry (it used to say "No tags yet"). After a refused move, if rooms can't load you see Couldn't load the other available rooms with Retry (it used to say every other room was booked).

Fixes

Closing a dialog while it saves is safe. In rooms, room types, users, teams, tags, custom calendar feeds and Repeating Sets, pressing Cancel mid-save and opening another item's dialog could see the first save close it, discard what you typed, show an unrelated error or change page. Now buttons that open another dialog wait and say why, and a save finishing after you closed its dialog leaves you alone (a failure shows a notice).
Closing a window returns you to its button. For buttons that load before opening, like Review on the Swap board, keyboard focus used to jump to the top of the page. It now goes back to the button you pressed.
A refused Capacity needed stops the booking. A number it can't use (like 2.5) used to let you carry on with the old capacity. Review & reserve, Continue and the room button now wait and say "Fix Capacity needed in step 1."
Roles remember what saved. If Apply changes in Settings → Roles saved some changes then hit an error, the saved ones still counted as unsaved, so undoing one (like a renamed role's old name) looked like nothing to save. Saved changes now count as saved.
The right day for evening events. Save and delete dialogs on repeating events showed dates a day late for evening starts ("Thu, Jan 7" for Wed, Jan 6 at 7:00 PM). They now show the day the event happens.
"No volunteers yet". An event's Volunteers list said Partly filled as soon as you turned on "Needs volunteers"; it now says No volunteers yet until someone signs up.
"See who's signed up" only for people who can. On the public volunteer page, the link under each event appeared for anyone signed in. Now only people who can see names get it; those who can open the event but not see names get Event in Venvy, and those who can't see the event get no link.
The email editor keeps your place. In Settings → Notifications, Bold, Italic, a list button, Link or a placeholder no longer moves you out of the text, and the buttons show which formatting is on at your cursor.
Easier to read. Day numbers from the next or previous month in date pickers, the month calendar and the public calendar, and week labels in the year view, now meet accessibility contrast guidelines (still dimmer than the current month). Faint gray text, such as calendar hour labels, availability notes and a team's contact emails, is now a darker gray.
"Color" and "canceled". Tag and room color settings and their help, and "canceled" in the app, emails and help, now use American spelling.