Trello

What Trello is and what organizing with cards means

Trello is Atlassian’s visual work organization service. Its recognizable unit is a card in a list on a board: it may represent a task, request, editorial asset or matter awaiting a decision. It is proprietary software delivered as a service, accessible through the web and Windows, macOS, iOS and Android applications. A team can start organizing a process without developing an application.

It is associated with kanban because work can be visualized in columns and moved between states. Columns alone do not implement kanban: the team still needs work-in-progress limits, priorities and completion criteria. Lists can instead represent topics or people, in which case position does not necessarily indicate progress. Choose one meaning and apply it consistently.

General uses include personal planning, campaigns, teaching coordination, software development and deliverable tracking. For occupational safety and health, its main value is coordination: it shows what is pending and who is preparing it, while preventive assessments and specialist evidence require their own context.

Reference documentation: Joel Spolsky — Announcing Trello, 13 September 2011 · Trello — Platforms · Trello — Product tour.

Origins and development: from Fog Creek to personal productivity

Trello originated at Fog Creek Software, associated with Joel Spolsky and Michael Pryor. The January 2011 Trellis prototype led to a public launch on 13 September 2011. Android arrived in 2012; Trello, Inc. was established in July 2014 with Pryor as CEO and $10.3 million in funding. Localized experiences for Brazil, Germany and Spain followed in May 2015.

The Power-Ups extension platform opened in 2016. Atlassian announced its purchase in January 2017 and confirmed completion on 3 February. The announcement and completed transaction are different milestones. In December 2018 it acquired Butler, bringing automation into the product. In October 2019 Trello introduced its template gallery and reported 50 million registered users: a historical registration figure, not daily activity.

On 22 May 2025 it announced general availability of an experience built around Inbox, Planner and task capture, with a gradual rollout. The change extended board collaboration towards organizing individual work. The MCP server, announced in July 2026, enabled interaction from AI assistants; a September update expanded its scope. Earlier guides may therefore describe a different interface or more restricted capabilities.

Reference documentation: Trello — About · Joel Spolsky — Announcing Trello, 13 September 2011 · Atlassian — acquisition completed, SEC filing · Atlassian — Butler acquisition, SEC filing · Atlassian — The new Trello, May 2025 · Atlassian — Templates and registered users, October 2019 · Atlassian — Trello MCP announcement · Atlassian — Trello acquisition announcement.

Cards, lists and transition rules

Trello organises work through boards, lists and cards. A card can represent a deliverable or task, while lists can describe its stages. The most useful design is usually not the one with the most columns, but the one that explains what is missing, who acts next and what evidence permits progress.

Checklists break down items within a card. Trello also documents automations built from triggers and actions, alongside buttons that execute operations. These can reduce repetitive steps, but distinguish a rule that moves a card from a review that approves its content. Visual movement does not establish that the next stage’s acceptance criterion has been met. Write those criteria in terms the whole team understands.

Reference documentation: Atlassian Support — Add, delete, and manage checklists · Atlassian Support — Create and manage automations.

Designing a readable board: structure, fields and ownership

A Workspace groups boards; each board contains lists and cards. Labels classify work, members identify participants and dates place commitments in time. Custom fields record consistent attributes, while comments keep discussion attached to the item. A card assigned to several people still needs a clear rule identifying who owns its next step.

An editorial workflow might separate “awaiting preparation”, “in preparation”, “under review” and “authorized”. Name the card after an observable result: “Warehouse poster, Spanish version” can be checked; “Improve safety” contains too much work and no acceptance criterion. One field might identify the site, another the review date, and a link the current document version.

Mirror cards represent one card on several boards without treating it as two independent tasks. Before adopting them, decide what each audience needs and check access to the original. Templates should retain structure and criteria but remove inherited names, attachments and dates that do not apply to the new project. Reusing a template does not mean its content is current.

Reference documentation: Atlassian Support — Add, delete, and manage checklists · Atlassian Support — Configure board permissions · Trello — Product tour · Atlassian Support — Card mirroring.

