Almost every project plan is a week count wearing a chart. "Twelve weeks to launch", "four weeks of testing", "a two-week sprint" - the week is the unit of planning because it matches how teams meet, report and rest. But a week on a timeline can mean three different things: elapsed calendar weeks, working weeks of five days, or the numbered weeks of the year. Plans go wrong when those meanings get mixed. This guide shows how to count weeks for a project timeline cleanly, with a worked example and the adjustments that separate a realistic plan from an optimistic one.
Step 1: fix the start and the deadline, then count
Every timeline count starts with two dates, not with a duration. Take the kickoff date and the delivery date and count the days between them, then divide by 7. A project that starts on Monday, March 2, 2026 and must deliver on Monday, May 25, 2026 spans 84 days - exactly 12 weeks. That clean answer is no accident: picking a Monday start and a Monday deadline keeps every project week aligned with the calendar week, so "week 6" means the same thing to everyone in the room. If your dates do not divide cleanly, you get full weeks plus leftover days - say 11 weeks and 5 days - and you should plan with both figures in view, not round the span up to 12 weeks and invent two extra days of capacity. The weeks between dates calculator gives you the full weeks, the leftover days and the decimal figure for any start and deadline pair.
Step 2: number the weeks and place the milestones
Number the project weeks from the start: Week 1 is the first seven days, not the first calendar week the project touches. With a March 2 start, Week 1 runs March 2-8, Week 6 runs April 6-12, and Week 12 ends on May 25. Milestones belong at week boundaries - "design signed off end of Week 3" means March 22 - because midweek milestones drift as soon as someone interprets them loosely. For reporting, pair each project week with its calendar dates, and, if your organization uses them, its ISO week numbers: the week starting Monday, June 1, 2026 is ISO week 23, which lets a timeline line up with other teams' plans without a conversion argument.
Step 3: convert elapsed weeks into working capacity
Twelve elapsed weeks contain at most 60 weekdays, and real projects never get all 60. Subtract the public holidays inside the span - in a March-to-May US span, Memorial Day on Monday, May 25, 2026 takes the deadline day itself out, which is the kind of detail a week count alone hides. Subtract known leave, part-time patterns and the standing meetings that eat Fridays. What remains is the working capacity, and it is usually 10 to 15 percent below the naive figure. This is why planners keep two numbers: elapsed weeks for the calendar promise, workdays for the workload. The days between calculator shows business days with US federal holidays removed for the same span, which is the fastest sanity check on a plan's capacity.

Step 4: handle the partial weeks at both ends
Real projects rarely start on Mondays. A Wednesday kickoff gives you a 3-working-day first week, and calling it "Week 1" without qualification leads someone to staff it as five days. Label it honestly - Week 1 (partial, 3 days) - or renumber so Week 1 is the first full week and the stub is Week 0. The same applies at the end: a deadline on a Wednesday means the final week holds 3 working days, and any task estimated at "a week" does not fit in it. Partial weeks are also where slippage hides; a plan that is "two days behind" in a partial week may actually have consumed half that week's capacity.
Step 5: add buffer as weeks, visibly
Experienced planners hold buffer in whole weeks at the end of the plan - one buffer week per six to eight working weeks is a common ratio for projects with outside dependencies - rather than padding every task. Whole weeks are the right granularity for buffer because risks arrive in week-sized lumps: a supplier slips a week, a review cycle takes a week, a key person is out a week. Visible buffer can be reported against ("we have used one of our two buffer weeks"), which keeps the deadline conversation honest. Padded tasks, by contrast, expand silently and the plan still delivers late.
Reporting progress in weeks without fooling yourself
Week counts also drive the status report, and here the honest measure is not elapsed weeks but completed work measured in weeks. A project at the end of Week 6 of 12 is 50 percent through its calendar, but if the two hardest integrations sit in Weeks 9 and 10, it is nowhere near 50 percent done. Mature teams track two week numbers side by side: weeks elapsed, and weeks of work earned - the planned duration of everything actually finished. When earned weeks trail elapsed weeks, the gap, expressed in weeks, is the slippage, and it can be compared directly with the buffer weeks you set aside. This only works if the original week count was honest: full weeks counted from real dates, partial weeks labeled, holidays removed from capacity. A timeline built on rounded week counts produces progress reports that look calm until the week they suddenly do not.
Sprints and other fixed cycles ride on the same count
Agile teams add one more layer: the sprint. A 12-week project planned in two-week sprints contains exactly 6 sprints, but only if sprint boundaries align with project weeks - a sprint that starts on the Wednesday of Week 1 ends mid-Week 3, and every later boundary sits awkwardly inside a week, so "end of sprint 4" and "end of Week 8" stop being the same day. When you lay the timeline out, choose one grid and force the other onto it: either sprints are the grid and milestones live at sprint ends, or calendar weeks are the grid and sprints are fitted inside them. Mixing the two grids informally is how a plan ends up with a milestone that falls on no boundary anyone tracks.
A counting checklist
| Check | Why it matters |
|---|---|
| Start and deadline on the same weekday | Gives whole weeks and unambiguous week numbers |
| Holidays inside the span listed | Each weekday holiday removes a working day from a week |
| Partial first and last weeks labeled | Stops a 3-day week being staffed as a 5-day week |
| Elapsed weeks and workdays both stated | Separates the calendar promise from the capacity |
| Buffer held in whole weeks at the end | Makes slippage visible instead of absorbed silently |
Frequently asked questions
How do I count weeks for a project timeline?
Fix the start date, count the days to the deadline, and divide by 7 for full weeks. A project from Monday, March 2 to Monday, May 25, 2026 runs 84 days, which is exactly 12 weeks. Then check which holidays fall inside those weeks and adjust the working time.
Should a project week start on Monday or on the start date?
Either works if you are consistent, but a Monday start aligns with calendars, week numbers and status meetings. If the project starts midweek, call the first partial stretch Week 0 or Week 1 (partial) so nobody counts it as a full week of capacity.
How do holidays affect a project week count?
They do not change the elapsed weeks, but they shrink the working days inside them. A 12-week span with two weekday holidays holds 58 working days instead of 60. Plan capacity in workdays and report progress in calendar weeks.
What is the difference between elapsed weeks and working weeks on a timeline?
Elapsed weeks measure time passing - 12 weeks from March 2 is May 25. Working weeks measure effort - five workdays each. A timeline needs both: elapsed weeks for dates, working weeks for how much can actually get done.
How much buffer should a week-based plan include?
A common rule is one buffer week for every six to eight planned weeks on work with outside dependencies, held at the end rather than padded into every task. Visible buffer gets managed; hidden padding just gets spent.
