What Are the Day Numbers in a SharePoint Calculated Column?
Use this interactive calculator to convert any date into the exact day number logic commonly used in SharePoint calculated columns. You can check day of month, day of year, weekday number, and the days between two dates using the same concepts behind formulas such as DAY, WEEKDAY, and simple date subtraction.
Results
Select a date and click the button to see the SharePoint-style day numbers.
Weekday Number Comparison Chart
Understanding day numbers in a SharePoint calculated column
If you have ever searched for “what are the day numbers SharePoint calculated column,” you are usually trying to answer one practical question: when SharePoint looks at a date, what number does it return for the day? The answer depends on which function you use. In SharePoint calculated columns, the most common date functions for this topic are DAY, WEEKDAY, and direct date subtraction. These are simple on the surface, but they are often confused because each one returns a different kind of day number.
Here is the fast version. DAY([Date]) returns the day of the month, so a date like May 19 returns 19. WEEKDAY([Date]) returns the day of the week as a number, but the numbering system can vary. Direct subtraction like [End Date]-[Start Date] returns the number of elapsed days between two dates. That means there is not just one “day number” in SharePoint. There are several, and your reporting logic depends on choosing the correct one.
This matters in real business lists. Teams use SharePoint calculated columns to classify tickets by weekday, create compliance deadlines, assign review windows, and label records according to reporting periods. If the wrong day-number system is selected, your labels can shift by one day, weekend rules can fail, and conditional formulas can route work to the wrong team. The calculator above helps you test those values before you build a production formula.
The three main meanings of “day number” in SharePoint
1. Day of the month
The most straightforward day number is the day of the month. This is what SharePoint returns with the DAY function. If a date column named Date contains 2025-03-14, then the formula below returns 14:
This is useful when you want monthly billing checkpoints, anniversary reminders, monthly grouping, or custom text like “Invoice due on day 15 of each month.” The range is always 1 through 31.
2. Day of the week
The second common meaning is the weekday number. This is where most confusion happens. In spreadsheet-style systems, weekday numbering can start on Sunday or Monday, and some systems start counting at zero rather than one. In SharePoint, formulas often follow Excel-like behavior, so you must verify the numbering method you want. A typical default interpretation is:
In a Sunday-first system, that usually means Sunday = 1, Monday = 2, Tuesday = 3, Wednesday = 4, Thursday = 5, Friday = 6, and Saturday = 7. However, some implementations and formula designs use Monday-first logic, especially when users are building workweek and SLA calculations.
3. Elapsed days between dates
The third meaning is the number of days between two dates. This is not a weekday code. It is a duration. For example, if you subtract Start Date from End Date, SharePoint returns the number of whole days between them:
This is ideal for aging reports, contract lead times, onboarding completion windows, project turnaround, and retention periods. If your search intent is to measure delay or elapsed time, this is the day number you probably need.
How weekday numbering systems compare
Below is a simple comparison of the three weekday numbering models users most often reference when designing a SharePoint calculated column. This is also the logic used by the calculator chart above.
| Weekday | System 1 | System 2 | System 3 | Best use case |
|---|---|---|---|---|
| Sunday | 1 | 7 | 6 | Reporting systems that treat Sunday as the first day of the week |
| Monday | 2 | 1 | 0 | Business workflows that start the workweek on Monday |
| Tuesday | 3 | 2 | 1 | Workweek calculations and scheduling logic |
| Wednesday | 4 | 3 | 2 | Middle of week milestone checks |
| Thursday | 5 | 4 | 3 | Escalation and cut-off routines |
| Friday | 6 | 5 | 4 | Weekend-trigger and payroll logic |
| Saturday | 7 | 6 | 5 | Weekend blocking and staffing rules |
When teams say “What are the day numbers?” they are often asking for this exact mapping. If you are building business-day formulas, always choose the numbering system before you write nested IF statements. A mismatch here is one of the most common causes of faulty weekend logic.
Examples of useful SharePoint day formulas
Return the day of month
Return a weekday number
Convert weekday number to a text label
Calculate elapsed days between two date columns
Flag weekends using a Sunday-first numbering system
Even though these formulas look simple, the business impact can be significant. For example, a records team may archive files 30 days after approval. A payroll team may calculate whether an employee submitted time before Friday cut-off. A customer support list may highlight tickets older than 3 days. Each of those scenarios uses a different type of day number.
Real calendar statistics that help explain SharePoint date logic
It may seem unusual to include calendar statistics on a SharePoint page, but they help explain why date formulas are stable and predictable. SharePoint ultimately relies on the Gregorian calendar structure used across modern business systems. That structure is not random.
| Gregorian 400-year cycle statistic | Value | Why it matters for formulas |
|---|---|---|
| Total days in 400 years | 146,097 | Date arithmetic remains consistent over long reporting periods |
| Total weeks in 400 years | 20,871 exact weeks | Because the total is an exact number of weeks, weekday distribution is perfectly balanced |
| Common years in cycle | 303 | Most years have 365 days, which affects annual elapsed-day formulas |
| Leap years in cycle | 97 | Leap years add an extra day and affect February, day-of-year, and difference calculations |
| Occurrences of each weekday in 400 years | 20,871 each | Every weekday appears the same number of times across the full cycle |
| Average year length | 365.2425 days | Explains why leap-year handling is required in enterprise systems |
That last point is especially useful. Across a full 400-year Gregorian cycle, each weekday occurs exactly 20,871 times. This statistical balance is one reason why weekday numbering systems are easy to transform mathematically. If your formula seems inconsistent, the issue is usually not the calendar. It is usually the chosen return type, regional settings, or an off-by-one logic error.
Common mistakes when using day numbers in SharePoint
- Confusing day of month with weekday number. DAY([Date]) and WEEKDAY([Date]) do not return the same thing.
- Assuming Monday is always 1. In many default setups, Sunday is 1 instead.
- Ignoring locale or site conventions. A global team may document weekdays one way while your formula uses another.
- Forgetting leap years. Day-of-year and elapsed-day calculations can shift around late February.
- Using date subtraction without checking time values. If time is included, partial-day behavior can surprise users.
- Building nested IF formulas before validating a sample date. Test with a known Monday, Friday, and Sunday first.
How to choose the right day-number method
- Define the business question. Are you classifying a weekday, extracting the date within a month, or measuring elapsed time?
- Choose the correct function. Use DAY for day of month, WEEKDAY for day of week, and subtraction for duration.
- Document the numbering system. Write down whether your workflow treats Sunday or Monday as the first day.
- Test sample dates. Use known calendar dates to confirm the exact values returned.
- Add text labels when needed. Numeric logic is efficient, but user-facing columns are often clearer with names like Monday or Friday.
- Validate with real process owners. Finance, HR, legal, and operations teams often define weeks differently.
Why this matters for reporting, automation, and governance
Day numbers are not just a formula detail. They affect dashboards, approval routing, reminders, retention schedules, and audit trails. A weekday-based escalation can fail if Sunday and Monday are swapped. A monthly review can trigger on the wrong date if DAY is confused with elapsed days. In regulated environments, even a one-day error may change whether an action is considered on time.
That is why mature SharePoint teams test date formulas with reference examples before launch. They also document the exact formula behavior in list settings, workflow notes, or governance standards. The calculator on this page is designed to make that validation easier. It gives you a fast way to see the different meanings of “day number” for a specific date and compare weekday numbering methods side by side.
Reference links and authoritative resources
If you want additional background on date systems, calendar structure, and institutional SharePoint environments, these sources are worth reviewing:
- National Institute of Standards and Technology: Time and Frequency Division
- NIST: A Walk Through Time
- Cornell University IT: SharePoint Online
Final answer: what are the day numbers in a SharePoint calculated column?
The best direct answer is this: there is no single day number in SharePoint. If you use DAY([Date]), the result is the day of the month from 1 to 31. If you use WEEKDAY([Date]), the result is the weekday number, such as Sunday = 1 through Saturday = 7 in a common default pattern. If you subtract one date from another, the result is the number of elapsed days between them. Once you know which meaning your workflow needs, the formula becomes much easier to design and test.