How to Use Trello for Project Management

To use Trello for project management, make one board per project, turn your workflow into lists such as Requests, Up next, Doing, In review and Done, and make each piece of work a card that moves from left to right. Put the detail on the card: a checklist for the steps, a due date, a label for the kind of work and the people responsible as members. Then write down how the board is used, save the setup as a template, and add views and automation as your plan allows. The steps below follow Trello’s own guide and help pages as of September 30, 2026, and end with a worked example board for a five-person team and an honest look at where Trello stops.

The four parts of a Trello board

Trello’s own guide↗ (opens in a new tab) describes a board as four things: the board, its lists, its cards and the board menu. A board is the place for one project, team or workflow. Lists hold cards in their stages of progress, and you can add as many as you like and name them however you want. Cards are the smallest unit, usually one task or idea each, with no limit on how many a board holds. The board menu on the right is where you manage members’ permissions, settings, Power-Ups and automations, and where the activity feed lives.

One tip from the same guide saves an afternoon when you move an existing backlog in: paste a list of lines into a new card and Trello turns each line into a card of its own.

Step 1: one board per project, lists for the workflow

• Name lists after states, not people. “Doing” tells everyone where a card is; “Maria” only tells them who has it.
• Keep to four to six lists. Every extra list is another place for a card to sit unnoticed.
• Make the first card on the board a “How we use this board” card: what each list means, what each label means, and who moves cards into Done.
• Keep one project per board. A board mixing two clients will eventually show one client the other’s work.

Step 2: cards that carry the detail

• Title: a verb and an outcome, such as “Add online booking to the contact page,” not “Booking.”
• Description: what is wrong or wanted, why it matters, and a link to anything relevant.
• Checklists: the steps inside one card. Progress shows on the front of the card, and any item that grows can be converted into a card of its own. Trello’s checklist help page↗ (opens in a new tab) covers advanced checklists, which add a person and a due date to each item.
• Dates: a start date, a due date and time, and a reminder. You can mark a card complete, and a recurring due date resets itself when the card is marked done, with no automation needed.
• Labels: a color and an optional name, applied per board. Use them for the kind of work (bug, feature, content) or for “Waiting on client,” never for status, because the list already says where a card is. A colorblind friendly mode adds symbols to every label.
• Members: adding a board member to a card is how Trello assigns work. Card members automatically watch the card and get notified of comments, date changes and moves.

One disagreement to know about: Trello’s plan pages list advanced checklists from the Standard plan up, while the checklist help page still says they need a Premium Workspace. If the option is missing, check which plan your Workspace is on.

Step 3: templates

• Card templates live on the board itself. Open a card, choose Make template from its menu, and use Create from template at the bottom of any list. They belong to one board, and editing a template does not change cards already made from it.
• Board templates copy a whole setup: lists, labels and example cards. Premium and Enterprise Workspaces can keep private or Workspace-only templates; on other plans, a board has to be public before it can become a template, which is rarely what a client project wants.
• Trello’s community template gallery has ready-made boards for most kinds of project. Treat them as a starting point and delete what you will not use.

Step 4: views, by plan

Trello has four plans: Free, Standard, Premium and Enterprise. According to Trello’s plan guide↗ (opens in a new tab), every plan has the board view and unlimited Power-Ups. Standard adds unlimited boards, Custom Fields, advanced checklists and card mirroring. Premium adds the other views, Calendar, Timeline, Table, Dashboard and Map, plus Workspace-wide Table and Calendar views, template boards, and observers who can see a board without changing it. Enterprise gets every Premium feature in every Workspace. On Free, a Workspace is limited to 10 boards and 10 collaborators, counted across the whole Workspace rather than per board.

Two newer personal features sit beside the boards: Inbox, a private list for capturing to-dos from email, Slack and elsewhere, and Planner, which shows your Google or Outlook calendar next to your cards so you can block time for them. Inbox is on every plan; Trello’s pricing page lists Planner as view-only on Free, with full access from Standard up.

Step 5: Power-Ups and automation

