Project Deadlines: Working Days vs Calendar Days, and What to Use When

The Question Every Schedule Has To Answer

Two project plans of "60 days" can mean very different things. Sixty calendar days from 1 March is 30 April. Sixty working days from 1 March, in a country with three intervening public holidays, is 27 May — almost a full month later. Project managers, lawyers, and clients often discover this gap only after a missed milestone. The cure is to nominate the unit explicitly in every schedule line, in every contract clause, and in every status report.

How Experienced PMs Choose

The choice is rarely arbitrary. It tends to follow three rules of thumb:

• If the work depends on people doing it — design, coding, review, manual fabrication — count working days. Weekends and holidays do not advance the work.
• If the work depends on time itself passing — concrete curing, paint drying, soil settling, fermentation, market windows, regulatory clocks — count calendar days. Weekends do not pause chemistry.
• If the deadline is externally imposed — a regulator, a court, a grant agency — match whatever unit the external party uses. Almost all statutory deadlines are calendar days.

Most professional schedules end up using working days for the activity duration and calendar days for the milestone. The Gantt chart computes effort in working days; the contract states the milestone in calendar form so it is unambiguous.

Industry Conventions

Construction

Construction contracts almost universally express completion dates in calendar days. The standard FIDIC Red Book and the AIA A201 both define the "Time for Completion" in calendar terms because weather, curing time, and statutory inspections do not respect a five-day week. Liquidated damages clauses tick over every calendar day past the deadline, even Sundays. Internal contractor scheduling, however, is done in working days because crews and subcontractors are paid by the day.

Software and IT Services

Software estimates are almost always in working days. Story points convert to ideal days of effort, sprints are two working weeks, and "person-days" are billable working days. Master service agreements often hedge by writing "30 business days" for delivery milestones and "30 calendar days" for payment terms.

Legal and Regulatory

Court filing deadlines, statutes of limitation, and regulatory windows are calendar days by default, but most jurisdictions roll a deadline that falls on a weekend or court holiday to the next working day. Tax authorities are similar: a "60 day response window" is calendar, but if the 60th day is a Sunday, the response is due Monday.

Logistics and Shipping

"3–5 business days" delivery is the universal e-commerce promise. The carrier's SLA excludes weekends and the public holidays of the origin and destination countries — which is why a package shipped on Friday afternoon often arrives later than a package shipped Monday morning, despite the same nominal lead time.

Finance

Settlement timelines (T+1, T+2) count trading days, which exclude weekends and exchange holidays. Loan interest accrues per calendar day. A bond's coupon date follows the calendar but coupon payment moves to the next business day if the calendar date is a holiday.

The Cost of Getting It Wrong

The financial impact of a unit confusion is rarely small. Three real examples:

• A construction subcontractor in the UK signed a "120 day" liquidated damages clause assuming working days. The court read it as calendar days. The interpretation cost the subcontractor 24 working days of damages — about £180,000 on a £4 million project.
• An IT vendor promised "delivery in 90 days" in calendar terms but sized the team in working days. The team finished in 90 working days = 126 calendar days. The 36-day overrun triggered a 10% penalty.
• A startup's investor agreement set a 30-day cure period for a covenant breach in calendar days. The CFO planned around 30 working days. The company missed the cure window by a week and triggered a default clause.

A Quick Decision Framework

1. Identify what is actually consumed by the duration: human effort, machine time, calendar time, or external waiting.
2. Pick working days for human effort and calendar days for everything else.
3. Convert once for the contract milestone. Compute the effort in working days, then translate to a single calendar date and write that date into the agreement.
4. State the holiday calendar when working days are used: which country, which year, which version.
5. Define what happens if a deadline falls on a weekend. The default in most jurisdictions is "next working day", but make it explicit.

Reporting Conventions for Mixed Schedules

Always report progress in the same unit you planned in. A "30 working days" task that has burned 22 calendar days has not necessarily burned 22 working days — there may have been a long weekend in the middle.

Modern scheduling tools — Microsoft Project, Primavera P6, smartsheet — let you maintain a project calendar with custom non-working days, then automatically display each task's start and finish in calendar dates while tracking effort in working hours. Use that capability rather than computing both by hand and inviting transcription errors.

The One-Sentence Rule

If a date matters, write the actual date. If a duration matters, write the unit. Never let a number sit naked next to "days" in a contract or a status report.

Try the Working Days Calculator →