Use two related records: a recurring-task definition for the continuing instruction, and one occurrence for each planned date. Staff close, skip or reschedule the occurrence—not the definition.
- The definition says what should repeat and when the rule changes.
- Each occurrence holds its own planned date, actual outcome and evidence.
- A skipped occurrence remains skipped; it is not silently treated as complete or moved into the next date.
- A future rule change starts at a stated effective boundary and does not rewrite past outcomes.
1. Define the rule and the dated work as different things
A recurring-task definition is the standing instruction: for example, “check office supplies every Monday.” It can hold the task name, normal owner, recurrence pattern, expected evidence and the date from which that rule applies. It is a template for work that may happen repeatedly; it is not itself a record that this week’s check happened.
An occurrence is one dated commitment created from that definition. It needs its own stable reference, planned date, status, owner where relevant, and outcome. This distinction prevents a familiar failure: someone marks the recurring card done on Monday, then reopens the same card next week. The team can no longer tell which Monday was completed, what was checked, or whether an earlier date was missed.
Suggested practice: write a one-sentence definition your team can use. “One occurrence is one planned instance of this duty on one date.” Use that sentence when reviewing spreadsheets, task boards and proposed system screens. Do not let a changing task-card status stand in for a dated history.
Send one current workflow and BossFlow will suggest the first system worth reviewing.
Send Workflow to BossFlow2. Keep planned and actual dates distinct
The planned date answers, “When did this occurrence need attention?” The actual completion date answers, “When was it closed?” They may match, but they should not be assumed to match. Replacing the planned date with the completion date removes evidence that work was late; replacing the completion date with the planned date hides when the outcome was recorded.
Suggested practice: retain both fields even for a simple process. Also keep a clear outcome status such as open, completed, skipped or rescheduled. Avoid a single vague status such as “done later,” because it mixes a result with a scheduling decision. A supervisor reviewing Monday’s workload should still see Monday’s occurrence, even when its outcome was entered on Tuesday.
Where staff need to explain a difference, use a short occurrence note rather than editing the recurring instruction. The rule can continue to say what normally happens; the dated occurrence can explain what actually happened that time. This keeps routine planning useful without turning it into a misleading history.
3. Close each occurrence with its own evidence
Completion should belong to the occurrence. Record only evidence that helps your team verify the duty was handled: a short result note, a linked internal record, a named checker, or another agreed operational reference. Decide the minimum evidence before the work is generated, so staff do not have to guess after the fact.
Suggested practice: make the evidence requirement proportionate. A weekly visual check may need a brief note and the person who performed it. A more consequential internal check may need a second reviewer or linked record. The purpose is not to create paperwork; it is to let a later colleague understand what was closed on that date without relying on memory or chat messages.
Do not copy evidence from one date to the next. A prior note may be useful context, but it is not proof for a new occurrence. Likewise, completing today’s occurrence must not automatically mark a later occurrence complete. Each date remains independently open until its own outcome is recorded.
4. Record skips and one-off reschedules honestly
A skip is an outcome, not an empty space. If the planned work did not happen because the premises were closed, the relevant person was unavailable, or the check was unnecessary under an agreed condition, mark that occurrence as skipped and record a concise reason. This is different from completed: the team can see that the duty was considered and deliberately not performed.
A reschedule is also not a rewrite of the original plan. Keep the original occurrence with its planned date and mark its outcome as rescheduled. Create or identify the replacement occurrence with a planned date and a rescheduled-from reference. This preserves the relationship between the intended date and the replacement date.
Suggested practice: agree who may skip or reschedule and what minimum reason is required. Do not silently drag an overdue task to a later date, because the later date then appears to have been the original plan. If a task is simply still open, leave its planned date intact and record its actual closure when it occurs.
5. Change future rules at an effective boundary
Recurring work changes: a weekly check may move from Monday to Friday, change owner, or require different evidence. These are changes to the definition for future work, not corrections to completed history. State an effective-from date or boundary, then use the earlier rule for occurrences before that boundary and the new rule after it.
Suggested practice: record what changed, who agreed it, and when the new rule starts. Review any already planned future occurrences around the boundary so the team does not create duplicates or leave a gap. Do not alter old occurrences merely to make them look as though they followed the newer rule; their records should describe what was planned and concluded at the time.
If an earlier occurrence contains an error, correct it through a visible correction process rather than silently overwriting the original meaning. The related guide on correction history can help your team decide what to preserve when a record needs amendment.
6. Fictional example: a weekly office-supply check
Fictional example: A fictional office uses one definition called “Weekly office-supply check,” normally planned for Monday. The definition names the usual owner and says the occurrence needs a short stock note. On 6 April, an occurrence is planned for Monday and is completed that afternoon with its own note. That note belongs to 6 April only.
On 13 April, the office is closed. The occurrence remains dated 13 April, has status “skipped,” and includes “office closed” as the reason. It is not marked completed, and the 20 April occurrence is not treated as proof that the 13 April check happened. On 20 April, the normal owner is unavailable. The 20 April occurrence is marked “rescheduled”; a replacement occurrence is planned for 21 April and records that it was rescheduled from 20 April.
In May, the office decides future checks should happen on Fridays. The definition records an effective-from boundary. Earlier Monday occurrences remain unchanged, while later Friday occurrences follow the new rule. This fictional example is teaching material, not a customer story or a claim about a particular tool.
7. Prepare the record decision before implementation
Before requesting a build, make a small worksheet with: recurring-task definition reference; occurrence reference; task name; planned date; actual completion date; outcome; evidence; skip reason; rescheduled-from reference; and rule-change effective boundary. Test it using one ordinary completion, one skip and one reschedule. Ask a colleague whether they can tell exactly what happened on each planned date.
Microsoft Support’s “Recurring tasks in Planner” says that Planner displays the current occurrence as its own task and that occurrences can be completed, tracked and filtered independently. That statement is specific to Microsoft Planner. The worksheet and suggested practices in this guide are original SME workflow advice; they do not promise identical behaviour in another product.
Once the worksheet is agreed, BossFlow can review recurring generation, permissions, notifications, automation and implementation. SME Systems provides this education; implementation and quotation discussion remain with BossFlow. Source note: Microsoft Support, “Recurring tasks in Planner” — product-specific information about separate current occurrences and independent tracking.
Practical Checklist
- Write a one-sentence definition of one recurring-task occurrence.
- Keep a recurring definition reference separate from every occurrence reference.
- Record planned date and actual completion date as separate fields.
- Choose clear outcomes, including completed, skipped and rescheduled.
- Require a concise skip reason whenever work is deliberately not performed.
- Keep the original planned occurrence when rescheduling, and link the replacement with rescheduled-from.
- Set and record an effective-from boundary when changing a future rule.
- Test the worksheet with one completion, one skip and one reschedule before discussing implementation.