NETWORKDAYS.INTL()
Counts whole working days between two dates using a customizable weekend schedule.
NETWORKDAYS.INTL(start_date, end_date, [weekend], [holidays])NETWORKDAYS.INTL works like NETWORKDAYS, but lets you define which days count as the weekend instead of assuming Saturday and Sunday. This matters for businesses in regions where the weekend falls on different days, such as Friday-Saturday.
weekend accepts either a number code (1 = Sat/Sun, the default, through 7 = Fri/Sat, plus 11 through 17 for single weekend days) or a 7-character string of 1s and 0s representing Monday through Sunday, where 1 marks a non-working day.
As with NETWORKDAYS, an optional holidays range excludes specific dates on top of the weekend pattern, and both start_date and end_date are counted as working days if they don't fall on a weekend or holiday.
Arguments
- start_date
- The starting date.
- end_date
- The ending date.
- weekendoptional
- A weekend number code (1-7 or 11-17) or a 7-character string marking non-working days. Default is 1 (Saturday/Sunday).
- holidaysoptional
- An optional range of dates to exclude in addition to weekends.
Examples
=NETWORKDAYS.INTL(DATE(2024,1,1), DATE(2024,1,5), 7)Weekend code 7 treats Friday and Saturday as the weekend, so Friday January 5 is excluded; the same range under the default Saturday/Sunday weekend would count all 5 days.
=NETWORKDAYS.INTL(DATE(2024,1,1), DATE(2024,1,31), "0000001")A custom weekend string marking only Sunday as non-working models a 6-day work week, giving more working days than the default 5-day week.
NETWORKDAYS.INTL tricks, tips, and workbook hacks
NETWORKDAYS.INTL is easier to remember when you learn the small patterns around it: where it fits, what can break it, and how to combine it with neighboring functions.
Use these practical notes as a working checklist before putting the formula into a real report, model, dashboard, tracker, or reusable template.
Quick wins before you trust the result
- Start with the simplest NETWORKDAYS.INTL formula that answers the question, then add conditions or error handling only when needed.
- Keep input ranges consistent in size, shape, and meaning.
- Test the formula on one row or one small sample before filling it down a large workbook.
- Add a note beside important formulas explaining what business question they answer.
- Pair the formula with related checks so mistakes are easier to spot.
| Trick or hack | Formula pattern | Best use | Watch out |
|---|---|---|---|
| Build the formula in layers | NETWORKDAYS.INTL(start_date, end_date, [weekend], [holidays]) | When the full formula feels hard to read or debug. | Confirm each argument or nested function before combining everything. |
| Use structured references | =NETWORKDAYS.INTL(Table1[Column]) | Excel Tables make formulas easier to read and expand automatically. | Rename table columns carefully so formulas remain clear. |
| Protect against bad input | =IFERROR(NETWORKDAYS.INTL(...),"Check input") | Dashboards and shared templates where users need a readable message. | Do not hide errors until you understand why they happen. |
| Document the expected result | Add a note or nearby label | Reusable workbooks, finance models, templates, and handoff files. | A clever formula without context becomes expensive to maintain. |
| Mistake | What it looks like | Fix |
|---|---|---|
| Using a wider range than intended | The result changes unexpectedly after new rows or helper columns are added. | Use Excel Tables or named ranges to make the intended input explicit. |
| Mixing text, numbers, dates, and blanks | The answer technically works but does not match the business meaning. | Clean and validate the source column before applying the function. |
| Copying a formula with moving references | The first row works; later rows drift into the wrong range. | Use absolute references, structured references, or named ranges where needed. |
| Scenario | Use | Avoid |
|---|---|---|
| You need a quick answer from clean data | NETWORKDAYS.INTL with the smallest clear range | Overbuilding the formula with unnecessary wrappers |
| The result will appear in a dashboard | Add checks, labels, and readable fallbacks | Leaving raw errors or unexplained blanks for viewers |
| The workbook will grow over time | Excel Tables, named ranges, or structured references | Hard-coded ranges that miss new rows |
| The data comes from another system | Clean inputs before summarizing or transforming | Assuming pasted data has correct types and spacing |
Practice drills
- Write NETWORKDAYS.INTL once with direct cell references and once with an Excel Table reference.
- Break the formula on purpose, then use the error message to identify which argument failed.
- Create a small before/after example that explains the formula to another learner.
