AI & Business Process consulting.
monday.com Platinum Partner.
Every monday.com account we’ve ever been brought in to fix looks roughly the same by the time someone calls us.
Dozens of boards with names like “Copy of Copy of Client Tracker (2).” Three workspaces doing the same job. Dashboards pulling from boards nobody’s touched in eight months. Nobody quite knows what’s safe to delete.
The instinct is to blame the platform. It isn’t the platform. monday.com will let an account get exactly as messy as the people using it allow, because nothing forces structure on you by default. That’s a feature when you’re starting out and need to move fast. It’s a liability eighteen months later when forty people have each been quietly adding boards without anyone owning the bigger picture.
How it actually happens
Nobody sits down and decides to build a messy account. It happens one reasonable decision at a time.
A new hire needs a board, so they duplicate the closest one and rename it, keeping the original just in case. A project wraps up and everyone moves on without archiving anything, because archiving isn’t anyone’s job. A department reorganises and the old workspace structure no longer matches how the team actually works, but rebuilding feels like a bigger job than living with the mismatch. Each of these is a sensible call in isolation. Stack a few hundred of them across a year and you get an account where finding anything takes longer than doing the work itself.
The pattern underneath all of it: structure is nobody’s explicit responsibility. Everyone’s responsible for their own corner, and nobody owns the whole account.
The fix isn’t a bigger cleanup, it’s ownership
A one-off clean-up will get you back to zero, but if nothing changes about who’s responsible for structure going forward, you’ll be back here in a year. The accounts that stay clean have someone, usually one admin, who treats account structure as an actual, ongoing job, not an occasional chore.
That doesn’t need to be complicated. Here’s the framework we use with clients, three categories, reviewed on a set cadence rather than in a panic.
Keep.
Boards and dashboards with recent activity that are actively supporting current work. Leave these alone.
Archive.
Anything inactive for 60 to 90 days that still has reference value, completed projects, historical records, anything someone might reasonably need to pull up again. Archiving keeps the data intact and out of Trash’s 30-day window, while getting it out of the active view. This should be the default move whenever you’re unsure.
Review.
Anything you’re not confident belongs in either bucket, duplicate boards, half-finished setups, boards with no clear owner. These need a human decision, not an automatic rule.
Run this as a genuine review, monthly for a fast-growing account, quarterly for a stable one, and set monday.com’s scheduled cleaning to handle the obvious cases automatically (archiving boards untouched for a set period) so the manual review only has to deal with judgement calls.
Archive by default, delete rarely
One rule that saves most of the pain: archive, don’t delete, unless you’re certain. Archived boards keep their data indefinitely and can be restored any time. Deleted items sit in Trash for 30 days and then they’re gone for good, no exceptions, no support ticket that brings them back. The cost of archiving something you didn’t need to keep is basically zero. The cost of deleting something you did need is often unrecoverable.
What good structure actually looks like
For most teams, one workspace per department or major function works better than one giant shared workspace or a workspace per project. Inside each workspace, a small number of folders, current work, ongoing operational boards, templates, and a year-based archive, keeps things findable without over-engineering it. The specific structure matters less than having one at all, and having someone who checks it’s still being followed.
Where this becomes a bigger conversation
A structured monthly review keeps a stable account clean. It won’t fix an account that’s already 200 boards deep with no clear ownership model, or one that’s about to scale from 20 users to 200 and needs a workspace structure that’ll hold. That’s a proper structural project, mapping how your teams actually work, then building an account architecture around that rather than around history. That’s the kind of engagement we run for clients who’ve outgrown the DIY clean-up.