FAR 50.205-4—Authorization of awards made presuming SAFETY Act designation or certification after contract award.
Plain-English Summary
FAR 50.205-4 explains when a contracting officer may move forward with an award before the Department of Homeland Security (DHS) has actually issued SAFETY Act protections, by treating the award as if a designation or certification will be granted after award. It covers the limited conditions for making that kind of presumption, including the need to satisfy the underlying criteria in FAR 50.205-3(a), obtain approval from the chief of the contracting office or another agency-designated official, and coordinate timing with DHS so the agency can reasonably complete its review of offerors’ applications. The section also draws an important distinction between presuming a SAFETY Act designation and presuming a SAFETY Act certification, and it generally prohibits the latter unless a block certification applies to the technology class being acquired. In practice, this provision is about balancing mission urgency and acquisition schedule needs against the risk of awarding before DHS protections are in place. It gives agencies a controlled path to proceed when waiting for DHS would delay the procurement, while still requiring senior approval and DHS consultation to avoid unrealistic award assumptions.
Key Rules
Award before DHS action
A contracting officer may award a contract before DHS issues SAFETY Act protections only in limited circumstances. The award may be made on the assumption that DHS will later issue the needed designation or certification after contract award.
Underlying criteria must be met
The action is allowed only if the criteria in FAR 50.205-3(a) are satisfied. That means the procurement must already qualify for this special treatment under the earlier rule, not merely be time-sensitive.
Senior approval required
The chief of the contracting office, or another official specifically designated by agency procedures, must approve the decision. This adds an internal control to ensure the presumption is used only when justified.
Coordinate with DHS timing
The contracting officer must notify DHS of the expected award timeline and consult with DHS on how long it would reasonably take to evaluate offerors’ SAFETY Act applications. This is intended to align the acquisition schedule with DHS review capacity.
Designation versus certification
A contracting officer may not presume that SAFETY Act certification will be obtained unless a block certification applies to the class of technology being acquired. The rule is more restrictive for certification than for designation.
Block certification exception
If a block certification applies to the technology class in the solicitation, the prohibition on presuming certification does not apply. In that case, the acquisition may proceed under the broader class-based certification framework.
Responsibilities
Contracting Officer
Determine whether the procurement qualifies under FAR 50.205-3(a), coordinate with DHS on award timing and review timelines, and ensure the solicitation or award approach does not improperly presume certification unless a block certification applies.
Chief of the Contracting Office / Designated Agency Official
Review and approve the decision to award before DHS has issued SAFETY Act protections, providing oversight and accountability for the exception.
DHS
Advise the contracting officer on the likely time needed to evaluate SAFETY Act applications and, ultimately, review and decide whether to issue the designation or certification after award.
Offerors / Contractors
Submit SAFETY Act applications as needed and understand that an award made under this provision depends on DHS later issuing the applicable protection; they should not assume certification will be treated as available unless the solicitation falls within a block certification.
Agency Acquisition Officials
Establish procedures identifying who may approve these awards and ensure contracting staff understand the distinction between designation and certification and the limits on presuming each.
Practical Implications
This rule is mainly a schedule-management tool: it lets agencies award sooner when waiting for DHS would jeopardize mission needs, but only with extra controls.
A common pitfall is treating designation and certification as interchangeable; the rule is stricter for certification and generally forbids presuming it unless a block certification exists.
Another risk is failing to consult DHS early enough, which can lead to unrealistic award dates and a mismatch between contract performance start and DHS review time.
Contracting officers should document the basis for the presumption, the approval obtained, and the DHS coordination to protect the file and support the decision.
Contractors should pay close attention to whether the solicitation is relying on a designation, a certification, or a block certification, because that affects both proposal strategy and post-award expectations.
Official Regulatory Text
(a) When necessary to award a contract prior to DHS issuing SAFETY Act protections, contracting officers may award contracts presuming that DHS will issue a SAFETY Act designation/certification to the contractor after contract award only if- (1) The criteria of 50.205-3 (a) are met; (2) The chief of the contracting office (or other official designated in agency procedures) approves the action; and (3) The contracting officer advises DHS of the timelines for potential award and consults DHS as to when DHS could reasonably complete evaluations of offerors’ applications for SAFETY Act designations or certifications. (b) Contracting officers shall not authorize offers presuming that SAFETY Act certification will be obtained (as opposed to a SAFETY Act designation), unless a block certification applies to the class of technology to be acquired under the solicitation.