Schedule definition
Frequency, next due date, work type, default owner, reminder lead, criteria, and active state.
Pause, skip, reassign, or revise the schedule with a reason.Recurring task management
Make repeated work reliable without recreating it by hand
Separate the recurring schedule from each work instance so owners, dates, reminders, blockers, evidence, and verification remain accurate over time.
A recurring task is not just a repeated reminder. It needs a schedule, generated work record, accountable owner, exception path, completion evidence, and control history.
- One schedule can create many accountable work instances
- Exceptions remain visible without changing the master cadence
- Verification and evidence support operational control
Keep the rule separate from each occurrence
Editing one overdue task should not silently change future work.
Generated task
A dated work instance with owner, status, priority, blocker, next action, and source schedule.
Handle delay or reassignment on this occurrence without corrupting future dates.Completion and verification
Evidence, completed date, reviewer, accepted or returned outcome, and comments.
Return incomplete work and retain the failed verification history.Control review
Missed frequency, overdue instances, repeated returns, and recurring blockers by schedule.
Change the cadence, owner, criteria, training, or underlying process.Focus managers on the repeated work that broke its expected pattern
A clean exception queue is more useful than a long calendar of healthy occurrences.
Not generated
Enters when
A due schedule has no corresponding task instance.
Respond by
Repair the generation rule or create the missing work.
Due soon
Enters when
A recurring task approaches due without progress or evidence.
Respond by
Remind, reassign, or surface the expected blocker.
Overdue recurrence
Enters when
The work instance missed its commitment.
Respond by
Recover the task and protect the next cycle.
Repeated failure
Enters when
The same schedule repeatedly runs late, blocks, or returns.
Respond by
Improve the process rather than escalating every occurrence separately.
Change the schedule rule without rewriting historical tasks
The team should be able to improve future occurrences while preserving what already happened.
Adding a cadence, reminder lead, evidence rule, exception queue, and review measure can take 2–10 business days in a fixed-product or development queue.
A trained administrator can often configure and test that focused recurring-work change in 30 minutes–3 hours.
- Move a monthly check to the last business day
- Add a two-day pre-due reminder
- Require a photo for one task type
- Escalate two consecutive returns
Design repeated work that remains auditable
Why separate a recurring schedule from the task?
The schedule defines the repeating rule; each task records what actually happened on a particular date. Separating them preserves history and prevents one exception from changing every future occurrence.
How should missed recurring tasks be handled?
Keep the missed instance open or close it with an explicit outcome, record the cause, protect the next occurrence, and review repeated misses at the schedule level.
Can recurring work require evidence?
Yes. Configure the evidence and verification appropriate to the task, such as a file, photo, checklist, measured result, reviewer decision, or completion note.
What recurring tasks fit Jodoo?
Operational checks, reviews, renewals, reconciliations, maintenance coordination, follow-ups, audits, reporting, and other repeated work whose fields, routing, evidence, and dashboards need configuration.
Pilot one schedule through two real occurrences
Generate the task, change one occurrence, complete and verify it, then confirm the next occurrence and schedule history remain correct.