# Flowchart Sign for Milestone: Which Shape to Use and Why Canonical: https://sakura5.app/blog/flowchart-sign-for-milestone/ Published: 2026-10-28 Author: the Sakura5 team · 8 min read Updated: 2026-10-28 Publisher: Sakura5 (https://sakura5.app) · support@sakura5.app > **TL;DR:** There is no official flowchart sign for a milestone. Learn the three signs that work, where to place them, and see a six-week website launch example. ![Flowchart Sign for Milestone: Which Shape to Use and Why](https://sakura5.app/img/blog/inline/flowchart-sign-for-milestone-1.jpg) There is no official flowchart sign for a milestone: the ISO 5807 flowchart standard has no milestone symbol, so the convention borrowed from project charts is a small diamond — and because a diamond already means “decision” in a flowchart, the safest choice is a milestone shape that can’t be confused with it, such as a filled black diamond, a flag, or a bold-outlined oval, explained in a one-line legend. Pick one, use it the same way every time, and say what it means. That answer matters because milestones are where a process chart and a project plan meet. A flowchart shows how work moves; a milestone marks the moment something is finished and checked. If the reader can’t tell a milestone from a yes-or-no question, they’ll misread the whole chart. This guide covers where the diamond convention comes from, the three milestone signs that work inside a flowchart, a step-by-step way to add them, a worked example of a six-week website launch, the edge cases people hit, and answers to the most common questions. ## Why there’s no standard flowchart sign for a milestone Flowchart symbols were standardized to describe processes and data: start and end, steps, decisions, inputs and outputs. The [ISO 5807 standard](https://www.iso.org/standard/11955.html) defines those shapes, and none of them means “a checkpoint in time.” A flowchart is about order, not dates, so the people who wrote the symbol sets never needed one. Project tools needed one badly. In Gantt charts and timelines, a task is a bar with a length, and a milestone is an event with zero duration — “design approved,” “site live.” A bar can’t show zero length, so those tools draw a small diamond on the date instead. That’s where most people learned that “diamond equals milestone.” The trouble starts when that habit moves into a flowchart. In a flowchart, the diamond is the decision symbol, and every arrow leaving it should carry an answer like “Yes” or “No.” Drop a milestone diamond into the same chart and the reader sees a question with only one exit. If you need a refresher on what each core shape means, our guide to [flowchart symbols and meanings for beginners](https://sakura5.app/blog/flowchart-symbols-and-meanings-for-beginners/) covers all six. ## Three milestone signs that work in a flowchart Any of these is fine. What isn’t fine is mixing them in one chart. ### 1. A filled diamond, sized smaller than your decisions Keep the project-chart convention but make it visibly different: a small solid black diamond sitting on the arrow between two steps, with the milestone name next to it rather than inside. Decisions stay as large, outlined diamonds with text inside and two labeled exits. This works best when your readers already live in Gantt charts and expect a diamond. ### 2. A flag A small flag shape is the least ambiguous option because no core flowchart symbol looks like it. Most drawing tools include one in their basic shapes or icon set. Use it when the chart will be read by people who aren’t familiar with project conventions — clients, new teammates, students. ### 3. A bold-outlined oval The oval already marks the edges of a process, so a heavier-lined oval in the middle of the flow reads naturally as “the end of one phase, the start of the next.” Label it in past tense: “Copy approved,” “Payment received.” This suits charts that split a long process into stages. Our post on the [flowchart start symbol](https://sakura5.app/blog/flowchart-start-symbol/) explains why the oval works as a boundary. Whichever sign you choose, add a legend in a corner of the chart: one shape, one sentence. “◆ = milestone: work before this point is complete and signed off.” That line does more for clarity than the shape itself. ## How to add milestones to a flowchart Milestones are easy to draw and easy to overuse. These steps keep them meaningful. ![How to add milestones to a flowchart — flowchart sign for milestone](https://sakura5.app/img/blog/inline/flowchart-sign-for-milestone-2.jpg) *Milestones are easy to draw and easy to overuse.* ### 1. Map the work before you draw the chart Before shapes and arrows, list what has to happen and group it into phases. A mind map is quicker than a flowchart at this stage because you can add, merge and move ideas without redrawing connectors. In [MindMap AI](https://sakura5.app/mindmapai/) you can drop in a project brief or a few lines of notes and get a map of the work on an infinite canvas, then expand the nodes that are still vague and drag tasks between phases until the grouping feels right. ### 2. Turn the end of each phase into a milestone A milestone belongs where a phase finishes and someone can check it. If you can’t name the person or the test that confirms it, it’s a task, not a milestone. Write each one as a completed event: “Homepage design approved,” not “Design homepage.” ### 3. Draw the flow, then place milestones on the arrows Lay out the steps and decisions first. Then put each milestone on the arrow leaving the last step of its phase. Milestones don’t do work and don’t branch, so they never get more than one arrow in and one arrow out. ### 4. Put dates next to milestones, not inside steps If the chart needs dates, attach them to milestones only. Dated steps turn the flowchart into a cramped Gantt chart. A milestone with a target date gives the reader the timeline without breaking the flow. ### 5. Add the legend and read the chart cold Add the legend, then follow the chart from start to end as if you’ve never seen it. Every diamond should ask a question. Every milestone should mark something finished. If either job is muddled, fix the shape before you share it. ## A worked example: a six-week website launch Say Mai runs a small bakery and is relaunching its website with one freelance designer. The deadline is six weeks out. Here’s how the chart comes together. ![A worked example: a six-week website launch — flowchart sign for milestone](https://sakura5.app/img/blog/inline/flowchart-sign-for-milestone-3.jpg) *Say Mai runs a small bakery and is relaunching its website with one freelance designer.* **Mapping the work.** Mai pastes her notes into a mind map: menu photos, new copy, online ordering, domain, launch post. The map sorts into four branches — Content, Design, Build, Launch — with eleven tasks under them. Two tasks, “fix opening hours” and “update Google listing,” turn out not to depend on anything, so she pulls them out of the chart entirely. **Choosing milestones.** She picks three, each at the end of a phase and each with a clear checker: - **Week 2 — Copy and photos approved** (Mai signs off). - **Week 4 — Design approved** (Mai signs off on the designer’s mockups). - **Week 6 — Site live** (a test order goes through and arrives in the kitchen inbox). **Drawing the flow.** The chart starts with an oval, “Relaunch agreed.” Rectangles cover the content tasks, then a flag labeled “Copy and photos approved — end of week 2.” The design phase includes one real decision: a diamond asking “Mockups approved?” with “No” looping back to “Revise mockups” and “Yes” leading to the second flag. The build phase has another diamond, “Test order received?”, and only its “Yes” arrow reaches the final flag and the end oval. Notice what that does. The diamonds hold the two moments where things can go back a step; the flags hold the three moments where the project moves forward for good. Anyone reading the chart can see both at a glance, and the legend in the corner reads: “Flag = milestone, signed off by Mai.” The full chart has eighteen shapes — small enough to fit on one screen. Mai keeps the original map too. When the designer asks what “Content” includes, she sends the map’s outline view instead of the flowchart. [MindMap AI](https://sakura5.app/mindmapai/) shows any map as a collapsible outline and can export it as a PDF, which is a clean way to share the task list behind each milestone. ## Edge cases and common mistakes ### Too many milestones If every third shape is a milestone, none of them stand out. A useful test: would anyone hold a short check-in or send an update at this point? If not, it’s a step. ### Milestones that branch A milestone with two exits is really a decision. Split it: a diamond asking “Approved?” followed by the milestone on the “Yes” path only. ### Parallel work that must finish together When two streams — say copy and photos — both have to finish before the milestone, draw both arrows into the milestone sign. That is the one time a milestone takes more than one arrow in, and it’s the clearest way to show the dependency. ### Charts that switch tools If the flowchart will later feed into a Gantt chart, choose the filled diamond so the sign means the same thing in both places. If it will stay a standalone process chart, the flag is clearer. For the wider question of process charts versus other diagram types, see [how to make a flowchart for a process](https://sakura5.app/blog/how-to-make-a-flowchart-for-a-process/). ## FAQ **What is the flowchart sign for a milestone?** There is no official flowchart sign for a milestone; the ISO 5807 symbol set doesn’t include one. Project charts use a small diamond, but in flowcharts the diamond means a decision, so most people use a filled diamond, a flag or a bold-outlined oval instead, explained in a legend on the chart. **Why are milestones shown as diamonds?** Milestones have zero duration, so a timeline can’t draw them as bars the way it draws tasks. Gantt charts and project tools mark the date with a small diamond instead, and the habit spread. It works on a timeline but clashes with the flowchart decision diamond, which is why flowcharts need a distinct milestone shape. **Can a milestone have more than one exit arrow?** No. A milestone marks something finished, so it has one way forward. If the process can go two ways at that point, there’s a hidden decision: draw a diamond with labeled exits first, then place the milestone on the path where the work was accepted. Multiple incoming arrows are fine when parallel work must finish together. **How many milestones should a flowchart have?** Usually one per phase, which in practice means a handful for most projects. A milestone should mark a point where someone checks the work or reports progress. If you can’t name who confirms it or how, it’s an ordinary step and belongs in a rectangle. About the app: [MindMap AI: Mind Map Maker](https://sakura5.app/mindmapai/) · App Store: https://sakura5.app/go/mindmapai?from=/blog/flowchart-sign-for-milestone/