Solution · team operations
A schedule in one click and cascading shifts: 5 minutes instead of 2–3 hours
Moving one event means hours of manual recalculation, and every launch’s schedule is rebuilt from scratch. This solution deploys a schedule from a reference template in one click, shifts later events by itself when something changes, and creates next year’s project around public holidays.
What it looks like
Mock-ups with demo data, no real data
📅Schedule: day 1
| Event | Start | End | Host |
|---|---|---|---|
| Welcome | 10:00 | 10:45 → 11:00 | EEthan |
| Block 1 | 11:00 → 11:15 | 12:30 → 12:45 | MMaria |
| Lunch | 12:30 → 12:45 | 13:30 → 13:45 | — |
| Block 2 | 13:30 → 13:45 | 15:00 → 15:15 | AAnna |
At a glance
- In production
- At a client under NDA
- Fits
- Courses, intensives, events — anything with a repeating schedule
- Needs
- A reference schedule and an events database in Notion
Result at the client
2–3 h → 5 min
to rebuild the schedule after a change
Rebuilding the schedule after a change
Estimate for your company
≈12 h
a month of schedule rework
Assumption: 5 schedule changes a month × ~2.5 hours of manual work
This is a calculation, not a promise: plug in your own volumes and the figure changes.
Before
- Each launch’s schedule is rebuilt from scratch even though it nearly repeats the last one.
- One event moves and the coordinator recalculates the whole day by hand.
- Next year’s project is created from zero, with dates picked by hand around holidays.
What was built
A schedule in one click
The button takes the reference template of the right length and deploys the events with owners assigned by role.
Cascading shifts
When an event’s end time changes, the following ones move by themselves. Times can be typed short: “1201” → 12:01.
Next year’s project
A finished project is duplicated for next year, dates move to working days around holidays, and a Telegram message asks someone to check.
Stack
- Notion
- n8n
- Public holiday calendar (API)
- Telegram
Where it runs
Questions
What if a launch has a different length?
There can be several reference templates, and the button picks the right one by project length.
Can the cascade mess up the schedule?
It reacts only to manual changes: rows the button deployed are skipped, so there is no chain reaction.