> ## Documentation Index
> Fetch the complete documentation index at: https://help.zarms.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# How ZARMS thinks about work

> What ZARMS aims to be, a database that connects your work, and the five ideas behind it: remove stalls by design, keep work open, keep the history, AI drafts and people decide, and help people move work forward.

ZARMS aims to be **a database that connects your work**. We sometimes call it a project management tool to make it easier to explain, but tracking progress is not the point. The point is to connect, as a team record, who took on what, what they made, and who they handed it to.

If you are used to other tools, a few ZARMS rules may make you ask "why does it work this way?" They all come from the ideas on this page.

## Remove stalls by design

Work rarely stalls because someone is lazy. It stalls in the gaps: "Who has this?", "It's waiting for review and nobody noticed", "Who asked for this, and who gets the result?"

ZARMS closes these gaps with structure, not personal effort. Every card has four roles. When you move a card's status forward, ZARMS decides who acts next (who **has the ball**). You don't need to ask "whose turn is it?" You can see it on the screen.

→ [Why cards have four roles and a ball](https://help.zarms.cloud/en/concepts/ball-and-roles.md)

## Keep work open

ZARMS believes that work inside a company should be visible to everyone by default. ZARMS is designed for organizations like a team of about 20 people working in one office. You wouldn't put the schedule on the office whiteboard where only one department could see it.

That's why boards have no private setting. Pricing is a flat rate per team that doesn't change with headcount, so everyone can look at the same place.

→ [Why boards can't be private](https://help.zarms.cloud/en/concepts/open-boards.md)

## Keep the history

You should always be able to trace back why something turned out the way it did.

* You can't delete cards. Work you stopped is **Cancelled**, and finished work goes to **Archive**. Both stay on record.
* When you change a status or a date, the change is recorded in the card's comments.
* Each card has its own Google Doc and folder, so the description, meeting notes, and deliverables stay in one place.

→ [Why you can't delete cards](https://help.zarms.cloud/en/concepts/no-delete.md), [Why descriptions live in Google Docs](https://help.zarms.cloud/en/concepts/google-docs.md)

## AI drafts, people decide

ZARMS AI drafts cards, suggests the right Processor, and summarizes how a board is doing. But people make the decisions. A card that AI drafts is created only after you check it. An action you ask AI to take runs only after you click **Continue**.

AI doesn't replace people. It helps them make decisions more easily.

→ [Ask AI and have it take actions](https://help.zarms.cloud/en/ai/ask.md)

## Help people move work forward, not watch them

ZARMS is not a tool for managers to watch their team. It helps each person find "what I need to do next" without guessing, get it done, and hand it to the next person.

That's why Home and **My Board** show only the cards where you have the ball.

## Coming from another tool?

If you've used other project management tools, read [How ZARMS differs from typical project management tools](https://help.zarms.cloud/en/concepts/differences.md) first. For the meaning of terms, see the [Glossary](https://help.zarms.cloud/en/concepts/glossary.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.