Inbox, Planner and views: capturing is not committing

Inbox is a personal space for collecting items before organizing them. Tasks can arrive from messages and emails; AI capture can extract elements from their text. Planner places tasks alongside a connected Google or Microsoft calendar for scheduling time. Separate receiving a request, accepting it as work and finding a realistic slot. A date extracted from an email may belong to the message rather than the commitment.

Premium’s Calendar, Timeline, Table, Dashboard and Map views offer different perspectives on the same cards. A calendar reveals clashing deadlines, a table helps inspect attributes and a map places locations. None automatically makes heterogeneous cards comparable. Counting ten small cards and one entire campaign as eleven equal jobs can conceal actual workload.

A reasonable approach is to reserve preparation time for a meeting while retaining its card under review until comments are resolved. A calendar block records reserved time, not attendance or completed work. Assess capacity through commitments, estimated duration and blockers rather than the number of cards moved.

Reference documentation: Atlassian Support — Trello Planner · Atlassian — The new Trello, May 2025 · Trello — Activate views.

Automation, Power-Ups and connected assistants

Built-in automation, originating in Butler, runs rules and buttons against board events. Power-Ups provide extensions and integrations; some external services require separate subscriptions. Distinguish a file link from data synchronization: one opens a resource, while the other may create or change objects in another system.

Trello MCP lets compatible assistants read and change work through granted permissions. The 28 September 2026 update added multiple Workspaces, comments and expanded activity information. Current documentation allows link attachments but not local file uploads through this server. Available operations and user permissions are separate limits: access to a card does not guarantee that a connector supports every operation.

Test a reminder rule with an overdue card, a completed card and a reopened card. Check recipient, time zone and repeated execution. With an assistant, start by requesting pending items and inspect the returned set before authorizing changes. “Clean up the board” is ambiguous: it could mean archive, reorder or mark tasks. Specify the operation and selection criteria explicitly.

Reference documentation: Atlassian Support — Create and manage automations · Atlassian Support — Trello MCP · Atlassian Team — MCP update, 28 September 2026 · Atlassian — Trello MCP announcement · Trello — Product tour.

Plans, exports and work continuity

The reviewed comparison limits Free to ten collaborators and ten boards per Workspace. Standard adds features including custom fields and mirror cards; Premium adds views; Enterprise expands organizational administration. Automation quotas and guest conditions also affect selection. An extension’s appearance in the directory does not mean all its costs are included.

Members can export a board as JSON; Premium offers CSV and Workspace export. CSV excludes comments, while a board’s JSON contains its thousand most recent actions. Attachments may need a specific export option. These files cannot be natively reimported to reconstruct the complete board.

An exit test should therefore check content, relationships and documents, not merely successful download. Select a card with several comments, an attachment and another archived card; inspect what survives each export. Keep a field dictionary and an explanation of the lists so the dataset remains understandable outside Trello. An unreadable or incomplete copy does not establish operational continuity.

Reference documentation: Trello — Pricing and plan comparison · Atlassian Support — Export data from Trello · Trello — Platforms.

Historical architecture and the current service

In January 2012 the team described a single-page application: CoffeeScript compiled to JavaScript, Backbone and Mustache on the client; Node.js and MongoDB on the server; Socket.io and WebSockets to propagate changes. This is historical documentation, not a certified inventory of today’s infrastructure.

The practical implication is that a visible card belongs to a shared service: concurrent changes, permissions, connectivity and integrations affect what each person sees. A screenshot preserves one view but not necessarily its comments, history or links. When using it as evidence, record date, origin and context so an old image is not mistaken for the current state.

Reference documentation: Atlassian — The Trello tech stack, 2012.

Reception, data exposure and practical lessons

PCMag’s May 2025 review valued Trello’s ease and flexibility while finding it less suitable for large, complex projects. That is an editorial assessment, not a universal performance measure for every team.

WIRED documented sensitive information exposed on public boards in February 2020. Separately, Have I Been Pwned recorded January 2024 data covering more than fifteen million email addresses, names and usernames collected by enumerating a public resource. Its record says Trello denied unauthorized access. These are different episodes.

