
Costs
Part of Why a year's working day total starts with 260, 261 or 262 weekdays
Working Days Per Year Examples: Fiscal Baseline Checks
Working days per year examples: build a fiscal-span weekday baseline from monthly counts, subtract the federal holiday list for three spans, and reverse-check a reported total.
Working days per year examples can be misleading when the period is not January through December. This guide builds a weekday baseline for a fiscal or other twelve-month span from its component months, then reverse-checks a reported working-day total against the closure days it subtracts.
The worked span runs from April 1, 2027, through March 31, 2028, with both endpoints counted. It separates the weekday baseline from an organization-specific closure list, so a reported net total can be checked rather than treated as a black-box result.
Define the period before you count
Write down the first date included and the last date included before using a yearly total. Fiscal-year labels do not tell you the boundaries by themselves: the U.S. federal government fiscal year begins October 1 and ends September 30 of the following year. A different organization or reporting task may use a different span.
Also record whether the endpoints count. The example below includes both April 1 and March 31, and its monthly pieces cover every date in that interval exactly once. If the range starts or ends partway through a month, use only the dates inside the range for that partial month; do not add the full month’s count.
Finally, define which days count as workdays for the task. A weekday baseline is not automatically a working-day total: closures must be applied separately, and a different rest-day convention changes the baseline. The monthly formula explains how to get month counts; the fiscal-span task is to select and combine only the months that belong to your date range.
Assemble the fiscal-span baseline
For April 1, 2027, through March 31, 2028, first total April through December 2027. In month order, those weekday counts are 22, 21, 22, 22, 22, 22, 21, 22, and 23, for a subtotal of 197. Then add January, February, and March 2028: 21, 21, and 23, for a subtotal of 65. The full span contains 262 weekdays before closures.
| Part of the span | Monthly weekday counts | Subtotal |
|---|---|---|
| April–December 2027 | 22, 21, 22, 22, 22, 22, 21, 22, 23 | 197 |
| January–March 2028 | 21, 21, 23 | 65 |
| Full span | 262 |
The 2027 monthly chart is a useful visual cross-check for the first part of this calculation. It is not a ready-made fiscal-year answer: the span also includes three months from 2028, and partial months in other date ranges need separate treatment. Keep the month sequence or a month-by-month worksheet with the calculation so another person can reproduce the subtotal.
The weekend or rest-day convention belongs in the calculation record, too. The 2027 comparison below shows why a year total is not transferable across conventions; a fiscal span must apply one selected convention consistently to every included date. See how national calendars differ when the applicable convention depends on the location or calendar.
2027 totals by rest days
Rest days
- Saturday and Sunday
- 261
- Friday and Saturday
- 260
- Thursday and Friday
- 260
- Sunday only
- 313
- Friday only
- 312
2027 total
- Saturday and Sunday
- Friday and Saturday
- Thursday and Friday
- Sunday only
- Friday only
Subtract a holiday list: net totals for three spans
A weekday baseline becomes a working-day total only after a closure list is applied. The U.S. Office of Personnel Management publishes the federal holiday schedule with observed dates: a holiday on a Saturday is observed on the preceding Friday, and one on a Sunday moves to Monday.
For April 1, 2027, through March 31, 2028, eleven federal holidays fall inside the span, all on weekdays: May 31, June 18, July 5, September 6, October 11, November 11, November 25, December 24 and December 31, 2027, then January 17 and February 21, 2028. June 18, July 5, December 24 and December 31 are observed dates. The net total is 262 minus 11, or 251.
The same method works for other spans. These totals apply the federal list only. A private employer chooses its own closures.
| Span | Weekdays | Federal holidays inside | Net working days |
|---|---|---|---|
| April 1, 2027 to March 31, 2028 | 262 | 11 | 251 |
| October 1, 2026 to September 30, 2027 (federal fiscal year) | 261 | 11 | 250 |
| Calendar year 2028 (leap year) | 260 | 10 | 250 |
The federal fiscal year 2027 holidays are October 12, November 11, November 26 and December 25, 2026, then January 1, January 18, February 15, May 31, June 18 (observed), July 5 (observed) and September 6, 2027. Calendar 2028 has 366 days but only 260 weekdays, because its two extra days fall on a Saturday and a Sunday. New Year's Day 2028 is observed on December 31, 2027, so it does not reduce the 2028 total, and Veterans Day is observed on Friday, November 10.
The rest-day convention changes the baseline before any holiday is subtracted. For calendar 2027 a Sunday-to-Thursday week gives 260 days, against 261 for Monday to Friday, because the one extra day in 2027 is a Friday. Holiday lists also differ by country, so apply the list that matches the calendar.
Reverse-check a reported working-day total
A useful audit works backward from the claimed result. Start with the weekday baseline for the exact date range, then subtract only closure dates that fall on days that would otherwise count as workdays under the chosen convention. In compact form: baseline minus qualifying closure days equals the reported working-day total.
For the April–March example, the baseline is 262. If someone supplies a lower total, subtract that claim from 262 to find how many weekday closures the claim implies. Then request the dated closure list and check each entry against the range and the selected workday convention. A count of closure entries is not enough: entries outside the span or on rest days may not reduce the baseline.
The 2027 example shows the same audit on a calendar year, with a hypothetical claim. A claimed total of 252 against a weekday baseline of 261 implies nine weekday closure deductions. If the list has eleven entries, two fall on weekends, and there is no substitution rule, the nine deductions reconcile. If the list has nine entries but one falls on Sunday, the total should be 253 instead: one listed closure was subtracted even though it did not remove a weekday from the baseline.
For each item, note the date, whether it lies inside the span, whether it falls on a workday under the selected convention, and whether the calendar being checked treats it as a closure. Do not infer a substitute closure date unless the applicable list or rule supplies one. The dated closure days page is relevant when a particular calendar’s closure dates are part of the question.
Make the result reproducible
Keep a compact audit record alongside the number. It should let a reviewer identify the span, reproduce the baseline, and see precisely which entries were subtracted.
- Record the first included date, last included date, and endpoint convention.
- State the workday or rest-day convention used for the baseline.
- Save the month counts and the arithmetic for any cross-year span.
- List every closure deduction by date, including the reason it qualifies.
- Recalculate the period independently, either from its component dates or from the month totals, and compare the result.
If two totals disagree, compare the underlying records before changing the arithmetic. A difference may come from an omitted or duplicated boundary date, a closure outside the range, a weekend entry treated as a closure, or inconsistent treatment of substitute dates. The day-stepping version uses related date-by-date arithmetic, but an annual audit still needs the correct date range and closure list.







