Recurring routines & the calendar
The repeating parts of your week — client check-ins, content days, the school run, a Friday deploy review — shouldn't be re-typed every Monday. Define a routine once and KnightLeap schedules it into every week for you.
Turn a story into a routine
Any story can become a recurring template. On the story, set its recurrence:
| Recurrence | Schedules |
|---|---|
Each sprint | One instance per sprint, on the sprint's start day |
Weekly days | One instance on each weekday you pick (e.g. Mon / Wed / Fri) |
Give it a start time (so it lands at 6:30am or 2:00pm), a checklist, an estimate, and its assignee and reviewer. Templates live in their own Recurring Stories table on the Backlog — separate from one-off work, and deliberately not draggable into sprints, because the app stamps out their instances for you.
Instances appear automatically
As each week's sprint is planned, the routine's instances are created in that sprint — on the right days, at the right times, with the checklist and people copied over. You execute the instances; the template stays the source of truth.
See your week on the calendar
The Calendar lays out your week as days × hours and places the stories assigned to you that have a start time, sized by their estimate. The 6:30 school run and the 10:00 client call sit where they actually fall, completed ones checked off, with a line marking now.
Times are shown in your profile time zone, so make sure yours is set correctly — a 6:30 routine should read 6:30 to you and to everyone on your team.
And on Today
Your Today page shows the routine instances that are actually actionable today — future-dated ones wait their turn, and once you've done everything possible it says so rather than nagging you for tomorrow's work.