Release procedures
Release of long-range acquisition estimates must be carefully managed to support industry planning while safeguarding security, fairness, and non-binding government interests.
Overview
FAR 5.404-1 outlines the procedures agencies must follow when releasing long-range acquisition estimates to the public. The regulation is designed to help industry plan for future government needs while ensuring that the release of information does not lead to market manipulation, security breaches, or premature disclosure of sensitive acquisition details. The agency head or designee is responsible for determining when such information can be released and must ensure that all releases comply with security, transparency, and fairness requirements.
Key Rules
- Application of Release
- Long-range acquisition estimates may be released if they assist industry planning, do not encourage undesirable practices, and do not signal industry-wide mobilization.
- Conditions for Release
- Classified information must be handled through proper security channels. Releases must be publicized widely and simultaneously, include disclaimers about the non-binding nature of the estimates, and provide contracting officer contact information. Any modifications must be promptly publicized. Coordination with small business and public relations personnel is required, and releases should include relevant acquisition details and potential small business set-aside statements.
Responsibilities
- Contracting Officers: Ensure all releases meet the outlined conditions, coordinate with relevant personnel, and provide accurate, non-binding information.
- Contractors: Use released estimates for planning but recognize they are subject to change and not binding.
- Agencies: Oversee the release process, ensure compliance with security and public information requirements, and update releases as necessary.
Practical Implications
This section exists to balance transparency with market fairness and security. It enables industry to prepare for future government needs without giving any party an unfair advantage or compromising sensitive information. Common pitfalls include failing to coordinate releases, not updating modifications promptly, or inadvertently disclosing sensitive or binding information.