Work moves through four columns.
Not a project management system. Four columns, a ticket per piece of work, and enough structure that a month of it stays readable.
Backlog, in progress, review, done
Drag it across. Assign it to a person and a project, which is what makes it appear on their day and on the client invoice.
Every ticket carries its own notes
A description, the decisions made on it, and the thread it came from. Picking up someone else’s work does not start with a call.
Archive the month
When the month closes, the done column archives in one action. The board reads like this month’s work rather than a year of it.
Four columns, deliberately
Backlog, in progress, review, done. No custom workflow builder, no sub-states, no swimlane configuration. The constraint is the feature: four columns stay legible when four people are looking at them for the first time.
Tickets carry their work
A description, notes, attachments and recordings on the ticket itself, so picking up someone else’s work does not start with a call. Time logged from a board card attaches to the ticket, which is how estimates and actuals eventually line up.
- Assignee, project, due date, notes
- Attachments and recordings on the ticket
- Clock in from the card
- Workspace-wide board with a filtered view per channel
Closing the month
One action archives what is done, so the board is this month rather than this year. Archived tickets stay searchable and stay attached to the hours logged against them.