Just over a quarter of desk workers feel unable to say no to extra work, even when they’re already at capacity, according to Resource Guru’s State of (Over)working 2025 survey of 2,000 UK desk workers. It shows up in project schedules everywhere: plans that look tidy on paper, then buckle when real workloads hit them.
The downstream cost is steep. Only 36% of organizations mostly or always deliver projects on time, according to Wellingtone’s 2026 State of Project Management report. A big reason is that most schedules rest on a fiction: that everyone is available full-time, every day, for your project alone.
This guide is for project managers, delivery leads, and agency owners tired of that gap. It shows how to create a project schedule around your team’s real availability, so the plan survives contact with real work.
Creating a reality-based project schedule at a glance
- A project schedule maps every task, its duration, its dependencies, and its owner onto a timeline, then commits to dates.
- Most project schedules fail because they assume full-time availability, when real teams take leave, work part-time, and split time across projects.
- To build a project schedule that holds, gather each person’s real availability before you set dates, instead of leveling an idealized plan afterward.
- Assign work against each person’s genuine capacity, and treat around 80% utilization as a healthy target that leaves room for the unexpected.
- Treat a project schedule as a living forecast, updating it whenever leave, priorities, or capacity change.
What is a project schedule?
A project schedule is a time-based plan that shows what work needs to happen, in what order, by when, and who is responsible for each part. It turns a task list into a sequence of dated commitments, mapping durations, dependencies, and milestones so a team can see the path from start to finish.A complete project schedule usually contains:
- Tasks and deliverables you can track.
- Durations and effort estimates.
- Dependencies between tasks.
- Milestones that mark meaningful progress.
- An owner for every task.
- Each person’s real capacity and availability.
Why project schedules break on real team availability
A project schedule tends to unravel the moment it meets real team availability, often because it is built for an idealized team that is free full-time, and almost no team ever is. Most scheduling advice stops at tasks, dependencies, and dates, then treats each person as fully available, so the plan collides with leave, part-time patterns, and other projects.No one is available 100% of the time, and good project managers have priced that in for years. The usual workaround is to plan against a flat efficiency factor, booking people to a fixed share of the week, not the whole of it. The trouble with a single blanket percentage is that it hides where the real constraints sit: It treats a fully booked specialist and a wide-open junior as if they had the same time to give.
The failures follow a predictable pattern:
- People take annual leave, public holidays, and sick days the plan ignores.
- Part-time and compressed-hours patterns mean some were never available five days a week.
- Your best people are split across two or three live projects, so their availability for yours is a fraction of full-time.
- Meetings, admin, and context-switching eat into every working day.
A step by step guide to creating a project schedule
Every project schedule that holds is built in the same order, and getting that order right is what most plans miss. Map the work and sequence it, then set the dates against the capacity each person genuinely has. Skip that last step and the dates are just a guess.The steps below walk through each part in turn, with the detail that makes them hold.
1. Map the work: Scope, tasks, and milestones
Start by listing everything the project must deliver, then break each deliverable into tasks small enough to estimate and track. A useful test: one person or a small group can own a task and finish it within a few days.
Add milestones to mark meaningful progress, such as a client sign-off, a phase completion, or a release. Unlike tasks, milestones carry no effort or duration of their own; each one marks the point where a distinct stage of the work is finished.
A schedule is one part of the wider project management plan, so you don’t need every detail here, just enough to sequence and resource the work.
2. Sequence tasks and map dependencies
Once you have your tasks, put them in order and record what depends on what. A dependency means one task can’t start or finish until another does, so a page can’t be published until its copy is signed off.
Keep the types plain: most schedules only need to know that task B waits on task A. Make those links visible in the schedule itself, not buried in a notes column.
Mapping the chain of dependent tasks also reveals your critical path, the longest sequence that sets the earliest possible finish. The critical path method shows which slips move your end date and which don’t.
3. Get real availability before you set dates
This is the step most schedules get wrong. Before you commit to a single date, find out how much time each person actually has for this project. Done well, it’s about how you plan and distribute tasks across a team: You build the schedule from the hours people genuinely have to give.
Gather four things for everyone on the team:
- Booked time off: Annual leave, public holidays, and known appointments.
- Working pattern: Who works part-time, compressed hours, or protected non-project days.
- Existing commitments: How much of each week is already allocated to other live projects.
- A realistic utilization target: Aim for around 80% rather than 100%, leaving room for meetings, admin, and the unexpected.
The fastest way to see all of this at once is a capacity planning view showing each person’s real availability across every project they’re on, not just yours. Then you’re scheduling against reality instead of a hopeful guess.
4. Estimate durations with the people doing the work
Estimates are more accurate when they come from the people who’ll do the work. Ask each task owner how long it realistically takes, then sense-check against similar past projects.
Build in the time real work needs but plans forget:
- Reviews and approvals, which often wait on someone else’s availability.
- Rework after feedback, because few deliverables are right first time.
- Handovers between people, where context has to transfer.
5. Build the schedule around capacity, not full-time assumptions
Now assign the work. Place each task against the real availability you gathered, not an idealized full-time week, and watch what happens to your dates.
This is where over-allocation shows up honestly. If a designer is already 70% committed to two other projects, they don’t have room for a task that assumes their whole week. You see the clash straight away, while you can still fix it, instead of in week three.
Resolve it before you lock any dates. You have a few levers:
- Move the task to someone with genuine capacity.
- Push the start until the owner is free.
- Reduce the scope, or split the task.
6. Add buffers and protect the critical path
Even a schedule built on real availability needs breathing room. Add buffers where risk is highest: tasks with uncertain estimates, external dependencies, or client inputs you don’t control.
Put the buffer where it protects the outcome, concentrated in a few deliberate places. Hold some at the end of the critical path, where slippage in the tasks that drive your end date has somewhere to go.
Keep the critical path realistic given real capacity. If the sequence that sets your finish date runs through one over-committed person, no buffer will save it. Protecting the critical path usually means protecting the availability of the people on it.
7. Share it, then monitor and re-forecast as availability changes
A schedule is a living forecast, not a document you publish once and file away. The moment someone books leave, a priority shifts, or a task runs long, the plan needs to catch up.
Share it somewhere the whole team can see and update, so availability changes surface early rather than at the deadline. When capacity moves, re-forecast: shift the affected tasks, check the knock-on effects on the critical path, and confirm the end date still holds.
Deadlines hold when the schedule stays honest. Meeting deadlines is far less about heroics near the end than about keeping the plan in step with real capacity throughout.
An example of a project schedule built around availability
Take a small website project at a five-person agency: three weeks of work on paper, staffed by a designer, a developer, and a copywriter, all assumed to be free full-time. Scheduled that way it looks comfortable, every task fits, and the timeline lands on day 15.
Now rebuild it around real availability:
- The designer is already 60% booked on another client, so their two-day task spans a week.
- The developer has two days of pre-booked leave in week two.
- The copywriter works a four-day week.
| Assumption | Designer’s task | Developer window | Finish |
|---|---|---|---|
| Idealized full-time | Days 1 – 2 | Days 6 – 8 | Day 15 |
| Real availability | Days 1 – 5, part-time | Days 8 – 11, after leave | Day 21 |
Where project schedules break: Common availability pitfalls
Most schedules break at the same few points, and each comes from planning around an ideal team. The good news is they are easy to spot once you know what to look for, so check for these four before you commit to any dates:
- The full-time fiction. The plan assumes everyone is free five days a week for your project alone. Check whether any name is booked near 100% once their other work is counted.
- The over-committed specialist. One person sits across three projects, booked well beyond full capacity. Total each person’s commitments across all their projects, yours included.
- The mid-project disappearance. A key person has leave booked partway through the plan that nobody accounted for. Check time off across the whole timeline before dates are set.
- Capacity as an afterthought. The schedule is built first and resourced later, so clashes appear only once work starts. Gather availability first, before you commit to any dates.
Frequently asked questions about creating project schedules
How do you make a simple project schedule?
You make a simple project schedule by listing the tasks, putting them in order, estimating each one, and assigning owners against their real availability. Keep it to the essentials: the tasks, the dates, the dependencies between them, and who is responsible for doing what.
How can I create a project schedule in Excel?
You create a project schedule in Excel by listing tasks down the rows, with columns for the start date, duration, owner, and dependencies, then adding a bar chart for a basic Gantt view. It works for small projects, though keeping real availability current by hand grows painful as the team scales.
Is there a free template for project planning?
Free templates for project planning are widely available, from spreadsheet Gantt charts to task lists and milestone trackers, and any of them give you a running start. A template supplies the structure, but it cannot capture your team’s real availability, so you still have to gather and maintain that yourself. Your best bet is to use purpose-built project planning software to minimize that overhead.
What is an example of a project schedule?
An example of a project schedule is a three-week website build with tasks for design, development, and copy, each carrying a duration, an owner, and its dependencies. The realistic version sequences those tasks around each person’s genuine availability instead of an idealized full-time week, so the dates actually hold.
How do you schedule around team availability?
You can schedule around team availability by gathering each person’s real capacity before you set any dates: their booked leave, their working pattern, and their existing commitments on other projects. Total those commitments across every project, assign work against what is genuinely left, and re-forecast the plan whenever that capacity shifts.
Build a schedule your team can actually deliver
A schedule holds when it is built around the people you actually have, with their leave, part-time weeks, and other projects priced in from the start. Discipline and sharper estimates help, but they cannot save a plan that assumed an ideal team. Availability-first scheduling front-loads those hard truths while options remain.
You find where people are overcommitted while there is still time to move work, well before it surfaces in a status update. Build the schedule around real availability and the date you publish is the date you actually hit.
To go deeper on the mechanics, Resource Guru’s guide to resource scheduling covers how to keep capacity visible as projects change.