What monday.com is and which products it covers
monday.com is an Israeli-origin software company and a proprietary cloud platform for organizing work. It is headquartered in Tel Aviv, with founders Roy Mann and Eran Zinman serving as co-CEOs. Its offering combines a configurable visual foundation with products for work management, customer relationships, development and service requests.
Distinguish the company, platform and purchased product. A monday work management board is not equivalent to a complete deployment of monday CRM, monday dev or monday service. They share concepts, but features and commercial conditions are not interchangeable. An icon in a presentation does not establish that an account has that capability enabled.
For occupational safety and health, it can coordinate campaigns, assign deliverables and track committee decisions. The record needs an external criterion explaining which activity is accepted and what evidence is retained. General collaboration features do not make the platform a specialized preventive management system.
Reference documentation: monday.com — Corporate chronology · monday.com — Management · monday.com — AI Work Platform, 6 May 2026 · monday.com — Plans.
From dapulse to a publicly traded company
The project originated within Wix. Roy Mann and Eran Zinman founded the company in 2012 as dapulse. Commercial launch followed in 2014 and a mobile application in 2016. The monday.com brand was announced in 2017 to reflect a tool intended for teams across different functions.
Funding accompanied expansion: an initial $1.5 million, $7.6 million in 2016 and $25 million in 2017. The company began trading on Nasdaq on 10 June 2021 under MNDY. These dates describe corporate stages rather than versions users need to install.
Annual reports present financial results, customer counts and staffing at specific reporting dates. They are not interchangeable with active users or evidence of suitability for a particular organization. Continuity assessment should combine provider information with an internal plan for exporting data and replacing critical processes.
Reference documentation: monday.com — Corporate chronology · dapulse — Rename announcement · monday.com — Management · monday.com — 2025 annual report · TechCrunch — Wix spin-off, 2012 · monday.com — IPO closed, June 2021.
Structured boards for organising work
monday.com organises information into boards containing groups, columns, items and subitems. An item can represent an activity, with columns describing attributes such as owner, date and status. Subitems break down additional work, but decide whether they represent steps within one activity or independent results needing their own follow-up.
Documentation distinguishes main, shareable and private boards by access. Choosing the type and available permissions is part of process design, not an afterthought. The same visual structure can represent very different situations; before copying a template, define every row, status and reported total. Readers should be able to explain what one completed item means without relying on the template’s appearance.
Reference documentation: monday.com Support — The basics of a board.
Relationships, mirror columns and reporting
Connect Boards relates items across boards, while Mirror displays data from those relationships. Dashboards combine widgets fed by connected boards. This presents different levels of work without manually reproducing every piece of information.
A useful structure could separate a site directory, campaign plan and materials board. The campaign retains its site and dates; each material has its version and owner. A relationship expresses membership rather than a separate copy of the campaign. Before configuring a total, decide whether it counts campaigns, materials or deliveries: these are different units.
Mirror visibility depends on access to the source board and column. A value someone cannot see should not be interpreted as zero or no activity. Test the dashboard with the same account type as the person expected to make decisions.
A monthly report needs a cutoff date and inclusion rule. Moving an activity into the following month can remove it from a due-date filter without completing it. The report should explain that change. An attractive dashboard is useful when its figures can be reconstructed from source items.
Reference documentation: monday Help — Mirror permissions · monday Help — Mirror Column · monday Help — Dashboards.
From Work OS to AI Work Platform
The product developed from board-based work organization into a configurable environment known as Work OS and several specialized products. Magic, Vibe and Sidekick emerged in 2025. On 6 May 2026, the company introduced AI Work Platform with an explicit focus on people and agents working together.
Sidekick is the contextual assistant; agents can receive tasks and use tools. Workflows combine steps and conditions. A coordination example might classify a request and propose an owner while leaving scope and date acceptance to the person managing the work. Not every stage needs AI: a stable due-date rule is usually easier to explain through conventional automation.
AI credits depend on the capability used and execution complexity. They do not necessarily equal a task, item or automation action. AI Work Platform commercial documentation specifies its scope relative to CRM, dev and service. A pilot should measure consumption per useful request, including retries and corrections.
Reference documentation: monday.com — AI Work Platform, 6 May 2026 · monday Help — AI Credits · monday.com — July 2025 AI capabilities.
Vibe: generated applications over work data
Magic uses existing building blocks such as boards and forms; Vibe creates custom applications. Reviewed documentation limits execution to active use, without scheduled background jobs, and does not offer exporting apps outside monday.com. Publishing requires an app package; Enterprise adds role controls over creation and publication.
A possible OSH application could show campaign materials awaiting review and let reviewers record observations. Its specification should identify readable fields, editable fields and what submission means. Start with a small dataset containing an approved material, a withdrawn one and one without an owner, then test each path.
For external integrations, an application’s shared token can broaden the information available to its users. Restrict its scope and test different roles. A generated interface may look complete before deleted records, empty relationships or connection loss have been handled. These cases are part of the design rather than final decoration.
Reference documentation: monday Help — Vibe FAQs · monday Help — Vibe permissions and pricing.
External agents and their own permissions
Bring Your Own Agent is listed as beta. An agent retains its logic on the external platform and receives an identity in monday.com. Content access requires explicit permission for each asset rather than automatically inheriting the connecting user’s rights. By contrast, MCP operates with the initiating user’s permissions.
This matters for an assistant preparing campaign summaries. Separate the tracking board from repositories containing restricted information and decide what each agent needs. Test requests to find withdrawn material or explain another site’s activity. A correct answer about the user’s own campaign does not establish that isolation works.
Distinguish instructions, tools and execution records. Telling an agent not to change dates is a behavioral rule; removing its editing tool reduces available actions. Specify how proposals are reviewed and what happens if the agent fails partway through a sequence.
Reference documentation: monday Help — External agents.
Plans, access and retaining information
The reviewed offering lists Free, Basic, Standard, Pro and Enterprise. Limits, views, automations and controls differ. The service provides web access and iOS and Android mobile apps. Selection should consider participants, guests, activity volume and administration alongside the feature shown in a demonstration.
Excel export captures table views, does not reproduce every board view and excludes subitem updates. An exported file may therefore show completion without retaining the conversation explaining it. Identify which evidence resides in columns, comments, files or links.
An exit test could use one closed campaign, one ongoing campaign and one cancelled campaign. Check whether someone without monday.com access can reconstruct owners, dates, decisions and deliverables from the retained package. Also record automation rules and metric definitions. Portability depends on that reconstruction rather than merely obtaining a file.
Reference documentation: monday Help — Export to Excel · monday.com — Plans.
Corporate development and the AI debate
In February 2026, monday.com’s share-price decline occurred amid concerns about management software growth in the AI era. June brought Monday Ventures, with a planned allocation of up to $200 million. On 22 July, the company announced restructuring involving an approximately 20% workforce reduction, linking it to its AI Work Platform strategy.
These are different corporate events: investment, market reaction and organizational decisions do not establish a feature’s effectiveness. Teams can evaluate preparation time, assignment errors and rework before and after a pilot. Keep scope constant and also record time spent configuring and supervising automations.
Reference documentation: monday.com — July 2026 SEC filing · The Next Web — Monday Ventures.
Uses for coordinating a preventive plan
- Annual planning: organise activities by period or site, exposing owners, deliverables and dates awaiting confirmation.
- Multi-part campaigns: separate material preparation, review, logistics and delivery while preserving the relationship between a campaign and its tasks.
- Follow-up meetings: review exceptions and blockers from a common register rather than reconstructing status from scattered messages.
These are uses proposed by Sabentis. The board describes coordination and execution; it does not automatically establish whether preventive content is appropriate or whether a completed activity achieved its intended effect. Identify where that subsequent evaluation will be recorded.
Worked example: keeping an annual plan interpretable
Hypothetical example. A team consolidates preventive activities across several sites and needs to explain what was planned, completed and changed during the year.
- Define one item per planned activity with identifier, site, objective, owner and date. Agree which information belongs in a subitem so the same work is not counted twice.
- Separate the initial plan from approved changes. Record why a date or scope changed rather than deleting the original reference without explanation.
- Define pending, in-progress, performed and verified states. Identify the evidence required for the latter two.
- Prepare an exceptions-focused meeting: activities without owners, unconfirmed dates, execution without evidence and outstanding dependencies.
- Test the summary with a cancelled activity and another split into several tasks. Confirm that totals still represent the agreed unit and that restructuring does not create apparent extra delivery.
The acceptable result reconstructs the plan, its changes and actual execution. An overall percentage should include its calculation rules and significant outstanding activities. Keep cancelled work distinguishable from completed work so reducing the scope does not silently improve the completion figure.
Assume twenty original activities: twelve completed, six pending and two cancelled by documented decision. Completion against the original plan is 12/20, or 60%. Against the revised plan of eighteen, it is 12/18, or 66.7%. Showing both explains the effect of cancellations. If the twelve completed activities contain thirty finished subitems, those thirty steps are not added to the activity numerator.
Reference documentation: monday.com Support — The basics of a board.
Permissions, detail and comparable progress
Access-control options vary by plan. Enterprise permissions documentation describes roles and configurable actions on items, columns and other board components; do not assume every account has those controls. Check the subscribed environment and effective member and guest views before sharing information.
Aggregating items and subitems without defining their relationship can inflate completed-task counts. Comparing small activities with long projects inside one percentage can also mislead. Explain what progress represents and retain exception detail. Where boards are connected, document relationships before archiving or deleting one because associated information may be affected. Review the effect of structural changes with the people who use the resulting reports.
Reference documentation: monday.com Support — The basics of a board · monday.com Support — Board permissions on Enterprise.
When to choose monday.com
It may fit a team needing a structured visual register that will maintain fields, rules and permissions consistently. The initial trial should include a change of owner, cancelled activity and delay as well as the ideal path. This tests whether the structure represents real work.
Compare ClickUp where adaptable workflows at several levels matter, and Asana where project dependencies are decisive. Choose based on the process, available controls and the team’s ability to maintain them, rather than a demonstration template alone.
Frequently asked questions about monday.com in OSH
Should an item and a subitem count equally?
It depends on the defined unit. If the subitem is part of an activity, counting both as independent results may duplicate progress.
Does changing a date correctly update the plan?
A date can change without explaining why. Record the decision, reason and effects on other activities where relevant.
Does a private board guarantee every confidentiality requirement?
It is an access setting to review alongside roles, guests, links and associated documents. The board type’s name does not replace that check.
Reference documentation: monday.com Support — The basics of a board · monday.com Support — Board permissions on Enterprise.
