Addressing Non-Compliant Vendors

A.

When addressing a vendor that is not complying with the project deliverables, the first document that should be used is the Request for Proposal (RFP).

An RFP is a document that outlines the requirements, expectations, and scope of a project. It is typically used to solicit proposals from vendors or suppliers who can provide the goods or services required for a project.

If a vendor is not complying with the project deliverables, it is likely that they are not meeting the requirements outlined in the RFP. By reviewing the RFP, the project manager can determine if the vendor is in breach of the contract and identify specific areas where the vendor is not meeting expectations.

The SLA (Service Level Agreement) is a contract between a service provider and a customer that outlines the level of service that will be provided. It is typically used for ongoing services, rather than for a one-time project. While an SLA may be used as part of a vendor contract, it is not the first document that should be used when addressing a vendor that is not complying with project deliverables.

The Project Charter outlines the objectives, scope, and stakeholders of a project. While the Project Charter is an important document that provides an overview of the project, it does not provide specific requirements or expectations that can be used to address a vendor that is not complying with project deliverables.

The Risk Register is a document that identifies potential risks to a project and outlines strategies for mitigating those risks. While the Risk Register may be useful in identifying risks associated with a vendor not complying with project deliverables, it is not the first document that should be used when addressing this issue.

In summary, the RFP is the document that should be used first when addressing a vendor that is not complying with project deliverables. It provides specific requirements and expectations that can be used to determine if the vendor is in breach of the contract.