Power-Ups add features or connect other services, such as Google Drive, GitHub or Salesforce, from the Power-Ups menu in the board header. Trello sets no limit on how many a board can have, on any plan, though some partner Power-Ups need a subscription of their own.

Trello’s automation↗ (opens in a new tab) comes in five types: rules that fire when something happens, card buttons, board buttons, scheduled commands and due date commands. It is available in every Workspace, with larger monthly quotas on paid plans. You may know it as Butler: Trello built it into the product and its help pages now call it Automation, though the Butler name survives in some page addresses, and the old Butler Bot is no longer officially supported. Trello’s pricing page counts the quota in “command runs” and the help pages in “automation runs”; they are the same thing.

Rule:           when a card is moved into "Done", mark its due date complete
Card button:    "Ready for review" -> move card to "In review", add label "Needs review"
Scheduled:      every Monday at 9 am, sort "Up next" by due date
Due date:       2 days before a card is due, add the label "Due soon"

A worked example: a five-person web team

Picture a small agency in Austin building a website for a dental practice: two developers, a designer, a writer and an account lead. One board, five lists, four labels, and every card set up the same way.

LISTS    Requests -> Up next -> Doing -> In review -> Done
LABELS   Bug (red) · Feature (green) · Content (blue) · Waiting on client (yellow)

REQUESTS     Online booking from the contact page          [Feature]
             Spanish-language service pages                 [Feature] [Content]
UP NEXT      Staff bios for the About page                  [Content] [Waiting on client]  due Oct 3
DOING        Mobile menu overlaps the logo on iPhone        [Bug]      Jamal               due Oct 7
             Homepage hero copy                             [Content]  Priya               due Oct 2
IN REVIEW    Contact form lets spam through                 [Bug]      Dev                 checklist 3/4
DONE         Hosting and domain set up                      [Feature]

CARD BACK: Mobile menu overlaps the logo on iPhone
  Members     Jamal
  Due         Oct 7
  Checklist   Reproduce on iPhone Safari · Fix header CSS · Test on Android Chrome · Deploy to staging
  Comment     "Only below 390px wide. Screenshot attached."

• Monday: the account lead moves the week’s work from Requests into Up next, oldest promise first.
• Every day: people move their own cards into Doing, no more than two each, and write the limit on the “How we use this board” card so it is a rule, not a mood.
• In review: a card moves to Done only after someone other than its member has checked it.
• Waiting on client: the yellow label goes on the card and the account lead asks the client the same day, in a comment on that card.
• Friday: archive what has been in Done for a week and send the client a short written update.

Where Trello stops

• Access is coarse below Premium. Trello’s help pages say a normal board member can edit or add to the board without restrictions, and read-only observers need Premium. Trello’s help page on adding people to cards↗ (opens in a new tab) is plain about it: once someone is on a board, they can see every card and list, and there is no way to show them only the cards they are on. Client portals covers what to do when a client needs a view of the work.
• Structure is yours to invent and to enforce. Lists, labels and card layouts differ from board to board, and the rules live on a card people may not read.
• Planning views cost more. Timeline, Calendar and Dashboard are Premium, so a Free or Standard team plans in the board view or elsewhere.
• Scrum is yours to model. Sprints, story points and velocity become lists, labels, Custom Fields or Power-Ups that someone has to keep up; what is Scrum sets out what the framework actually asks for, which is less than most tools add.
• AI assistants can reach Trello through its official MCP server, which acts with your own Trello permissions. Trello MCP with Claude Code and Trello MCP or CLI cover the setup and the choices.

If you want a board with fewer choices

fenbs goes the other way from Trello. Its four lanes, To Do, Next Up, In Progress and Completed, cannot be changed; every task is a feature, an enhancement or a bug; and roles are set per company, with Client and Reporter suggested for people outside the team. AI assistants join the board as members, and History records every change with who made it. It also has much less: no due dates, no assignee you can set, no Power-Ups, no automation rules and no calendar or timeline views. fenbs vs Trello compares the two in full.