Workday Movement-Break Itinerary

Arrange workday movement breaks around entered windows and busy periods.

On-device No sign-up Free to use

Build break itinerary controls

?

One tab-separated row per work window, exactly two columns, in 24-hour HH:MM. Add +1d to an endpoint that falls on the following day, for example 22:00 to 06:00, or 01:00+1d for 1am the next morning. An earlier ordinary end time is read as running past midnight once. Equal start and end clocks are refused unless the end explicitly carries +1d for a full day. Up to 6 windows, each 24 hours or less, and windows must not overlap.

?

One tab-separated row per busy period, exactly three columns. The start and end use the same HH:MM form and may carry +1d, so 01:00+1d to 02:00+1d is a busy hour on the morning after the window starts. The label is up to 60 characters. Busy periods stay on the itinerary, and a break that would fall inside one is reported as a clash instead of being placed there. Leave the box empty for a clear day.

?

How long each break lasts. This is your own choice; the tool does not set a target.

?

How often you want a break, counted from the start of each work window. The tool places the slots you asked for and reports any that cannot be used.

?

Your own label for the break, up to 40 characters, such as Walk around the block. It is printed on the itinerary as your choice, not as a recommendation. Leave it empty and the itinerary prints Break.

Drop your file here

or choose one from your device

Open a JSON project saved by this page. The file names the tool and schema it was written for; values in the file replace the matching fields above and are checked the same way as typed input.

    Processed in your browser. Your inputs stay on this device.

    Showing an example. Change the fields, then use build break itinerary to update it.

    Result

    Showing an example.

    With the two sample work windows, the cadence proposes six slots. The 10:00 and 15:30 starts clash with entered busy periods; the other four become five-minute breaks. No proposed slot is too short to finish.

    Placed 4 breaks, with 2 clashes and 0 unplaced periods.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/workday-movement-break-itinerary · 20 November 2026

    Was this helpful?

    How to use Workday Movement-Break Itinerary

    1. Replace the sample Work windows with the periods you want covered. Enter 24-hour start/end times; separate windows must not overlap.
    2. Add Busy periods with a short label, or remove the sample rows for a clear day. For next-day busy times, choose +1d explicitly, such as 01:00+1d to 02:00+1d.
    3. Set Break length and Minutes between break starts. The first candidate is one cadence after each window starts: a 09:00 window with 60-minute cadence first proposes 10:00. Cadence must be at least the break length.
    4. Optionally name the activity, then select Build break itinerary. A busy-time candidate becomes a Clash and is not shifted to another slot; the next candidate stays on the same cadence.
    5. Review Unplaced rows for a candidate that starts before the window ends but cannot fit the whole break. Adjust your windows, busy periods or cadence if you want a different plan.
    6. Download workday-movement-break-itinerary.pdf or its CSV for the static itinerary. Save the JSON project to restore the editable settings. This page does not run reminders or a live timer.

    Example: Workday Movement-Break Itinerary

    With the two sample work windows, the cadence proposes six slots. The 10:00 and 15:30 starts clash with entered busy periods; the other four become five-minute breaks. No proposed slot is too short to finish.

    You add
    Work windows: start, end (tabs): 09:00 12:30 13:30 17:30; Busy periods: start, end, label (tabs): 10:00 10:30 Example meeting 15:00 16:00 Example focus block; Break length in minutes: 5; Minutes between break starts: 60
    You get
    Placed 4 breaks, with 2 clashes and 0 unplaced periods.

    Options

    Editable fields
    Work windows: Window start, Start day, Window end, End day. Busy periods: Busy start, Start day, Busy end, End day, Label. Add or remove these records with the labeled controls; each new row starts blank.
    Advanced raw input
    Work windows use two tab-separated cells, start and end. Busy rows use three, start, end and required label. A clock may include +1d through +7d. Ordinary clocks are on day 0; an earlier end rolls past midnight once, but equal clocks need an explicit next-day marker.
    Cadence and duration
    Cadence is the gap between proposed starts. It must be at least the chosen duration so breaks do not overlap.
    Overnight entries
    Ordinary clock times start on day 0. Use an explicit +1d suffix for a following-morning busy period, such as 01:00+1d.
    Your activity
    An optional short activity label appears on the itinerary without generating an exercise recommendation.

    Supported inputs and limits

    • Use 1 to 6 nonoverlapping work windows and up to 100 busy periods, with at most 100,000 characters per list.
    • Each range must be positive and no longer than 24 hours.
    • Busy labels allow 60 characters and the optional break activity 40.
    • Clock suffixes identify relative days from +0d to +7d; they are not dates or time zones.
    • Break length is 1 to 120 whole minutes; cadence is 5 to 480 whole minutes and cannot be shorter than the break.
    More details

    Candidate starts advance from each window start by the cadence.

    A clash is reported, not retried, and a short remaining candidate is unplaced; time before the first candidate is not treated as a missed break.

    This is clock arithmetic without a daylight-saving model, calendar integration or movement prescription.

    Processing is local without automatic saving.

    JSON projects are limited to 100,000 bytes and characters;

    PDF text uses the supported standard-font character set.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    Conflicts are reported rather than silently moved

    The requested cadence produces candidate slots inside each work window. A slot overlapping a busy period is reported as a clash, and a slot that cannot fit is not presented as a usable break. The page organises your chosen timing and activity without prescribing an exercise interval or claiming a health benefit.

    Questions about Workday Movement-Break Itinerary

    Does it choose how often I should take a break?

    No. You enter the cadence and duration. The tool uses those values to construct the itinerary.

    Will it move a conflicting break automatically?

    The result identifies clashes instead of presenting a busy-time slot as free. Review the report and change the plan when needed.

    Can a work window run past midnight?

    Yes. An earlier ordinary end time rolls into the following day once, such as 22:00 to 06:00. For equal start/end clocks, add +1d to the end for a full 24-hour range. Mark next-day busy periods explicitly and review printed day offsets.

    Page updated · Project managed by Tony Hines · Report a problem with Workday Movement-Break Itinerary