Why a board helps MSP project teams
A project engineer at an MSP switches between tickets and project tasks all day. A board answers the questions they ask when they come back to the project: what is next, what is blocked, and what is waiting on the customer. Stand-ups get shorter because everyone is looking at the same picture.
A board also makes waiting visible. Most MSP projects stall waiting on a customer decision, a vendor delivery or a change window, and a column for each of those shows the project manager where to push.
How columns map to Autotask task statuses
Each column has a name, a colour, an optional work-in-progress limit, and one or more linked Autotask task statuses picked from your own status list. The first linked status is the column’s primary status.
Several statuses can share a column. Link Waiting Customer and Waiting Vendor to one Waiting column, and cards with either status sit there. A status that no column claims lands in a Needs a column lane instead of disappearing, and a Planner is prompted to link it. That happens when someone adds a new task status in Autotask.
Columns are set once, on the default board template, so every project’s board looks the same. Change the template and every board follows. Saving a template changes nothing in Autotask.
What happens when you move a card
Drop a card in a column and ProjectSmith writes the column’s primary status to the task in Autotask, then reads the task back so both systems agree. Any failed write puts the card back and shows the reason: a field your workflow makes mandatory for that status, the write-scope guard being on for that project, or Autotask not answering.
Card order and colours stay in ProjectSmith. They help the team and never clutter your Autotask records.
Designing a board for MSP projects
A few rules of thumb from MSP delivery teams:
- Keep to four to six columns. A column per Autotask status is usually noise.
- Give waiting its own column, and split customer from vendor only if you act on them differently.
- Set a work-in-progress limit on In progress. When an engineer has five tasks in progress, none of them is.
- Link your Done column to Autotask’s Complete status, so finished work closes in Autotask too.
Board, list and Gantt on the same data
The board is one of three views of the same Autotask tasks. The list view groups tasks by phase with estimated and logged hours. The Gantt chart shows dates and dependencies. Open any task to see its estimate against actual, assignees, dependencies and activity history. Logged hours include approved ProjectSmith time and time entered straight into Autotask.