Project Planning Template: Build One in Excel or Google Sheets

A project planning template is one sheet that holds every task in a project with its owner, dates, dependency and status, so the whole plan fits on one screen. You can build one yourself in Excel or Google Sheets in under an hour: break the work down first, give each task one row, let a formula compute end dates, and add a status list plus a bar chart or timeline. It works well for one project and a small team. It starts to strain once dates have to move together and several people update it.

What every project plan template needs

Start with the work, not the columns. Dates come later. List the deliverables, then split each into tasks small enough that one person can own them. That breakdown is your plan's skeleton, and it follows one rule worth knowing: the breakdown should include 100% of the work in scope, and the pieces under each parent should add up to exactly that parent, nothing more ^[1]. Our work breakdown structure guide covers that step in depth.

Then give each task one row with eight columns. ID (1, 1.1, 1.2) keeps the hierarchy readable. Task names the work as a verb plus an object. Owner is one name, never a team. Start, Duration in working days, and End set the schedule. Depends on holds the ID of the task that must finish first. Status closes the row.

Google's own guide to a project plan in Sheets suggests a lighter starting set of columns: tasks, task owners, due dates, status and comments ^[2]. That is enough for a to-do style plan. Add Start, Duration and Depends on when the order of work matters.

Build the project planning template in Excel, step by step

This is the project plan template Excel users can build from a blank workbook. Every menu path below comes from Microsoft's help pages.

1. Type the eight headers in row 1, select any cell in the range and press Ctrl+T to turn it into a table. Name it Plan in Table Design > Table Name. New rows then pick up formulas and formatting on their own.
2. Fill the hierarchy in the ID column: 1 for a phase, 1.1 and 1.2 for its tasks. Indent task names with a leading space or the Increase Indent button.
3. In the End column, enter =WORKDAY([@Start],[@Duration]-1). The task's first day counts as day one, weekends drop out, and end dates update when you change a start or a duration.
4. For a task that waits on another, set its Start to the day after the predecessor ends: =WORKDAY(XLOOKUP([@[Depends on]],[ID],[End]),1). Now a slip upstream pushes this row too.
5. Create the status list. On a spare sheet type Not started, In progress, Done and Blocked. Select the Status column, go to Data > Data Validation, set Allow to List, and point Source at your four values.
6. Add conditional formatting so a row turns red when the end date has passed and the status is not Done: =AND($F2<TODAY(),$H2<>"Done").
7. Put a progress line above the table: =COUNTIF(Plan[Status],"Done")/COUNTA(Plan[Status]), formatted as a percentage. COUNTA counts only rows that have a status, so phase header rows don't drag the figure down.

Turn it into a Gantt chart

Excel has no built-in Gantt chart type. Microsoft's method is to fake one with a stacked bar chart of start dates and durations ^[3]. Select the Task, Start and Duration columns, then choose Insert > Recommended Charts > Stacked Bar. Click the Start series and set Format > Shape Fill > No Fill, so only the duration bars remain. Last, select the vertical axis, open Format Axis, and tick Categories in reverse order so task 1 sits on top.

Save the finished file as an Excel template (.xltx). Every new project then starts from a clean copy instead of last quarter's leftovers.

The same layout as a project management template in Google Sheets

Google Sheets takes the same structure, with two features that fit a shared plan well. Create it from Google Drive with New > Google Sheets > Blank spreadsheet, name it, and add your columns. The WORKDAY formula works the same way. For a dependent start, use =WORKDAY(XLOOKUP(G3,A:A,F:F),1), where G holds Depends on, A the ID and F the End date, so the link follows the ID even if rows move.

1. Status options. Highlight the Status column and add a dropdown list of options such as Not started, In progress and Complete. Google suggests a color per option, so progress reads at a glance. Or use Insert > Checkbox for a simple done flag.
2. Filters per person. Select the range and choose Data > Create a filter. Each owner can show only their own rows. Anyone with edit rights can change the filter, so share a filter view link instead of the shared filter.
3. Timeline view. Click Insert > Timeline, select your data range and click OK ^[4]. Each task becomes a card on a calendar strip. It needs a card title, a start date and an end date, and the start must come before the end, or the card shows no length. A card group column, such as Owner, stacks each person's tasks on one row.

Timeline view is listed for specific Google Workspace editions, so check that yours includes it. If it does not, the stacked bar method from Excel also works in Sheets charts.

Project planning examples: a website launch in nine rows

Here is the template filled in for a small website relaunch with three people. Durations are in working days. Notice that every task has one owner and that only one task, 1.1, starts without waiting on another.

Read it the way a Gantt chart would. The design task is on the critical chain: if it slips two days, development and launch slip two days. Copy runs in parallel and has slack. It can wait. It still has to land before 3.1, which in reality waits on both 2.3 and 2.2. That is the two-predecessor case the single lookup formula cannot carry (see below), so note it in the row and keep an eye on it. Even so, the Depends on column earns its place: it shows which delays matter and which ones you can absorb.

Add a WBS template tab before the schedule

For anything bigger than a dozen tasks, keep a second tab with the breakdown alone. A WBS template needs only three columns: ID, deliverable or work package, and a one-line description of what done means. Build it top down. Write the final outcome, split it into three to six deliverables, and split each until a piece is small enough to estimate and assign.

Check it against the 100% rule before you schedule anything. If a task in your plan has no parent in the WBS, either the WBS is missing scope or the task is outside the project. Then copy the lowest-level items into the plan tab as rows. Phases become your 1, 2, 3 headers, and work packages become the tasks underneath.

Where the spreadsheet stops working

The template above handles one project, a handful of people and a weekly check-in well. It breaks at specific points. They rarely arrive alone.

• Dates that don't cascade cleanly. The dependency formula covers one predecessor per task. A task waiting on two others, a sort that reorders rows, or a deleted row with a referenced ID will quietly break the chain.
• Several people editing. Owners overwrite each other's statuses, and nobody knows which version of the plan is current.
• Status by hand. Someone has to chase updates before every meeting, and the sheet is only as fresh as the last chase.
• No notifications. Assigning a task in a cell tells no one. A due date passing turns a cell red, but only for whoever opens the file.
• The second project. Copying the template works, but seeing all projects side by side means building a summary sheet you then maintain by hand.

When those hit, a project tool takes over the mechanics: assignments notify people, dependent dates move, and templates become reusable plans. Our guide to project planning tools compares the options by team type. These three keep the template idea at their center.

The bottom line

A good project planning template is less about the file and more about the order you fill it in: break the work down, give every task one owner, link the tasks that wait on each other, then let formulas carry the dates. Excel and Google Sheets both handle that well for a single project. Keep the spreadsheet while one person can keep it current. Move the plan into a tool once updates, notifications and cross-project views start costing you an hour a week.