Knowledge base

Automations, checklists and the AI on a board

The rules that keep a board honest without anybody tidying it, and what the AI is actually useful for.

A board that needs tidying is a board people stop updating. These are the features that keep it current on its own.

Automations

Rules that fire when something happens on the board — a card arriving in a column, a due date passing, a checklist completing. Use them for the moves nobody should have to remember:

  • Move a card to Review when its checklist is finished.
  • Nudge a card that has not moved in a fortnight.
  • Mark a card client-visible when it reaches your delivery column.

That last one is worth setting up early. The commonest reason a client stops trusting a shared board is that it goes quiet — not because work stopped, but because nobody remembered to share the card.

Checklists

Sub-tasks inside a card, for work that is one deliverable and several steps. A card with a checklist shows its progress on the board, so a stage that looks stuck for a week is visibly 80% done rather than apparently abandoned.

Saved views

The board, filtered the way one person works — their own cards, one client, everything due this week — saved so they do not rebuild it every morning. Views are per person; changing yours does not change anybody else's board.

What the AI is for

Three things it is genuinely good at:

  • Turning a message into a card. Paste a rambling client email and get a card with a clear
  • title and a body that says what the work is.

  • Summarising movement. "What changed on this board this week?" — into something you can
  • actually send, rather than a list of card moves.

  • Saying what is stuck. It reads due dates, checklist progress and how long things have sat
  • still, which is exactly the question a Monday morning starts with.

What it does not do is decide what your client sees. Anything the AI creates is internal until a person shares it.

GitHub Projects

If the work lives in GitHub, link the board and issues and project items stay in step in both directions. Your developers never open a second tool, and your client never sees a repository — the board is the layer in between, which is the point.

Automations, checklists, saved views, the AI and the GitHub sync are included in Boards Pro and above, and in every Agency hosting plan.

Latest from the blog

What we have been writing about hosting, SEO and running sites at scale.

SEO and Link Building from the Hosting Layer: A 2026 Operator's View

How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.

Read the post →

Making WordPress Fast and Secure: A Performance and Plugin Checklist

A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.

Read the post →

How to Choose Managed Web Hosting in 2026: A Buyer's Guide

What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.

Read the post →

Read the blog →

Still stuck?

Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.

Contact support → All articles →