A deadline dashboard can look precise while mixing dates that mean different things: calendar days, business days, local time, notice dates, renewal dates and effective dates. Sorting the strings does not solve the ambiguity.
function normalizeDeadline(item) { const required = ["label", "date", "timezone", "basis", "source"]; const missing = required.filter((key) => !item[key]); if (missing.length) { return { status: "review", missing }; } const parsed = Date.parse(item.date); if (!Number.isFinite(parsed)) { return { status: "review", missing: ["valid date"] }; } if (!["calendar", "business", "fixed"].includes(item.basis)) { return { status: "review", missing: ["recognized basis"] }; } return { status: "ready", epochMs: parsed, label: item.label, timezone: item.timezone, basis: item.basis, source: item.source }; } The useful behavior is the review queue. A missing timezone or undefined day-count basis is not a zero-value field; it is an unresolved interpretation that should stay visible.
For operational use, retain the source clause or document reference beside every normalized record. Record who confirmed the interpretation and when it became effective. If a deadline depends on an event such as acceptance, delivery or notice, keep that triggering event separate from the calculated date.
This synthetic example demonstrates input validation only. It does not interpret a real agreement and is not legal advice.
Disclosure: AI assistance was used during drafting and the code was reviewed for the stated demonstration scope.


