Scope Evaluation and Gap Analysis

Introduction
Scope Evaluation and Gap Analysis is a core competency within the Scope and Change Order Management domain of the PMI Construction Professional (PMI-CP) certification. In construction, scope is defined across many sources: contracts, drawings, specifications, bills of quantities, permits, owner requirements and site conditions. When these sources are incomplete, inconsistent or misaligned, the result is disputes, change orders, cost overruns and delays. Scope evaluation and gap analysis is the disciplined process of finding those weaknesses before they become problems.

Why Scope Evaluation and Gap Analysis Is Important
1. It prevents costly change orders. Most construction change orders come from scope gaps, ambiguities, omissions or design errors. Finding them early, during bidding, contract award or pre-construction, is far cheaper than fixing them in the field.
2. It protects the contractual position. Contractors and owners both need a clear baseline. Without it, entitlement to extra time or money cannot be proven.
3. It supports accurate estimating and scheduling. Missing scope means missing cost and missing activities. Gap analysis makes the Work Breakdown Structure (WBS), estimate and schedule complete.
4. It reduces disputes and claims. Construction involves many parties: owner, designer, general contractor, subcontractors and suppliers. Scope overlaps and gaps between trade packages are a leading cause of conflict.
5. It aligns stakeholder expectations. It confirms that what the owner expects, what the designer drew and what the contractor priced are the same thing.
6. It enables risk management. Identified gaps feed directly into the risk register as threats, assumptions or contingencies.
7. It supports regulatory and quality compliance. Scope must reflect codes, permits, environmental requirements and quality standards.

What Is Scope Evaluation?
Scope evaluation is the systematic review of all documents and information that define the project's work. The goal is to confirm that the scope is complete, clear, consistent, constructible and contractually sound. It answers questions such as:
- What exactly are we being asked to deliver?
- Are the requirements measurable and verifiable?
- Do the drawings, specifications and contract agree with each other?
- Are inclusions, exclusions, assumptions and constraints clearly stated?
- Who is responsible for each element of work?

What Is Gap Analysis?
Gap analysis compares the current state (what is defined, designed, contracted or planned) with the required or desired state (what the project actually needs to deliver the intended outcome). The difference is the gap. In construction, gaps commonly include:
- Scope gaps: work no party is contractually responsible for, such as temporary power, final cleaning, firestopping at trade interfaces, or testing and commissioning.
- Scope overlaps: work included in more than one trade package, causing double pricing or conflict.
- Design gaps: incomplete drawings or missing details, such as connections not detailed.
- Specification conflicts: drawings say one thing and specifications say another.
- Requirement gaps: owner needs not translated into design, such as operational, maintenance or sustainability requirements.
- Regulatory gaps: permit or code requirements not reflected in the scope.
- Interface gaps: unclear boundaries between contractors, utilities or phases.
- Capability gaps: the team lacks the resources, skills or equipment to perform the defined scope.

How Scope Evaluation and Gap Analysis Works: Step by Step
Step 1: Gather the scope baseline documents.
Collect the contract and general/special conditions, drawings, specifications, scope statement, WBS and WBS dictionary, bid documents, addenda, RFIs, geotechnical reports, permits, owner project requirements (OPR), basis of design (BOD) and stakeholder requirements.

Step 2: Understand the order of precedence.
Contracts usually define which document governs when conflicts exist, for example: agreement, then special conditions, then general conditions, then specifications, then drawings. Knowing this is essential for resolving gaps.

Step 3: Perform a structured document review.
Use techniques such as:
- Constructability reviews: can it actually be built as designed?
- Cross-discipline coordination reviews: architectural versus structural versus MEP.
- BIM clash detection: 3D model coordination to identify physical conflicts.
- Checklists: standard lists of commonly missed items.
- Requirements traceability matrix (RTM): traces each requirement to its design element, deliverable and acceptance criteria.

Step 4: Compare current state to required state.
Map each owner requirement and contractual obligation against the design, the WBS and the trade packages. Use a scope matrix or responsibility matrix, such as RACI or a trade responsibility matrix, to confirm that every element has exactly one owner.

Step 5: Identify and categorize gaps.
Classify each finding as an omission, ambiguity, conflict, overlap or error. Assess its impact on cost, schedule, quality, safety and risk.

Step 6: Determine root cause and responsibility.
Is the gap a design error (designer or owner risk), a contractor omission (contractor risk), a changed condition, or an owner-directed change? This determines entitlement.

Step 7: Resolve the gaps through proper channels.
- Before contract award: issue RFIs, request addenda, clarify with qualifications, exclusions and assumptions in bids, or hold pre-bid meetings.
- After award: submit RFIs, issue notices per contract requirements, prepare change requests and change orders, or use construction change directives where needed.
- Internally: update the WBS, estimate, schedule, risk register and subcontract scopes.

Step 8: Document and communicate.
Record findings in a gap log or issues log, update the scope baseline through integrated change control, and inform the relevant stakeholders.

