Ten weeks on one page, with Hebrew and Gregorian dates, Shabbat, holidays and space to write your tasks.
This page builds a printable project timeline planner: a rolling ten-week grid that always starts with the current week, where every day is an empty cell to write in, each Gregorian date carries its Hebrew date beside it, and Shabbat and the holidays are already marked in color. Ten weeks is roughly a quarter: close enough that a promise you made a client is still real, far enough out that you can still change it. Print it, put it on the wall, and draw a bar for each task from its start day to its end day.
Small businesses rarely fail from too little work. They fail from waves: three weeks slammed, then two empty ones nobody saw coming. Once a whole quarter sits on one page, those waves stop hiding: two deliveries landing the same week, a month with no lead-generating work in it, event prep that started two weeks late. None of that is a problem when you catch it early. The damage only happens when you catch it late.
And once it's all written down, saying no gets easier too: you can see exactly what would have to move to make room for something new.
An annual plan for 2026 usually starts big: three or four milestones spread across the year — a busy season, a launch, a trade show, closing the books. A calendar of months is enough to draw those. What decides whether the dates hold is the step after: breaking each milestone into weeks and seeing what collides with what. That is what this page does, from the current week forward.
Once the board is in front of you, the less pleasant part arrives: not everything fits. A single sheet covering ten weeks is a physical limit, and that is really its advantage: it forces a decision that is easy to dodge for as long as everything still lives on an endless to-do list.
The simplest method works before you draw anything at all. List every task in the margin and mark each one as near-term money, long-term building, or must-happen. The first group moves onto the board first, and the rest only get a place if there is room left for them.
The rule that saves the plan is one about parallelism: no more than three large tasks running in any single week. If four bars cross the same week, one of them is not really going to happen, and it is better to choose which one now than to find out afterwards. Whatever stays off is not deleted: it moves to a side list, and next time you print a board it is first in line.
A Gantt chart is a simple way to show work against time: every task becomes a bar stretched along the axis, showing when it starts, how long it takes, and when it ends. The idea is over a century old, and it outlived every tool that came after it for a reason. It shows what happens when and what runs alongside what, both in a single glance, which is exactly the information that is hardest to hold in your head.
A monthly Gantt works at the resolution of days and weeks, and that is the resolution most small businesses actually live in: a launch, a renovation, a hire, a campaign, a content schedule, a client project with milestones. Each of those runs for a few weeks and contains a few dozen tasks at most, precisely the size a single sheet of paper holds without shrinking.
As a project grows, the advantage moves the other way. A project with dozens of dependencies shifting daily, where changing one date has to move twenty others automatically, belongs in software. A printed board wins under the opposite conditions: a fairly stable plan that needs to stay in front of you all day, on a wall rather than behind a browser tab.
The form dates to the early twentieth century, to the American engineer Henry Gantt, who wanted a schedule a manager and a worker could both read at a glance. Dozens of software packages have been built around it since, and the drawing itself has barely changed — because it is made of five things.
A task row. One line per task, named so you can mark it "done". "Marketing" is not a task; "write three posts for the campaign" is.
A time axis. Across the sheet, in steps of a day or a week. It is what turns a list into a schedule.
A bar. From the start day to the end day. Its length is your estimate, and it is the only part of the chart that asks for a real decision.
A milestone. A point in time rather than a duration: client sign-off, launch day, a payment. Mark it with a small symbol on the axis, and you can check whether you are on pace without reading the whole sheet.
Order and dependency. What has to finish before what. In software that is an arrow between bars; on paper it is simply the order you put the rows in, top to bottom, by what happens first.
Working with a team, add a sixth narrow column down the side: who owns it. One name per row, not two.
Planning a project on a printed sheet sounds old-fashioned, but it forces an order that digital tools let you skip. Five steps, and at any size of project they are the same five.
1. Define the finish. One target date, and one sentence describing what counts as done. It sounds trivial, but without that sentence there is nothing to measure the rest against, and the project tends to run until somebody gets tired.
2. Break the work into tasks. A good task takes between two days and two weeks. A one-day task is detail that only crowds the page, and a two-month task almost always hides a problem you have not found yet. Break it down and it shows itself.
3. Order them by dependency. Go through the list and ask, for each task, what has to finish before it can start. Anything that depends on nothing can run in parallel, and that is where nearly all your saved time comes from.
4. Draw the bars. Each task gets a row of its own, from its start day to its end day. Add roughly 20% slack to every duration, not out of pessimism, but because that is how it ends up almost every time.
5. Mark milestones. Three to five points on the sheet where you stop and check whether the plan is still true, and if it no longer is, print a fresh one. This is where most plans break: a board that never gets updated stops being a plan and becomes wall decoration.
The five steps are easier to see on a real project. A small business is launching a new website, and the only fixed date is launch day at the end of week eight.
Once it is drawn, the sheet starts talking. Week 7 carries two heavy bars, so that is the week at risk; a few days of slack are left before launch; and if the photography slips by two weeks it lands exactly on testing. No to-do list shows you any of that.
The resolution follows the length of the project, and it is worth choosing before you draw anything.
A daily Gantt suits one or two intense weeks: an event, an office move, a launch week. Every day gets a column.
A monthly Gantt is the default for most small businesses. Bars are measured in days, the view covers a month to a quarter, and that is the range in which a commitment you gave a client is still accurate and still changeable. A project this size holds ten to twenty tasks, which is exactly what one sheet carries without shrinking.
A yearly Gantt gives up days and shows months. Good for the overview, less good for daily work.
The board at the top of this page works at the middle resolution: ten weeks forward from the current week, day by day, with the Hebrew date beside the civil one and Shabbat and the holidays already coloured in. That changes bar lengths in practice — a week containing a festival is three working days, and anyone who cannot see that on the sheet promises a date they will miss.
Too much detail. Forty rows on one sheet make it unreadable. A good task runs between two days and two weeks; anything shorter belongs on the daily list, not on the board.
No slack. Draw every bar at exactly your estimate and the plan breaks in week one. Adding about a fifth to each duration is not pessimism, it is experience.
Too much in parallel. If four large bars cross the same week, one of them is not really going to happen. Better to choose which one now than to find out afterwards.
A board that never gets updated. This is the mistake that actually happens. A Gantt chart is a snapshot, and after a month it is no longer accurate. Set one point a month to go over the sheet, and if it no longer describes reality, print a fresh one and copy across what is left.
The Jewish working year is not divided into equal months, and anyone who has tried to plan a quarter containing Tishrei knows it. Tishrei swallows two and a half weeks, Pesach takes one, the summer break halves a team's availability, and September–October can hold fewer working days than an ordinary month. Outside Israel the effect is milder, but it is still there.
So holidays and Shabbatot are marked here in color ahead of time, and every Gregorian date carries its Hebrew date beside it. The difference shows the moment you draw a bar: a task crossing Sukkot looks exactly as long as any other task, but the color reveals that it holds three working days. That is the difference between a plan that survives and one that falls apart in week two.
The Hebrew date works in the other direction too. Anything scheduled by the Hebrew calendar (events, memorial dates, family occasions) sits on the same sheet as everything else, with no cross-referencing between two calendars.
What is a Gantt chart? A drawing of work against time: each task is a bar stretched from its start day to its end day, and together they show at a glance what happens when and what runs alongside what.
What are the 7 elements of a Gantt chart? Tasks, start dates, end dates, durations, the bars themselves, dependencies between them, and milestones, laid out against a time axis. The section above breaks the same thing into five parts, because on paper the dates and durations are read straight off the bar rather than listed beside it.
How do you make a Gantt chart for a business? Set one delivery date, break the work into ten to twenty tasks, order them by what must finish before what, and draw a bar per task. The five steps and a full worked example are above. For a small business the whole exercise takes about an hour the first time and fifteen minutes for each update.
Is there an example of a Gantt chart? There is a full one above: a website launch over eight weeks, row by row. The board on this page is the grid you draw exactly that on, with ten weeks marked and the dates already in place.
Does Microsoft Excel have a Gantt chart? Not as a built-in chart type, and neither does Google Sheets. People build one from a stacked bar chart with the first series hidden, or colour cells by hand, which works but takes a while to set up. If you want a file that recalculates, that is the route. If you want something on the wall today, print this page.
Can ChatGPT make a Gantt chart? It can draft the task list and suggest durations, which is genuinely the slow part. What it hands back is text. Paste that task list next to this printed board and draw the bars yourself.
Do I need to sign up, and what date does it start from? No account, no payment. The board always starts from the Sunday of the current week. To save it, choose "Save as PDF" in the browser's print dialog instead of a printer.