# Workflow Diagram: How to Cut Off a Repeated Task

Canonical: https://sakura5.app/blog/workflow-diagram-cut-off-a-repeated-task/  
Published: 2026-11-11  
Author: the Sakura5 team · 7 min read  
Updated: 2026-11-11  
Publisher: Sakura5 (https://sakura5.app) · support@sakura5.app

> **TL;DR:** Cut off a repeated task in a workflow diagram: draw one loop, add an exit rule and send the last attempt to a named owner. Includes a worked example.

![Workflow Diagram: How to Cut Off a Repeated Task](https://sakura5.app/img/blog/inline/workflow-diagram-cut-off-a-repeated-task-1.jpg)

To cut off a repeated task in a workflow diagram, draw the repetition as a loop with a decision diamond on it, and give that diamond an exit that does not depend on luck: a maximum count, a time limit, or a condition that is checked every pass. Without that exit the arrow points back to the earlier step forever, and the diagram describes a task that never ends.

This matters because repeated tasks are where real processes leak time. Chasing a payment, re-running a failed export, asking a reviewer for sign-off again: each one starts as a reasonable retry and slowly becomes the whole job. A workflow diagram that shows the loop — and where it stops — is the cheapest way to make that visible.

Below: why repeated steps get drawn badly, a five-step method for cutting one off, a worked example with numbers, the awkward cases (loops inside loops, loops nobody owns), and short answers to the questions people ask most.

## Why a repeated task keeps escaping your workflow diagram

The first problem is that people draw a repeat as a bare arrow going backwards. An arrow from “Send reminder” back to “Wait” says *this can happen again*, but not how many times, or what ends it. Anyone reading the chart has to guess, and they usually guess “until it works.”

The second is copy-pasting. When a task happens three times in a row, it is tempting to draw three identical boxes. The diagram grows, nobody can tell whether the third box differs from the first, and the real rule — “try up to three times” — is buried in the layout instead of written down.

The third is the missing owner. A loop that runs in the background, such as an automatic retry, often has no person attached to it. It keeps going until someone notices. If you have ever found a scheduled job that failed quietly forty times, you have seen a loop with no cut-off and no owner.

## The shapes you need to cut off a loop

You do not need new symbols. A loop in a flowchart is built from the same pieces as everything else: a rectangle for the action, a diamond for the question, arrows for flow. If you want the basics, our guide to [flowchart symbols and meanings for beginners](https://sakura5.app/blog/flowchart-symbols-and-meanings-for-beginners/) covers them. What changes is where you put the diamond.

The standard pattern is: action, then a diamond that asks whether the loop is finished, then one arrow forward (finished) and one arrow back (not yet). The “not yet” arrow should pass through a small counter step, or the diamond should include the limit in its wording. For background reading, the [Wikipedia article on flowcharts](https://en.wikipedia.org/wiki/Flowchart) shows how the same shapes combine into branches and loops.

## How to cut off a repeated task in five steps

Do the first three steps as notes. Draw only at step four. If you want a place to sort the notes first, a mind map in [MindMap AI](https://sakura5.app/mindmapai/) works well.

![How to cut off a repeated task in five steps — workflow diagram cut off a repeated task](https://sakura5.app/img/blog/inline/workflow-diagram-cut-off-a-repeated-task-2.jpg)

*If you want a place to sort the notes first, a mind map in MindMap AI works well.*

### 1. Name the repeated task as one verb phrase

“Follow up” is vague. “Email the client a payment reminder” is a task. If you cannot write it as one action, you have two loops mixed together, and each needs its own cut-off.

### 2. Decide what counts as success

Write the condition that ends the loop happily: the invoice is paid, the file uploads, the reviewer replies. This is the diamond’s “yes” arrow, and it should be something observable, not a feeling.

### 3. Set the cut-off

Pick one limit and write it on the chart. A count (“three attempts”), a deadline (“14 days after the first attempt”), or both, with whichever comes first winning. Then decide what happens at the limit. Cutting off a repeat is only half the job; the other half is the exit path, which usually means a different action, a different person, or closing the case.

### 4. Draw the loop once

One action box, one diamond, one arrow back. Add a small counter note on the return arrow, such as “attempt + 1.” Resist the urge to draw the repeats out; the loop is the compact way to say it.

### 5. Draw the exit path and give it an owner

The “limit reached” arrow leaves the loop and lands on a named step: “Phone the client,” “Escalate to the account manager,” or “Mark as written off.” If that step belongs to someone different, put it in their swimlane, as described in our guide to [making a process flow diagram](https://sakura5.app/blog/how-to-make-a-process-flow-diagram/).

## A worked example: chasing a late invoice

Take a small design studio that bills clients on 30-day terms. Today, the bookkeeper, Maya, chases late invoices by feel. In a typical rough chart she sketches, the steps look like this: invoice goes out, client doesn’t pay, Maya sends a reminder, waits, sends another, and so on. The arrow just loops.

![A worked example: chasing a late invoice — workflow diagram cut off a repeated task](https://sakura5.app/img/blog/inline/workflow-diagram-cut-off-a-repeated-task-3.jpg)

*Take a small design studio that bills clients on 30-day terms.*

When she lists the actual history of one stubborn invoice, she finds eight reminder emails over ten weeks, and no phone call at all. The loop had no cut-off, so nothing ever changed channel.

Here is the redrawn version, using the five steps above.

1. **Repeated task:** email the client a payment reminder.
2. **Success:** payment received in the bank account.
3. **Cut-off:** three reminders, at days 3, 7 and 14 after the due date, or payment, whichever comes first.
4. **Loop:** “Send reminder” then diamond “Paid?” with “yes” to “Close invoice” and “no” to a second diamond “Three reminders sent?” — “no” returns to the wait step.
5. **Exit path:** “yes” goes to “Studio owner phones the client,” placed in the owner’s swimlane. If still unpaid 7 days after the call, the next step is “Pause new work for this client.”

The new chart has seven boxes instead of fifteen, and the rule is readable at a glance. More important, the eight-email outcome can no longer happen quietly: after the third reminder the work moves to a person with the authority to do something different.

## Drafting the loop in a mind map first

If the process is messy, a flowchart is the wrong place to start, because you do not yet know which steps repeat. A mind map is better for the thinking stage: put the task in the middle, branch out the things that can go wrong, and mark the branches that you end up doing more than once.

In [MindMap AI](https://sakura5.app/mindmapai/) you can type the task as the central topic and add branches for each attempt, outcome and fallback, then reorganise them freely. With MindMap Pro you can also have the AI suggest branches you may have missed, which is useful for the exit path: it often turns up a fallback you had not considered. Treat what it suggests as a prompt, delete what does not fit your business, and then redraw the confirmed steps as a flowchart. The same two-stage approach is covered in [our flowchart for troubleshooting a problem](https://sakura5.app/blog/flowchart-for-troubleshooting-a-problem/) guide, where loops after every fix are the main structure.

## Edge cases: nested loops, shared loops and loops nobody owns

A loop inside a loop is where charts become unreadable. If each reminder email is itself retried when it bounces, do not draw both on the same level. Collapse the inner loop into a single box labelled “Send reminder (retry up to 2 times)” and give it its own small diagram. The outer chart stays clear, and the inner rule has a home.

A shared loop, such as two teams both chasing the same client, needs one owner. Pick who runs the loop and show the other team as a receiver of the exit path, not a second sender.

An automatic loop, like a retry in software, still needs a cut-off and a named person who gets the alert when it is reached. Write that person on the chart. If no one is named, the loop is not cut off; it is just hidden.

If you keep the whole process as a map in [MindMap AI](https://sakura5.app/mindmapai/), you can revisit the cut-off rule each time the process changes. Finally, some repeats are legitimate and should not be cut: a daily checklist, a weekly report. Those are cycles, not retries. Mark them with a recurrence note, such as “every Monday,” instead of a limit, so readers do not mistake them for a failing loop.

## FAQ

**How do you show a repeated task in a workflow diagram?**

Draw the task once, follow it with a decision diamond asking whether the repetition is finished, and send the “not yet” arrow back to the task or the step before it. Label the diamond with the exit condition, such as “Paid?” or “Three attempts made?” so the loop has a visible way out.

**What is the difference between a loop and a cut-off in a flowchart?**

A loop is the backwards arrow that lets a step happen again. A cut-off is the rule that stops it: a maximum count, a time limit or a success condition. A loop without a cut-off can run forever, so every repeated step on a chart should have both, drawn together.

**Should I draw each repeat as a separate box?**

Usually not. Separate boxes make the chart longer and hide the rule. Draw one box and a loop with a counter. The exception is when the attempts genuinely differ, for example a polite email first, then a phone call, then a formal letter. In that case they are different steps and deserve their own boxes.

**What should happen when the cut-off is reached?**

The workflow should change something: the channel, the person or the outcome. Typical exits are escalating to a manager, switching from email to a phone call, or closing the case. An exit that simply stops the process leaves the work undone, so always send it to a named step with an owner.

About the app: [MindMap AI: Mind Map Maker](https://sakura5.app/mindmapai/) · App Store: https://sakura5.app/go/mindmapai?from=/blog/workflow-diagram-cut-off-a-repeated-task/