A chain of solutions · 5 steps · part of the big case
A new project launches in 15 minutes — with tasks, owners and a personal plan for everyone
The manager presses a button and enters the start date, then says who owns what in this project with one record per role. Everything else happens on its own: hundreds of tasks appear with deadlines, find their owners, people get access, and every morning they see their tasks in a personal dashboard and in Telegram.
The problem
When projects are many and alike — launches, openings, client projects — each new one starts the same way: copy the old task list, recalculate deadlines, hand out tasks, open access. A 700-task project costs a week of manual work.
People in roles change from project to project. Reassigning a hundred tasks one by one is an hour of clicks and guaranteed mistakes. Newcomers get access by hand, and people who left keep it.
So the manager spends time not on the project but on making sure everyone knows what to do. The chain removes that work step by step: the template gives tasks, the role gives an owner, the owner gets access and a personal plan. Tasks are not gathered into a project — the project unfolds into tasks.
Every link works on its own. The difference between a set of automations and a system is knowing where the next link will attach.
How the chain works
🚀 Product launch
Start date: March 1
Status: Preparing
Sub-projects
- 1
Template
A 700-task project with sub-projects — in 15 minutes instead of 40 hours
A button creates the project with sub-projects and every task — deadlines are counted from the start date.
40 h → 15 min to launch one project
↓ Opens up next: Every task already has an owner role — all that is left is to say who plays which role in this project.
- 2
Assignments
Assign a person to a role — and all 100–200 of their tasks in the project are assigned
One “role → person” record assigns them to every task of that role in the project — 100–200 tasks at once.
1 record instead of picking the owner in 100–200 tasks
↓ Opens up next: The system knows who owns what — the same database can grant access.
- 3
Access
Assign a role — the person sees what they need; the project ends — access is removed on its own
A person sees the pages they need at once, and access is removed when the project ends.
15–30 min → instant to give a newcomer access
↓ Opens up next: Everyone has their own tasks and access — they can be gathered into one view.
- 4
Dashboard
One view per person: only my tasks and my meetings across all projects
A “Mine” page: only my tasks and my meetings across all projects, in one view.
≈10 h a month of the manager collecting statuses
↓ Opens up next: The personal plan is ready — it can be sent where the person already is every day.
- 5
The outcome
- A new 700-task project launches in 15 minutes, not a week.
- Who owns what in every project is visible in one database, and replacing someone in a role takes one record.
- Access is granted and removed on its own — former participants do not see working data.
- Everyone knows today’s tasks in the morning, and the manager spends time on the project, not on reminders.
Who it fits
Any company with a remote team and more than one project. For example:
Agencies and studios
client projects from one template, with a team assembled anew for each
Product teams
releases and launches with the same steps and different owners
Chains and franchises
opening a location means hundreds of identical tasks with new people in the roles
Event organisers
several projects at once, the same roles, different people
Online schools
every cohort launch repeats the previous one, tutors change
Production
shoots, seasons, episodes — a repeatable process with contractors
Consulting and implementation
onboarding each client follows the same work plan
HR and onboarding
a new hire means a checklist of tasks across departments
Common questions
Is all of this n8n?
No. The template, buttons, deadlines, role assignments and the dashboard are built-in Notion features. n8n is used where Notion cannot manage alone: granting and removing access and the morning Telegram digest.
Can I take only part of it?
Yes. The template with a button works on its own. Role assignments make sense once template tasks have roles. Access, the dashboard and the digest rely on assignments.
How does this connect to meetings?
The dashboard shows a person’s meetings next to their tasks — the Meetings chain collects them. And decisions from meetings are checked against these same tasks.