Sidebus starter guide
Study System Sprint Pack
Study planning pack and printable review guide
This file is designed to feel finished when it leaves the site: clear enough to use immediately, clean enough to print, and structured enough to hand to someone else without extra cleanup.
Printable guide
7 guide blocks
Built by Sidebus
Build the first useful version
Get each block standing cleanly, then improve it from real usage instead of adding complexity before the workflow earns it.
01
Weekly study map
Set up Weekly study map so the next action is obvious, the owner can see what happened quickly, and nothing important lives only in someone's memory.
Build
- Define the trigger that starts Weekly study map and the condition that counts as complete.
- Choose the single place where Weekly study map is recorded, checked, and handed off.
- Write the default message, rule, or operating step that should happen every time.
- Name the owner and the review rhythm before adding any extra automation.
Review
- Weekly study map can be reviewed in under two minutes without opening five different tools.
- There is one obvious next step for every new weekly study map item.
- An operator can tell whether weekly study map is healthy without guessing.
02
Recall session plan
Set up Recall session plan so the next action is obvious, the owner can see what happened quickly, and nothing important lives only in someone's memory.
Build
- Define the trigger that starts Recall session plan and the condition that counts as complete.
- Choose the single place where Recall session plan is recorded, checked, and handed off.
- Write the default message, rule, or operating step that should happen every time.
- Name the owner and the review rhythm before adding any extra automation.
Review
- Recall session plan can be reviewed in under two minutes without opening five different tools.
- There is one obvious next step for every new recall session plan item.
- An operator can tell whether recall session plan is healthy without guessing.
03
Course notes structure
Set up Course notes structure so the next action is obvious, the owner can see what happened quickly, and nothing important lives only in someone's memory.
Build
- Define the trigger that starts Course notes structure and the condition that counts as complete.
- Choose the single place where Course notes structure is recorded, checked, and handed off.
- Write the default message, rule, or operating step that should happen every time.
- Name the owner and the review rhythm before adding any extra automation.
Review
- Course notes structure can be reviewed in under two minutes without opening five different tools.
- There is one obvious next step for every new course notes structure item.
- An operator can tell whether course notes structure is healthy without guessing.
04
Exam countdown board
Set up Exam countdown board so the next action is obvious, the owner can see what happened quickly, and nothing important lives only in someone's memory.
Build
- Define the trigger that starts Exam countdown board and the condition that counts as complete.
- Choose the single place where Exam countdown board is recorded, checked, and handed off.
- Write the default message, rule, or operating step that should happen every time.
- Name the owner and the review rhythm before adding any extra automation.
Review
- Exam countdown board can be reviewed in under two minutes without opening five different tools.
- There is one obvious next step for every new exam countdown board item.
- An operator can tell whether exam countdown board is healthy without guessing.
05
Revision review loop
Set up Revision review loop so the next action is obvious, the owner can see what happened quickly, and nothing important lives only in someone's memory.
Build
- Define the trigger that starts Revision review loop and the condition that counts as complete.
- Choose the single place where Revision review loop is recorded, checked, and handed off.
- Write the default message, rule, or operating step that should happen every time.
- Name the owner and the review rhythm before adding any extra automation.
Review
- Revision review loop can be reviewed in under two minutes without opening five different tools.
- There is one obvious next step for every new revision review loop item.
- An operator can tell whether revision review loop is healthy without guessing.
06
Distraction controls
Set up Distraction controls so the next action is obvious, the owner can see what happened quickly, and nothing important lives only in someone's memory.
Build
- Define the trigger that starts Distraction controls and the condition that counts as complete.
- Choose the single place where Distraction controls is recorded, checked, and handed off.
- Write the default message, rule, or operating step that should happen every time.
- Name the owner and the review rhythm before adding any extra automation.
Review
- Distraction controls can be reviewed in under two minutes without opening five different tools.
- There is one obvious next step for every new distraction controls item.
- An operator can tell whether distraction controls is healthy without guessing.
07
Progress dashboard
Set up Progress dashboard so the next action is obvious, the owner can see what happened quickly, and nothing important lives only in someone's memory.
Build
- Define the trigger that starts Progress dashboard and the condition that counts as complete.
- Choose the single place where Progress dashboard is recorded, checked, and handed off.
- Write the default message, rule, or operating step that should happen every time.
- Name the owner and the review rhythm before adding any extra automation.
Review
- Progress dashboard can be reviewed in under two minutes without opening five different tools.
- There is one obvious next step for every new progress dashboard item.
- An operator can tell whether progress dashboard is healthy without guessing.