Work through issues

A check that finds things isn't the end of the job — it's the start of a queue. Every issue shows its rule, its evidence, and the file, so the call takes seconds and the record keeps it.

Triage the queue

1. Work the queues — needs review, open, snoozed, resolved, dismissed — filtered by standard and severity. Each issue shows the rule behind it, the evidence, and the asset itself.
2. Assign, snooze, or resolve. Assign to a teammate; snooze until a date you choose, with a note; resolve with a reason, or mark it not an issue or won't fix. Discuss any issue in its own comment thread.
3. Jump to the fix. Straight from the issue to the file that needs changing — and see everywhere that file is used before deciding.

Tip: an issue that comes back after being resolved reappears clearly marked as returned, with its history intact. You're notified when an issue is assigned to you.

Lock what's approved

Lock an approved file so nobody can rename, retag, re-version, move, or delete it — reads, downloads, and publishing stay open. Unlocking asks for a written reason, and that reason is kept as part of the record.

Where issues bite

A campaign post cannot publish while a file attached to it carries an unresolved blocking issue — the publish pre-flight names the issue and links you straight to it. Lower severities inform; they don't block.