Declined jobs deserve a second look
We added a dedicated panel for reviewing declined jobs straight from the pipeline view — because a decline isn't always a dead end, and the data inside one is too useful to bury.
When we first shipped the jobs pipeline, declined jobs did exactly what the name suggests: they left the pipeline. Out of sight, out of the funnel, out of your weekly review. That felt clean. In practice, it threw away signal.
The pattern we kept hearing from teams was the same: a job gets declined, and then two weeks later someone asks "didn't we already look at one like this?" — and nobody can find it. The decline was a decision, but the context around it was gone. So we built a way to pull that context back without cluttering the active pipeline.
Why a separate panel, not a filter
The obvious move would have been a status filter on the main jobs list. We tried it. It made the pipeline noisier for the 95% of the time you don't care about declined work, and it made the declined jobs themselves harder to scan because they were interleaved with everything else.
A dedicated panel, opened from the jobs page header, keeps the two views honest View Declined Jobs. The pipeline stays focused on what's live. The declined panel is where you go deliberately, when you're doing a retro, chasing a pattern, or reconsidering a no.
What this unlocks
A few workflows we've already seen internally:
- Reopening close calls. Some declines are "not now," not "not ever." Having them one click away makes it realistic to revisit them when conditions change.
- Spotting patterns in what you turn down. If you're declining the same shape of job over and over, that's worth knowing — either your intake is miscalibrated, or there's an underserved segment you keep walking past.
- Auditing decisions. New team members can see what got declined and, by inference, what the bar looks like.
None of this requires new data; the declines were always there. What was missing was a deliberate surface to look at them.
What's next
This is the smallest version of the idea: a panel, the list, the basics. The interesting follow-ups are around making declined jobs actionable again — bulk reconsideration, decline reasons that flow into reporting, and surfacing relevant declined jobs when a similar new one comes in. We'd rather ship the lookup first, learn how teams actually use it, and then build on the patterns that emerge.