Procurement Documentation
The complete set of records and files used to create, administer, and finalize a contract or purchase; it may also include materials prepared before the project begins.
Key Points
- Covers the entire procurement life cycle: formation, administration, and closeout of agreements.
- May include pre-project artifacts such as market research, master agreements, or prior vendor correspondence.
- Typically includes RFIs/RFPs/RFQs, bids/proposals, evaluations, contracts/POs, SOWs, change orders, performance and inspection reports, invoices, acceptance and closure records, and communications.
- Should be organized, version-controlled, and retained to meet legal, audit, and organizational requirements.
Example
A city IT upgrade project stores the vendor's proposal, evaluation scores, the signed contract and SOW, purchase orders, approved change requests, delivery notes, test and inspection reports, invoices, and the final acceptance certificate in a centralized repository, along with a pre-project market analysis report and a preexisting master services agreement.
PMP Example Question
During a procurement audit, the project manager discovers that vendor evaluation forms completed before project initiation are missing from the repository. What should be done?
- Ignore them because they were created before the project started.
- Add them to the procurement documentation repository.
- Only file the signed contract and change orders.
- Attach them to the risk register instead.
Correct Answer: B — Include the pre-project evaluation forms in the procurement documentation
Explanation: Procurement documentation can include materials created before the project, and should capture all records used to form, manage, and close the agreement.
