Understanding the Abandon Bid Status (and when to mark lost)
The Abandon status in RhinoDox is intentionally different from Lost and is designed to support early pipeline and Go / No-Go workflows. Understanding the difference helps keep your bid data accurate and your pipeline clean.
What the Abandon Status Is For
Abandon is used when you make a deliberate decision not to pursue a project, or to stop pursuing it before it becomes a competitive bid.
Common use cases include:
-
A project is added to the pipeline early (often just job name and GC)
-
A Go / No-Go decision is made later
-
The team decides not to bid → the project is marked Abandon
This workflow is most common with companies that:
-
Use bid coordinators
-
Track opportunities early
-
Hold weekly Go / No-Go meetings
In less common cases, Abandon may also be used if:
-
Some estimating effort was started
-
The company decides to retract before the bid is truly in play
What the Lost Status Is For
Lost should be used when you competed on the job.
Examples:
-
You submitted a bid and were told you lost
-
You submitted a bid and never received feedback
If you bid the job and didn’t win—regardless of whether you heard back—the correct status is Lost.
Why the Project “Disappeared” After Marking Abandon
When a project is marked Abandon, it is filtered out of the pipeline by default.
This is intentional. Most users want the pipeline to show:
-
Active bids
-
Jobs currently being pursued
Nothing is deleted.
How to Find and Change an Abandoned Project
You can change a project’s status at any time.
To view abandoned projects:
-
Go to the Pipeline
-
Click Filters (orange dropdown in the upper-left)
-
Turn on Abandon
-
Open the project and update the status (for example, to Lost)
Afterward, remember to turn the Abandon filter back off to keep your pipeline focused on active work.
Quick Summary
-
Abandon = You chose not to bid
-
Lost = You bid and did not win
-
Projects marked Abandon are hidden by default, not deleted
-
All bid statuses are editable at any time