GratisAI career · count the working days inside a notice period · local-first FREE TIER 1 Free Run Available
working-day ladder · climbing rung ladder

Count the Working Days Inside a Notice Period

Calendar weeks are not working weeks. Before you promise handover dates or book a start date, count the days your notice period actually holds — weekends out, your holidays out, end date exclusive.

1 · Period code | start YYYY-MM-DD | end YYYY-MM-DD | holiday dates or none

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: The working-day ladder processes Period code | start YYYY-MM-DD | end YYYY-MM-DD | holiday dates or none locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Perspective: Before: a notice period was a block of calendar weeks. After: it is a counted ladder of working days with weekends and holidays visibly removed.

2 · Read the working-day ladder

Date arithmetic only, not legal or contractual advice. Confirm notice start, last working day and applicable holidays with your contract, HR or a qualified adviser before acting on the count.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the working-day ladder

Dates use ISO YYYY-MM-DD and are treated as one local calendar — the tool does not convert time zones. Each period includes its start date and excludes its end date; if you mean to include the final day, enter the following day as the end. The weekly model is yours to choose: five means Saturday and Sunday are non-working, six means only Sunday is. Holiday dates must be entered explicitly, one row's holidays apply only to that row, and a holiday outside the row's span is reported in the row note rather than silently applied. Shift patterns, on-call days and part-time weeks are outside the model; if your working week is neither five nor six consecutive-ish days, this count is only a starting approximation.

Boundary and sources

Date arithmetic only, not legal or contractual advice. Confirm notice start, last working day and applicable holidays with your contract, HR or a qualified adviser before acting on the count.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this working-day ladder for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a working-day ladder. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Period code | start YYYY-MM-DD | end YYYY-MM-DD | holiday dates or none; the setting is Weekly working-day model: 5 (Sat+Sun off) or 6 (Sun off). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.