Which board or template for your team

Quick pick

There are three boards (Scrum, Kanban, Delivery pipeline) and eight templates built on them; every plan can pick every template. You pick one at Create project, and a project's template cannot change later (except plain Kanban → Feedback / Idea box, once). Plans and prices: https://www.boardmark.ai/pricing

A product team working in 2-week sprints

• Use: The Scrum template (every plan)
• Why: Sprints, story points, a drag-and-drop Backlog planning page and a burndown per sprint
• What you get: A To Do → In Progress → In Review → Test Rejected → Done board, a Start sprint form that checks issues and points, an “n days overdue” badge, a choice of where unfinished work goes at closing, and closed sprints with what was done in them
• Turn on: Who can run sprints = all members (if not only admins) · Parallel sprints for several teams on one board · Releases (paid plans) · GitHub / GitLab (Pro, Premium) · automatic standup and Sprint review + Insights (Premium)

First three steps: 1) A company admin presses Create project → the Scrum template, with a name and key (such as APP) 2) Backlog tab: create cards with points, press Create sprint and drag cards into it 3) Press Start sprint, pick 2 weeks and a goal; invite the team in the Admin console and add them in Project settings → Members & access

A support or ops team with continuous flow

• Use: The Kanban template + WIP limits + the On Hold column
• Why: No sprints — work flows in and through; a WIP limit warns when a column takes on too much, and On Hold parks work waiting for a customer or another team without counting it as WIP
• What you get: A Backlog column before To Do, weekly throughput on the board, done cards clearing off the board every week, and a List view where ] and [ move a status
• Turn on: On Hold in Project settings (Columns) · a WIP limit per column in Board columns (Premium) · webhooks to Slack / Teams / Google Chat / Discord (every plan) · Telegram (Pro, Premium) or LINE (Premium) notifications

First three steps: 1) Create project → the Kanban template 2) Project settings: turn On Hold on and (Premium) set a WIP limit on In Progress 3) Project settings → Integrations: add a webhook to the team's chat with issue.created and issue.status_changed

QA across several environments

• Use: The Delivery pipeline template + Releases + the gate
• Why: Every card shows which environment it is on, with Testing and Passed columns per environment, and Test Rejected sends it back to development with a reason
• What you get: Developing → Dev Done → Testing (env) → Passed (env) → … → Done, a Releases tab showing Blocked / At risk / On track / Ready per feature, a release gate with automatic checks plus items people tick, and bugs with a severity
• Turn on: Releases (paid plans) and the Manage releases switch for release managers · GitHub / GitLab with auto-move rules (Pro, Premium) · automatic Release review (Premium)

First three steps: 1) Create project → Delivery pipeline with your environments in delivery order, such as develop, UAT, production 2) Project settings → turn Releases on, then New release with a production date and milestones 3) Put epics into the release (+ Add issues), give bugs a severity, and follow the Releases tab

Management OKRs and quarterly goals

• Use: The Roadmap & Goals template + Timeline + links across projects (every plan)
• Why: A goal's progress is never typed — it comes from the cards and releases linked to it in other teams' projects, and On track / At risk / Off track come from the dates
• What you get: One goal per card with quarter, start / end, owner and a RICE score; a Timeline zoomed by quarter / month / week where you drag a bar to move dates; saved filters Off track · At risk · This quarter
• Turn on: The weekly or monthly executive report (Premium) with each project's health and the goals · company Insights (Premium)

First three steps: 1) Create project → the Roadmap & Goals template (it opens on the Timeline) 2) Create a goal: quarter, start, end, owner and reach / impact / confidence / effort 3) In the goal, press Link to…, pick the project, then the cards or releases that deliver it

Collecting feedback and ideas

• Use: The Feedback / Idea box template + votes (every plan)
• Why: Posting is as quick as chat — one post per card, one vote per person — and Accepted links to the real work with its progress, so posters never have to ask where it stands
• What you get: New → Reviewing → Accepted → Shipped, or Declined (a reason is required); a Top voted filter; posters are notified when the status changes
• Turn on: Company-wide access = member so everyone in the company can post · edit the area options in Project settings · an AI agent can triage (set the area, link duplicates, sum up the top-voted posts)

First three steps: 1) Create project → the Feedback / Idea box template 2) Project settings → Members & access → Company-wide access: Everyone as member 3) Share the project link (click the project name on the board to copy it); admins move posts to Reviewing / Accepted

