How to Estimate a Team's Project Timeline

If you’ve ever multiplied team size by 40 hours and called it a project timeline, you’ve probably watched that estimate quietly fall apart by week two. The math itself is simple, but the assumption baked into it isn’t: nobody works a full 40 hours of focused, deliverable-producing time in a real week. Estimating a timeline well starts with a more honest number for how much a person can actually get done, then multiplying it by team size and dividing it into the total work.

Why 40 hours per person is the wrong number

Every team has a nominal workweek, usually 40 hours, but that number describes paid time, not productive time. Meetings, email, Slack, one-on-ones, interruptions, and context switching all draw down the hours before someone sits down to actually do the work. Depending on the role and the company, the realistic figure often lands somewhere between 25 and 35 focused hours a week, not 40.

That gap matters more than it looks like on paper. If you plan a project assuming 40 hours per person and your team actually delivers 30, you’ll miss your target date by 25 percent, not by a rounding error. The fix isn’t complicated: use a number you’ve actually observed, not the number printed on the offer letter.

Combined weekly capacity

Once you have a realistic per-person number, add up the team. A team’s combined weekly capacity is simply the number of people multiplied by how many real hours each one contributes in a week. A team of four people who each do 32 focused hours a week has a combined capacity of 128 hours, not 160. That 32-hour figure, not 40, is the one that should drive your timeline.

The formula

Combined Weekly Capacity = Team Size × Real Hours Per Person Per Week
Weeks Needed = Total Work Required ÷ Combined Weekly Capacity, rounded up to a whole week

Rounding up matters because a project that needs 1.2 weeks of work still needs two full work weeks on the calendar. There’s no such thing as delivering on day two of a partial week for most planning purposes, so the rounded figure, not the exact one, is the number to put on a schedule.

Worked example: 200 hours of work, team of 4

Say you have 200 hours of work to get through, a team of four people, and each person realistically delivers 32 focused hours a week.

• Combined weekly capacity: 4 × 32 = 128 hours
• Weeks needed (exact): 200 ÷ 128 = 1.56 weeks
• Weeks needed (rounded up): 2 weeks

Even though the math says 1.56 weeks, you can’t schedule a partial week, so the honest answer is two weeks. Anyone who told you this project would ship in a week and a half was quietly assuming a 40-hour week that doesn’t exist.

Worked example: 500 hours of work, team of 5

Now scale it up: 500 hours of work, a team of five, each contributing 30 real hours a week.

• Combined weekly capacity: 5 × 30 = 150 hours
• Weeks needed (exact): 500 ÷ 150 = 3.33 weeks
• Weeks needed (rounded up): 4 weeks

That’s a full extra week beyond the exact math, and it’s the difference between a timeline that holds and one that slips right before the deadline. Rounding up isn’t pessimism, it’s just acknowledging how calendars actually work.

What this estimate doesn’t capture

This kind of calculation assumes the work divides cleanly across the team and that adding capacity always shortens the timeline proportionally. In practice, two things push back against that.

Coordination overhead grows with team size. More people means more meetings, more handoffs, and more time spent making sure everyone’s version of the plan matches everyone else’s. A team of ten doesn’t automatically finish 2.5 times faster than a team of four, even if the combined-hours math says it should.

Not all work parallelizes. Some tasks are inherently sequential: a design has to exist before it can be built, and a build has to exist before it can be tested. Throwing more people at a bottleneck task doesn’t make it move faster, it just means part of the team ends up waiting.

Treat the weeks-needed number as a best-case floor, not a guarantee. It’s a useful sanity check against wildly unrealistic plans and a good starting point for a schedule, but it isn’t a substitute for actually breaking the project into tasks and dependencies.

FAQ

How do I figure out a realistic number of hours per person per week? Look at recent history rather than guessing. If your team tracks time, or even just has a rough sense of hours spent in meetings versus heads-down work, use that. Many teams land in the 25-35 hour range for focused output out of a nominal 40-hour week, but it varies by role and company. A support-heavy role with constant interruptions will be lower than a role with long blocks of uninterrupted time.

Should I use the same real-hours-per-week figure for every person on the team? Only as a starting simplification. Different roles and seniority levels often have different realistic capacities; a manager with a full calendar of one-on-ones has less focused time than an individual contributor. If your team is mixed, you can run the calculator once per role group and add the results together for a more accurate combined capacity.

Why round up to a whole week instead of giving a decimal answer? Because calendars don’t work in fractions of a week for most planning purposes. A project that needs 3.33 weeks still occupies four separate calendar weeks; the work doesn’t stop three-tenths of the way through the fourth week. Rounding up gives you a date you can actually commit to.

Use the Workload Calculator to run your own numbers.