Recurring Tasks Software

Let's be direct: there's no recurrence scheduler

Search "recurring tasks software" and the feature you're picturing is a rule: this task, every week, forever, spawning a fresh card on schedule without anyone touching it. ShipSprint just doesn't have that. No "repeats every" field on a task, no cron-style configuration, no queue of future cards waiting to appear. If that specific mechanism is what you need, it's fair to know now rather than after setting up a workspace around it.

It's a common enough request that it's worth explaining plainly why we haven't added it, rather than leaving it as an unexplained gap. It's not an oversight, and it's not a backlog item waiting for engineering time. It's a considered choice, based on what we've watched happen to recurring cards on other tools once a team's been running for a year or two.

What we built instead comes from watching what actually happens to recurring work on real teams, which is usually messier than "same task, same interval." The Monday report changes shape every few months. The client check-in gets skipped during a slow week and nobody minds. The security review has a fixed cadence, but the checklist inside it evolves. A rigid scheduler handles the clean case and gets quietly ignored the moment reality diverges from it, which is most weeks, for most recurring work.

So instead of automating the creation of the task, ShipSprint makes the request for it cheap to raise and easy to find. A wiki page holds the current version of what "the Monday report" actually involves, with history showing how it's changed. And when it's time to do it again, that page, or a line on it, becomes a task in one click, current as of today rather than a template written eight months ago. That one click is really the whole point: teams get the speed of automation without the slow rot of a rule nobody remembers writing.

This is the one place in this whole set of pages where we'd underline the honesty of the gap rather than soften it: if what you need is a scheduler that spawns cards without a person involved, ShipSprint genuinely does not have that, in any form, on any plan. There's no roadmap note promising it's coming next quarter buried in this page. The wiki-plus-triage pattern below is the real, complete answer, not a workaround pending a future feature.

Why we didn't build the scheduler, on purpose

An auto-generated recurring task has a specific failure mode: it keeps appearing after it stops being needed. Someone leaves, a process changes, a report gets replaced by a dashboard, and the card still shows up every Monday, because deleting a recurrence rule requires someone to remember it exists. We've seen boards where a third of the backlog was recurring tasks nobody was doing anymore, just accumulating.

The wiki-and-triage approach can't silently outlive its usefulness the same way, because nothing appears unless someone actively creates it that cycle. The honest cost is that it's not automatic: somebody has to remember to do it. In practice, that's a much smaller cost than it sounds, because the reminder is usually the recurring meeting or calendar event the task supports, not the software itself. Teams that switch tend to notice their backlog stop growing quietly in the background, since nothing gets added that nobody actually asked for that week.

There's a second, quieter cost too: a wiki page can drift out of date the same way anything maintained by hand can, if nobody updates it after the process changes. Page history at least makes that visible: you can see the last edit date on the page you're about to turn into a task, something a silent, self-perpetuating recurrence rule would never show you.

What this looks like day to day

• The "weekly status update" wiki page gets opened every Friday, and the current instructions, not last quarter's, become that day's task.
• A request that's shown up in triage three times gets promoted to a standing wiki page instead of being re-typed a fourth time.
• A recurring task that's no longer relevant simply stops being created; there's no rule to go find and switch off.
• A monthly close checklist grows a new line after an audit finding, and everyone doing the task next month sees the update on the same page.
• Someone checks the page's edit history before relying on it, and notices it hasn't been touched in four months, a good prompt to double-check the process is still accurate.
• A person asks the workspace, in plain language, to spin up this cycle's version of a recurring task from the wiki page, instead of opening it and clicking through by hand.