Government Furnished Equipment and Schedule Risk

GFE schedule risk is the risk that Government-Furnished Equipment will arrive late, incomplete, damaged, unsuitable, improperly configured, or otherwise unavailable when the program needs it. A delayed GFE item can hold up installation, integration, test, production, training, or delivery even when the contractor’s preceding work remains on plan.

The Integrated Master Schedule (IMS) should therefore show each significant GFE dependency, the date the contract says the Government will provide it, the contractor’s actual need date, and the work required to make the item ready for use. However, the specific contractual obligation depends on the contract, applicable clauses, Government-Furnished Property attachment, and any tailored reporting requirements. A scheduling convention alone does not create a contractual delivery commitment.

GFE Is a Schedule Interface, Not Just a Property Record

Government-Furnished Equipment is commonly discussed as a subset of Government-Furnished Property (GFP). The Federal Acquisition Regulation Part 45 defines GFP broadly as property in the Government’s possession, or acquired directly by the Government, and later furnished to a contractor for contract performance. Government property can include equipment, material, special tooling, special test equipment, and real property.

The terminology in the contract controls. Some programs use GFE as an operational term, while the governing clauses and attachments use GFP. Schedulers should understand both terms and avoid assuming that every Government interface qualifies as property. Government-Furnished Information, test facilities, ranges, approvals, and Government personnel can create similar schedule dependencies, but they may fall under different contract provisions.

From a scheduling perspective, the key question is not simply whether the property appears in an accountability system. Instead, ask when the item must become available and suitable for the next planned activity. That date may occur well before the contractual delivery date for the end item.

What the Contract May Require

The contract establishes the parties’ obligations. The IMS then models how those obligations affect execution.

FAR 52.245-1, Government Property, states that contract delivery and performance dates are based on the expectation that described Government-furnished property will be suitable and delivered by the dates stated in the contract. If the property arrives late, the Contracting Officer must consider an equitable adjustment after a timely written contractor request. The clause also addresses unsuitable property, substitutions, quantity changes, and withdrawal of authority to use property.

That language does not guarantee automatic schedule relief. The contractor must follow the clause, document the facts, submit communications in writing, and support the effect on contract performance. In addition, property furnished in an as-is condition carries different suitability provisions.

For Department of Defense acquisitions, DFARS 245.103-72 requires contracting officers to include a GFP attachment in solicitations and awards when performance requires GFP. The attachment identifies the authorized property, but the complete contract must be reviewed to determine applicable dates, conditions, responsibilities, and remedies.

During acquisition planning, FAR 7.105 calls for acquisition plans to identify Government property and discuss considerations such as its availability or acquisition schedule. This reinforces a practical point: GFE availability should be addressed before award, not discovered after the execution schedule has been baselined.

How to Model GFE Schedule Risk in the IMS

A single milestone labeled “Receive GFE” rarely provides enough information. It can hide the distinction between shipment, physical receipt, inspection, discrepancy resolution, configuration, and readiness for use.

For each schedule-significant item, consider a chain such as:

1. Government release or planned ship date, if credible forecast data exist.
2. Contractual GFE delivery milestone.
3. Contractor receipt and property processing.
4. Inspection for quantity, condition, and configuration.
5. Resolution of shortages, damage, or technical discrepancies.
6. Installation, calibration, software loading, or site preparation.
7. Functional checkout or acceptance.
8. GFE ready-for-use milestone.
9. Successor integration, test, production, or training work.

Not every item needs this level of detail. Use it when the item can drive a contractual milestone, major technical event, critical path, near-critical path, or high-value work package. The broader goal is a credible, logically connected schedule, as discussed in the DoD Integrated Master Schedule guide.

Separate the Contract Date, Forecast Date, and Need Date

These three dates answer different questions:

• Contract date: When the contract states that the Government will furnish the item.
• Current forecast date: When the program now expects the item to arrive.
• Need date: The latest date the contractor can receive the item without affecting its planned work.

