Study guide
25.2 Project Management, Dependencies and Procurement Schedule Risk
Certified Professional Public Buyer CPPB
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Map and Contracting Authority
1.1 CPPB Exam Map and Applied Study Method 1.2 Statutory Authority, Enabling Legislation & the ABA Model Code 1.3 Delegation, Ratification and Model Codes
2 Chapter 2: Federal Assistance and Public Records
2.1 Intergovernmental Standards & Federal Grant Compliance 2.2 Transparency, Sunshine Laws & Public Records Compliance 2.3 Confidential Information and Records Retention
3 Chapter 3: Ethics, Fraud and International Purchasing
3.1 Ethics, Integrity & Anti-Corruption in Public Purchasing 3.2 Post-Employment Rules, Collusion and Fraud 3.3 International Procurement, Currency, Customs and Logistics
4 Chapter 4: Needs and Specifications
4.1 Needs Identification, Scopes of Work & Stakeholder Engagement 4.2 Specification Types & Restrictive Specification Avoidance 4.3 Product Qualification and Restrictive Specifications
5 Chapter 5: Market Information and Strategic Planning
5.1 Market Research, Industry Engagement & Requests for Information 5.2 RFIs, Industry Engagement and Conflicts 5.3 Strategic Goals, Spend Analysis and Standardization
6 Chapter 6: Sourcing Methods and Cooperative Models
6.1 Sourcing Methods, Thresholds & Non-Competitive Justifications 6.2 Competitive and Noncompetitive Sourcing 6.3 Cooperative Purchasing, Piggybacking & Consortium Contracts
7 Chapter 7: Cooperative Review and Construction Methods
7.1 Cooperative Due Diligence, Fees and Value 7.2 Public Works, Construction Delivery & Qualifications-Based Selection 7.3 QBS, Subcontractors and Construction Compliance
8 Chapter 8: Specialized Needs and Solicitation Issuance
8.1 Specialized Requirements: Human Services, Controlled Goods and Technology 8.2 Solicitation Drafting, Public Notice & Pre-Bid Conferences 8.3 Addenda, Equal Notice and Closing Extensions
9 Chapter 9: Bid Receipt, Defects and Supplier Capability
9.1 Receipt, Opening & Responsiveness Determinations 9.2 Bid Defects and Mistakes 9.3 Supplier Responsibility Determinations & Pre-Qualification
10 Chapter 10: Supplier Eligibility and Evaluation Governance
10.1 Prequalification, Exclusions and Responsibility Findings 10.2 Evaluation Committee Management & Scoring Methodologies 10.3 Scoring, Consensus and Price Formulas
11 Chapter 11: Discussions, Final Offers and Award
11.1 Competitive Range, Clarifications & Best and Final Offers 11.2 Negotiation Integrity and Final Offers 11.3 Award Determinations, Debriefings & Bid Protests
12 Chapter 12: Debriefings and Contract Pricing Models
12.1 Debriefings, Protests and Remedies 12.2 Public Contract Types & Pricing Structures 12.3 T&M, IDIQ and Requirements Agreements
13 Chapter 13: Contract Approval and Terms
13.1 Contract Formation and Approval Controls 13.2 Essential Terms, Standard Conditions & Risk Allocation 13.3 Intellectual Property and Document Precedence
14 Chapter 14: Bonds, Insurance and Administration
14.1 Public Construction Surety Bonds & Insurance Requirements 14.2 Insurance Coverage and Endorsement Verification 14.3 Contract Administration Planning & Performance Monitoring
15 Chapter 15: Receiving, Payments and Modifications
15.1 Receiving, Acceptance and Defect Remedies 15.2 Ordering Controls, Receiving and Payment Schedules 15.3 Contract Modifications, Change Orders & Equitable Adjustments
16 Chapter 16: Scope, Adjustments and Renewals
16.1 Scope Boundaries and Constructive Changes 16.2 Equitable Adjustments and Change Pricing 16.3 Renewals, Options, Extensions and Transition 16.4 Contract Disputes, Claims and Resolution Records
17 Chapter 17: Remedies, Termination and Closeout
17.1 Contract Remedies, Disputes, Terminations & Closeout 17.2 Convenience and Default Termination 17.3 Completion, Recovery and Contract Closeout
18 Chapter 18: Records and Stakeholder Relationships
18.1 Contract File Maintenance, Version Control and Retention 18.2 Stakeholder Relationship Management & Strategic Communication 18.3 Executive Communication and Stakeholder Expectations
19 Chapter 19: Negotiation and Supplier Management
19.1 Principled Negotiations & Conflict Resolution 19.2 Impasse, Conflict Styles and Mediation 19.3 Supplier Relationship Management & Continuous Improvement
20 Chapter 20: Supplier Improvement and Procurement Leadership
20.1 Supplier Improvement and Value Engineering 20.2 Professional Advocacy, Governance & Public Stewardship 20.3 Professional Development and Public Stewardship
21 Chapter 21: Procurement Value, Learning and Price Analysis
21.1 Reporting Procurement Value and ROI 21.2 Professional Resources, Continuing Learning and Mentorship 21.3 Outreach, Partnerships and Stakeholder Guidance 21.4 Cost Analysis vs Price Analysis & Fair/Reasonable Pricing
22 Chapter 22: Cost Analysis and Life-Cycle Principles
22.1 Cost Principles, Indirect Rates and Realism 22.2 Price Documentation and a Worked Cost Negotiation 22.3 Life-Cycle Costing & Total Cost of Ownership (TCO)
23 Chapter 23: Life-Cycle Evaluation and Public Finance
23.1 Discounted Fleet Cost and Evaluation Assumptions 23.2 Public Budgeting Cycles & Fiscal Appropriation Controls 23.3 Spending Authority and Multi-Year Funding
24 Chapter 24: Inventory and Procurement Technology
24.1 Inventory Management, Warehousing & Surplus Property Disposition 24.2 Inventory Controls and Surplus Disposition 24.3 Procurement Technology, E-Sourcing & Commercial Purchasing Cards
25 Chapter 25: Payment Controls, Projects and Data
25.1 P-Card Controls and Blanket Orders 25.2 Project Management, Dependencies and Procurement Schedule Risk 25.3 Procurement Data Quality, Integrity and Reconciliation
26 Chapter 26: Process Improvement and Emerging Trends
26.1 Continuous Procurement Process Improvement 26.2 Emerging Trends and Procurement Technology Assessment
27 Chapter 27: Continuity and Specialty Programs
27.1 Disasters, Emergencies and Procurement Continuity 27.2 Socioeconomic Programs, Supplier Diversity & Sustainable Purchasing 27.3 Sustainability and Circular Purchasing
25.2 Project Management, Dependencies and Procurement Schedule Risk
Key Takeaways Explain This Topic AI
Critical-path analysis uses actual dependencies, durations, calendars, and assumptions rather than desired completion dates alone.
Fast-tracking overlaps work and can increase rework risk; crashing adds resources or cost where shortening is feasible.
Track baseline, approved changes, forecast, risks, issues, and decision owners separately.
Last updated: October 2026
Procurement is part of the project schedule
A project's desired completion date does not establish how quickly procurement can lawfully occur. The buyer must coordinate needs definition, funding, market research, approvals, notice, supplier preparation, evaluation, negotiations, award, delivery, installation, testing, and transition. A schedule that omits approval or manufacturing time creates false urgency later. Identify dependencies before promising a date to stakeholders.
A project charter records the objective, scope, sponsor, participants, constraints, and decision authority. A work breakdown structure divides the required work into manageable deliverables or activities. The procurement plan connects those activities to sourcing events and contract responsibilities. A list of desired dates without predecessors, owners, and resources is not a complete plan.
Use dependencies and the critical path
A dependency states what must occur before another activity can start or finish. Some are technical, such as installing equipment before testing it. Others are legal or administrative, such as completing approval before execution. A buyer cannot eliminate a statutory dependency merely by asking a supplier to start early. Review whether activities can lawfully overlap without exposing the entity to an unauthorized commitment.
The critical path is the longest-duration dependency path through the planned network. Under the current assumptions it determines the earliest project completion. Float is the time an activity can be delayed without delaying the relevant completion or successor constraint. Float is not a permanent entitlement: a change to durations, calendars, or dependencies can create a different controlling path.
Worked network example
Assume all durations use business days, resources are available, and there are no additional lags. Activity A is requirements approval and takes five days. B is solicitation preparation and takes eight days after A. C is funding confirmation and takes four days after A. D is final release approval and takes three days after both B and C.
- Activity Duration Predecessor Earliest finish
- A 5 None Day 5
- B 8 A Day 13
- C 4 A Day 9
- D 3 B and C Day 16
The A–B–D path is 5 + 8 + 3 = 16 business days . A–C–D is 5 + 4 + 3 = 12 business days , so C has four days of float before it would delay D in this simple network. A two-day delay to B moves the earliest finish to day 18 unless the team achieves a valid recovery. A two-day delay to C leaves the earliest finish at day 16. The arithmetic does not justify shortening a legal notice period in a later phase.
Schedule risk and recovery
Record the baseline schedule and the assumptions supporting supplier lead time, review turnaround, staff availability, approval meetings, and testing. Distinguish an issue , which has already occurred, from a risk , an uncertain future event. A supplier's confirmed missed manufacturing slot is an issue; the possibility of port congestion is a risk. Both need owners and responses, but neither should be hidden in an unexplained contingency allowance.
Use a risk register with the event, cause, likelihood, impact, mitigation, trigger, owner, and contingency. A long-lead transformer might require early market engagement, an alternate approved specification, staged delivery, or temporary equipment. Assess the legal method and full cost of each response. Ordering equipment before design approval can save time but create an unusable asset if the design later changes.
Fast-tracking overlaps activities that would otherwise occur sequentially and can increase rework or coordination risk. Crashing adds resources or other cost to shorten activity duration where feasible. Neither technique automatically works on every task. Additional evaluators may not shorten the supplier's statutory response period, and extra inspectors cannot replace a laboratory's required test duration.
Control changes and project information
A change request should identify the scope change, reason, alternatives, cost, funding, schedule effect, risk, and approval authority. Analyze effects on the critical path rather than simply adding every claimed delay to the completion date. Preserve the baseline, approved revisions, and current forecast as separate records so stakeholders can see both commitments and emerging problems.
Communicate status using evidence: completed deliverables, unresolved decisions, forecast dates, cost commitments, and actions needed. “Ninety percent complete” is weak information if the remaining ten percent includes untested security, missing permits, or a critical interface. A milestone should have an objective completion condition and named approver.
Apply the method to a procurement scenario
Suppose a department needs a public-service system operational by September 1. Procurement discovers that the planned schedule ignores two board meetings, a data-migration exercise, and user acceptance testing. The buyer should present a feasible schedule and options with their risks, not promise to compress every activity into an arbitrary emergency purchase.
Work with the project manager to distinguish essential go-live scope from optional later enhancements, verify any phased procurement authority, and plan service continuity. Keep competition, funding, technical readiness, and stakeholder decisions visible. The strongest applied answer addresses the actual dependency and authorized response, rather than choosing the most forceful-sounding instruction to the supplier.