What are Recurring Projects?
Recurring Projects
A recurring project clones itself automatically on a schedule, resetting statuses and shifting deadlines, so retainer work doesn't need rebuilding from scratch every cycle.
Recurring projects are project boards that clone themselves automatically on a schedule. Instead of rebuilding the same task structure at the start of every retainer cycle, the PM sets up the project once and the system creates a fresh copy when the next cycle begins.
For agencies running monthly retainer clients (SEO, content production, social media, development sprints), the underlying project structure is identical each cycle. Tasks, columns, and assignments repeat. Only the content and dates change.
Recurring projects eliminate the monthly setup overhead. They also enforce consistency: every cycle starts with the same structure, regardless of which PM handles it.
What Gets Cloned, What Gets Reset
When a recurring project fires, it creates a new project with these elements carried over from the template:
- Kanban columns: same structure as the original project
- Tasks: same names, descriptions, and role assignments
- Subtask structure: subtasks and their nesting carry over
- Assignee roles: role mappings (not specific person assignments) carry over
What Resets in Each New Cycle
Each clone starts clean:
- Task statuses: all tasks reset to their default state (typically 'To Do')
- Time logged: no hours carry over from the previous cycle
- Comments: the new project starts with no comments or discussion history
- Completion flags: all checkboxes and done-states reset
How Deadlines Shift
Tasks in the original project have deadlines relative to the project start date. When a recurring project clones, those relative deadlines recalculate from the new cycle's start date.
Example: a task with 'due in 5 days from project start' that was June 5 in the original project becomes August 5 in the August clone (if the cycle starts August 1). The PM doesn't manually update dates: the system shifts everything forward by the cycle length.
When Recurring Projects Make Sense
Recurring projects work well for repeating work with a consistent structure and predictable cadence. Common use cases:
**Monthly retainers**: SEO reporting, content production, social media management, development maintenance. Same tasks every month, new deliverables.
**Quarterly reviews**: performance reporting, OKR reviews, financial reporting. Same structure, updated numbers.
**Weekly sprints**: development teams running weekly cycles. Same column structure, new backlog each week.
Recurring projects are less useful when each project cycle is substantively different: different scope, different team, different client requirements. In those cases, Smart Templates are more appropriate: a starting structure you customize per project rather than a fixed repeat.
Recurring Projects in Melororium
Recurring Projects is a Starter+ module. Enable it on any project by setting the cycle frequency and the next run date. The system checks daily for due projects and clones automatically. The team receives a notification when the new cycle opens.
Starter plan at $29/mo covers 4 users. Agency at $59/mo covers 15 users. Both include Recurring Projects.
In Melororium
Recurring Projects in Melororium Starter
Common mistakes with recurring projects
What teams get wrong most often, and what to do instead.
- 1
Not adjusting the template as work evolves
Cloning the exact same task list every month even after the real scope of work has changed.
- 2
No review before each new cycle starts
Letting the clone generate and run with zero check; errors repeat automatically.
- 3
Deadlines that don't shift correctly
Assuming dates will work out relative to the new cycle without checking.
- 4
Using it for work that isn't identical each time
Forcing genuinely variable work into a recurring template built for repetition.
Frequently asked questions
How is a recurring project different from a project template?
A project template is a starting structure you manually use to create a new project whenever you want. A recurring project fires automatically on a schedule without any manual action. Templates give you a head start; recurring projects eliminate the step entirely.
Can I have different cycle frequencies for different clients?
Yes. Each project has its own cycle settings. One client's retainer can be monthly, another's can be weekly, and a third can be quarterly, all running independently on their own schedules.
What happens if I need to make changes to the template for the next cycle?
Edit the recurring project before the next clone date. Changes to task names, structure, or columns apply to the next clone. They don't retroactively change the current cycle.