If the IMS shows only the current forecast, the team may lose visibility into the original obligation. If it shows only the contract date, it may ignore an emerging delay. In addition, receipt may not equal readiness. The need date should account for inspection, installation, configuration, and checkout.

Where Integrated Program Management Data and Analysis Report requirements apply, the applicable contract and Data Item Description determine the required schedule content. The IPMDAR Implementation Guide describes an integrated schedule containing significant external interfaces and GFE, information, or property dependencies, including required and projected delivery dates. Teams should confirm the contract’s exact reporting requirements rather than treating implementation guidance as a universal mandate.

Use Logic Instead of Artificial Constraints

Connect the GFE ready-for-use milestone to the work that consumes the equipment. This allows the schedule network to calculate the effect of a forecast change.

Avoid forcing the consuming activity to a fixed date with an unnecessary hard constraint. A constraint may conceal the dependency, generate misleading float, or prevent the schedule from forecasting a slip correctly. The distinction between legitimate contract constraints and artificial date controls is covered in hard constraints versus soft constraints.

Also avoid using a long lag to represent inspection or installation. Those are real activities with owners, durations, status, and completion criteria. Model them as work rather than hiding them inside relationship logic.

Assign Ownership Without Taking Credit for Government Work

Identify Government-controlled milestones as external interfaces. The contractor may forecast them based on customer information, but it should not report unsupported actual progress for Government work.

Meanwhile, contractor receipt, inspection, installation, and checkout activities can have assigned responsibility and measurable completion criteria. A Government delivery milestone normally carries no contractor budget. However, the contractor’s processing and integration work may belong in budgeted work packages when it forms part of the authorized scope.

Assess More Than the Chance of Late Delivery

A GFE risk assessment should address both probability and consequence. The item may arrive on time but still fail to support the planned work.

Common risk conditions include:

• The supplying program has an immature design or unstable production schedule.
• The item depends on another contract, depot, laboratory, or Government organization.
• The delivery date leaves little time for inspection and checkout.
• Required cables, adapters, software, drawings, licenses, or security material are missing.
• The equipment configuration does not match the contractor’s integration baseline.
• Transportation, site access, handling, storage, or security restrictions are unresolved.
• Only one unit is available, creating competition between development, test, and training users.
• The item will be furnished as-is or has an uncertain service condition.

First, trace the path from the GFE interface to the next major milestone. Then determine its total float and whether related work sits on a near-critical path. A dependency with positive float can still present material risk if the forecast uncertainty exceeds the available float. See critical path analysis in an IMS for the broader tracing method.

For a Schedule Risk Analysis, model uncertainty around the realistic delivery or readiness forecast. Also consider conditional risk, such as a chance that inspection finds damage and triggers repair or replacement work. Do not add hidden padding or arbitrary lags. Instead, document the uncertainty assumptions and any explicit contingency allowed by the program’s scheduling procedures.

Address GFE During Proposal Development

Proposal teams should identify GFE dependencies before building a fully constrained execution plan. Otherwise, an aggressive schedule may rely on equipment that the Government cannot provide by the assumed date.

For each schedule-significant item, the proposal team should reconcile:

• The solicitation and draft GFP attachment.
• The Statement of Work and technical requirements.
• The proposed contract delivery schedule.
• The basis of estimate for integration and test work.
• The supplier or Government source schedule.
• The contractor’s required-on-site and ready-for-use dates.
• Any proposal assumptions, exceptions, or requested clarifications.

This review is especially important when the Government plans to transfer property from another contract. The supplying contract may have different priorities, acceptance criteria, or delivery risks. The proposal IMS should show the interface clearly enough for evaluators to understand what happens if the assumption changes.

Manage GFE Delays During Execution

Once execution begins, status the schedule to the actual condition. Do not mark the GFE milestone complete because the item shipped, received a tracking number, or reached the facility gate if the milestone’s completion criteria require usable equipment.

When a delay emerges, the scheduler and program-controls team should:

