Teach your workflows the days you don’t work

A Business Calendar is a shared list of your holidays. Attach one to a workflow and every date it computes starts skipping the days your team is off — weekends and the holidays you define. Due dates count in business days, and a date that still lands on a day off snaps to a real working day or, for a recurring run, moves or skips.

Start free trial. * No credit card required.

Already using Manifestly? Open Business Calendars

US Holidays 2026 · 11 dates
Imported Custom
New Year’s DayImportedThu, Jan 1
JuneteenthImportedFri, Jun 19
Independence DayImportedFri, Jul 3
Founders’ DayCustomMon, Oct 12
Winter shutdownCustomDec 24–31

Stop scheduling work on days nobody’s in

A recurring workflow doesn’t know it’s a holiday. Left alone, a “due in 3 days” step lands on the 4th of July, a reminder fires while the office is closed, and a monthly run kicks off on New Year’s Day. A Business Calendar teaches your workflows the days your team actually works.

Weekends only
  • Due dates land on public holidays
  • Reminders fire while the office is closed
  • Recurring runs start on a day off
With a Business Calendar
  • Holidays skipped alongside weekends
  • Dates snap to a real working day
  • Recurring runs move or skip the holiday

One calendar, three ways it shows up

The calendar itself

A shared, account-wide list of the dates your team is off — imported from a regional template and topped up with your own custom closures.

Due dates & reminders

Business-day counting steps over the calendar’s holidays, and a landing rule snaps a computed date off any day off it still hits.

Recurring runs

A scheduled run that falls on a holiday or weekend can move to the next or previous business day — or skip that occurrence entirely.

Set it up once, in three steps

1

Build a calendar

Under Settings → Holiday Calendars, add a calendar and import a regional template — US, UK, Canadian, or Australian dates. Add any custom closures the template can’t know about.

2

Attach it to a workflow

Point a workflow at the calendar. From then on its holidays count as non-business days everywhere that workflow works with dates.

3

Choose how dates behave

Set the workflow’s landing rule for due dates and reminders, and the weekend/holiday rule for its recurring schedule. Each run stamps these when it starts.

Import your region, then make it yours

Import a regional template and Manifestly fills the calendar with the observed holiday dates — shifted to the weekday offices actually close on, not the raw date on the wall calendar. Those imported dates sit alongside any custom dates you add, each clearly marked, and the whole calendar is yours to edit.

  • Templates for the US, the UK (England & Wales), Canada (Ontario), and Australia (NSW).
  • Add custom dates — a founders’ day, a company-wide shutdown week, a floating closure.
  • Imported calendars extend themselves ~5 years ahead automatically, so you never re-import each January.
US Holidays Not attached
2026 11 dates
Imported Custom
Memorial DayImportedMon, May 25
Independence DayImportedFri, Jul 3
Founders’ DayCustomMon, Oct 12
ThanksgivingImportedThu, Nov 26
Coverage through 2031 — kept topped up automatically.

Due dates that count business days — and land on one

Business-day counting already steps over weekends and the calendar’s holidays, so “due in 3 business days” reaches a day people are working. The landing rule handles the edges — a due date anchored to a fixed day, or a reminder that happens to fall on a holiday. Pick the behavior once and every run of that workflow follows it.

Next business day
Falls on Jul 4 → moves to Jul 6
Previous business day
Falls on Jul 4 → moves to Jul 3
Leave it
Keeps the date exactly where it lands
“Due in 3 business days” from Wed, Jul 1
S
M
T
W
T
F
S
28
29
30
1
2
3
4
5
6
7
8
9
10
11
Holiday Weekend Due date
Thu 2 is day one; Fri 3 is the observed holiday and the weekend follows, so days two and three are Mon 6 and Wed… landing on Wed 8.

Recurring runs that don’t start on a day off

A schedule that fires “on the 1st” or “every Monday” will eventually land on a holiday. With a calendar attached, the schedule treats those holidays like weekends — and you choose what happens when an occurrence falls on one.

Move forward
Start it on the next business day instead
Move back
Start it on the previous business day instead
Skip it
Skip that occurrence — no run starts on the holiday

