When exactly are you allowed to say you won?
That question has three answers, they are governed by three different rulebooks, and getting any one of them wrong turns a good-news announcement into a problem for your customer, your general counsel, or both. Most guidance on writing a contract award press release skips straight to the template. The template is the easy part. The timing is what separates a communications team that gets invited back into the loop from one that gets routed around.
Wait for the Government to Announce First
On a federal award, the government announces before you do, and this is not etiquette. It is a rule binding the contracting officer you are working with.
FAR 5.303 requires contracting officers to make information available on awards over $5.5 million in sufficient time for the agency to announce it by 5 p.m. Washington time on the day of award, and states that agencies “shall not release information on awards before the public release time of 5 p.m. Washington, DC time.” If you put out a release at 10 a.m., you have handed your customer’s public affairs office a problem on a day they were going to give you a free headline.
Note the figure. The threshold is $5.5 million in the current FAR. The widely repeated “$7.5 million FAR threshold” is a stale citation, and it gets copied between PR blogs constantly.
Defense adds its own layer. DFARS 205.303 sets the Defense reporting threshold at $9 million and requires contractual actions above it, including modifications, to be reported to the Office of the Assistant to the Secretary of Defense for Public Affairs by close of business the day before the proposed award, under a specific report control symbol. Members of Congress for the affected state or district receive similar information concurrent with the public announcement, which means your client’s local congressional office may well comment before your release lands.
The public-facing daily list, which posts each business day at 5 p.m., is reported to carry awards valued at $7.5 million or more. We could not load that page directly to quote it, so treat the threshold as reported rather than verified. What is verified is the DFARS figure, and the two do not match. The safe reading: $9 million is the reporting threshold the regulation imposes on agencies, and the public list appears to publish from a lower one. Either way, the operative time for your release is after 5 p.m. Eastern on award day.
The rule carries exclusions that occasionally work in your favour. FAR 5.303 does not apply to Small Business Administration 8(a) awards, to awards to foreign firms where delivery and performance happen outside the United States and its outlying areas, or to awards whose synopsis was exempted. Agencies may also release award information to local press and media, and above the simplified acquisition threshold those local announcements must state the method of competition used. If your client’s win falls into one of those categories, or if the agency’s own public affairs team is planning a local push, the sequencing conversation is worth having directly with the contracting officer rather than guessing from the regulation.
Count the Protest Window Before You Celebrate
The second clock is the one that wrecks announcements, and it is the reason experienced government contracting communications teams look unenthusiastic on award day.
Under FAR 33.104, when the agency receives notice of a protest from GAO within 10 days after contract award, or within 5 days after a debriefing date offered to the protester for a required debriefing, whichever is later, the contracting officer “shall immediately suspend performance or terminate the awarded contract.” The head of the contracting activity can override that on a nondelegable written finding of urgent and compelling circumstances or best interests of the United States, and cannot authorise performance until GAO has been notified of the finding.
The debriefing mechanics feed directly into that window. A disappointed offeror can request a postaward debriefing in writing within 3 days of being notified of award, and the debriefing should occur within 5 days of that request where practicable. Defense runs an enhanced debriefing process that extends the exchange and therefore shifts protest timeliness.
There is also a detail in FAR 15.506(d) worth telling your client before they approve a release boasting about price competitiveness: the debriefing must disclose the awardee’s overall evaluated cost or price, including unit prices, along with the technical rating and the ranking of all offerors. Your competitors are about to learn your number.
So the award is public at 5 p.m. on award day, and it is not safe for roughly ten more days. Mature teams either wait out the stay window or hedge the verb: “has been selected for,” “subject to completion of the award process.” Reaching for “has been awarded” on day one is a bet, and sometimes it loses in public.
Check Whether the Award Triggers an 8-K
The third clock applies only to public companies, and it is the shortest.
Form 8-K Item 1.01 requires disclosure of entry into a material definitive agreement, defined as an agreement providing for obligations material to and enforceable against the registrant, where that agreement is not made in the ordinary course of business. General Instruction B.1 gives four business days from the event.
The phrase doing the work is “ordinary course of business,” and it is why Lockheed Martin does not file an 8-K every time it wins a program. Regulation S-K Item 601(b)(10) deems a contract to be in the ordinary course if it “is such as ordinarily accompanies the kind of business conducted” by the registrant. For a prime defense contractor, a $300 million award is routine. The provision that catches smaller companies is Item 601(b)(10)(ii)(B), covering any contract on which the registrant’s business is substantially dependent, including continuing contracts to sell the major part of its products or services. There is no bright-line dollar or percentage threshold for materiality, and the SEC has declined to add one.
The common filing pattern in practice pairs Item 1.01 for the agreement with Item 7.01 for Regulation FD, furnishing the press release itself as Exhibit 99.1. A release that precedes the filing can raise selective disclosure questions, which is the actual reason the regulated disclosure wires exist as a product category.
Negotiate the Three Variables With Your Customer
Before drafting, settle three questions with the customer, because in government and large-project work the release clears their approval and these are the only things actually up for negotiation.
Is the customer named? Is the value stated? How is the scope characterised?
Every combination occurs in the wild. Fluor named Teck Resources on the Highland Valley Copper mine life extension in December 2025 while recognising “its portion of the undisclosed contract value.” Fisk Electric announced a $29.5 million electrical project in Florida for a “confidential customer.” Palantir’s September 2026 release on delivering eight TITAN systems to the US Army named the customer and omitted the money, while Army Times reported the Army’s figures of $192 million combined, $127 million to Palantir and $65 million to Anduril. And Accenture Federal Services issued nothing at all on a five-year task order worth up to $821 million, which DefenseScoop reported from government open sources and market intelligence trackers.
That last case is the one to internalise. The award became public whether or not the contractor said anything. Classified work, foreign military sales sensitivity and competitive sensitivity routinely produce a release with no number, or no release.
Build the approval sequence into your timeline rather than discovering it. On a government award that usually means the contracting officer or the agency public affairs office sees the draft, and on commercial work it means the customer’s communications lead does. Two review rounds at two business days each is a realistic assumption, which puts your drafting start roughly a week before the award date you are anticipating. Draft on the assumption that the customer will strike the value and soften one adjective, and decide in advance which version you would still be willing to issue. A release held for three weeks waiting on an approval nobody chased has lost the news hook that made it worth writing.
Write the Release the Way the Beat Reporters Read It
The structure of a contract award press release holds across every example above, and it is shorter than most people write.
The headline carries the number when the number is disclosable, because the number is the news hook. When it is not, the headline leads on customer and scope instead. The dateline is the corporate or business-unit city rather than the customer’s. The lead paragraph carries five facts: awarding entity, the exact legal awardee, the instrument type, scope, and quantity. Palantir’s care in naming “Palantir USG, Inc., a wholly-owned subsidiary” is the kind of precision that matters when a reporter is checking a filing.
After that comes a short scope explainer, one or two quotes from the program lead rather than the chief executive for a routine award, and teammate naming where it serves the ecosystem. Palantir named Anduril, L3Harris, Sierra Nevada and two integrators in its release, which buys goodwill and gives four other communications teams a reason to amplify.
Public companies add a backlog or revenue recognition sentence. Tutor Perini’s subsidiary release said the value “will be reflected in the Company’s backlog for the second quarter of 2026.” Then boilerplate and a contact, and note that Tutor Perini routes that contact to investor relations rather than press, which tells you who they expect to call.
One structural departure worth watching: Lockheed Martin’s February 2026 release on a $328.5 million Legion-ES award used explicit subheads reading “The Big Picture,” “Why It Matters,” “Expert Perspective” and “Additional Context.” That is a deliberate break from the inverted pyramid, built for readers who skim and for machines that extract.
Then cut it. The Fisk Electric announcement runs roughly a hundred words of actual news and about three hundred including boilerplate. Lockheed’s structured release is longer and still comfortably under a page. The instinct to explain the program at length is the instinct to write for your own subject-matter experts rather than for a reporter who covers fourteen awards a week, and it is why most contract award releases get skimmed to the second paragraph and abandoned.
What earns space is anything a reporter cannot get from the agency announcement: the scope in plain language, what the work replaces or improves, where it will be performed, and headcount if there is any. What wastes space is the history of your capability, the adjectives attached to your partnership, and any sentence containing the word proud.
Stop Counting Syndication as Coverage
Here is where most reporting on these releases becomes fiction.
When Palantir’s TITAN release went out, it was reproduced near-verbatim on Nasdaq and on the FT’s company announcements feed. Those are automated republication of the wire. Counting them as pickup is the single most common inflation in press release reporting, and it is how a client ends up with a report claiming forty placements for an announcement that generated four stories.
The actual coverage came from somewhere else. Breaking Defense, Army Times and others covered the award within a day or two, working from the Army’s announcement and the dollar figures the government disclosed, not from the vendor release that carried no number. DefenseScoop explicitly sourced the Accenture task order to government open sources, market intelligence trackers and three people familiar with the award. These reporters work the daily agency list and the procurement databases. They are not waiting for your email.
The honest conclusion for govcon specifically: the release is a positioning and search document, not the thing that generates the coverage. It is where your framing of the win lives, where the scope is described in your words rather than the contracting officer’s, and what shows up when somebody searches the program name in two years. That is worth doing well. It is not worth reporting as earned media.
Nobody publishes credible coverage-rate data for this release type. The only figures in circulation come from distribution vendors, and the best of them, a 2026 claim that 63% of releases earned at least one non-syndicated pickup, is self-published, averaged across all release types, and sets the bar at a single outlet.
A contract award press release that respects all three clocks and claims nothing it cannot support is a small, useful document. The model to copy is PCL Construction, which announced a $190 million drinking water facility contract in September 2025 and a $43.2 million Schofield Barracks housing modernisation in August 2026. Named customer, stated value, specific scope, local relevance, issued after the award was public, and pitched to the trade and regional business press who actually cover that beat. No wire theatrics, and a release that does exactly one job well.