Planning deadlines with a calendar that matches the board

Agency deadlines rarely fail on the day. They fail a fortnight earlier, when three jobs quietly land on the same Thursday and nobody notices, because the board shows stages and not dates.

The usual fix is a separate calendar or a planning spreadsheet. It works for a week. Then a date changes on the board and not in the plan, and the team has two versions of the truth. This article shows how to plan agency deadlines from a project calendar view that is the board, seen by date, and how to use it each week without it drifting.

Why a board alone hides clashes#

A kanban board answers "where is each job?" very well. It answers "what is due on Thursday?" badly. Due dates sit on the cards, spread across columns, and a clash only shows up when someone reads every card in turn.

A separate plan has the opposite problem. It shows dates well, but it is a copy. Every change has to be made twice, and the day someone forgets, the plan is wrong in a way nobody can see.

What you want is one set of jobs you can look at two ways: by stage when you are doing the work, and by date when you are planning it.

One set of jobs, seen by date#

In Skybase, every project has a Calendar next to Board and Table. It isn't a copy of the board. It is the same jobs, placed on the day they are due. Change a date on the calendar and the job changes, for everyone on the project, as it happens. Your filters come with you when you switch between the three views.

The calendar is part of Skybase. It shows your project's due dates inside the app, and it doesn't connect to any other calendar app. That keeps the dates in one place: the job.

Read the month before you plan it#

Open Calendar and you see a month grid. Today and the arrows move between months. Each day lists the jobs due that day, with their priority, first label and assignee, so you can read a day without opening anything.

Within a day, open jobs come before completed ones, and the most urgent priority comes first. When a day holds more jobs than fit, it shows how many more, and one click opens the full list for that day. A day that keeps showing "more" is the first thing to look at.

You can move around from the keyboard too. The arrow keys move by day and week, Home and End jump to the edges of the week, and Page Up and Page Down change the month.

Schedule work from the Unscheduled tray#

A job with no due date is a job nobody has committed to. On the calendar, those jobs wait in the Unscheduled tray beside the month.

1. Open Calendar. The tray lists every open job with no due date.
2. Drag a job from the tray onto a day to give it that date.
3. Drag a job to another day to reschedule it, or back to the tray to clear its date.

If you would rather not drag, each job you can change has a Set date… menu, where you pick a date or choose Remove date. Completed jobs stay out of the tray, so it only ever holds work that still needs a date. The Unscheduled button shows or hides the tray, and your browser remembers which you chose.

Due dates are days, not times#

Due dates in Skybase are calendar days, and they read the way you would say them: Today, Tomorrow, in 3d, then the date. An overdue job says how late it is, such as 2d overdue.

That shapes how to plan. A due date should be the day the client needs the work, not the hour. If a job has internal steps with their own dates, such as a first draft before a review, give those steps to tasks on the job. Each task can have its own assignee and due date, while the calendar keeps showing the job's date, the one the client sees.

Plan backwards from the client's date#

Here is the routine I would use for a new piece of client work:

1. Put the client-facing dates in first. Launches, presentations and sign-offs go on the calendar before anything else.
2. Work backwards. For each one, give the jobs that feed it a date that leaves room for a round of review before the deadline.
3. Look for clashes by person. Filter Members to one person and read their month. Three jobs on one day is a conversation to have now, not on the day.
4. Leave a gap before client review. Feedback rarely arrives the hour you ask for it.
5. Empty the tray. Anything left in Unscheduled either gets a date or gets questioned.

Save the views you plan from#

The same filters sit at the top of the board, the table and the calendar. For planning, the due date filter is the useful one: Overdue, Due today, Due this week (today and the six days after) or No due date.

When a filtered calendar is worth keeping, save it. Choose Views, then Save current view…, give it a Name, and turn on Share with the project if everyone should see it. A saved view remembers that it is a calendar and which filters it uses.

One detail makes shared views much more useful. If you filter Members by yourself before saving a shared view, it shows each person their own work, because a saved view reads your name as whoever opens it. One shared view can give every designer their own month. How to save and share views covers the rest.

On a phone, the month becomes a day#

On a small screen, the calendar becomes a day-by-day agenda. Pick a day in the month at the top and its jobs are listed below it, with the unscheduled jobs after them. Use Set date… on a job to reschedule it, since there is no dragging on a phone.

Who can move a date#

Administrators and team members can reschedule any job they can see. Guests can only reschedule jobs they raised, are assigned to or were added to. For everything else, the calendar shows them the date without the controls to change it. A client can follow the plan without being able to rearrange it.

Let reminders do the chasing#

A plan only works if people notice what is due. Skybase sends due reminders the day before, on the day and when a job is overdue. Anyone who wants a daily summary can turn on the morning roundup, an email at 09:00 covering what is overdue, due today and coming up. An inbox your team can triage in ten minutes covers how to keep those from turning into noise.

A worked example: Harbour Studio plans a launch month#

Take a small agency, say Harbour Studio, rebranding its client Northwind. The launch is at the end of the month, and Maya Chen, the studio lead, plans it on a Monday morning.

Maya opens the Northwind project's Calendar. The launch presentation goes on first, on its day. Working back, the review deck gets a date three working days before it, leaving time for a round of changes.

The Unscheduled tray holds "Social launch kit", a Design job with no date. Maya drags it onto the Thursday before the launch, and Priya Shah, who owns it, sees the new date straight away.

Next, Maya filters Members to Leo Ortiz. Leo has three jobs due on the same Wednesday. One of them, the icon set, can move, so it goes to the following Monday.

"Brand guidelines v3" is showing as overdue, sitting with Tom Becker at Northwind for review. Moving the date would hide the problem, so Maya leaves it and chases Tom instead.

Last, Maya saves a calendar view called "Due this week", filtered to Due this week and to Maya's own name in Members, and shares it with the project. On Monday morning, each person on Northwind opens the same view and sees their own week.

A weekly planning checklist#

• Open the calendar and read the whole month before changing anything.
• Put client-facing dates in first, then work backwards.
• Check each person's month for clashes.
• Leave room before every client review.
• Empty the Unscheduled tray.
• Keep a shared "Due this week" view for the team.

The calendar works best on a well-built board. How to set up a kanban board for agencies covers the structure, and the guide to the board, table and calendar views covers every control. For how a campaign team plans launches on the same calendar, see marketing project management.

A calendar you have to keep in step by hand will drift. A calendar that is the board, seen by date, can't. Plan from it once a week and the Thursday clash shows up while there is still time to move it.