Skipping is unique to recurring runs — a due date is always moved to a real day, but a scheduled run can simply sit out a holiday.

A monthly run scheduled for the 1st
M
T
W
T
F
S
S
1
2
3
4
5
6
7
Jan 1 is a holiday — move forward
Move
Run starts Fri, Jan 2
Skip
No January run — next is Feb 1
New Year’s Day is on the calendar, so the schedule steps around it however you chose.

Predictable, and under control

  • Calendars are account-wide, so one set of holidays serves every team that attaches it.
  • Only master admins create and edit calendars — the days-off rules stay centrally managed.
  • Each run stamps its workflow’s calendar and rules when it starts, so a change never reshuffles the dates of runs already in flight.
  • Past the calendar’s last covered date, dates simply fall back to weekends-only — a coverage badge shows how far ahead you’re set.
Monthly Close
calendar: US Holidays · landing: next business day
Run started Jul 1
keeps the rules it began with
Run started Aug 1
picks up any newer rules

Manage it by hand or over the API

Everything you can do in Manifestly you can also drive through the v2 API — import a region onto a calendar, add a custom date, attach a calendar to a workflow, or set its landing rule from your own tooling.

  • Create calendars, generate regional dates, and add individual holidays.
  • Attach a calendar and set the business-day rule per workflow.
  • AI agents can manage calendars over MCP — ask in plain language and let the agent generate the dates.
# Import US federal holidays onto a calendar
POST /api/v2/business_calendars/3/generate
{
  "region_key":   "us_federal",
  "through_year": 2031
}

# Attach it to a workflow and snap forward
PATCH /api/v2/workflows/42
{
  "business_calendar_id": 3,
  "business_day_rule":    "next_business_day"
}

Regional templates, ready to import

United Statesus_federal UK — England & Walesuk_england_wales Canada — Ontarioca_ontario Australia — NSWau_nsw

A template is a starting point — once imported, the dates are yours to add to or trim.

Where a Business Calendar earns its keep

Finance & accounting

Month-end and payroll close on the right working day.

“Close by the 3rd business day” counts past the holiday instead of landing on it.

Compliance & filings

Deadlines and review reminders stay on business days.

A filing reminder that would fire on a bank holiday snaps to the previous business day.

Recurring operations

Daily and weekly runs step around holiday closures.

A daily open-store run skips the holiday, then resumes the next business day.

Business Calendars, answered

Weekends always count as non-business days. When you attach a Business Calendar to a workflow, that calendar’s dates are treated as non-business days too — skipped by business-day counting, moved off by the landing rule, and stepped around by recurring schedules. Detach the calendar and it reverts to weekends only.

US federal holidays, UK bank holidays (England & Wales), Canada (Ontario), and Australia (NSW). Importing a template stamps the observed dates — shifted to the weekday offices actually close on — and you’re free to add or remove dates afterward. You can also build a calendar entirely from your own custom dates without any template.

Imported dates come from a regional template and are kept topped up several years ahead automatically. Custom dates are ones you add yourself — a founders’ day, a company shutdown week, a local closure. Both are marked in the calendar, and both are treated the same way when a workflow uses the calendar.

A due date is always moved to a real working day — the next or previous business day. A recurring run has one more option: it can be skipped. When a scheduled occurrence lands on a holiday or weekend, you can move it to the next or previous business day, or skip that occurrence entirely so no run starts until the next scheduled date.

Each run stamps its workflow’s calendar and rules when it starts, so runs already in flight keep the dates they were given. New runs started after the change pick up the new settings.

Business Calendars are account-wide and managed by master admins, so the days-off rules are set once and shared across teams. Attaching a calendar and choosing its rules happen on the workflow. You can do all of it in Manifestly or through the v2 API.

Other Features

Design your process

Workflow Customization

Shape exactly how each workflow behaves — logic, data, timing, and documentation.

Trusted by organizations big and small for their recurring workflows

Compass logo
Sheraton logo
Foxconn logo
Coldwell logo
Plural Sight logo
BDO logo
KW logo
UT Austin logo

Keep Your Workflow Dates Off Weekends And Holidays

With Manifestly, your team will Never Miss a Thing.