Routine belongs in the system - not in someone's memory
Series for tasks and regular meetings, building blocks and templates for everything that comes back, processes in a diagram - and built-in clockworks the system runs itself.
The rhythm of routine
The task that keeps coming back becomes a series in one click - the system creates the cards automatically to the rule's rhythm.
Why routine fails today
Rarely at discipline - mostly because repetition is manual labour.
The same card, typed for the twelfth time
Month-end close, maintenance, review loop: every month somebody creates the same task anew - with slightly different details each time.
Open items don't survive the meeting
What was left open in the regular meeting gets hunted down in an old protocol next time - or never resurfaces.
The proven gets rebuilt instead of reused
The test phase, the approval package, the standard agenda: all built before - and reinvented every single time.
The process lives in one head
Who does what after the request is known to the person who always does it. When they're on holiday, the process stands still.
Routine in five stations - from series card to running clockwork
This is how the recurring becomes structure: define series, use the series memory, save the proven as blocks, model the processes - and let the built-in rhythms do their work.
The third repetition becomes a series
The card that keeps coming back becomes a series in one click: the existing card turns into the template, and the rule knows the rhythm - daily, weekly or monthly -, interval, weekdays, time, time zone and end date. The system creates the new cards automatically to the rule's rhythm - at night and on weekends, too. The dialog shows the upcoming dates before you save, over holiday periods you pause the series without deleting it, and an overview per board keeps all rules in sight.
Upcoming dates in the dialog:
From the existing card to a series in one click - the system creates the new cards automatically to the rule's rhythm.
The series has a memory - across all its dates
Weeklies and steering committees run as meeting series with their project context: the next date is created according to the recurrence rule, agenda templates provide the structure, and the series evaluation bundles open tasks and all decisions across every date. Whatever is left over travels into the next agenda issue as a card.
The next date is created according to the recurrence rule - open items travel into the next agenda.
Build once - insert everywhere
You save proven structures as blocks: a container including its chosen sub-tree and active features, stored in an organisation-wide library with name, description and category - and inserted again at any position. On top come meeting templates for the regular meetings and document templates in seven categories, from status report to meeting minutes.
The library keeps name, description and category - the proven stays findable.
The process lives in a diagram - not in a head
You model recurring procedures as workflows in the visual editor with twelve node types. They start manually or on an event from your projects, with condition filters - on what actually happens, not on a date. Every task step carries a deadline, a reminder and an escalation, and the template gallery offers built-in system templates as well as your own, with a change history.
Twelve node types in the editor - started on what happens, not on a date.
Clockworks the system runs itself
Some rhythms are built in: daily at seven the system creates due status-report drafts and informs the project lead, daily at eight it reminds about the weekly timesheets, hourly it sweeps card due dates against their lead time - and series cards are created automatically to their rule's rhythm. On top, review cycles pace the risk resubmission and the submission weekday paces time tracking - rhythm is a system property here, not a discipline question.
Built-in rhythms - series cards are created automatically, too. Pace as a system property, not a discipline question.
And where repetition means handing over, the “Task delegation” use case helps - from sub-task to reminder.
One routine, six modules - one data foundation
In WORKSPACE.PM, recurring processes are not a special module but a property of the platform: everything that comes back has a place - and a rhythm.
Project management
Meeting management
AI & automation
One data foundation - rule, template and rhythm included
Series, block and process live with the data they concern. None of it is a second system - and none of it forgets.
And the fear of uniformity?
Repetition here means a starting point - not a corset.
Routine yes - stencil no
Series can be paused, blocks are inserted with a selectable depth and selectable features, process templates are freely adaptable after use. The standard is the beginning, not the end.
Events instead of calendar automation
Processes start on what actually happens - a status change, a card falling due, a new report. Time-triggered process starts deliberately don't exist; the built-in rhythms are run by the system itself.
The process belongs to the organisation
Blocks are organisation-wide, workflow templates carry a change history, meeting templates are managed centrally. The knowledge about procedures doesn't leave the company with one person.
Related use cases
The routine is running - this is what comes next.
Frequently asked questions about recurring processes
What teams and process owners want to know before switching.
Fastest from the existing card: “make recurring” clones it as the template, and the rule sets the rhythm - daily, weekly or monthly -, interval, weekdays, time, time zone and end date. The system creates the cards automatically to the rule's rhythm; the dialog shows the upcoming dates before saving, and pausing and resuming works any time without losing the series.
Yes - as structure blocks: a container is saved with its chosen sub-tree and active features into an organisation-wide library and inserted again at any position. A whole-project template deliberately doesn't exist - blocks cover this more precisely, phase by phase.
No, deliberately not: processes start manually or on events from your projects, with condition filters; the timer is a node inside the process. The built-in time rhythms - daily report drafts, time reminders, the hourly due-date sweep - are run by the system itself.
Through the series: the series evaluation bundles open tasks and all decisions across every date, agenda templates give each date the same structure, and open cards travel into the next issue via “put on next agenda”.
Structure blocks for the project plan, meeting templates for regular meetings, workflow templates - built-in and your own, with change history - and document templates in seven categories. Generic card or checklist templates don't exist; that role is taken by a series' template card.
Give routine a place - and a rhythm
Start for free: create the first series, save a block, model a process - and in 30 days you'll know whether it fits.