Managing Vendors on a Project: A Beginner-Friendly Explainer

Vendor management on a project is the practice of overseeing the performance of external suppliers, contractors, and service providers who are delivering specific elements of the project on behalf of the project owner. In capital and infrastructure projects, vendors often deliver the majority of the project scope -- design, construction, procurement of major equipment, IT integration, testing, and commissioning. The project manager's role is not to do this work directly, but to ensure that the vendors doing it are delivering what was agreed, within the budget and timeline committed.

Here is a beginner-friendly overview of the key concepts in vendor management on a project.

What Vendor Management Involves

Vendor management on a project involves four interconnected activities: setting up the relationship correctly at the start (contract review, kick-off meeting, baseline establishment), monitoring performance during delivery (regular reporting, site visits, milestone reviews), managing changes (scope changes, schedule changes, cost changes), and closing out the vendor relationship at project end (final acceptance, warranty activation, lessons learned).

The Most Important Documents

• The contract: The contract defines what the vendor has committed to deliver, by when, for what price, and under what conditions. The project manager does not need to be a lawyer, but must understand what the contract says about scope, schedule, payment milestones, change management, and termination. A project manager who has not read the contract cannot manage vendor performance against it.

• The contract schedule: Most capital project contracts include a detailed schedule showing when major deliverables are due, what dependencies exist between deliverables, and what the critical path is. The project manager compares actual progress against this schedule at regular intervals.

• The risk register: Vendor performance risks should be captured in the project risk register -- risks that the vendor may be late, that the vendor's design may require revision, that the vendor's subcontractors may cause delays. These risks should have mitigation plans and owners.

• Change orders: Every change to the vendor's scope, schedule, or budget should be documented in a formal change order, reviewed against the contract terms, and approved before the vendor begins the changed work. Verbal approvals to change work are not change orders.

The Most Important Behaviours

• Start with a kick-off meeting that leaves no ambiguity. Confirm the scope, the schedule, the communication plan, the escalation path, and the definition of done. Written minutes of the kick-off meeting reduce disputes later about what was agreed.

• Hold regular performance reviews -- at a cadence that matches the pace of the work. A weekly review for a fast-paced construction contract; a monthly review for a longer design engagement. Review actual progress against planned progress, not against vendor assertions.

• Manage changes proactively. Scope creep -- small, incremental changes that individually seem minor but cumulatively are significant -- is one of the most common causes of project cost and schedule overrun. Every change request, no matter how small, should be reviewed against the contract and documented.

XNM provides project management advisory services to public-sector and capital-project clients, including vendor management frameworks and contract oversight. Reach out to XNM's program & project delivery advisory team to discuss vendor management and project delivery for your project.