Book Your Discovery Call

Six signs your monday.com account needs an audit

Somebody asks a simple question in a Monday morning meeting. How many active projects do we have right now?

There is a pause. Someone says they will pull it together. Two people open different boards and get different numbers. A third points out that the board everyone is looking at has not been updated since the team stopped using it, and the real work moved to a duplicate that someone made in March. Twenty minutes later the meeting has moved on and nobody has answered the question.

The platform is not broken. Every board in that account works exactly as designed. What has happened is subtler and much more common: the account has drifted away from the business it was built to support, one reasonable decision at a time.

Short answer, if you came here for one: a monday.com account needs an audit when nobody can describe its current state, meaning how many boards are live, which automations still run, which integrations still sync, and who is actually using it. The signs below are the symptoms of that gap. All six can be checked yourself.

Why accounts drift, even well-built ones

This is worth understanding before the list, because the instinct is to treat drift as a discipline problem. It is not. It is a structural consequence of how these platforms succeed.

The thing that makes monday.com valuable is that a team lead can stand up a board on a Tuesday without filing a ticket. No IT queue, no configuration project, no waiting. That autonomy is the entire point, and it is why adoption spreads.

It is also why accounts sprawl. Every board created in five minutes was created without a view of the other four hundred. Nobody was being careless. The person who duplicated a board to test a change had a good reason. The person who built an automation on a Friday afternoon solved a real problem. Two years of those decisions compound into an account that no single person can describe, and there is nothing inside the platform that reports on the whole of itself.

So drift is the default. The question is only whether anyone looks.

Sign 1: Nobody can say how many boards you have

Ask three people how many boards are in your account and you will get three answers, all of them guesses.

Why it happens. Boards get created constantly and archived almost never. There is no cost to leaving one live, so nobody does the tidying, and the total climbs quietly.

What it costs. More than clutter. When a team member searches for the right board and finds four plausible candidates, they either pick wrong or ask someone. Both are expensive at scale, and the wrong pick means work recorded somewhere nobody is watching. It also makes onboarding slow, because a new hire cannot learn a system that nobody can draw.

How to check. Count your boards. Then define what “in use” means before you look, for example any item created, updated, or status changed in the last 30 days, and count how many meet it. The ratio between those two numbers is the single most useful figure about your account. Most people are surprised by it.

Sign 2: Every new need becomes a new board

Someone raises a new type of work, and the answer in the room is “let’s just make a board for it.”

Why it happens. Making a board is easier than deciding where the work belongs. The alternative, working out which existing process this fits into and whether that process needs changing, is slower and requires someone to have authority over the structure. Usually nobody does.

What it costs. Every new board is a new place for work to hide, and a new thing to keep in sync by hand. Ten boards for ten related processes means ten places to look and no way to see across them. This is the sign that predicts the others: an account with this habit will produce all five remaining symptoms within a year.

How to check. Look at the boards created in the last six months. For each, ask whether the work it holds could have lived in an existing board with an extra column or view. If the honest answer is yes for most of them, the account is growing by accretion rather than by design.

Sign 3: Someone rebuilds the same report by hand every week

There is a person on your team whose Thursday afternoon goes into copying numbers out of monday.com into a spreadsheet or a slide, so a meeting can happen on Friday.

Why it happens. Usually because the data needed for that report lives across boards that were never designed to be read together, or the dashboard that was supposed to produce it was built once, drifted, and nobody trusts it any more. So a human becomes the integration layer.

What it costs. This is the most measurable waste in the whole list. Take the hours, multiply by the loaded cost of the person doing it, and multiply by the weeks in a year. It is nearly always more than fixing the underlying structure would cost. And the report is stale the moment it is finished, which means decisions are being made on a snapshot rather than the current state.

How to check. Ask your team a direct question: what do you copy from one place to another every week? People answer this one readily, because manual copying is the part of a job everyone resents. The answers will point straight at the structural gaps.

Sign 4: An automation stopped working, and the person who built it has left

This one usually surfaces as a complaint rather than an alert. A client asks why they never got their report. Someone checks, and the automation that was supposed to send it has not run since the spring.

