Gantt Chart for Vendor Selection

Vendor selection is one of the most consequential procurement processes an organization runs. A poor vendor choice locks you into multi-year contracts with underperforming partners. Yet most teams manage it informally — a shared spreadsheet, a few email threads, a gut-feel shortlist — without a structured timeline that forces rigor at every stage.

A Gantt chart for vendor selection fixes this. It maps every phase of the process — from requirements gathering through contract execution — onto a shared calendar, assigns owners to each workstream, and creates decision gates that prevent the process from drifting or collapsing under stakeholder pressure. Whether you're selecting a SaaS platform, a logistics partner, a professional services firm, or a manufacturing supplier, the same project management discipline applies.

This guide walks through a complete vendor selection Gantt chart, phase by phase.

Phase 1: Requirements and RFP Development (Weeks 1–4)

Every vendor selection starts with defining what you need. Skip this phase, and your RFP becomes a wish list that vendors game rather than a specification they must meet.

Business requirements gathering is the core deliverable of week one and two. This means documenting four categories of requirements:

Functional requirements: What the vendor or product must do — features, capabilities, service levels.
Technical requirements: Integration needs (APIs, data formats, authentication protocols), infrastructure compatibility, security standards (SOC 2, ISO 27001, FedRAMP).
SLA requirements: Uptime guarantees, support response times, escalation paths, SLA credits.
Budget range: Your internal ceiling — not necessarily disclosed in the RFP, but required for TCO modeling later.

Once requirements are documented, establish your vendor evaluation criteria and weights. A scoring rubric with defined weights (e.g., functionality 35%, total cost 25%, implementation support 20%, vendor stability 10%, references 10%) prevents post-hoc rationalization of a preferred vendor.

Approved vendor list vs. open market sourcing: Does your organization have a pre-qualified vendor list? If so, is your target vendor on it? If you're sourcing from the open market, decide whether you need a Request for Information (RFI) first. For a mature category where you know the key players, skip the RFI. For an emerging technology or an unfamiliar category, a 2-week RFI phase (weeks 1–2) surfaces the market landscape before you write the RFP.

RFP development (weeks 2–4) produces the document itself: scope of work, evaluation criteria disclosed to vendors, pricing template (force vendors into your format so responses are comparable), required responses, and open questions. Have legal review the RFP before distribution — vendor NDAs, response ownership, and disqualification language all need to be right.

Phase 2: Proposal Evaluation (Weeks 5–8)

Distribute the RFP at the start of week five. Include a vendor Q&A period (one week is standard) and a response deadline. A four-week response window is typical for complex procurements; two weeks works for simpler categories.

Proposal receipt and completeness check: When responses arrive, first check that each vendor completed every required section. Incomplete responses — missing a pricing template, skipping the security questionnaire — are disqualifying or score zero on the omitted criteria. Don't chase incomplete responses; it signals implementation rigor.

Scoring committee formation: Assemble a cross-functional team: business sponsor, IT, procurement, legal, and finance. For major purchases, add a subject matter expert who has lived with a similar system before.

Blind scoring of written proposals: Each committee member scores independently before the group convenes. Blind scoring reduces anchoring on a colleague's opinion. Score against your rubric — no freestyle commentary that can't be traced to a criterion.

Score tabulation and shortlist selection: Aggregate scores, discuss outliers where committee members diverged significantly, and select three to five vendors for the demonstration phase. Document the selection rationale in writing.

Phase 3: Demonstrations and Deep Dives (Weeks 9–13)

The demonstration phase is where vendor claims meet reality.

Demo script development: Before any vendor demo, write a script of specific use cases drawn from your requirements. Don't let vendors run their standard pitch deck. Give them the script two weeks in advance and ask them to demonstrate your scenarios. A vendor that struggles with your demo script will struggle in production.

Vendor demo sessions (2–4 hours per vendor): Schedule with at least three business days between sessions to allow scoring before recall degrades. After each demo, each committee member scores independently using the same rubric.

Reference checks: Require three references per finalist — specifically peer organizations (similar size, industry, use case). A vendor's references are self-selected, so probe hard: How long did implementation take vs. the original estimate? How does support behave when there's a critical incident? Would you buy again? Did the pricing hold?

Security questionnaire responses review: If your IT or security team submitted a questionnaire during RFP, the demos are the time to clarify outstanding answers in a technical deep-dive session.

Site visit (optional): For hardware vendors, manufacturing suppliers, or data center providers, a site visit is warranted. Add one week to the Gantt for scheduling, travel, and debrief.

Phase 4: Final Evaluation (Weeks 14–16)

