How to use User-Defined Sleep Schedule Planner
- Enter Sleep opportunity start as a date and 24-hour local time, then supply the UTC offset in force at that start.
- Enter your chosen Sleep opportunity length in whole minutes. Leave End UTC offset blank if it stays the same; otherwise enter the offset at the end. The chosen elapsed length remains unchanged.
- Replace the sample Entered commitments with names and full start/end dates, times and offsets. Write the next date explicitly for an overnight commitment; the planner does not roll its end forward for you.
- Select Check my sleep window. Read the calculated sleep start/end in the result text and each commitment’s Overlap with sleep in the table. A commitment touching an endpoint without entering the sleep interval has no overlap.
- Revise the inputs yourself if a conflict matters. Download the PDF for the sleep window and commitment report, CSV for commitment rows, or JSON to restore the editable plan.
Example: User-Defined Sleep Schedule Planner
Starting at 23:00 +06:00 for 480 minutes ends at 07:00 the next day. The sample shift starts at 06:00, so it overlaps the chosen window by 60 minutes.
Options
- Editable fields
- Entered commitments: Commitment, Start date, Start time, Start UTC offset, End date, End time, End UTC offset. Add or remove these records with the labeled controls; each new row starts blank.
- Advanced raw input
- Raw commitments use five tab-separated cells: name, start date/time, start offset, end date/time and end offset. The editable controls separate each date/time into two controls but keep the same stored row.
- Elapsed opportunity
- The chosen minutes add to the actual start instant. Changing the display offset does not change that elapsed length.
- Commitments
- Actual dates and offsets govern order. An earlier local end clock during a clock change may still be a later instant; a backwards instant is refused.
Supported inputs and limits
- Choose 1 to 1,440 whole minutes.
- Commitments are optional, with up to 100 rows and 100,000 characters; names allow 80 characters.
- Each entered endpoint needs a real date, minute-resolution clock time and explicit Z or ±HH:MM offset.
- Commitment end must follow start after applying offsets.
- A changed end offset changes the displayed local sleep end, not its elapsed length.
More details
Overlaps compare actual instants; the planner neither guesses a named time zone nor looks up clock changes.
No sleep duration, sleep stage, fixed-cycle wake time or replacement schedule is recommended.
Processing is local without automatic saving.
JSON projects from this page are limited to 100,000 bytes and characters.
Saved files contain your entered details, and 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.
Opportunity length is your own assumption
The planner places the entered number of minutes from the supplied start instant. An end offset changes its displayed local end time without changing that elapsed length. Commitments need actual dates and offsets at both ends. The output does not judge sleep need, treat shift-work problems or recommend a circadian schedule.
Questions about User-Defined Sleep Schedule Planner
Does it recommend a sleep duration?
No. You choose the length and the tool reports conflicts with the commitments you enter.
How are clock changes represented?
Supply the UTC offset in force at each relevant endpoint. No time zone is guessed from your device.
Does a conflict change the plan automatically?
No. The overlap report helps you review your own schedule; it does not prescribe a replacement window.