Why every household calendar should have a vacation mode
NestBoard · 2026-05-13
We shipped vacation mode. You add a trip on the Vacation page with a start date, an end date, and an optional label like "Beach trip," and NestBoard knows the household is away.
With a trip on the books, chores due during it stop nagging. The daily summary email, whenever you have it set to arrive, stops listing an overdue pile you can't do anything about from a hotel room. The calendar tints those days so everyone in the family sees at a glance that you're gone.
It sounds simple. It was not the first thing built.
The problem we kept ignoring
The easy assumption is that people will snooze things by hand before a trip. Turn off notifications, archive a few chores, maybe add a calendar event called "VACATION" in all caps.
But that's six different interactions spread across the app. And when you're packing sunscreen and printing boarding passes, the last thing you want to do is audit your household software.
More importantly, it puts the burden on you to remember what to turn off, and then to turn it back on when you get home. Forget the second half and a week away ends in a pile of overdue chore notifications and some guilt-inducing leaderboard math. That is not calm. That is punishment for taking a break.
What vacation mode actually does
You pick a date range. Any chore whose due date lands inside it reads as due the day after you get home, so while you're away nothing is overdue, nothing buzzes about it, and Robin doesn't scold anyone about the trash. Medication reminders keep running, because bodies don't take vacations.
On the month view the calendar tints those days in a soft sand wash with a small palm tree, and the day view shows the trip's name and dates. It's visible to everyone in the household. Calendar events and routines stay exactly where you put them, because a flight and a birthday are still happening whether or not you're home.
Nothing is rewritten in the database when the shift happens. It's a read-time transform, so deleting the trip puts every original due date straight back. And when the vacation ends, the pile you were dreading is just the next morning's normal list.
Why it was harder than it looks
The first question is what "away" even means. Is a long weekend away? What about a work trip where one parent is gone but the household keeps running?
The second is where the logic lives. It started life in the browser, which meant the dashboard could report nothing overdue during a trip while Robin, reading the same API, still counted the chores and named them. The shift had to move out of the browser into a single shared transform that the app, the server, Robin and the morning email all run. Otherwise two surfaces answer the same question two different ways, and neither of them is trustworthy.
It is one trip on a page now. Behind it is a decision about what a household calendar should assume about absence and rest.
Your home routines should bend when you're gone, not break. And if the trip itself is the stressful part, our family vacation packing list is the same one-list-many-hands idea applied to the suitcase.