Then comes the second half of the problem. The person who built that automation left the company months ago. Their login was handed to somebody else, who now owns a system they can operate but cannot evaluate. They can see the automation. They cannot tell you what it was meant to do, what else points at it, or whether changing it breaks something three boards away. So it stays exactly as it is, broken, because leaving it alone feels safer than touching it.

Why it happens. Automations run under the account of whoever created them, and they are almost never documented. The reasoning lives in one person’s head, and it walks out with them. Worse, when that account is deactivated, the automations it owns stop executing with no visible error at all. The toggle stays green. Nothing on the board indicates anything is wrong.

What it costs. Two ways, and they compound. First, whatever the automation was doing silently stops, and you find out from the person downstream who was relying on it, weeks later. Second, the account becomes progressively harder to change, because every improvement risks breaking something nobody understands. Teams in this position stop building and start working around, which is how a system that cost real money to implement slowly turns back into email and spreadsheets.

How to check. Open the run history on your most business-critical automations and look at the last successful run date rather than the toggle, because the toggle tells you an automation is enabled, not that it is working. Then check the owner of each one against your active user list. Anyone who has left is a live risk. monday.com covers ownership transfer in its Automations support section, and moving critical automations onto a service account rather than a person is the standard prevention. We went through this failure mode and four others in why monday.com automations stop working without telling you.

Sign 5: Nobody can say which integrations are still live

Your account connects to other systems. A CRM, a finance tool, a form on the website, a shared drive. Ask which of those connections is still syncing today and the room goes quiet.

Why it happens. Integrations are set up once, usually during a rollout, and then nobody looks at them again. They fail quietly. A token expires, a password rotates, a connected account gets deprovisioned during an offboarding, and the sync stops. There is no banner on the board announcing that the data in it went stale five weeks ago.

What it costs. This is the most dangerous failure on the list, because the board still looks populated. People carry on reading it and making decisions from it, unaware that it stopped reflecting reality more than a month ago. A board that is obviously empty gets investigated. A board that is quietly out of date does not.

How to check. List every connected app in your account. For each, confirm two things separately: that it is still authenticating, and that it is still writing to the board you believe it writes to. Those are different questions, and an integration can pass the first while failing the second, usually after somebody restructured the destination board.

Sign 6: Adoption stalled after go-live and nobody knows where

The rollout went well. Six months later, some teams live in the system and others quietly went back to email and spreadsheets. Nobody can say precisely which teams, or when it happened.

Why it happens. Adoption is treated as a launch event rather than something with a running number. After go-live, attention moves on, and the drop off is invisible because the boards still exist and still look populated.

What it costs. Licence spend on seats nobody uses, which is the obvious part. The larger cost is that the system stops being a reliable picture of the business. Once one department’s work is not in the platform, cross department reporting is broken for everyone, and leadership starts making decisions on partial data without knowing it is partial.

How to check. Compare licensed seats against seats with recorded activity in the last 30 days, then look at activity per board against the boards each team is supposed to be using. The gap tells you where process design or training never landed. Worth noting before you reach for monday AI to fix it: AI workflows inherit whatever structure sits underneath them, so adding automation to a process a team abandoned automates an abandoned process. Sequence matters more than enthusiasm here.

What an audit actually looks at

If two or more of those signs are familiar, a review is worth the time. A complete one covers five areas, and the order matters because each gives context for the next.

Structure. Workspaces, boards and folders, and which have genuine recent activity.

Automations. Not enabled state but execution: last successful run, current owner, and what still depends on each one.

Integrations. Every connected app, whether it is still authenticating, and whether it still syncs to the board you believe it does.

Permissions and ownership. Who holds admin, which boards are private or public and whether that still matches need, and which critical assets belong to an individual rather than a service account. This section turns up real risk rather than tidiness issues.

Adoption. Active users against licensed seats, and activity per board.

Record numbers rather than adjectives. “Cluttered” cannot be tracked and cannot be improved against. Boards active out of total, automations running out of total, integrations syncing out of total, seats used out of seats paid for, and assets with a single owner: five ratios that tell you almost everything, and give you a baseline to compare against in six months.