After demos and references, you have enough data to do financial analysis.

Total cost of ownership (TCO) model: Build a 3–5 year TCO model per finalist vendor. Include:

License fees or SaaS subscription (including per-user or usage-based pricing tiers)
Implementation costs (vendor professional services + internal time)
Integration development
Training
Ongoing support costs
Annual price escalation clauses (common in multi-year contracts)

The vendor with the lowest Year 1 price is not always the lowest TCO.

Risk assessment: Evaluate vendor financial stability (Dun & Bradstreet rating, years in business, customer concentration — are they dependent on one or two anchor clients?). A vendor going out of business three years into a five-year contract is a catastrophe.

BAFO — Best and Final Offer: If you're negotiating with multiple finalists, issue a BAFO request. Include your specific asks: pricing reduction, implementation credits, extended SLA commitments, payment terms, cap on annual price escalation. Give vendors five business days to respond.

Scoring finalization and recommendation: Combine technical scores, reference quality, TCO, and risk assessment into a final ranking. Document the recommendation in a selection memo with full rationale.

Phase 5: Selection and Contracting (Weeks 17–20)

Selection recommendation memo: Before contract negotiations begin, get the selection approved. The memo goes to the business sponsor and any required finance or legal approvers. Include: selected vendor, runner-up, rationale, TCO comparison, risks, and implementation timeline.

Stakeholder approvals: Depending on contract value, procurement policy may require additional approvals — CFO sign-off above a spend threshold, board approval for strategic vendor relationships. Build these into your Gantt; they can add 1–2 weeks.

Contract negotiation: The key terms to negotiate:

Pricing: Upfront discount, multi-year commitment in exchange for rate lock, payment milestones tied to deliverables.
SLAs: Response times, uptime commitments, SLA credit structure.
IP ownership: Who owns customizations, data, or outputs from the relationship?
Data handling: Data residency, encryption standards, breach notification, data deletion on termination.
Termination provisions: Termination for convenience (can you exit?), termination for cause, transition assistance.
Liability caps: Mutual or asymmetric, relationship to annual contract value.

MSA and SOW execution: The Master Services Agreement (MSA) governs the relationship; the Statement of Work (SOW) governs the specific engagement. Both need to be executed before any work begins.

Phase 6: Implementation Kickoff

The final milestone on the vendor selection Gantt is the handoff from the procurement team to the implementation project team. This means:

Introducing the implementation PM to the vendor's project manager
Transferring the selection documentation (requirements, evaluation notes, contract)
Scheduling the formal implementation kickoff meeting
Creating the implementation Gantt chart (a separate project)

Key Decision Gates on Your Vendor Selection Gantt

Mark these as red diamond milestones on your Gantt chart:

Requirements approved before RFP is distributed
Shortlist selected after proposal scoring (typically 3–5 vendors)
Selection recommendation approved before contract negotiations begin
Contract executed before implementation kickoff

Without explicit decision gates, vendor selection projects drift — stakeholders revisit shortlists, introduce new vendors late in the process, or start implementation work before the contract is signed.

Common Vendor Selection Timeline Pitfalls

Compressing the reference check phase: Three references per finalist takes real calendar time — references need to schedule 30-minute calls, and they have their own calendars. Allow two weeks for reference check scheduling and completion.

Underestimating contract negotiation: For enterprise software, contract negotiation commonly takes four to six weeks. Legal teams on both sides, procurement policy review, and executive approval chains are slow. Don't plan for a two-week turnaround on a complex MSA.

Letting a vendor skip the demo script: When vendors deviate from your demo script ("let me show you something better"), it's a yellow flag. Either they can't do what you asked, or they're salespeople first and product experts second. Enforce your script.

Starting with a preferred vendor: Stakeholder pressure to select a predetermined winner undermines the process. Document all evaluation scores and keep them auditable. The Gantt chart — with its explicit scoring milestones and committee sign-offs — creates accountability.

Building Your Vendor Selection Gantt Chart

A vendor selection Gantt chart typically runs 16–22 weeks for complex enterprise procurements. Simpler vendor selections (smaller contract value, commodity categories) can run 6–10 weeks by compressing the evaluation phases.

Use Gantt Chart Maker to build your vendor selection timeline. Create parallel tracks for each evaluation workstream, mark decision gates as milestones, and assign committee member names to scoring tasks. Share the Gantt with your steering committee as the single source of truth on where the process stands.

A structured timeline doesn't slow down vendor selection. It accelerates it — by preventing re-work, misaligned expectations, and the last-minute contract scrambles that push go-live dates back by months.