HKSM

Key Points

• Covers the full lifecycle from planning and solicitation through contract administration and closeout.
• Defines requirements, acceptance criteria, schedule, pricing, service levels, and responsibilities.
• Enables fair and objective seller selection through clear instructions and evaluation criteria.
• Forms the legal and operational baseline for performance, changes, payments, and dispute handling.
• Must be version controlled, traceable to requirements, and stored in a secure repository.
• Should align with organizational policy, legal and regulatory needs, and the chosen procurement strategy.

Purpose

• Communicate what is being procured, how responses should be submitted, and how they will be evaluated.
• Create a single source of truth for scope, quality expectations, and acceptance criteria.
• Provide the basis for contract terms, performance management, and payment milestones.
• Support transparency, auditability, and compliance with laws and internal controls.
• Reduce risk by clarifying responsibilities, dependencies, and change control.

Key Terms & Clauses

• Procurement SOW or Statement of Requirements: detailed scope, deliverables, and acceptance criteria.
• Solicitation types: RFI, RFQ, RFP, Invitation to Tender, including bidder instructions and timelines.
• Evaluation criteria and weighting: technical capability, cost, schedule, risk, quality, and past performance.
• Contract types: firm fixed price, fixed price with incentives, cost reimbursable, time and materials.
• Service levels and KPIs: uptime, response/resolve times, service credits, and reporting.
• Payment terms: milestones, progress payments, retainage, not-to-exceed limits, invoicing rules.
• Change control: change requests, approvals, variation orders, and pricing mechanisms.
• IP, confidentiality, data protection, audit rights, warranties, indemnities, and insurance.
• Dispute resolution, governing law, force majeure, termination for cause or convenience, and transition-out.

How to Develop/Evaluate

• Confirm the need and complete a make-or-buy analysis and procurement strategy.
• Define scope, requirements, acceptance criteria, and quality standards with stakeholders.
• Select contract type and draft the solicitation with instructions, evaluation method, and model terms.
• Set clear, weighted evaluation criteria and minimum compliance thresholds.
• Review with legal, finance, security, and compliance; finalize and issue the package.
• Manage bidder Q&A and addenda; log and control all clarifications.
• Receive proposals, screen for compliance, score using the matrix, and document due diligence.
• Negotiate, capture outcomes in the contract, and issue an award justification and notice.

How to Use

• Baseline deliverables, SLAs, and milestones; integrate with the schedule and quality plan.
• Administer the contract: track performance against KPIs, hold reviews, and apply service credits if needed.
• Control changes via documented requests, impact analysis, approvals, and contract amendments.
• Maintain a correspondence log for notices, decisions, and approvals; keep records organized.
• Match invoices to accepted deliverables or milestones; enforce payment terms and retainage.
• Capture lessons learned and archive a complete closeout package at contract completion.

Example Snippet

Excerpt from an RFP:

• Scope: Supplier will deliver the specified solution, including configuration, training, and support.
• Deliverables and acceptance: Each deliverable will be accepted within 5 business days based on documented criteria.
• Service levels: 99.9% monthly availability; P1 incidents response in 30 minutes, resolve in 4 hours; service credits apply.
• Evaluation: Technical 50%, Cost 30%, Delivery approach 15%, References 5%; minimum technical score 70% to qualify.
• Proposal format: Executive summary, approach, schedule, risk register, pricing, and assumptions; due by 17:00 on the stated date.
• Contract: Firm fixed price with milestone payments; 10% retainage until final acceptance.

Risks & Tips

• Risk: Vague scope or missing acceptance criteria leads to disputes and change inflation.
• Risk: Misaligned or undocumented evaluation criteria can trigger challenges or poor supplier fit.
• Risk: Conflicting documents or uncontrolled addenda create ambiguity and claims.
• Risk: Omitting IP, data, or regulatory clauses exposes the project to compliance issues.
• Tip: Use vetted templates, involve legal early, and maintain strict version control.
• Tip: Trace requirements through evaluation to the contract; document all decisions and negotiations.
• Tip: Publish clear bidder Q&A and hold a conference when needed to level the field.
• Tip: Define practical SLAs with meaningful credits and include transition and knowledge transfer plans.

PMP Example Question

Which item should a project manager include in procurement documentation to enable objective comparison of vendor proposals?

1. A weighted evaluation criteria matrix.
2. A stakeholder engagement assessment.
3. A team charter.
4. A product backlog.

Correct Answer: A - A weighted evaluation criteria matrix

Explanation: Clear criteria with weights allow consistent, transparent scoring of proposals. The other options are internal artifacts not used to evaluate suppliers.