Agency or consulting sales

• Use: The Sales & Billing template + sales documents as PDF (every plan)
• Why: One card per quotation or contract answers at once: has the customer signed, is it time to bill or chase, and has everything been collected
• What you get: Draft → Sent → Signed → In delivery → Billing → Closed / Lost, installments inside the card, the bill_due / due_soon / overdue / awaiting_signature / all_paid flags, reminders at 08:00, and Thai + English quotation, billing note and receipt PDFs numbered for you
• Turn on: Complete the company tax profile (it is the seller on every document), then set the logo, bank account, signer and default VAT in Company settings → Sales documents · link a deal to the development team's release to see Delivery · N% — BoardMark issues no tax invoices

First three steps: 1) Create project → the Sales & Billing template 2) Create a deal: customer, amount, payment_terms, then Generate from terms 3) Issue the quotation PDF from the card; at each installment issue the billing note, and mark it paid when the money arrives

An internal service desk with SLA

• Use: The Service desk template (every plan)
• Why: Take admin, finance, IT or HR requests on behalf of the requester; the SLA comes from the urgency, and a request in Waiting carries no SLA flag
• What you get: New → Triage → In progress → Waiting → Done, fields requester · category · urgency · sla_due · channel, the SLA soon / Past SLA flags, saved filters Past SLA · Mine · Waiting · New today
• Turn on: Adjust the SLA days per urgency in Project settings · the SLA due notification switch · handlers and the requester are picked from the members — when someone asks by LINE, email, walk-in or phone, the team logs the request on their behalf and records it in channel

First three steps: 1) Create project → the Service desk template 2) Check the SLA days (Urgent 1 · High 3 · Normal 7 · Low 14) in Project settings 3) Log the first request: category, urgency and channel, then assign it

A yearly budget

• Use: The Budget planning template (every plan)
• Why: One card per budget line; remaining is computed, and you see at once which lines are over or nearly spent
• What you get: Proposed → Approved → Spending → Closed / Rejected, a list view grouped by quarter with Σ planned / actual / remaining, the Over budget and ≥ 80% spent flags
• Turn on: Adjust the warning % in Project settings · fill cost_center and vendor to filter — actual is typed in, not read from your accounting system

First three steps: 1) Create project → the Budget planning template 2) Create budget lines: planned, owner, quarter, cost_center 3) Update actual during the year and watch the Over budget and ≥ 80% spent filters

A team of people and AI agents

• Use: Any board + MCP + the company and project briefs
• Why: People and agents share one board; an agent gets exactly the connecting user's rights, is told to read the rules in the briefs first, and sees who is doing what before it starts
• What you get: Card work context (working / touches and a one-call claim), the unresolved_blocker and touch_overlap warnings, the agent inbox over MCP, history that names the agent client (every plan); Agent accounts with their own name and an accountable owner, not a seat (Premium)
• Turn on: Give each agent token a role (Developer, QA …) — software boards come with default lanes (BA, Developer, QA, DevOps) that warn an agent leaving its role; editing lanes is Premium · comment.mentioned and issue.unblocked webhooks to wake an agent · ?tools=lean to save tokens

First three steps: 1) An admin writes the working rules in the company brief (Admin console) or the project brief (gear → Docs) 2) Connect the agent with https://mcp.boardmark.ai/connect.md or the web app's Agent & MCP access page (Premium: Company settings → Agents → Create agent) 3) Assign it cards or @mention it, and follow its work in History and the Audit log

Several companies or clients

• Use: One account in several companies + company-wide access + teams + moving a project between companies
• Why: Data, billing and members stay separate per company, you switch from the account menu, and you can hand a project over to the client's company when the work ends
• What you get: Switch company in the account menu, Create new company in Settings → Companies, teams that grant several projects at once, and a one-use 7-day transfer key to move a project (company admins on both sides)
• Turn on: Clients who look in must be invited and take a seat in the inviting company — give them the viewer role if they only read · each company has its own free tier and bill

First three steps: 1) Decide: one project per client in your company, or one company per client (Settings → Companies → Create new company) 2) Admin console → Teams: create a team per client, then add the team in each project's Project settings → Members & access 3) At hand-over: Project settings → Move to another company → Make transfer key, and send it to the client company's admin