The operational lesson is to review board visibility, profiles, guests and connected applications separately. A private board does not make every kind of information suitable for that space. Preventive coordination often needs only an identifier, owner, deadline and link to the authorized repository; copying personal details into comments may unnecessarily widen their circulation. Test access with an account in the intended role, particularly after membership changes or board reuse.

Reference documentation: Have I Been Pwned — Trello · WIRED — Public Trello boards, February 2020 · PCMag via Yahoo — Trello review, May 2025 · Atlassian Support — Configure board permissions.

Coordinating preventive deliverables without losing review

• Awareness materials: follow work from draft through technical review, graphic adaptation and authorised publication.
• Meeting preparation: collect outstanding documents, questions and logistical tasks while keeping blockers visible.
• Bounded improvements: organise simple actions with an owner and evidence where the process does not need additional controls unverified in Trello.

These are uses proposed by Sabentis, not certified preventive workflows. For every board, define what finishing a card means. Its author may have completed the work while another person’s verification remains outstanding. A shared label is useful only if participants apply the same meaning to it.

Worked example: publishing a reviewed communication

Hypothetical example. A team is preparing a housekeeping campaign and wants to avoid distributing a graphic before checking its text and suitability for the site.

1. Create one card per piece, with audience, intended channel, owner and a working-document link. Do not combine materials needing different approvals into one card.
2. Define lists such as draft, technical review, final adjustment and ready to publish. Write entry and exit criteria for each stage.
3. Add a checklist covering content source, readability, version and review. Specify where approval is recorded as well as ticking the item.
4. If automation is used, initially limit it to assignment or reminders. Test the trigger on a trial card and review its execution log.
5. Before distribution, check that the approved version matches the final file. After authorised publication, record the actual link and date.

The acceptable result is a piece traceable from source to published version. A card in the final list does not prove publication: evidence of the result in the intended channel is needed. Keep a route for withdrawing or correcting a piece if an error is found later.

To validate the example, assume six planned assets: four published with verified links, one authorized but unpublished and one returned for review. Publication progress is 4/6, approximately 67%, even though five are authorized. Also check that no published asset links to a superseded version. This distinguishes approval from publication and measures outcomes rather than card movements.

Reference documentation: Atlassian Support — Add, delete, and manage checklists · Atlassian Support — Create and manage automations.

Completed boxes, automation and access

A checklist shows that someone marked items, not the quality of the checking. Define the evidence required and who may accept it. If an item needs its own discussion or documentation, a separate task may be clearer than hiding it inside a long checklist.

Automations can run because of other participants’ actions, not only the creator’s. Test repeated events, status changes and errors before using a rule on live work. Review visibility, members and permissions: a public or overly shared board can expose comments and documents to unintended audiences. Consider what happens when a card is copied, archived or reassigned, so the team does not mistake the copy for the approved original.

Reference documentation: Atlassian Support — Add, delete, and manage checklists · Atlassian Support — Create and manage automations · Atlassian Support — Configure board permissions.

When to choose a Trello board

Trello fits a simple visual workflow where a small number of stages helps a team coordinate deliverables. Before expanding it, check that labels, lists and cards still represent a process any participant can explain.

Where task dependencies and scheduling are central, compare Asana. If each item needs extensive written context, Notion can complement coordination. Avoid maintaining a task’s status in several places without identifying which is authoritative. Confirm that the chosen plan supports the specific controls the process relies on.

Frequently asked questions about Trello in OSH

Does moving a card to Done mean an action is verified?

Only where the process defines verification and evidence exists. The card’s position does not establish it automatically.

Must the board be automated immediately?

No. Stabilise stages and criteria first. Automating an ambiguous process can multiply confusion and unnecessary alerts.

Can every checklist assign people and dates?

Advanced options depend on the plan. Verify availability before designing a procedure around them.

Reference documentation: Atlassian Support — Add, delete, and manage checklists · Atlassian Support — Create and manage automations.