Name your boards so people can find them later

Name your boards so people can find them later: a subject, kind and state pattern, where each board should live, and when to retire one for good.

Written by
FlowDraw Team
Published
Reading time
5 min read
The words "Name it so you find it" in large type, beside a small FlowDraw board with a Sitemap drawing.

A new board in FlowDraw is called “Untitled”, and a duplicate is called “Copy of” whatever came before it. Leave those names alone for a year and nobody will know which of your three checkout boards is the real one.

Quick Answer

Name your boards so a stranger could find and trust them: subject, then kind, then state, as in “Refunds, swimlane, current”. The title carries the load because FlowDraw search covers board titles, spaces, folders and templates, not the text on a board. Then file each board where its team works, and retire old ones on purpose.

Why the board name does most of the work

Search in FlowDraw looks at board titles, spaces, folders and templates. It does not read the text on a board. A board called “Q3 workshop” that holds your whole refund process will not turn up when someone searches for refunds. That is a limit of the product, and the habits below are how we suggest working with it.

Better search would only go so far. Even a tool that indexes every word on a canvas gives you a list of results, and you choose from that list by reading titles. Three hits for “refund” still leave you asking which one is current.

A title also travels. It is what people see in My boards and “Shared with me”, and it becomes the file name when someone exports the board.

A naming pattern for boards: subject, kind, state

Use three parts, always in the same order.

PartThe question it answersExamples
SubjectWhat is this about, in the words people search for?Refunds, Checkout, Billing service, Support onboarding
KindWhat sort of drawing is it?Swimlane, flowchart, ER, C4 container, retro
StateCan I trust it?Draft, proposed, current, retired, or a date

Subject comes first because that is what people search for, and because a list sorted by “Name” then keeps all your checkout boards together. Use the word your colleagues use, not a project code name. “Project Falcon” means nothing to someone who joins next year.

Kind comes second because one subject usually has several drawings. “Checkout, flowchart” and “Checkout, sequence” have different readers and answer different questions.

State comes last, from a short list your team agrees on. We would drop “final” and “v2” altogether, since neither tells a reader whether to trust the board. Meeting and workshop boards get a date instead, written year-month-day so they sort in order.

Applied to some familiar names:

BeforeAfter
UntitledRefunds, swimlane, current
Copy of New flow v3 FINALCheckout, flowchart, proposed
DB stuffOrders schema, ER, current
Alex’s boardSupport onboarding, flowchart, draft
Workshop notesRelease planning, retro, 2026-11-05

Rename a board as soon as you create or duplicate it, with “Rename” in the board menu. It takes seconds then and rarely happens later. When a proposed flow goes live, change the state in the title as part of the same piece of work.

Where to put a board

A name says what a board is. Its location says whose it is.

My boards is for your own drafts. A board there is visible only to its owner and its board members, and search respects that, so nobody else will find it. Anything your team relies on should not stay there.

Spaces follow teams. On Team, spaces have members and roles, so give each lasting team or area its own: Support, Payments, Platform. We would file by owner and not by project, because projects end and processes carry on. On Free and Pro a space is private to its creator, so there you share individual boards with people instead.

Folders are one level deep. FlowDraw folders do not nest, and we think a handful is plenty: Processes, Architecture, Retros, Archive. If you feel you need a folder inside a folder, that detail probably belongs in the title.

When to retire a board

A retired board that still looks current does more harm than a missing one, because people act on it. Process diagrams go stale on their own, so somebody has to take them out of circulation. There are three moments to do it.

  • A newer board replaces it. Do it the same day, as part of the change. Rename the old swimlane or flowchart with “retired” as its state, add a note at the top naming the board that replaced it, and move it to your Archive folder.
  • A workshop is over and its outcome lives somewhere else. Keep the date in the title and archive it.
  • Nobody will claim it. Once a quarter, sort a space by “Last modified” and look at the oldest boards. If nobody says a board is theirs within a week, archive it.

Archive rather than delete when there is any chance someone will ask why a decision was made. “Move to Trash” is for what nobody could need, because a board there is deleted for good after 30 days, along with its versions and comments. For deciding which boards deserve to stay at all, see what to keep and what to cut.

FAQ

No. Search covers board titles, spaces, folders and templates, and it only returns what you are allowed to see. Text inside a board is not searched, so put the words people will look for in the title.

Continue Reading

The words "Draw the unhappy path" in large type, beside a small FlowDraw board with a Bug triage workflow drawing.

Insights·

Draw the unhappy path first

Draw the unhappy path first: failures and retries are where processes break and teams disagree. A worked checkout example shows how to find them early.

Ready to create your first diagram?

Turn your ideas, notes, or documents into a clear,
editable flowchart in seconds.

Get Started Free