Step 9: Monitor continuously.
Gap analysis is not a one-time event. Repeat it at each design stage (schematic, design development, construction documents), at procurement, at subcontract award, and when changes occur.

Key Tools and Techniques
- Scope statement and WBS / WBS dictionary
- Requirements traceability matrix
- Scope of work matrix / trade responsibility matrix
- RACI chart
- Constructability and value engineering reviews
- BIM and clash detection
- Expert judgment and lessons learned
- Bid leveling, which compares subcontractor bids line by line to expose scope gaps and exclusions
- RFI process and change management procedures
- Site investigations and existing condition surveys

Common Construction Examples
- The electrical subcontract excludes trenching and the civil subcontract excludes trenching for electrical conduits, so no one carries it. This is a scope gap.
- Both the mechanical and controls subcontractors priced control wiring. This is a scope overlap.
- The specification calls for a Class A fire rating but the drawings show a material that is not rated. This is a conflict.
- The owner requires LEED certification but the specifications contain no commissioning or documentation requirements. This is a requirement gap.

Relationship to Other PMI Concepts
- Collect Requirements, Define Scope, Create WBS: gap analysis validates these outputs.
- Validate Scope and Control Scope: gap analysis supports detecting scope creep and deviations.
- Perform Integrated Change Control: resolved gaps that alter the baseline must go through formal change control.
- Risk Management: unresolved gaps become risks or assumptions.
- Procurement Management: gap analysis ensures subcontract packages are complete and non-overlapping.

Exam Tips: Answering Questions on Scope Evaluation and Gap Analysis
1. Favor proactive, early action. PMI rewards identifying problems early. If a question asks what the project manager should do before bidding, award or construction, choose reviewing documents, performing constructability reviews, or issuing RFIs. Avoid answers that wait until work is underway.

2. Review and analyze before acting. When a gap or discrepancy is discovered, the best first step is usually to evaluate it: review the contract, check the order of precedence, and assess impact. Do not jump straight to issuing a change order, stopping work, or escalating to the sponsor.

3. Refer to the contract. In construction questions, the contract is the governing document. Answers that say "review the contract terms" or "follow the contractual notice and change procedure" are frequently correct.

4. Never implement unapproved changes. If a gap means extra work, the correct path is to document it and submit a change request through integrated change control. Doing the work first and asking later is almost always wrong, unless there is an immediate safety emergency.

5. Use the RFI for ambiguity, and change requests for scope changes. An RFI clarifies design intent or resolves ambiguities. A change request or change order alters scope, cost or time. Know the difference.

6. Recognize scope gaps between trade packages. Questions often describe work that falls between subcontractors. The best answer usually involves a scope or responsibility matrix, bid leveling, or clarifying scope before subcontract award.

7. Respect the order of precedence. If drawings and specifications conflict, the answer may involve applying the contract's order of precedence clause, then confirming with the designer through an RFI.

8. Link gaps to risk. Unresolved gaps, assumptions and exclusions should be logged in the risk register and the assumption log. Answers that integrate gap findings into risk management are strong.

9. Engage stakeholders collaboratively. PMI favors collaboration over confrontation. Choose answers that involve meeting with the owner, designer or subcontractors to clarify scope, rather than blaming parties or filing claims immediately.

10. Update the baselines. After a gap is resolved through an approved change, update the scope statement, WBS, schedule, cost baseline and related documents.

11. Watch for keywords.
- "Discrepancy," "conflict," "unclear" point to review, then RFI.
- "Missing work," "not included" point to gap analysis, then change request if it is outside the baseline.
- "Before award" points to clarification, addenda, bid leveling, and qualifications.
- "Owner wants additional features" points to a change request and impact analysis.
- "Subcontractor claims work is not in their scope" points to reviewing the subcontract, scope matrix and contract documents.

12. Eliminate extreme answers. Options such as terminating the contract, ignoring the issue, absorbing the cost without analysis, or proceeding without documentation are rarely correct.

13. Think about the contract type. Under lump sum or fixed price contracts, the contractor carries more scope risk, so thorough pre-bid gap analysis is critical. Under cost-reimbursable or GMP contracts, scope clarity still affects the allowances, contingency and owner's exposure.

Sample Exam-Style Question
During pre-construction, the project manager notices that neither the earthwork nor the utility subcontract includes backfilling of utility trenches. What should the project manager do FIRST?
A. Issue a change order to the owner for the additional work
B. Direct the earthwork subcontractor to perform the work
C. Review the contract documents and the scope responsibility matrix to confirm the gap and determine responsibility
D. Add the cost to the project contingency
Correct answer: C. Evaluate first, confirm the gap, determine responsibility, then take the appropriate contractual action.

Summary
Scope evaluation and gap analysis ensure that the construction scope is complete, consistent and clearly assigned. The process involves collecting scope documents, reviewing them systematically, comparing requirements to what has been defined, identifying and categorizing gaps, and resolving them through RFIs, clarifications and formal change control. For the PMI-CP exam, remember: identify early, analyze before acting, follow the contract, use formal change control, collaborate with stakeholders, and update baselines and risk records.