CONTRACTOR STATUS REPORT

Project Title:
Vendor:

Date Prepared:
Contract #:

Scope Performance This Reporting Period

Quality Performance This Reporting Period

Schedule Performance This Reporting Period

Page 1 of 3

CONTRACTOR STATUS REPORT

Cost Performance This Reporting Period

Forecast Performance for Future Reporting Periods

Claims or Disputes

Risks

Page 2 of 3

CONTRACTOR STATUS REPORT

Planned Corrective or Preventive Action

Issues

Comments

Page 3 of 3

196

Monitoring and Control Forms

4.6 FORMAL ACCEPTANCE

The Formal Acceptance form is used to document acceptance by the customer or other stakeholder. Formal
Acceptance can be done periodically throughout the project, as with partial or interim deliverables, or for the project as a whole.
There are two aspects regarding the deliverables formal acceptance:
1. Verify the correctness of the deliverable; this is performed during the Control Quality process.
2. Validate that the verified deliverable meets the acceptance criteria agreed upon with the customer; this is
performed during Validate Scope.
Deliverables that meet the acceptance criteria are formally signed off and approved by the customer or sponsor. This formal documentation is forwarded to the Close Project or Phase process (Section 4.6).
The Formal Acceptance form may include, but is not limited to:

Requirements
Method of validation
Acceptance criteria
Status of deliverable
Signoff

Use the information from your project to tailor the form to best meet your needs.
The Formal Acceptance form can receive information from:

Project Management Plan

Requirements Documentation
Requirements Traceability Matrix
Work Performance Data

It provides information to:

Project Performance Reports
Change Requests
Project Closeout Report
This form can be used in conjunction with processes 8.3 Control Quality and 5.5 Validate Scope in the
PMBOK GuideFifth Edition.
You can use the element descriptions in Table 4.6 to assist you in developing a Product Acceptance report.
TABLE 4.6. Elements of Product Acceptance
Document Elements

Description

ID

Enter a unique requirement identifier from the requirements documentation.

Requirement

Enter the requirement description from the requirements documentation.

Acceptance criteria

Enter the criteria for acceptance from the requirements documentation.

Validation method

Describe the method of validating that the requirement meets the stakeholders needs.

Status

Document whether the requirement or deliverable was accepted or not.

Comments

Document why the requirement or deliverable was not accepted and the required changes for
being accepted.

Signoff

Obtain the signature of the party accepting the product.