Remove or eliminate a vendor from a project
Choose the right exit action while preserving evidence and an auditable decision trail.
Elimination records that a vendor was considered and did not continue; removal detaches an unwanted project relationship. Prefer elimination once meaningful outreach or evidence exists, because it preserves the decision context. Use removal for mistakes, duplicates or records added before work began, and read the confirmation carefully when related data may be affected.
Before you start
• Review questionnaires, meetings, proposals, notes and outstanding portal activity before changing the relationship.
• Confirm the project’s decision policy and whether colleagues still need the vendor for comparison or audit purposes.
Step by step
1. Review the vendor history
Open Projects → Vendors and the vendor detail. Check activity, contacts, evaluations, commercial evidence and any unresolved tasks.
2. Use elimination for a decision
Choose Eliminate when the vendor has been assessed but should no longer progress. Add a concise reason supported by the project evidence.
3. Use removal for an erroneous record
Choose Remove only when the project relationship itself is unnecessary, such as a duplicate or accidental addition. Read the dependency and deletion warning before confirming.
4. Resolve active invitations
Withdraw or close any live RFI, demo, survey or portal request that should no longer accept work. Do not assume a status change cancels every external link.
5. Verify downstream views
Check comparison, proposal and decision views. Eliminated vendors may remain visible for traceability but should be excluded from active work where the screen indicates.
What happens next
• Keep the elimination reason neutral, specific and suitable for later audit.
• Restore or re-add a vendor only when the project decision changes and the team understands which evidence remains current.
Troubleshooting
The vendor still appears after elimination
Elimination preserves the record. Filter active vendors where available; keep the eliminated entry for project history.
Removal is blocked
Resolve dependent requests or choose elimination when evidence must be retained. If the record is a true duplicate with dependencies, ask an admin for a safe consolidation path.
The vendor can still open an invitation
Withdraw or close the specific external assignment. Pipeline state and invitation state are separate controls.
Related guides
Related articles
Still stuck? Contact us →