Can you do this yourself?

For a smaller account, yes. Under twenty boards and a handful of integrations, a focused afternoon with the automations list and the activity log will get you most of the way. Everything described above is checkable by hand.

Two things make it harder at scale. The first is volume: several hundred boards cannot be reviewed by hand in a way you would trust. The second is more awkward. The person who built the account is rarely the best person to evaluate it, because every questionable structure has a reason behind it that they remember and can defend. An outside read carries none of that history.

There is also the point raised by sign 4. If the people who understood the original decisions have left, an internal review can only describe what exists. It cannot recover the intent behind it, which is usually the thing you actually need in order to decide what to keep.

Where to start

An audit tells you the state of your platform. It can show you a board nobody has opened since March, and it can show you an automation that stopped firing in the spring. What it gives you is a picture of the whole account at once, which is the thing no individual inside it currently has.

That is what our Platform Audit does. We read the entire live account, boards, automations, integrations and AI, and hand back a map of the whole thing, a plain language findings summary, a ranked roadmap of what to fix first, and a baseline adoption score you can measure against later.

One honest caveat before you book anything, ours or anyone else’s. An audit describes the platform, not the process underneath it. Boards multiply because nobody defined where work belongs. Reports get rebuilt by hand because nobody agreed what the reporting process actually is. A good audit will name those gaps as it finds them, and the ranked roadmap should tell you which ones are worth fixing first. Just do not expect a cleanup on its own to hold. Process first, always.

See where your account actually stands: www.eligeo.ai/platform-audit

Trust the Process.

Common questions

My monday.com automation is not working, what should I do?

Check the run history rather than the toggle, because the toggle only shows that an automation is enabled, not that it ran. Look at the last successful run date and any error recorded against recent attempts. Then check three things in order: whether the owner of the automation is still an active user, whether a status label or column used in the trigger was renamed, and whether your account has hit its monthly action limit. If that check turns up more than one or two, running the same sweep across every automation in the account is exactly what we do in a Platform Audit.

Automations run under the account of whoever created them. When that person’s seat is deactivated, the automations they own stop executing, usually with no error shown and the toggle still switched on. Reassign ownership of business critical automations, ideally to a service account rather than an individual, so the next departure does not repeat it. Finding every automation still tied to a former employee is one of the first things a Platform Audit surfaces.

Open the automation from the board’s automation centre and check its owner, then compare that name against your active user list. Doing this across every business critical automation is one of the fastest audits you can run, and it is usually the one that turns up the most.

Start with what is failing rather than what is untidy. List your critical automations and their last successful run, list your integrations and whether they are still syncing, and check which boards have had activity in the last 30 days. That gives you a picture of the current state without needing to know the reasoning behind the original build. If you would rather not reverse engineer an inherited account by hand, that is precisely the situation a Platform Audit is built for.

If nobody can say how many boards are live, if every new requirement becomes a new board, if someone rebuilds a report by hand each week, if an automation broke and the person who built it has gone, if nobody knows which integrations still sync, or if adoption stalled after go-live. Two or more of those means the account has drifted from the business it supports. Our Platform Audit reads the whole live account and comes back with the findings ranked, so you know which of them to fix first.

There is no fixed number. The useful measure is the ratio of boards with recent activity to total boards. If well under half of your boards have had any activity in the last 30 days, the account has accumulated rather than grown.

Compare licensed seats against seats with activity in the last 30 days, then look at which teams stopped. Adoption usually stalls where the workflow configured in the platform did not match how that team actually works, which is a process problem rather than a training problem. A Platform Audit gives you that adoption picture per board and per user, plus a baseline you can measure the next six months against.

Archive. It removes the clutter while keeping the data recoverable, which matters when a board turns out to have been quarterly rather than abandoned.

You can, but it rarely helps. AI workflows inherit whatever structure sits underneath them and consume actions and credits as they run. Adding AI to a process a team stopped following automates an abandoned process rather than fixing it. Clean up first, then automate. A Platform Audit tells you what has to be cleaned up before AI is worth adding.