Milestone Schedule Register

Normalize milestone deadlines to UTC and retain the source timezone used for each conversion.

Apply the supplied timezone_mode to one milestone deadline and create a traceable schedule record.

1. Read the source value

Keep the deadline text exactly as received. Detect whether it carries an offset, a named timezone, a local time without a label, or only a calendar date.

2. Select the interpretation

Honor explicit labels first. Otherwise apply the default in the active timezone guidance. Use the offset that applies on the milestone date. A date-only value remains date-only unless a cutoff was provided.

3. Record the conversion

Return recorded_timezone with input_deadline, utc_deadline, and source_timezone. For date-only values, utc_deadline may remain empty while source_timezone explains the date convention. Reject impossible local times instead of silently shifting them.

Example

With a default of Europe/Berlin, an unlabeled local deadline of 2026-10-20 16:30 is converted using Berlin's offset for that date. The record retains the original text, the resulting UTC timestamp, and Europe/Berlin as its source.

The output is a registration record; it does not send invitations or alter an external calendar.

Interface reference

Input field: timezone_mode. Timezone mode selected from the active scheduling guidance.

Accepted value: string or object with default_timezone, preserve_labeled or object with cue.

Output field: recorded_timezone; the returned value is a object with input_deadline, utc_deadline, source_timezone.

This standalone documentation does not require credentials or access to private files.