Is the source a real timestamp or a local label?
Resolve whether the input means an exact instant, such as a Unix timestamp, or a local expression such as 'next Friday at 5 pm'.
Elysia Tools
Navigation
Workflow Playbook
Turn ambiguous or mixed-format date inputs into validated, timezone-aware, business-ready timestamps, deadlines, and duration facts.
Hubs
Date work usually fails before any calculation begins. A message such as 03/04/2026 09:00, next Monday, or 1725152400 may look precise while still hiding locale, timezone, or format ambiguity. Parse each source value first and decide whether it represents an exact instant, a local wall-clock time, or a deadline label.
Do not mix formatted strings, timestamps, and converted display values in the same decision. Convert everything into one canonical form, usually ISO 8601 plus the authoritative timezone. Once the representation is stable, it becomes much easier to compare two dates, compute elapsed time, or hand the result to another system.
Adding 48 hours is not the same as adding two working days. First calculate the raw offset, then apply weekday and holiday policies only when the business rule explicitly requires them. This keeps deadline handling auditable and prevents hidden calendar assumptions from leaking into ordinary date normalization.
Workflow playbook
Extract dates from raw text, reject malformed values, and confirm that the source range is internally consistent before doing any math.
Unify mixed formats and convert them into one stable representation so later comparisons and exports refer to the same instant or local time.
Convert the normalized time into the authoritative timezone and identify the weekday, week number, or elapsed duration that affects downstream decisions.
Add or subtract time, then adjust only if the policy requires working-day or holiday-aware deadline handling.
Resolve whether the input means an exact instant, such as a Unix timestamp, or a local expression such as 'next Friday at 5 pm'.
Pick one source of truth before conversion so the normalized output does not mix sender, viewer, and system timezones.
Use business-day and holiday rules only when the deadline policy explicitly excludes weekends or public holidays.