Skip to main content

Keeping Weekends and Holidays Off Your Schedule

J
Written by Joseph Kibe

Most crews don’t work Saturdays. So when the electrician pushes a day and you slide the rest of the job to match, you don’t want the tile work landing on a Sunday — you want it landing Monday.

Eano’s schedule can do two separate things about this, and it’s worth knowing they’re separate:

  • Skip weekends changes the math. When you shift a task and let the rest of the chain follow, the dates that get handed out skip weekends and major holidays.

  • Hide tasks on weekends changes the picture. Your calendar stops drawing task time on Saturdays and Sundays, so a job that technically spans a weekend reads as Friday-then-Monday.

You can use either one on its own. Here’s how each works.

Shifting a Schedule Without Landing on a Saturday

Open a project, go to its Schedule tab, and switch to the Gantt view. Turn on Cascade dependencies — the toggle that makes downstream tasks follow when you drag one. The moment you do, a Skip weekends checkbox appears next to it, already ticked.

Hover the little i beside it and you’ll see what it promises: “Cascading tasks will skip weekends and major holidays.”

With it on, every task the cascade touches moves by a number of working days rather than a number of calendar days. That one change is what makes the results feel right:

  • A one-day task sitting on Friday, pushed forward one day, lands on Monday — not Saturday.

  • That same Friday task pushed forward four days lands on Thursday. The weekend simply doesn’t count.

  • A task running Wednesday to Friday, pushed forward one day, comes out running Thursday to Monday. It’s still three working days of work; it just stretches across the weekend on the calendar.

  • A task on the Wednesday before Thanksgiving, pushed forward a day, lands the following Monday — Thanksgiving and the Friday after are both treated as days off.

It works pulling a schedule earlier, too, not just pushing it later.

The Holidays It Knows About

“Major holidays” means a specific list, and it’s a US list:

New Year’s Day, Martin Luther King Jr. Day, Presidents’ Day, Memorial Day, Independence Day, Labor Day, Veterans Day, Thanksgiving, the Friday after Thanksgiving, Christmas Eve, and Christmas Day.

It’s a deliberately practical list rather than the official federal one — it includes the day after Thanksgiving and Christmas Eve, because most crews aren’t on site either day. The list isn’t editable yet, and it doesn’t cover holidays outside the US. If that’s a gap for your business, tell us — that feedback is what decides what gets built next.

When a Task Is Already on a Weekend

There’s one deliberate exception. If a task already sits on a Saturday, Sunday, or holiday, Eano assumes you put it there on purpose — maybe it’s a weekend punch-list visit, or the one Saturday pour you agreed to. Shifting that task moves it by plain calendar days, so a Saturday task pushed forward one day goes to Sunday. Eano won’t “correct” a weekend you chose.

What Skip Weekends Doesn’t Touch

  • It only applies to cascades. With Cascade dependencies off, you’re in Move mode — dragging a single task puts it exactly where you dropped it, weekend or not. That’s why the checkbox only appears when Cascade is on.

  • It doesn’t reflow your existing schedule. Nothing moves until you drag something. Turning it on doesn’t go tidy up dates you’ve already set.

  • It’s a Gantt thing. The checkbox lives in the project Gantt view. The global Schedule page in the left nav is calendar-only, so there’s no cascade and no checkbox there.

Like the Cascade toggle it sits beside, Skip weekends is remembered per project, in your browser. Untick it on one job and it stays unticked for that job on that computer — but it won’t follow you to a different computer, where it’ll start ticked again.

Hiding Weekend Work on the Calendar

The second half is about how your calendar reads. A task running Friday through Monday is, on the calendar, a bar four days wide — and at a glance that looks like you’ve got crew on site all weekend.

Turn on Hide tasks on weekends and the calendar stops drawing the Saturday and Sunday portion of a task. That Friday-to-Monday job shows up on Friday and on Monday, with clean weekend columns in between.

You’ll find it behind the Display Settings button, which sits above the calendar in two places: the Schedule tab of any project, and the global Schedule page in the left nav.

Click it and a panel opens with the toggle and its description.

What Stays Visible

Three kinds of weekend work are never hidden, because hiding them would mean losing the task entirely:

  1. A task that starts on a weekend. Its first day still shows.

  2. A task that ends on a weekend. Its last day still shows.

  3. A task scheduled only on a weekend — a Saturday-only job stays a Saturday job.

