Is the interval calendar based or a fixed elapsed time?
Keep year and month components as calendar units and evaluate them at a stated anchor. Use approximate seconds only for a rough sense check, never to settle a month-end deadline.
Elysia Tools
Navigation
Workflow playbook
Turn a dated reporting anchor and a stated duration into an auditable calendar endpoint, ISO week label and fiscal-quarter assignment.
New to this workflow? Follow the steps in order, starting with the first tool below. Already know what you need? Jump straight to the matching step — every tool in this workflow is listed in the comparison table.
First tool: ISO 8601 Converter
Hubs
| Tool | What it does | Category |
|---|---|---|
| ISO 8601 Converter | Convert dates to and from ISO 8601 format | Date & Time |
| ISO 8601 Duration Builder | Convert between natural-language durations and ISO 8601 durations (PnYnMnDTnHnMnS) in both directions with validation of edge cases | Development |
| ISO 8601 Duration Parser & Arithmetic Workbench | Parse ISO 8601 durations, validate ISO 8601-2 extensions, run calendar-true arithmetic, sort by real length at an anchor, and diff datetimes. | Date & Time |
| ISO Week Number and Fiscal Quarter Anchor Finder | Convert any date to ISO 8601 week number, day-of-year, Julian Day, and fiscal-quarter boundaries (4-4-5, 4-5-4, 13-week, or standard). |
Hubs
| Utilities |
A reporting analyst needs more than a date string to define a defensible period. Record the source value, the authoritative timezone if it denotes an instant, and whether the reporting convention treats the end as included or excluded. Use iso-8601-converter to normalize the starting date or datetime, but keep the original input beside it. If the policy speaks only in dates, do not silently convert those dates into UTC instants. If several teams disagree about the timezone, settle that policy before calculating anything; this workflow does not replace the broader normalization and deadline checks in date-time-scheduling.
Use iso-8601-duration-builder to turn an agreed phrase such as one calendar month into a duration string. Its approximate seconds are a sense check, not a contract for when that month ends. Then use iso-8601-duration-parser-arithmetic-workbench with the same anchor to calculate the endpoint. A month added at the end of January can clamp to the end of February; multiplying by thirty days would answer a different question. If the duration contains mixed weeks or a leading sign, check whether the downstream consumer accepts ISO 8601-2 extensions or requires strict ISO 8601-1 notation. Keep the exact expression in the handoff so another analyst can reproduce the result.
The date converter parses the input before displaying it in the chosen zone. Supply an offset for an instant or YYYY-MM-DD for a reporting date. The duration workbench uses UTC, treats days as 24 hours, and drops fractional years and months during arithmetic; use whole calendar units and verify local daylight-saving deadlines separately.
Run iso-week-number-and-fiscal-quarter-anchor on both the start and calculated endpoint. Select the organization's standard, 4-4-5, 4-5-4 or 13-week convention and fiscal-year start month before labeling either date. At New Year, ISO week-year can differ from calendar year; note the full week label rather than just a week number. Finally write a short record containing source, ISO anchor, duration, endpoint, timezone or date-only rule, inclusive/exclusive end and fiscal convention. Recheck an adjacent period for overlap or gaps. For recurring meeting rules or ICS export, switch to calendar-recurrence-and-ics-scheduling; this page describes one reporting window, not a recurrence engine.
Supply the intended reporting date as YYYY-MM-DD. Week-based modes start on day 1 of the selected month and share 13-week quarter boundaries, not a retailer’s official weekday calendar. A late-year date can fall beyond the displayed quarter end. Compare the result against your organization’s fiscal calendar before publishing.
Workflow playbook
The date converter parses the input before displaying it in the chosen zone. Supply an offset for an instant or YYYY-MM-DD for a reporting date.
Convert a verbal period to an ISO duration and inspect its components; separate strict ISO 8601-1 notation from optional extensions.
The date converter parses the input before displaying it in the chosen zone. Supply an offset for an instant or YYYY-MM-DD for a reporting date. The duration workbench uses UTC, treats days as 24 hours, and drops fractional years and months during arithmetic; use whole calendar units and verify local daylight-saving deadlines separately.
Supply the intended reporting date as YYYY-MM-DD. Week-based modes start on day 1 of the selected month and share 13-week quarter boundaries, not a retailer’s official weekday calendar. A late-year date can fall beyond the displayed quarter end. Compare the result against your organization’s fiscal calendar before publishing.
Keep year and month components as calendar units and evaluate them at a stated anchor. Use approximate seconds only for a rough sense check, never to settle a month-end deadline.
Prefer a duration without mixed weeks or a leading sign for strict interchange; inspect any ISO 8601-2 extension before sending it to another system.
Choose standard, 4-4-5, 4-5-4 or equal 13-week quarters from the reporting policy before labeling the start and end dates.