Why every household calendar should have a vacation mode
The NestBoard team · 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 8am summary email 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, but it took us a year to add.
The problem we kept ignoring
Early on, we assumed people would just manually snooze things 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 turn back on when you get home. We watched families come back from a week away to a pile of overdue chore notifications and guilt-inducing leaderboard math. That's not calm. That's 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.
The calendar tints those days in a soft sand wash, labelled with the trip name. 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 took a year
We debated what "away" means. Is a long weekend away? What about a work trip where one parent is gone but the household keeps running?
We also had to move the logic somewhere the whole system could see it. It started life in the browser, which meant the dashboard said zero overdue during a trip while Robin, reading the same API, said six and named the trash. Vacation days had to become a real record in the database and a single shared transform that the app, the server, Robin and the morning email all run, or two surfaces answer the same question two different ways.
It's one trip on a page now. But behind it is a year of deciding what a household calendar should assume about absence, rest, and what it means to actually be off.
We think it was worth it. Your home routines should bend when you're gone, not break.