METHODOLOGY
How DatePilot builds and verifies its calculators
Every calculator is built from a stated rule and checked against boundary cases. This page explains what "verified" means here, how the tests work, and what the tools deliberately do not do.
What "verified" means on this site
"Verified" is not a guarantee. On DatePilot it means four things: the method is written down, the worked examples are reproducible, the calculator passes its automated tests, and the page links the sources behind the rule. It also means a human editor has reviewed the page and recorded the review date.
We do not describe a result as official, certified, or error-free. No date calculator can know the rules of a particular contract, employer, court, or country. The tools calculate a stated convention accurately; applying that convention to a consequential decision remains the user's responsibility.
The calculation pipeline
- Parse: read the input as a calendar date or a local date-time, rejecting impossible dates such as 31 February.
- Validate: check required fields, whole-number limits, and whether the end date is after the start date where the tool requires it.
- Calculate: apply the stated rule, using calendar arithmetic rather than average month or year lengths.
- Format: show the result with its weekday, unit, or time zone so the answer can be read in context.
- Explain: state the method, assumptions, and limitations beside the result and in the page methodology.
The same rule is used in the calculator and in the worked examples. That is deliberate: if an example and the tool ever disagree, one of them is wrong, and the discrepancy is a bug to be fixed.
Test strategy
| Test type | What it covers | Example case |
|---|---|---|
| Date arithmetic | Day, week, month, and year shifts; forward and backward movement | 31 January + 1 month clamps to 28 February in a common year |
| Leap and century rules | 29 February; years divisible by 4, 100, and 400 | 2024 and 2000 are leap years; 2100 is not |
| Business-day rules | Monday-to-Friday counting in both directions | Friday + 1 business day is Monday |
| Week numbering | ISO week 1, week 53, and the week-year boundary | 1 January 2027 is ISO week 53 of 2026 |
| Time zones | Named zones, UTC offsets, and daylight-saving transitions | New York is UTC−5 in January and UTC−4 in July |
| Recurring schedules | Month-end clamping, skipping, and weekday intervals | 31 January monthly clamps through February |
| Format conversion | Ambiguous numeric dates and explicit day/month order | 03/04/2026 is flagged instead of guessed |
| Integrity | Internal links, related tools, guide references, sitemap, and route shells | Every internal link resolves to a built page |
The repository runs these checks with the project test command and the production build. The build also validates that every route has a metadata entry and that the sitemap matches the route list, so a page cannot silently disappear from navigation or search.
Worked examples are reproducible
Each tool page includes a "Verified examples" table with fixed inputs and expected results. Enter the same inputs in the calculator and the same result should appear. If it does not, the page or the tool has changed in a way that was not reviewed. Report the difference using the Report an error page and include the inputs you used.
Examples are chosen to include a boundary case, not just an easy one. A day-count example crosses February. A month example lands on a 31st. A time-zone example crosses a daylight-saving change. A business-day example starts on a Friday. These are the cases where a plausible but wrong method gives a different answer.
Known limitations
- Device clock: countdown and time-since tools read the visitor's device clock, which may be unsynchronised.
- Time zone data: conversions use the browser's IANA database; a future political change may not yet be in that version.
- Holidays: working-day and business-day tools do not apply public holidays, regional holidays, or company closures.
- Legal and contractual rules: statutory notice periods, court deadlines, payroll rounding, and tax rules are not modelled.
- Time of birth: age tools use calendar dates and do not model legal age rules that depend on the time of day.
- Historical calendars: weekday and date tools use the proleptic Gregorian calendar, which may differ from the calendar a country used before its reform.
- Leap seconds: day counts use calendar midnights, not the sub-second adjustments that affect UTC timestamps.
- No professional advice: DatePilot is not a substitute for legal, financial, medical, or official advice.
Versioning and maintenance
Content and calculator changes are recorded on the changelog. Each content page carries a last-reviewed date, and the structured data on the page carries the same date as dateModified. When a source changes or a correction is confirmed, the page is updated and the date moves with it.
The review is not a claim that every conceivable case has been tested. It is a claim that the stated method is documented, the included cases pass, and the limitations are disclosed. If you rely on a result for something important, reproduce it with the worked example and, where the stakes are legal or financial, verify it with the responsible authority.
How to reproduce or challenge a result
- Open the tool page and find its "Verified examples" table.
- Enter the same inputs exactly as written, including the unit and direction.
- Compare the result with the expected result in the table.
- If they differ, check the convention: endpoint inclusion, business-day basis, time zone, or month-end rule.
- If the difference remains, report the page URL, inputs, expected result, and actual result through the Report an error page.
Tool-by-tool verification focus
| Tool | Primary verification focus |
|---|---|
| Date Calculator | Month-end clamping; year boundaries; negative amounts |
| Age Calculator | Leap-day birthdays; month borrowing; completed anniversaries |
| Age Difference Calculator | Input order; anniversary decomposition; total days |
| Days Between Dates | Exclusive counting; February; leap years |
| Days Calculator | Both directions; whole-day validation |
| Add Days / Subtract Days | Month and year overflow; weekends; clamping |
| Working Days | Inclusive endpoints; Monday-to-Friday rule |
| Business Date Calculator | Weekend skipping in both directions; start-date exclusion |
| Recurring Date Calculator | Month-end clamp/skip; weekday intervals; limit handling |
| Deadline Calculator | Forward and backward modes; calendar vs business days; buffers |
| Day of the Week | Gregorian weekday lookup; leap day |
| Week Number | ISO week 1, week 53, and week-year changes |
| Leap Year | Divisibility by 4, 100, and 400 |
| Quarter Calculator | Calendar and custom fiscal starts; inclusive day totals |
| Day of Year | Common vs leap years; remaining days and percentages |
| Countdown | 17:00 local target; device clock; passed targets |
| Time Since | Local past date-time; future input; live refresh |
| Time Difference | Cross-midnight spans; minute rounding; direction note |
| Work Hours | Overnight shifts; unpaid breaks; decimal hours |
| Time Zone Converter | IANA zones; daylight-saving offsets; date changes |
| Date Format Converter | Ambiguity handling; explicit day/month order; output variants |
Frequently Asked Questions
Are DatePilot calculators tested?
Yes. Date arithmetic, leap years, business days, week numbers, time zones, recurring schedules, and format conversion are covered by automated tests, and each tool page publishes fixed examples that can be reproduced in the calculator.
Why do some results differ from other websites?
Usually because the conventions differ: exclusive versus inclusive counting, calendar months versus 30-day months, Monday-to-Friday versus a local working week, or a different time zone database. Each DatePilot tool states its convention beside the result.
Can I rely on a DatePilot result for a legal deadline?
No. DatePilot provides general-purpose calculations, not legal or official advice. Verify legal, financial, employment, tax, and contractual deadlines with the responsible authority.
How do I report a wrong result?
Use the Report an error page and include the page URL, the inputs, the result you expected, and the result the site gave you. Confirmed calculation errors are prioritised.
Questions or corrections? Email bazminoadsense2@gmail.com or use the error report form.