to1: 05:00 to2: 11:00 to3: 15:30 is the example result. Read it using the units and relationship stated below.
Multi Time Zone Meeting Planner uses meeting hour (24h), meeting minute, source utc offset.
Preserving the meaning of a conversion or working record
For multi time zone meeting planner, the relationship is For each target, add (target UTC offset − source UTC offset) × 60 to source minutes. Wrap within 24 hours. Offsets are user supplied, not location or daylight-saving lookups. The amount depends on the supplied meeting hour (24h), meeting minute, rather than a live market price or a value imported from another record. A conversion is useful when the source value and unit remain traceable. Dates, elapsed time, percentages and ratios each have their own convention. Rounding can change a schedule or quantity when the output is copied into another system.
What the model includes
For each target, add (target UTC offset − source UTC offset) × 60 to source minutes. Wrap within 24 hours. Offsets are user supplied, not location or daylight-saving lookups. Use the format shown beside the input and keep both the original and converted value. A ratio is not automatically a percentage; a calendar-day difference is not automatically a working-day count. Record the convention before comparing results. Check the result against the task being performed. An arithmetic answer does not select a business policy, a service-level agreement or a calendar rule that the page has not implemented.
Example with the supplied inputs
Meeting hour (24h): 10; Meeting minute: 0; Source UTC offset: 0; Time zone 1 UTC offset: -5; Time zone 2 UTC offset: 1; Time zone 3 UTC offset: 5.5. Result: to1: 05:00
to2: 11:00
to3: 15:30. The values are illustrative.
Calculation rule
For each target, add (target UTC offset − source UTC offset) × 60 to source minutes. Wrap within 24 hours. Offsets are user supplied, not location or daylight-saving lookups.
Inputs and output
| Input | Example value | Entry convention |
|---|---|---|
| Meeting hour (24h) | 10 | Use the source quantity represented by meeting hour (24h). Keep the counted population fixed and avoid mixing a unit value with a period total. |
| Meeting minute | 0 | Use the source quantity represented by meeting minute. Keep the counted population fixed and avoid mixing a unit value with a period total. |
| Source UTC offset | 0 | Use the source quantity represented by source utc offset. Keep the counted population fixed and avoid mixing a unit value with a period total. |
| Time zone 1 UTC offset | -5 | Use the source quantity represented by time zone 1 utc offset. Keep the counted population fixed and avoid mixing a unit value with a period total. |
| Time zone 2 UTC offset | 1 | Use the source quantity represented by time zone 2 utc offset. Keep the counted population fixed and avoid mixing a unit value with a period total. |
| Time zone 3 UTC offset | 5.5 | Use the source quantity represented by time zone 3 utc offset. Keep the counted population fixed and avoid mixing a unit value with a period total. |
Output: to1: 05:00
to2: 11:00
to3: 15:30 is the example result. Read it using the units and relationship stated below. Use the formula to distinguish a cash amount, count, percentage or ratio.
How to use the page
Collect the inputs
Gather Meeting hour (24h), Meeting minute, Source UTC offset. Use one period and the units shown in the form.
Run the calculation
Enter the values and select the action. The calculation rule above explains how the inputs produce the result.
Compare a scenario
Keep the source values next to the output so the conversion or working record can be checked.
Worked example
With the example inputs listed above, the result is to1: 05:00
to2: 11:00
to3: 15:30.
Check the stated formula, units and limits before using the result in a decision.
Keep the displayed formula, input units and model scope with the result. Corrections or questions can be sent through the request section on this page.
Content updated: October 11, 2026