Review Queue

Review Queue is the safety gate between analysis and action. Anything created by Batch Run, a supported scan, or a submission-adjacent workflow should become a reviewable item before it consumes more effort. The queue keeps you from confusing generated output with an approved decision.

Review one item at a time. Check the role title, company, source, Worth Score, factor rationale, posting risk, and any warnings. Then choose the next state:

Approve means the role deserves application-package work. Use this for roles with strong fit, clear proof, acceptable effort, and a source path you understand.

Hold means the role may be worth pursuing but needs more information. Common reasons include missing compensation, unclear seniority, uncertain location, stale posting signals, or a profile gap you need to fill.

Skip means the role should leave the active work pile. Skipping is useful. It preserves the reason and prevents the same weak opportunity from stealing attention again.

Send back or regenerate means the item needs better source text, profile data, or evidence before you can decide.

Manual-required means the product has reached a boundary. This commonly applies to LinkedIn, Workday, login-required, captcha-protected, unsupported, or not-yet-proven flows. For Greenhouse, Lever, and Ashby, proceed only through review-gated, fixture-gated paths where the product explicitly supports the flow.

A healthy queue is small. Clear approvals and skips regularly, and move real applications into Pipeline immediately so follow-ups and outcomes are tracked.