The rule is really just “hide the weekend days a task passes through, never the weekend days it begins or ends on.” Work you deliberately put on a Saturday stays where you can see it.

A Few Specifics Worth Having

  • Your dates don’t change. This is purely how the calendar draws things. Open the task and you’ll still see its real start and end dates, weekend included, and the Gantt view still draws it as one continuous bar. Nothing about the underlying schedule moves.

  • It’s a company-wide setting, not a personal one. Turning it on changes the calendar for everyone on your team, and it saves to your account rather than your browser — so it follows you to every computer and to the mobile app. Anyone on your team who can open the Schedule can change it, so it’s worth a quick heads-up before you flip it.

  • It’s off until someone turns it on.

  • Calendar views only. Month, Week, and Day all respect it. The Gantt view deliberately doesn’t — a Gantt bar with holes punched in it would be harder to read, not easier.

  • Your exported PDF matches. Export the schedule from the Calendar view and the PDF hides the same weekend time your screen does.

  • Weekends only — not holidays. This is the one place the two features differ. Skip weekends treats Thanksgiving as a day off; Hide tasks on weekends doesn’t. Task time on a holiday still draws normally on the calendar.

  • It applies to tasks. Milestones, meetings, and other schedule items show up as they always have.

It’s on the Mobile App Too

Open the Schedule on the Eano Pro app, tap the filter icon, and Hide tasks on weekends sits at the bottom of the panel with the same description. It’s the same company-wide setting — flip it on your phone and your desktop calendar changes too.

The cascade Skip weekends checkbox is web-only, since the Gantt view itself is.

Two Other Places Weekends Now Get Respected

Two features that hand out dates for you have quietly learned the same holiday list. Neither has a toggle — they just behave better:

  • Generate Tasks and Schedule, the AI that turns your scope into a sequenced task list, already avoided weekends. Now it avoids the 11 holidays as well, so an AI-built schedule won’t put framing on Christmas Day.

  • Applying a Project Template places each task’s due date skipping weekends and holidays, so a template’s “three days of work” lands as three working days on the calendar instead of running through a Saturday.

A Few Things Worth Knowing

  • The two settings are independent. You can cascade with Skip weekends on and still let your calendar draw weekend time, or hide weekend time and never cascade at all. Neither one implies the other.

  • A cascaded task can get calendar-longer. That Wednesday-to-Friday task becoming Thursday-to-Monday isn’t a bug — it’s the same three working days, pushed across a weekend. If you also have Hide tasks on weekends on, it’ll read as Thursday-Friday-then-Monday, which is exactly what your crew will actually do.

  • Cascades still don’t notify anyone. That hasn’t changed. After a big shift, let the affected people know yourself.

  • Build your dependencies first. Skip weekends only improves the math on a cascade, and a cascade only reaches tasks that are actually linked. If nothing follows when you drag, check the dependency arrows.

FAQ

I dragged a task to Saturday and it stayed on Saturday. Why didn’t it skip? Almost certainly because Cascade dependencies was off. In Move mode, a task goes exactly where you drop it. Skip weekends only shapes the dates a cascade hands out. It also won’t override you if the task was already sitting on a weekend before you dragged it.

Can I add my company’s own holidays, or shut days off for my crew? Not yet — the list is fixed and it’s the US one. If your crew works Saturdays, or takes days the list doesn’t include, untick Skip weekends on that project and drag dates yourself. And do tell us what you’d want, because that’s what shapes where this goes.

I turned on Hide tasks on weekends and a task still shows on Saturday. That’s one of the three exceptions: the task starts on that Saturday, ends on it, or lives only on it. Open the task and check its dates — if it genuinely ends Saturday, the last day shows on purpose so the task doesn’t vanish.

Did hiding weekends change any of my task dates? No. It’s a display setting and nothing else. Every task keeps the start and end dates you gave it, the Gantt view still shows the full span, and turning the setting back off restores the old picture exactly.

Why does my teammate’s calendar look different from mine? It shouldn’t — Hide tasks on weekends is company-wide, so you’re all seeing the same thing. Skip weekends is the per-person one: it’s remembered in your browser, per project, so you and a teammate can genuinely have it set differently on the same job.

Does this work on the global Schedule page? The Hide tasks on weekends display setting, yes — Display Settings is there too. Skip weekends, no: the global page is calendar-only with no Gantt, so there’s no cascade to shape.

Did this answer your question?