1. Record the latest credible forecast and its source.
2. Confirm the contractual delivery date and contractor need date.
3. Update remaining durations for receipt, inspection, and readiness work.
4. Run the network calculation and trace affected paths.
5. Identify available float and forecasted milestone effects.
6. Evaluate resequencing, alternate equipment, emulators, partial deliveries, or split testing.
7. Coordinate written notice and impact documentation with contracts personnel.
8. Update the risk register, estimate to complete, and management forecast as appropriate.

The current schedule should forecast the expected outcome. However, the performance measurement baseline should not move merely because GFE is late. Baseline changes require authorization and must follow the contract and the contractor’s approved change-control process. For additional context, see how schedule changes affect the Performance Measurement Baseline and how to maintain baseline traceability.

Fictional Example: Late Test Equipment

Assume the fictional Falcon Ridge radar program requires a Government-furnished signal generator for system integration. The contract identifies May 15 as the delivery date. The contractor needs the equipment ready for use by June 3.

The IMS contains two days for receipt and inspection, three days for software and security configuration, and five days for calibration and checkout. Therefore, the scheduled ready-for-use date is May 29, leaving three working days of float before integration begins.

In April, the Government source forecasts delivery on June 2. After the contractor updates the external milestone, the ready-for-use date moves to June 12 and integration slips. The team also identifies a risk that an incompatible connector could add four days of rework.

Rather than holding the original integration date with a hard constraint, the scheduler allows the network to show the effect. The program team then evaluates three mitigations: perform preliminary integration with an emulator, obtain configuration data before shipment, and split testing so unaffected functions can begin first.

The contracts team separately reviews notice requirements and potential entitlement. The schedule analysis supports that review, but it does not determine contractual entitlement by itself.

Common GFE Scheduling Failures

• Using one milestone for the entire process. Physical receipt does not prove that the item is complete, suitable, configured, or ready.
• Confusing a forecast with a contract commitment. Preserve both dates and identify their source.
• Leaving GFE milestones without successors. An unconnected milestone cannot forecast downstream effects.
• Hiding work in lags. Inspection, installation, and checkout need visible activities when they are schedule-significant.
• Waiting until the item is late to assess risk. Review source maturity and float during proposal development and baseline planning.
• Automatically rebaselining after a delay. Update the forecast first. Change the baseline only through authorized change control.
• Assuming schedule relief is automatic. Contract clauses, facts, timely notice, causation, and documented impact govern the contractual process.
• Tracking equipment without associated data. Drawings, software, licenses, test procedures, and configuration records may be just as critical as the hardware.

Practical GFE Schedule Review Questions

• Does the contract identify the item and its delivery conditions?
• Are the contract date, current forecast, and contractor need date distinguishable?
• Does the schedule include the work between receipt and readiness?
• Is the GFE interface logically connected to all consuming activities?
• Does the forecast reflect the latest credible Government information?
• Could configuration, condition, quantity, data, or access problems delay use?
• Does available float cover realistic delivery and readiness uncertainty?
• Are risk mitigations represented as executable work rather than narrative only?
• Can the team trace forecast changes without losing the baseline obligation?
• Have contracts, property, engineering, logistics, and program controls reviewed the same assumptions?

Frequently Asked Questions

Should every GFE item appear in the IMS?

No. Include items that create a meaningful schedule interface or can affect contract performance. Routine property that does not drive planned work may remain in the property management system without detailed IMS representation.

Is a late GFE delivery automatically an excusable delay?

No automatic conclusion should be drawn from the schedule alone. Review the contract, applicable clauses, stated delivery dates, timely written communications, causation, available mitigation, and documented effect on performance.

Should the IMS use the contractual date or the current forecast?

Preserve both when they differ. The contractual date maintains traceability to the obligation, while the current forecast supports realistic schedule analysis. The contractor need date provides the third reference needed to understand available float and potential impact.

Effective GFE management connects contract language, property data, technical readiness, risk analysis, and schedule logic. When those elements remain aligned, the IMS becomes more than a list of Government dates. It becomes a practical tool for forecasting consequences, evaluating mitigation, and supporting fact-based program decisions.