Speed to bid

Upwork's own guide to unviewed proposals names the reason it matters: when a project draws many proposals, "clients may not get to those at the bottom of the list", and being an early applicant or a close match helps a proposal surface. Upwork's job alerts are offered so freelancers can be among the first to apply. Upwork publishes no figure for how early is early enough.

Two parts make up the time.

• Catching: how long after posting the job reaches whoever bids, which depends on how often the feed is read.
• Deciding and sending: scoring, drafting, any approval wait and the send itself.

A team bidding by hand mostly loses time in the second part. A campaign mostly loses it in the approval wait, which is the first setting to look at when time to bid is long.

How it is measured. For each sent proposal, time to bid is the send time minus the job's posting time, counted only where both are known. Groups report the median, not the mean, because a few jobs drafted hours later by hand would drag a mean far from the typical send. The total row is left blank, because a median of medians is not a median.

Faster is not always better. The first proposal is also the first one a client can dismiss, and a job's competition is not visible in its first minutes. Late bidding is the deliberate opposite, and bidding on clients flagged Hiring Now is the extreme of speed. Comparing reply rate across time-to-bid ranges is how to find where speed pays.

How Upsight uses it. Time to bid is a column in the bidder's breakdown by campaign, member and template, and proposal analytics can be filtered by it.