Team workflow
Findings are cheap; finished findings are the point. Anything in FM Fathom (a script, a field, a layout, an audit finding, an unused element) can become a tracked item with an owner, a discussion, and a status.
From any detail page
Every entity's detail page carries three controls:
- Add to board puts the item on the client's Kanban board (and flips to On board so you can see it's already tracked).
- Assign hands it to a teammate.
- Discuss opens a threaded conversation pinned to that exact object, with the message count visible so a live debate is obvious at a glance.
The discussion lives with the object, not in a chat app's scrollback. Six months from now, "why did we decide not to delete this field?" has an answer exactly where you'd look for it.
The board
The Kanban page shows the client's items in six columns: Unassigned, Assigned, In Progress, Blocked, Done, and Orphan. Drag items between columns; hide columns you don't use. Orphan is worth knowing about: it catches items whose underlying object disappeared from a newer upload, so the board never quietly points at things that no longer exist.
Board items and discussions survive re-uploads. Upload a new export and your tracked work carries forward, matched to the same objects in the new version.
Notifications
Assignments and mentions land in the notification bell in the top bar, and the notifications page keeps the trail.
Who sees what
Everyone with access to the client sees the same board, the same assignments, the same discussions. There is no private view; a client workspace is a shared workbench. See Clients and files.
Related
- Unused elements: the classic source of board items
- Accounts: who can be assigned things