Project schedule template: a free spreadsheet with a filled-in example.

What a project schedule is

A project schedule is the list of everything that needs to be done, with start date, end date, assignee and the order among tasks. It's the document that answers "when does this finish?" without depending on anyone's memory. When someone asks whether the deadline still stands, the answer is in the table.

The template above uses as its example the rollout of a management system at a company: four stages, eleven tasks and a column that says what each task is waiting on to start. Swap the content for your project and keep the structure.

How to fill it in, column by column

Step by step to build yours

1. Define the end date and what "done" means. Without that, the schedule has nowhere to go.
2. List the main deliverables and break each one into tasks of up to two weeks. If you need a more complete tree, start with a WBS.
3. Ask for the estimate from whoever will do the work. The duration a manager imagines tends to be shorter than the real one.
4. Mark the dependencies. In the example, "train the teams" only starts after "validate imported data" and after the material is ready. That link is what makes the schedule a decision-making tool.
5. Add some breathing room to tasks that depend on third parties (supplier, client, approval).
6. Review every week. A schedule that isn't updated becomes decoration.

Common mistakes

• Tasks that are too big. "Configure the system" over four weeks hides delay until the last minute. Break it into parts that fit in a few days.
• Everything starts on day one. If nothing depends on anything, either the project is trivial or the dependencies were left out.
• No milestones. Dates like go-live and the client approval meeting deserve their own row, even with a one-day duration.
• One person on two tasks at once. On paper the deadline works; in practice, nobody is two people. Check each assignee's workload.

When the spreadsheet template isn't enough

A spreadsheet works well for a small project, with one person looking after the dates. The problem shows up when a task slips: you have to remember which tasks depended on it and move each date by hand. With twenty or thirty rows, that's where the schedule stops reflecting reality.

The day-to-day side is also missing: the spreadsheet doesn't notify the assignee, doesn't show who is overloaded and has no comments or attachments on the task. To understand how bars and the critical path help you see this, read the Gantt chart guide.

How to use the schedule in Tasskee

1. Create the project and add each row of the spreadsheet as a task, with an assignee and start and end dates.
2. Use workstreams to group the stages (preparation, configuration, training, cutover).
3. Link the tasks by dependency: the "Depends on" column becomes a link in the Gantt, with milestones and the critical path.
4. Follow the day-to-day on the Kanban board: the spreadsheet's status becomes a board column.
5. Turn on an automatic alert before the due date and for stalled tasks, in the automations, so the schedule holds itself accountable.
6. If the client follows the project, invite them through the client portal, without taking up a plan seat.

Want to understand the project's design before putting dates together? Read the project management guide, or see how to set a realistic deadline in the post how to build a schedule your team will meet.