Run the whole shop's work from one task board
Claimory gives a collision repair shop one place for everything that has to happen today. Drag work across a four-column board, flip to a list that groups by what is late, hang a task off a claim or a cash job or nothing at all, push one task onto every open claim in a single action, and export exactly what your filters are showing.

Task statuses that already speak collision repair
- 01
To Do
Where a new task lands. Anything you write yourself, and anything Task per Claim fans out across the board, starts here waiting to be picked up.
- 02
In Progress
Someone has picked the task up. On the board a task moves here by dragging the card, which is the only status change that does not need a dialog.
- 03
Waiting
The task is real, it is not done, and it is not the shop's move. A supplement sitting with an adjuster and a part sitting on a truck both live here.
- 04
Done
Finished work, and the only column with a time filter. It shows today by default, then past week or past month, so a busy board does not fill up with last month's wins.
A board cannot tell you what is late

Kanban board
Drag a card, change its status
The kanban board is what opens by default. Each column is a status and each card is a task, carrying its claim number, its assignee, its priority and an overdue flag on the face of it. Drag a card from one column to the next and the status changes with it, which is the only way to move a task without opening a dialog. It is the view for a morning walk-through, when the question is what is everybody on.
List
Grouped by when it is due
The list view sets status aside and groups by due date instead: overdue, due today, due soon, no due date, and completed, each with its own count. It is the view for the question a wall of cards cannot answer, which is what is late and how far. Whichever view you leave it on is the one that opens next time, remembered per browser.
Assign it to somebody and they hear about it
Notified on assignment, and on reassignment
Putting a person on a task notifies that person, and changing the assignee later notifies the new one. Claimory stays quiet in the two cases where a message would be noise: assigning a task to yourself, and anyone who has turned that notification off in their own preferences.
It will not write the same task twice
The dialog says so itself: a task is created for every active claim that does not already have a task with the same title. Claims that already carry it open are skipped, and the result tells you both numbers. That is what makes running the same check again next week safe rather than a mess.

Log a task in two simple steps
- 01
Essentials
Title, description, status and priority, with To Do and Medium already chosen. The only thing you have to type is the title: that is the whole of what step one validates.
- 02
Context & Assign
Where the task gets its claim or its cash job, its assignee and its due date. A task with none of the three is still a valid task, which is why they are not on step one.

Push one check across every open claim tonight
Run Task per Claim on your real board and see how many claims were missing the thing you assumed everybody was already doing.
