NETWORKDAYS.INTL in PlanMaker: Count Custom Workdays

• Introduced: Named as new in SoftMaker Office Professional 2026; the first NX rollout date and mobile introduction are not established.
• Availability: Documented in the 2026 English reference; no final supported-version endpoint is established.
• Scope: Versioned documentation does not establish identical behavior across desktop, mobile or localized builds.
• Checked: October 14, 2026, against the official NETWORKDAYS.INTL reference, with independent calculations. No native PlanMaker test.

=NETWORKDAYS.INTL(StartDate; EndDate [; Weekend] [; Holidays])

The official reference prints semicolons in its syntax line but commas in its examples. This guide follows the comma-separated examples; use the separators accepted by your installed editor. Do not type optional brackets.

The function counts eligible dates, not hours, shifts or the number of days to advance from a starting date. The worked intervals include both endpoints when eligible. Use actual date values, preferably constructed with DATE, rather than ambiguous date text.

For a text mask, positions run Monday through Sunday. A 0 allows that weekday; a 1 excludes it. Thus "0000011" excludes Saturday/Sunday, "0000010" excludes Saturday only, and "0000110" excludes Friday/Saturday. "0000000" excludes no weekdays automatically.

Keep masks as text. In a formula, quote them; in a cell, use a text-producing formula such as ="0000010" so leading zeros are preserved. A mask is not a numeric weekend code.

Use a blank worksheet. Enter Start, End, Weekend, Workdays in A1:D1. Put =DATE(2021,1,1) in A2, =DATE(2021,1,31) in B2 and 17 in C2. Enter:

January 2021 has 31 dates, including five Saturdays and five Sundays. Excluding only Saturdays leaves 26; excluding both leaves 21. Format A2:B2 as dates and D2:D5 as numbers.

Put =DATE(2021,1,1) in H2 and =DATE(2021,1,6) in H3. These are sample exclusions, not a claim that every organization observes those holidays. In D7 enter:

=NETWORKDAYS.INTL(A2,B2,1,$H$2:$H$3)

Expect 19, matching SoftMaker’s example: both dates are otherwise eligible weekdays. Holidays are supplied by your workbook; the function does not infer a jurisdiction’s complete holiday calendar.

For a separate overlap check, put =DATE(2021,1,2) in H5. In D8 enter =NETWORKDAYS.INTL(A2,B2,1,H5). The expected count stays 21, because January 2 is already an excluded Saturday. This is a calendar-set check: excluding one date through two conditions does not create two missing workdays. Duplicate entries and invalid holiday cells are separate, undocumented edge cases.

Keep the January inputs intact. In A11:C15 enter the following start/end DATE formulas and weekend codes. In D11 enter =NETWORKDAYS.INTL(A11,B11,C11) and fill through D15:

Code 7 excludes Friday and Saturday, so Sunday is a workday. A same-day interval can therefore count either one or zero, depending on that day’s eligibility. The last row includes both Mondays and the intervening Tuesday–Friday.

For a project table with real holidays, add a fourth argument anchored to the populated holiday range, for example $H$2:$H$3. Use separate lists when teams observe different dates. Do not add sample holidays to a different year’s project merely because they occupy the same cells.

WORKDAY.INTL advances by a number of eligible days. =WORKDAY.INTL(DATE(2024,6,3),5,1) reaches June 10, 2024. NETWORKDAYS.INTL counts six eligible dates from June 3 through June 10 because it includes the eligible starting date.

For fixed Saturday/Sunday weekends, NETWORKDAYS provides the simpler interface. Neither function counts a partial workday or deducts lunch breaks.

• Too many days: check the weekend code, holiday list and whether your comparison accidentally excluded an endpoint.
• A mask loses zeros: keep it quoted or store it as text, not as the number 10.
• Sunday unexpectedly counts: it is eligible under Friday/Saturday weekend code 7.
• Different holiday rules: the formula uses your dates, not a built-in local entitlement policy.
• Reversed dates or invalid codes: the checked PlanMaker page does not define every exact result, error code, all-ones mask or date coercion. Excel’s additional rules do not establish PlanMaker behavior.

The valid examples were checked by enumerating calendar dates. Recalculation and localized date parsing still need checking when the workbook is exchanged with another application.