Convention 1: Inclusive of both ends (Excel NETWORKDAYS)
Excel's NETWORKDAYS(start, end, holidays) counts every workday from start to end including both, skipping Saturdays, Sundays and any dates in the holidays argument. A task running Wednesday to Wednesday counts both Wednesdays plus the five workdays between: six. This matches how people think about durations — a Monday-to-Friday work week is five days, not four.
Convention 2: Exclusive of the start (payment terms)
Net-30 terms mean you have thirty days to pay — the day the invoice lands is not a payment day. Operations teams formalize this as "count from the next business day". The same Wednesday-to-Wednesday span now yields five: the anchor Wednesday is excluded. This is the counting you want for SLAs, dispute windows and "days from receipt" clauses.
Convention 3: The +1 compensation
Sheets without a NETWORKDAYS column breed a workaround: subtract the dates, then add 1 back. Numerically it matches the inclusive count — but it inherits a trap. Plain date subtraction across a month boundary, daylight-saving transitions (in tools that count hours), or a mis-typed format can each silently shift the base value. If you see +1 in someone's formula, ask how the base subtraction is computed.
The holiday wildcard
Every convention above still has to pick a holiday list. U.S. federal holidays (OPM schedule, observed dates) are the most common default; state holidays add days like Patriots' Day; companies add floating days. Two ranges that look identical can differ by one business day per holiday they cross — over a Thanksgiving week, that is the difference between "Thursday delivery" and "Friday".
Which one should you use?
Whichever the document says. Failing a document: deadlines exclude the start day; durations include both ends; and whenever money or a dispute rides on the answer, compute all three with the business days calculator and raise the ambiguity before the deadline, not after.