Tracking Feedback to Done

Every pin and note starts as raw feedback and needs a clear path to being fixed and confirmed. Pinpoint gives each comment a status, an owner, and details like labels and due dates so your team always knows what is left to do and who is doing it.

The Four Statuses a Comment Moves Through

A comment travels through a fixed sequence of statuses. Anyone with permission to work tickets can move a comment forward, and the client who raised it has the final say on whether it is truly done.

Status	What it means	Who typically sets it
Open	New feedback that no one has started yet.	Set automatically when a pin is dropped.
In progress	Someone is actively working on the fix.	Teammate or admin.
Completed	The work is finished and ready for the client to confirm.	Teammate or admin.
Resolved	The client has confirmed the fix is good and the item is closed.	The client who raised it (or an admin).

When you mark a comment completed, the client can either confirm it as resolved or reject it to reopen the thread. A rejected comment comes back for another pass.

Assigning Owners and Adding Details

Beyond status, each comment can carry the details your team needs to prioritise and route it. Open any comment to set:

•Assignee — the teammate responsible for the fix, so it shows up in their own filtered view of work.

•Labels and tags — group related items such as bug, critical, ux or ui.

•Due date — a target date for when the item should be closed.

•Type and severity — describe the nature of the feedback and how serious it is.

Asking for Proof Before Closing

When you change a status, Pinpoint lets you attach a short reason so everyone on the thread understands why. Common phrasings are offered as one-tap presets — for example "Please add proof" or "This isn't working, please check" — which is useful when you want a teammate to show evidence of a fix before an item is confirmed.

Teammates can reply on the thread with proof-of-fix, including a screen recording or video, so the client can see the change before marking it resolved.

Working from the Board or the List

You can track feedback in whichever view suits the moment. The list view gives you a paginated, filterable rundown of every comment, while the Kanban board arranges comments as cards across status lanes so you can drag an item from one lane to the next as work progresses. Both views share the same filters for status, label, tag, assignee, date range and page, and a filtered view can be shared by link so a teammate opens exactly what you were looking at.

Related topics: Kanban board, Filter and search feedback, Reply and prove fixes.