Skip to main content

Bid activity: the review desk and bid log (formerly Lead Queue)

Jobs queued and waiting to be bid on — how the Lead Queue works, lead expiry, and where to find full lead history.

Written by Ivan Nedelkovski

What is Bid activity?

Bid activity (formerly the Lead Queue) has two parts: a queue at the top, where you review the jobs waiting for your OK, and a read-only log below it that shows every bid from the last 72 hours. Jobs expire automatically 72 hours after the job was posted, so the page stays focused on what you can still act on.


The queue

The queue panel shows how many jobs are waiting, chips by how old the jobs are (posted in the last 6h, today, over 24h old), the next few jobs and a Review all button. Opening any queued job opens the review desk. If nothing is waiting it says Queue is clear.

Got a pile of old jobs? Clear N stale skips every job over 24h old after you confirm, and you can Undo it right away.


The review desk

The desk is a full-screen view: the list of waiting jobs on the left, then the job description, the cover letter and bid settings, and the countdown, client details and AI fit for the selected job. You can edit the cover letter before sending.

  • S — send the proposal now.

  • X — skip the job. The skip goes through after 5 seconds, and Z undoes it until then.

  • J / K — next / previous job (the arrow keys work too).

  • P — pause the timer. The job then waits for you ("Until I approve") instead of sending by itself.

  • Esc — close the desk.

Every button shows its key, and a popup confirms the key each time you use an action. Jobs with an active countdown still send by themselves when the timer reaches zero if you don't intervene (you get a Slack or Discord notification first). When the timer runs out on a job you're looking at, it locks and moves to Sending.

When the countdown reaches zero on a lead you haven't approved, skipped or put on hold, the timer shows Sending… while the auto-bid starts. Once a bid is running, approving that lead by hand is blocked ("This lead is already being bid on"), and so is approving a lead whose proposal was already sent ("A proposal was already sent for this lead"). A lead whose bid genuinely failed can still be sent again.


The bid log

Below the queue, four tabs list every bid from the last 72 hours. Nothing here needs approving; it shows where each bid stands.

  • Sending — bids handed to the bidder, with a four-step timeline: In review, Handed to bidder, Submitting, Sent.

  • Sent — proposals that went out.

  • Skipped — jobs that were not bid on, with the reason, a link to fix it where there is one, and Send again.

  • Failed — bids that failed, with where each one stands and Send again.


Full lead history

The Bid activity page replaced the old Leads Overview page. Full lead history — every proposal analyzed, sent, viewed, replied, or rejected across all campaigns — is now on the Dashboard in the Recent Leads table. From there you can filter by status, search by job URL, export to CSV, and open any lead's detail drawer.


Proposal status signals

After a proposal is sent, Lancer syncs outcomes back from Upwork and shows small colored badge icons on each lead — visible in the campaign feed, the lead detail drawer, and the Dashboard's Recent Leads table. Hover any badge to see its label. Three signals are tracked:

  • Outboosted — your boost bid was outbid by a competing proposal. Upwork typically refunds the boost Connects. The proposal remains visible to the client.

  • Job cancelled — the client cancelled the job after your boosted proposal was submitted. Upwork typically refunds the Connects used to apply.

  • Proposal declined — the client explicitly declined your proposal.

Leads with no signal events show no badge. Signals are additional context and do not change the lead's status.

Did this answer your question?