AI working day audit: check a date against a fixed calendar

Specify a fictional working calendar before calculating

AI means artificial intelligence. An AI working day audit should start with an explicit date-counting contract. Our practice begins on Friday, 2026-10-23, and advances three eligible working dates after that start. The start date itself is not counted. Saturday and Sunday are skipped. One additional date, 2026-10-26, is excluded by the fictional exercise calendar.

That extra exclusion is a made-up closure for the exercise, not a statement about a public holiday or a real employer. There is no actual customer request, service-level agreement, legal deadline or delivery guarantee. The card uses dates only: no hours, time zones, partial days or request-acceptance cutoff. All of those would need their own rules in a real task.

Write the contract: “Practice V1; start 2026-10-23 excluded; advance three eligible dates; weekends Saturday/Sunday; additional exclusion 2026-10-26; stop when the count reaches three.” Preserve the explicit exclusion even though it falls on a weekday. A Monday is not automatically eligible when the supplied calendar says otherwise.

The business data analysis guide explains the broader habit of describing inputs. Here the deliverable is a saved date-by-date ledger showing skipped dates, counted dates and the resulting date under this one stipulated calendar.

Keep the five source conditions together

Use year-month-day notation throughout. For example, 2026-10-23 means 23 October 2026, not a month/day ambiguity. These dates and the closure were selected as teaching inputs. They are not observations from a business or results generated by an AI system. The calculation can be completed manually.

Before counting, read all five fields back. Three days and three eligible working dates are different instructions. The extra exclusion is also a separate condition from the weekend rule. Do not erase it because a general calendar application shows Monday as a weekday.

In a real handoff, unknown calendar inputs should remain questions. You might need confirmation of local closures, weekend patterns or the date from which counting begins. This exercise deliberately supplies those inputs so the reader can inspect the arithmetic without researching a real holiday schedule.

The spreadsheet prompt collection offers templates for describing columns and acceptance checks. For this audit, no spreadsheet subscription or formula execution is necessary. Keep a source card and a separate answer ledger rather than replacing the original inputs with a polished final date.

Which dates count, and which must be skipped?

Start at 2026-10-23 with a count of zero. The next date is Saturday the 24th, so skip it. Sunday the 25th is also skipped. Monday the 26th is a weekday but appears on the supplied exclusion list, so it does not increment the count. Tuesday the 27th is eligible and becomes day one; Wednesday the 28th becomes day two; Thursday the 29th becomes day three.

Stop when the counter reaches three. The result under this contract is 2026-10-29. Do not continue to another date simply because a workweek has five weekdays. The requested offset is three eligible dates, not one complete workweek or a fixed number of elapsed hours.

Now calculate the simpler calendar-date offset separately: three successive dates after the start are October 24, 25 and 26. That gives October 26, not October 29. It answers a different question. A fluent explanation calling October 26 a working-day result would conflict with both weekend skips and the explicit closure.

Keep every skipped date and its reason in the ledger. The final date alone cannot show whether the assistant respected the closure or merely arrived at the right answer through an unstated rule.

Recheck the result from the calendar conditions

Cover the final answer and make a second list of candidate dates after October 23. Mark October 24 and 25 as weekends. Mark October 26 as the listed fictional exclusion. The first three remaining dates are October 27, 28 and 29. That independent pass reproduces the third eligible date without copying the final row.

Record a control sentence: “Six calendar dates considered after the start; two weekend dates and one listed weekday excluded; three dates counted; third eligible date October 29.” The starting Friday is outside both the six candidate dates and the eligible-date count. This makes the treatment of the starting boundary visible.

If a proposed answer is October 28, inspect whether it ignored the listed Monday exclusion or counted the start. Those are possible rule differences to investigate, not claims about an assistant’s hidden reasoning. Ask for the per-date ledger and compare it with the stated contract. Correct the input rule or the output explicitly rather than silently changing one to fit the other.

Matching this exercise does not validate a real service deadline. Real acceptance times, holidays and calendar ownership remain outside the card. Keep the result qualified by its fictional inputs whenever you copy it into another note.

For the different task of checking whether predecessor work is complete, use the plan dependency audit. That graph check deliberately does not calculate a full project calendar. A dependency decision and a date offset are not interchangeable outputs.

Test three claims against the supplied calendar

Claim one says: “Three working days after October 23 is October 26.” Reject it for this card. October 24 and 25 are weekends, and October 26 is explicitly excluded. The third counted date is October 29. Preserve October 26 only as the result of the separate calendar-day calculation, with the correct label.

Claim two says: “We can count the starting Friday or ignore the Monday closure and still follow the same contract.” Reject that too. Either change alters a source condition. Another task might use a different calendar or starting convention, but that would need to be stated and checked as a different version, not smuggled into this one.

Claim three says: “October 29 is guaranteed for a real customer request.” Mark it unsupported. The inputs are fictional and contain no actual service promise, legal rule or company calendar. Write the unresolved question: “For the real task, which calendar, excluded dates and starting boundary have the responsible person confirmed?” Do not supply invented answers.

Microsoft’s WORKDAY documentation describes advancing by working days while excluding weekends and supplied holiday dates. Google’s WORKDAY documentation distinguishes finding an end date from counting working days between two dates, and specifies Saturday/Sunday as its weekend pattern. These sources support the concepts used here, not a claim that a formula was executed or a real calendar was verified.

The supplier quote comparison warns that business and calendar days are not interchangeable. Our output is not a vendor choice: it is an auditable date-counting ledger under fixed conditions. For another boundary-focused calculation, the response-time summary audit checks supplied durations rather than converting a duration into a deadline.

What should you save before closing the exercise?

On Windows, open Start, type Notepad and launch the application. Create a document headed “Working-date audit V1: fictional calendar.” Add the five-field source card, all seven ledger rows including the excluded start, the independent control sentence and the result 2026-10-29. Include all three claim decisions with their date evidence, then the unresolved real-calendar question.

Press Ctrl+S, choose Documents and save as working-date-audit-V1.txt. Close the editor and reopen the file from that folder. Check that October 23 is not counted, October 26 remains a listed fictional exclusion, and October 27/28/29 are counted one/two/three. Confirm that the result is not described as an actual public holiday calculation or guaranteed deadline.

For an optional AI comparison, supply only this fictional card to an assistant you already use. Copy this instruction: “Start 2026-10-23 is excluded. Advance three eligible dates. Skip Saturday and Sunday and the explicitly excluded fictional date 2026-10-26. Show every candidate date, weekday, skip/count reason and cumulative count. Stop at three. Do not invent real holidays, hours, service rules or delivery guarantees. Assess the three claims using the source card.”

Compare the returned ledger with the manual answer key. If access is unavailable, write “optional AI comparison not performed.” The account-free manual record can still be complete. No calendar event is created, no appointment is moved and no customer receives a message.

A suggested fifteen-minute allowance is three minutes for the source contract, four for the date ledger, four for the second pass and claims, and four for saving and reopening. This is a planning allowance rather than a measured completion result. In my earlier writing about perfection and effectiveness, I described project delays from pursuing every detail. Applied here, that working principle means finishing one reconstructable calculation before automating a schedule; it is not a personal delivery experiment or client outcome.

Finish with a limited acceptance note: “Under this fictional calendar, the third eligible date is October 29. A real task requires its own confirmed calendar and starting rule.” Another reader can now reproduce both the result and its limits without relying on an unexplained AI answer.