The short version: a spreadsheet project timeline needs six columns (task, owner, start date, duration, end date, status), one formula that calculates working days automatically, and a weekly ten-minute habit of updating it, otherwise it's fiction by day four. Templates from Google or Microsoft get you the layout in five minutes. What they don't give you is the discipline to keep it honest, and that's the bit that matters.
Why I still use a spreadsheet after twenty years of "proper" project tools
I've paid for Asana, Monday.com, ClickUp and about four others I can't even remember the names of now. For a complex, multi-team rollout, they're worth the money. But for most small projects, a fifteen-person webinar launch, a website rebuild, a content sprint, a spreadsheet does the job just as well and costs nothing.
Here's the thing nobody tells you when they're selling you software: the software doesn't fix a badly planned timeline. It just makes a badly planned timeline look prettier. I've seen teams pay £40 a month per seat for a tool and still miss deadlines because nobody bothered to work out realistic durations in the first place. A spreadsheet forces you to think through the actual work because there's no clever automation hiding the gaps.
The columns you need (most templates give you the wrong ones)
Open any free Gantt chart template from Google Sheets or Smartsheet and you'll usually see ten to fifteen columns. Half of them you'll never fill in. Here's what a working timeline needs, in this order:
- Task name - specific, not "design phase" but "draft homepage wireframe"
- Owner - one name, not a team, one person you can chase
- Start date
- Duration in working days
- End date - calculated, never typed in by hand
- Dependency - which task, if any, has to finish first
- Status - Not started, In progress, Done, Blocked
That's seven columns. Anything more than that and I've found teams stop filling it in within a fortnight because it feels like admin instead of a working document.
Step by step: building the timeline from scratch
I'll walk through this with a real example. Last year I planned an eight-week product launch for a client, a small SaaS company relaunching their onboarding flow. Forty-two tasks, five people, one hard deadline (a partner conference date that could not move). Here's exactly how I built it.
Step 1: list every task before you touch a single date
I spent ninety minutes with the team just listing tasks on sticky notes, no dates attached. This matters more than people think. If you start adding dates while you're still discovering tasks, you'll anchor to a deadline that was never realistic in the first place. We ended up with 42 tasks. If we'd started dating tasks from task one, we'd have run out of runway by task twenty and panicked.
Step 2: group tasks into phases
We split the 42 tasks into five phases: research (6 tasks), content and design (14 tasks), build (12 tasks), testing (6 tasks), launch (4 tasks). Phases aren't essential but they help you spot at a glance which chunk of the project is eating the most time, and content and design ate 14 out of 42 tasks, which told us where to add a freelancer.
Step 3: estimate duration in working days, not calendar days
This is where most spreadsheet timelines fall apart before they've even started. People estimate in calendar days ("that'll take a week") and forget weekends exist, or that their designer is part-time and only works Tuesdays and Wednesdays. Estimate in working days, then let the spreadsheet convert to actual dates.
Step 4: set the formula that calculates end dates automatically
This is the single most useful thing you can do in a project spreadsheet. In Google Sheets or Excel, use the WORKDAY function:
=WORKDAY(C2, D2)
Where C2 is the start date and D2 is the duration in working days. This automatically skips weekends. If your team has fixed holidays, WORKDAY has a third argument where you can list holiday dates and it'll skip those too. I add UK bank holidays for every project timeline I build, it takes two minutes and saves you from a launch date that lands on Boxing Day.
Step 5: chain the dependencies
For any task that can't start until another finishes, set its start date column to reference the previous task's end date, rather than typing a fixed date. So instead of typing "15 March" into the start date cell, you type =E5+1 (the end date of the previous row, plus one day). Do this and when one task slips, everything downstream shifts automatically. Type dates in manually and one delay means you're manually re-dating twenty rows by hand, which is exactly how timelines quietly stop being true.
Turning rows into a visual Gantt chart
Once your dates are calculating correctly, conditional formatting turns the spreadsheet into a Gantt chart without needing any special software. Add a row of date headers across the top (one column per day or week), then apply a conditional formatting rule that shades a cell if the date falls between the task's start and end date. In Google Sheets this is a custom formula rule:
=AND($C2<=E$1, $E2>=E$1)
Where C2 and E2 are your start and end dates and E1 is the date in that column's header. Colour the shaded cells by phase (research in blue, build in orange, testing in green) and you've got a useful visual timeline, built entirely with formulas that update themselves.
The bit that quietly ruins most spreadsheet timelines
Here's what almost nobody says out loud about spreadsheet timelines: the moment a task slips and nobody updates the sheet, the whole document becomes a lie that everyone keeps referring to as if it's true. I've sat in meetings where a team is discussing a "launch date" from a spreadsheet that hasn't been touched in eleven days, while two tasks are already three days behind in reality. The spreadsheet isn't wrong because the formulas are broken. It's wrong because updating it became optional the moment things got busy.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
The fix isn't a better template. It's a fifteen-minute recurring calendar slot, same time every week, where one person (usually the project owner, not whoever's free) goes through every row and updates status and actual dates. On that SaaS launch project, I did this every Friday at 4pm. It felt unnecessary about half the time. The other half, it caught a testing delay eleven days before it would have hit the launch date, giving us time to pull in an extra QA person rather than push the conference date.
If you're managing this across a bigger team, this is exactly where a lot of the friction around project management and collaboration across a business comes from, not the tool people use, but who's responsible for keeping the shared document true.
Building in buffer without lying to yourself
Add 15 to 20 percent buffer to your total timeline, not to individual tasks. If you pad every single task by 20 percent, Parkinson's Law kicks in and the work simply expands to fill the padded time, every task magically takes exactly as long as you allowed. Instead, estimate each task honestly and add one buffer block at the end of each phase. On the 42-task launch, we added a 3-day buffer after content and design, and a 2-day buffer before launch. We used the content buffer entirely (a rewrite request came in from the CEO), never touched the launch buffer, and still hit the conference date.
When a spreadsheet stops being the right tool
A spreadsheet works well up to somewhere around 50 to 60 tasks and five or six people. Past that, dependency chains get hard to trace visually, and you'll spend more time managing the spreadsheet than the project. Signs it's time to move on:
- You're spending more than 20 minutes a week just untangling formula errors
- More than one person needs to edit it at the same time and keeps overwriting each other
- You need automatic notifications when a task is overdue, spreadsheets can't nudge people, humans have to
At that point, tools built for this exist for a reason, and if you're bringing in someone to run projects, it's worth reading what a remote project manager's job involves day to day before you hire, because the spreadsheet-to-software jump usually happens at the same time a business brings in dedicated project management help.
What this looks like when the project is an AI rollout
I get asked a lot to help small businesses plan the timeline for adopting AI tools into their operations, and the exact same spreadsheet structure works, it's just the task list that changes. Instead of "draft homepage wireframe" you've got "audit which tools have API access," "train team on prompt structure," "run pilot on one department." If you're mapping this out, it's worth reading what to expect from an AI implementation project before you set your durations, because the estimation mistakes are identical, people always underestimate the change management tasks and overestimate how fast the technical setup will go. I've also written a realistic breakdown of how long AI implementation takes for a small business, and the honest range (6 to 14 weeks for most first projects) surprises almost everyone who's been told it's a weekend job by a software vendor.
A quick real example from my own business
When I was rebuilding my own business publicly a couple of years ago, I planned a content relaunch (rewriting 30 old blog posts and restructuring the site) using exactly this method. 30 tasks, one column for owner (me, mostly, plus one freelance editor), WORKDAY formulas, a Friday check in. I estimated six weeks. It took eight, because I'd underestimated how long research took for each rewrite by about 40 percent. The spreadsheet didn't stop the delay. What it did was show me the delay was happening two weeks before I'd have noticed it just by feeling generally behind, which meant I could tell the one person waiting on the output (my own editor) the real date, rather than the wishful one.
That's really the whole value of doing this in a spreadsheet rather than in your head or a scribbled notebook. Not the pretty bars. The fact that a bad date shows up as a bad date, in writing, in front of you, days or weeks before it becomes a missed deadline in front of a client.
Frequently asked questions
Which is better for a project timeline, Google Sheets or Excel?
Both handle this equally well, the WORKDAY function and conditional formatting work the same in either. Choose Google Sheets if more than one person needs to edit it at once, since real-time collaboration is smoother. Choose Excel if your organisation already lives in Microsoft 365 and you want offline access.
How many tasks is too many for a spreadsheet timeline?
Somewhere around 50 to 60 tasks with five or six people is the practical ceiling. Past that, dependency chains become hard to trace visually and you'll spend more time fixing the spreadsheet than running the project, at which point dedicated project management software earns its cost.
Do free Gantt chart templates work?
The layout works fine, most free templates from Google, Smartsheet or Vertex42 give you a decent starting structure. What they don't include is dependency-chained dates, most just have you typing dates in manually, which means the timeline silently goes wrong the first time a task slips and nobody updates every row by hand.
How much buffer should I add to a project timeline?
Add 15 to 20 percent buffer at the end of major phases rather than padding every individual task. Padding every task lets the work expand to fill the extra time, so you end up using all the buffer and still finishing late.
Primary sources
- Microsoft's own Excel documentation
Related reading: Is FlexJobs Worth Paying For When You're Job Hunting Remote? and The Jobs to Be Done Template Marketing Teams Use to Plan Content.
