A contract period of performance defines when the contractor may perform specified work. Therefore, the period of performance schedule establishes key time boundaries that the Integrated Master Schedule (IMS) must recognize. It affects the schedule start, contractual completion milestones, Contract Line Item Number (CLIN) windows, deliverable dates, option periods and the treatment of work forecast beyond an authorized date.
However, the contract period of performance does not replace detailed schedule logic. The IMS must still show how the authorized scope will reach each contractual delivery or completion date. If the network forecasts a later finish, the scheduler should show that result rather than force the schedule to appear compliant.
What the Contract Period of Performance Controls
The period of performance, often shortened to PoP, identifies the time allowed for contract performance. Depending on the contract, it may appear as specific calendar dates or as a duration measured from award, the effective date, receipt of award, notice to proceed or issuance of an order.
Federal Acquisition Regulation Subpart 11.4 states that delivery or performance time is an essential contract element. It also permits performance schedules based on calendar dates or defined periods from a specified triggering event.
For IMS development, the trigger matters as much as the duration. A requirement to complete work 24 months after award creates a different schedule boundary from 24 months after notice to proceed. The scheduler should identify the governing event and preserve the assumption in the schedule basis documentation.
In addition, one contract can contain several relevant time boundaries:
- The overall contract start and completion dates
- Separate periods of performance for individual CLINs or subline items
- Required delivery dates for hardware, software or services
- Contract Data Requirements List (CDRL) submission dates
- Interim technical milestones and reviews
- Option periods that the Government has not yet exercised
- Dates established or changed by contract modifications
Do not assume that one header-level PoP tells the whole story. Under FAR 4.1005-1, each deliverable line item or deliverable subline item must have its delivery schedule, destination, period of performance or place of performance expressly stated in the procurement instrument. As a result, the scheduler should review the contract at the CLIN and subline-item level.
How to Build the Period of Performance Schedule Into the IMS
Establish the correct start event
First, identify the event that authorizes or starts performance. Possible events include contract award, the contract effective date, receipt of award, notice to proceed or task-order issuance. These terms are not interchangeable.
Represent the applicable event as a zero-duration milestone when that approach supports traceability. Then connect the authorized work with valid logic. Avoid entering a convenient project start date that does not match the governing contract language.
Represent each binding completion date
Next, create clearly named milestones for contractual delivery and completion dates. Good milestone names identify the deliverable, CLIN and contractual basis. For example, CLIN 0002 Prototype Units Delivered communicates more than Contract Complete.
The IMS should also include relevant CDRL submissions and acceptance events when they affect downstream work or contract completion. See how contract deliverables should appear in an IMS for a focused treatment of CDRL logic and milestones.
A milestone does not become contractual merely because it appears in the IMS. Conversely, a contractual date should not disappear because the team manages to a different internal target. Use coding or custom fields to distinguish contract milestones, customer commitments and internal management dates.
Connect scope to the applicable CLIN window
A broad summary bar labeled with the contract PoP provides useful visibility, but it does not prove that the plan complies with the contract. The detailed network should connect the work to the applicable CLIN, Work Breakdown Structure (WBS) element, deliverable and completion milestone.
This traceability becomes especially important when CLINs overlap or end at different times. The relationship between scope and contractual structure is discussed further in What Is a CLIN in Government Contracting? and How the WBS Connects to the Statement of Work.
Let the network calculate the forecast
The contractual date is an obligation or target established outside the scheduling engine. The forecast date is the result of current logic, durations, status and calendars. Those dates may differ.
If the forecast exceeds the contract date, preserve the contractual milestone and show the variance. Do not shorten remaining durations without technical support, delete logic or add artificial constraints simply to eliminate the problem. A credible IMS should warn management when the current plan no longer supports the commitment.
Depending on the scheduling tool and approved procedures, teams may model the contractual target with a deadline, constraint, target field or separate comparison milestone. The modeling convention is a scheduling practice unless the contract or applicable data requirement specifies it. Microsoft Project users may find deadlines useful for monitoring dates without unnecessarily restricting the network.
The PoP End Date Is Not Always the Only Contract Finish
A common mistake is to create one contract completion milestone and connect every activity to it. That approach can hide separate delivery obligations and produce misleading float.
For example, hardware delivery may occur before the end of engineering support. A final report may have another date. Acceptance testing may also occur after physical delivery. The IMS should preserve those distinctions when the contract does.
Likewise, administrative closeout is not automatically part of the contractor’s authorized technical performance. Before scheduling work after the apparent PoP end, determine whether the contract requires that work, whether another CLIN covers it, or whether it represents an internal closeout activity. Label internal activities so reviewers do not mistake them for authorized contract scope.
Using a zero-duration overall PoP-end milestone is often helpful. However, it is a management convention, not a universal FAR requirement for every IMS.
How Unexercised Options Should Appear
An option period can affect long-range planning, staffing and supplier commitments. However, an unexercised option is not the same as currently authorized work. The clause at FAR 52.217-9, when included in a contract, states that a preliminary notice of intent does not commit the Government to an extension.
Whether unexercised option work must appear in a delivered IMS depends on the contract, CDRL, applicable data item description, customer direction and the contractor’s approved procedures. When included for visibility, option work should be clearly coded and separated from the current authorized baseline.
Do not present unexercised option scope as though it were funded and authorized. Also, do not load it into the Performance Measurement Baseline (PMB) without a valid authorization and the required change-control treatment. A planning model or separate schedule scenario may provide better visibility until the option is exercised.
Effect on Earned Value and Baseline Control
The IMS supports time-phasing of the PMB when Earned Value Management (EVM) applies. Therefore, a PoP change may affect work packages, planning packages, control account plans, resource forecasts and time-phased budgets. It can also change the Estimate to Complete (ETC) and Estimate at Completion (EAC).
However, a forecast slip does not automatically authorize a baseline change or revise the contract. The current schedule should show the forecast based on actual conditions while preserving the approved baseline for variance measurement.
If the contracting officer issues a modification that changes a delivery or completion date, the program should evaluate the full logic and cost impact. The baseline should then be updated through the contractor’s approved change-control process when appropriate. FAR Part 43 explains that contract modifications may be bilateral or unilateral depending on their purpose and authority.
Keep the contract modification, schedule change record, baseline change authorization and before-and-after schedule evidence aligned. For related guidance, see how schedule changes affect the PMB and how to maintain baseline traceability.
Fictional Example: A PoP That Contains Several Finish Dates
Assume a fictional sensor-modernization contract has a base PoP from January 6, 2027, through January 5, 2030. The contract contains the following requirements:
- CLIN 0001 design effort through a Critical Design Review on October 15, 2027
- CLIN 0002 prototype delivery by June 30, 2028
- CLIN 0003 test support through September 30, 2029
- A final technical report due January 5, 2030
- An optional sustainment period from January 6, 2030, through January 5, 2031
The scheduler creates separate contract milestones for the review, prototype delivery, end of test support and final report. Detailed engineering, procurement, integration and verification activities drive the prototype milestone. Meanwhile, test-support activities continue under CLIN 0003 after delivery.
During execution, late Government-furnished test equipment pushes the forecast prototype delivery into August 2028. The scheduler should show that forecast and trace the driving path through equipment availability, integration and verification. The June 30 contractual milestone remains visible so management can see the predicted miss.
The program should not move the contractual date simply because the forecast changed. If the contracting officer later modifies the delivery date, the team updates the current contract milestone and evaluates the associated baseline change. The scheduling team should also retain the prior date and modification reference for traceability. For more on this type of dependency, see Government Furnished Equipment and Schedule Risk.
Common Period-of-Performance Scheduling Mistakes
- Using only the header-level PoP. The team overlooks CLIN-specific delivery dates and performance windows.
- Confusing award with authorization to start. The IMS begins work before the governing notice or effective date.
- Hard-coding a compliant finish. Constraints prevent the schedule from revealing the true forecast.
- Moving baseline dates when forecasts slip. The program erases variance without approved change control.
- Treating an option as authorized scope. Unexercised work appears in the active baseline without a contractual basis.
- Scheduling unexplained work after PoP end. Reviewers cannot determine whether the work is contractual, proposed or administrative.
- Using one generic completion milestone. Separate delivery, acceptance, support and reporting obligations lose visibility.
- Ignoring Government dependencies. Government-furnished property, approvals and facilities remain outside the logic even though they drive completion.
Practical Review Questions for the Scheduler
- What exact event starts each applicable period of performance?
- Does every deliverable CLIN or subline item have a traceable schedule milestone?
- Are required CDRL dates represented where they affect execution?
- Does the logic-driven forecast support each contractual date?
- Can reviewers distinguish baseline, forecast and current contract dates?
- Are unexercised options clearly separated from authorized work?
- Does every activity after the stated PoP end have a valid basis?
- Have contract modifications been incorporated through controlled procedures?
- Do the IMS, PMB, ETC and EAC reflect the same authorized plan?
A reliable schedule should model the complete authorized scope and expose whether the current plan can meet approved commitments. The GAO Schedule Assessment Guide describes an integrated schedule as a model that shows when major events and their supporting activities should finish. That principle is central to PoP management: the IMS must calculate the answer rather than merely display the desired date.
Frequently Asked Questions
Can an IMS contain activities after the contract period of performance?
Yes, but each activity needs a clear basis. It may represent another CLIN, a required post-delivery action, authorized option work or an internal administrative activity. Do not portray unauthorized technical effort as current contract scope.
Does a late IMS forecast change the contract completion date?
No. A forecast identifies the expected result of the current plan. A contract date changes only through an authorized contractual action or another mechanism permitted by the contract.
Should the PoP end date be a milestone?
Usually, a clearly identified zero-duration milestone improves visibility and traceability. However, that modeling choice is a recommended scheduling practice unless the contract, CDRL or governing procedure requires it.
Should unexercised option periods be baselined?
Generally, teams should not treat unexercised options as authorized PMB scope. The contract, reporting requirement and approved EVMS procedures determine the exact treatment. Option work may still appear in a clearly separated planning scenario when useful.