How Federal Proposal Evaluators Score Proposals

This article is for general informational purposes only and does not constitute legal, financial, or business advice. Federal Acquisition Regulation, DFARS, and service-supplement provisions discussed here reflect publicly available government guidance as of July 2026; regulations, thresholds, and agency procedures are subject to change without notice, and the Revolutionary FAR Overhaul is actively amending FAR Part 15 through class deviations ahead of formal rulemaking. Verify current requirements against the live solicitation and current regulatory text before relying on any point here. Nothing in this article guarantees a favorable evaluation rating, contract award, or any particular competitive outcome.

Your Proposal Isn't Being Read. It's Being Scored.

Most losing proposals are well written. Clean prose, strong graphics, and a compelling story don’t lose to bad writing. They lose to proposals that scored higher.

Federal source selection is not a reading exercise. It is a documented, rule-bound scoring exercise conducted by a trained team working from worksheets, against criteria published in the solicitation, under conditions where every rating must survive legal challenge.

A note on terminology: Executive Order 14347, signed September 5, 2025, authorized “Department of War” as a secondary title. The legal name remains the Department of Defense pending congressional action — only an act of Congress can formally change it. This article uses DoW, but every clause and citation still reads “DoD” and “DFARS.” Never correct a citation to match the branding.

Who Actually Evaluates Your Proposal

For competitive negotiated procurements under FAR Part 15, a Source Selection Team executes the evaluation. The DoD Source Selection Procedures, dated August 20, 2022, define the roles: the Source Selection Authority (SSA) makes the final best-value decision, which FAR 15.303 frames as an independent, documented business judgment; the Source Selection Evaluation Board (SSEB) does the working evaluation; and a Source Selection Advisory Council (SSAC) is required at or above $100 million to provide the SSA a written comparative analysis. At that same threshold, the SSA must be someone other than the contracting officer.

Evaluators sign non-disclosure and conflict-of-interest statements and are trained on how to document the rationale for every rating and every assessed strength, weakness, uncertainty, risk, and deficiency.

Read that again. The evaluator’s actual job is documentation. That single insight reorganizes everything else.

The Findings Vocabulary

These definitions come verbatim from the DoD Source Selection Procedures and FAR 15.001:

• Strength — an aspect of the proposal with merit or that will exceed specified performance or capability requirements to the advantage of the Government during contract performance.
• Significant Strength — an aspect with appreciable merit or that exceeds requirements to the considerable advantage of the Government.
• Weakness — a flaw that increases the risk of unsuccessful contract performance.
• Significant Weakness — a flaw that appreciably increases that risk.
• Deficiency — a material failure to meet a Government requirement, or a combination of significant weaknesses that raises risk to an unacceptable level. A deficiency makes you unawardable.
• Uncertainty — any aspect where the intent of the offer is unclear: more than one reasonable interpretation, or internal inconsistencies suggesting an error or omission.

Notice what’s absent from the definition of “strength”: clarity, polish, professionalism, enthusiasm, corporate pedigree. A strength is merit or exceeding a requirement, to the Government’s advantage. If your paragraph can’t be mapped to that definition, it isn’t scoring.

The Rating Table That Explains Everything

The DoD SSP Technical Rating (Table 2A) runs Blue/Outstanding (exceptional approach; multiple strengths and/or at least one significant strength), Purple/Good (thorough approach; at least one strength or significant strength), Green/Acceptable (adequate approach and understanding), Yellow/Marginal (has not demonstrated an adequate approach), and Red/Unacceptable (contains one or more deficiencies; unawardable).

Stop on Green. “Acceptable” is the rating for a proposal with no strengths. It’s fully compliant. It answers every question. And in a tradeoff it loses, because the Government has no documented basis to prefer you.

The step from Green to Purple is one strength. The step from Purple to Blue is multiple strengths or one significant strength. That’s the entire game, in the Government’s own words.

Two more scales matter: the Technical Risk Rating (Low / Moderate / High / Unacceptable) and the Performance Confidence Assessment (Substantial / Satisfactory / Neutral / Limited / No Confidence). Cost and price are never assigned an adjectival rating under the SSP.

The Worksheet Problem

Here’s the mechanic written policy describes only obliquely. Your evaluator is likely an engineer, contract specialist, or logistician doing source selection on top of a full-time job, working from a worksheet that requires a written narrative justification for every finding. That justification gets reviewed by the SSEB chair, may be summarized for the SSAC, informs the SSA’s decision document, and could appear verbatim in a GAO protest record.

So the practical question isn’t “is my approach strong?” It’s: can a tired evaluator find my strength in thirty seconds, understand why it exceeds the requirement, and lift my language straight into their justification without inventing the argument themselves?

If not, the strength doesn’t exist for scoring purposes. Unfound strengths score as Acceptable.

Compliance Versus Compellingness

Compliance means meeting every Section L instruction and addressing every Section M factor. It’s a gate — it earns you nothing, it only keeps you eligible. Compellingness means giving the evaluator documented, provable reasons to assess strengths and low risk. Most teams spend eighty percent of their effort on compliance and then wonder why they placed second.

The three-part strength construction: every strength-seeking paragraph needs a feature (what you’ll specifically do), a benefit (the advantage to the Government, in the language of the Section M factor), and proof (quantified, verifiable evidence you’ve done it before). Drop the proof and you have an unsubstantiated claim. Drop the benefit and the evaluator has to build your argument for you — and they usually won’t. Skip the superlatives; “world-class” and “best-in-class” earn nothing and mark the document as boilerplate.

Section L Is Your Outline. Section M Is Your Argument.

FAR 15.204 establishes the Uniform Contract Format, Sections A through M. Two sections govern proposal work. Section L — Instructions, Conditions, and Notices to Offerors — tells you what to submit, in what volumes, in what order, with what page limits, fonts, margins, and file formats. Section M — Evaluation Factors for Award — tells you how it will be scored: the factors, subfactors, their relative importance, and the basis for award.

The PWS, SOW, or SOO defines the work. The CDRLs define the deliverables. Sections L and M translate all of it into submission instructions and evaluation criteria. A proposal is not a description of your company — it’s a response engineered against L and scored against M.

Build the outline from L. Build the argument for M. The single most reliable structural discipline in this business: your proposal outline is Section L, in Section L’s order, using Section L’s headings and numbering.

Then build a compliance matrix cross-walking every Section L instruction to its corresponding Section M factor, with columns for the responsible author, the page or paragraph where it’s addressed, and — the column most teams omit — the finding you intend to earn there. Run it at every review gate, not just at the end.

A useful test at the annotated-outline stage: for each Section M factor, can you name the specific discriminator you intend to convert into a strength? If not, that section isn’t ready to be written. You’re about to produce compliant text that scores Green.

When Section L and Section M Conflict

They conflict more often than people expect — different drafters, different timelines, late amendments. The safe course is to satisfy both: address the item where Section L directs it and ensure the Section M factor is fully covered, even if that means brief cross-referenced treatment in two places. Submit a clarifying question during the Q&A window and document the conflict internally.

Patent versus latent ambiguity — the rule that can cost you your protest rights. GAO distinguishes between the two, and the distinction is jurisdictional. A patent ambiguity — an obvious inconsistency apparent on the face of the solicitation — must be challenged before the proposal due date. If you bid without objecting, the objection is waived, and you can’t raise it after award no matter how badly it hurt you. A latent ambiguity, not reasonably discoverable before submission, can support relief later.

The practical rule: if your team spots a real conflict, ask the question in writing during Q&A. That question is free. Silence can be fatal.

Not Every DoW Solicitation Uses the UCF

Increasingly, many don’t. FAR Part 12 commercial-item procedures use the streamlined 52.212-1 / 52.212-2 construct. FAR Part 13 simplified acquisitions collapse instructions and evaluation into a combined notice. Orders under FAR Subpart 8.4 (Federal Supply Schedules) and FAR 16.505 (fair opportunity under multiple-award IDIQs) are far more streamlined than Part 15, with narrower protest and debriefing rights. And Other Transaction Agreements and Commercial Solutions Openings don’t use the UCF at all.

Diagnosing which regime you’re in — before you write a word — is a capture function, not a proposal function. Teams that discover it during Pink Team have already lost time they can’t recover.

Writing for the Evaluator

Structure gets your content found. These make it scoreable:

• Topic sentences that state the point, not announce the topic. “Our approach reduces transition risk by retaining 85% of incumbent staff” beats “This section describes our transition approach.”
• Explicit “so what” statements naming the benefit in the language of the Section M factor.
• Action captions on every graphic — a caption stating the benefit, not “Figure 3: Program Organization.” Many evaluators read captions and headings first.
• Quantify everything. Numbers are evidence. Adjectives are noise.
• White space and short paragraphs. Dense text hides strengths, and hidden strengths don’t score.

Is There a DoW Standard for Scoring Proposals?

Clients ask this constantly: does the Air Force score proposals differently than the Army? Does Navy? Does DLA? The answer has two layers.

Layer One: FAR Part 15, Government-Wide

The citations worth knowing by number: FAR 15.101 (the best-value continuum), FAR 15.101-1 (the tradeoff process, permitting a premium for higher-rated non-price merit), FAR 15.101-2 (LPTA), FAR 15.304 (evaluation factors and significant subfactors), FAR 15.306 (exchanges — clarifications, competitive range communications, and discussions, where DoD Evaluation Notices are issued), and FAR 15.308 (the source selection decision).

The most important is FAR 15.305: the agency may evaluate only against the factors stated in the solicitation. That’s your greatest protection and the source of most sustained protests.

Layer Two: the DoW Standard

The DoD Source Selection Procedures (August 20, 2022), linked to DFARS PGI 215.300, are mandatory for competitive FAR Part 15 acquisitions above $10 million and for major systems. They exist explicitly to create uniformity for both Government and industry — standardizing the rating tables, findings definitions, and team roles across Army, Navy, Marine Corps, and Air Force. One caveat: solicitations whose source selection plan was approved before September 1, 2022 may still run on the April 1, 2016 version. Check which one your RFP references.

So the honest answer: the vocabulary and the scales are standardized DoW-wide; governance, thresholds, and technique are tailored by service and program.

Army

AFARS Subpart 5115.3 and the Army Source Selection Supplement at AFARS Appendix AA supplement the DoD SSP. The Army uses the standard color and adjectival tables, and numerical or point weighting of factors is prohibited — relative importance is expressed in words. The AS3 identifies the subjective tradeoff process as appropriate for most Army source selections and permits entry-gate criteria that screen proposals before full evaluation.

Navy and Marine Corps

NMCARS Subpart 5215.3 governs. SSA authority for ACAT I programs rests with PEOs and SYSCOM commanders and may not be further delegated. NMCARS discourages point-scoring of cost and price on the grounds that it obscures the tradeoff the SSA is required to make.

Department of the Air Force

DAFFARS MP5315.3 follows the numbering convention of the DoD SSP and supplements rather than replaces it. Several sections — including Definitions and Best Value Continuum — are marked “No DAF Text,” confirming that the DoD color ratings and Performance Confidence Assessment apply Air Force-wide. The Air Force is known operationally for confidence-based tradeoffs, including Performance Price Tradeoff, where award may go to a higher-confidence, higher-priced offeror.

A caution: industry references to a distinct Air Force “Level of Confidence” scale, one-step and two-step downselects, and “Preferred/Alternate Approaches” generally derive from legacy AFFARS and AFMC practice or program-specific Section M design — not current mandatory MP text. Verify against the live solicitation.

Defense Logistics Agency

The sharpest divergence in the department, and the one that trips up small businesses most often. Governed by the Defense Logistics Acquisition Directive, DLA buys millions of National Stock Numbers through highly automated simplified acquisition, with awards frequently going to the lowest-priced approved source.

For source-controlled items, the gate isn’t a proposal — it’s a Source Approval Request (SAR) or Alternate Offer. You must document that your item is identical to, or physically, mechanically, electrically, and functionally interchangeable with, the approved item, supported by a technical data package reviewed by the Competition Advocate Office, Value Engineering, and the cognizant Engineering Support Activity, with possible qualification testing.

Two points that save clients money and disappointment. First, timelines vary by supply chain and are long — DLA Aviation’s instructions advise that review can take over 180 days from receipt, and any subsequent qualification or testing phase can add a year or more. Second, SAR approval grants the right to compete, not an award. It’s an eligibility gate, not a scoring event.

DARPA, DIU, SBIR/STTR, and the OTA/CSO World

Fundamentally different mechanics. Commercial Solutions Openings evaluate each proposal on its own merits, not comparatively against other offerors. The Defense Innovation Unit uses Other Transaction Authority through a three-phase CSO — solution brief, pitch, request for prototype proposal — awarding prototype agreements in as few as 60–90 days, with a current average closer to 120, and a successful prototype can support a sole-source production follow-on. SBIR/STTR and Broad Agency Announcements are exempt from the DoD SSP entirely. Teams that port a Part 15 proposal template into a DIU pitch lose on the first cut.

LPTA Restrictions Unique to DoW

This matters because LPTA changes your entire strategy — under LPTA, exceeding a requirement earns you nothing. Section 813 of the FY2017 NDAA is implemented at DFARS 215.101-2-70. LPTA may be used only where minimum requirements can be comprehensively described, there’s no value in exceeding them, minimal subjective judgment is required, and the contracting officer documents a life-cycle-cost determination. It directs contracting officers to avoid LPTA to the maximum extent practicable for IT, cybersecurity, systems engineering and technical assistance, advanced electronic testing, audit and audit-readiness, other knowledge-based professional services, personal protective equipment, and knowledge-based training or logistics in contingency operations. Section 832 of the FY2018 NDAA prohibits LPTA outright for engineering and manufacturing development of major defense acquisition programs.

If you see LPTA on a knowledge-based DoW services requirement, that’s worth a question during Q&A — and possibly a pre-award challenge.

The FAR Overhaul: Verify Before You Rely

Executive Order 14275 (April 15, 2025) and OMB Memorandum M-25-26 launched a rewrite of the FAR to its statutory core, implemented first through class deviations, part by part, ahead of formal rulemaking. DoD has issued Revolutionary FAR Overhaul class deviations for DFARS and PGI Part 15. Practitioner reporting indicates the Part 15 deviation retains multiple competitive approaches including Highest Technically Rated with a Fair and Reasonable Price, and reinforces that a lack of relevant past performance may be assessed only for currency and relevance.

The consequence: “the FAR” is now increasingly contract-specific. Read the solicitation to determine whether it runs on the codified FAR or a deviated version. Don’t assume.

Three Ways DoW Evaluation Differs From Civilian Federal

If you bid across both DoW and civilian agencies, three differences are big enough to change your strategy — and one is a genuine advantage most small businesses never use.

1. Enhanced Debriefings — a Genuine DoW Advantage

Section 818 of the FY2018 NDAA, implemented at DFARS 215.506 via the final rule published March 18, 2022, requires that for contracts and orders at or above $10 million, DoD allow a disappointed offeror to submit additional written questions within two business days of the debriefing. The agency then has five business days to respond, and the debriefing isn’t considered closed — and the protest clock doesn’t start — until those written answers are delivered. The Federal Circuit confirmed the timing effect in Nika Technologies.

Civilian agencies operate under standard FAR 15.506 debriefings, with no equivalent Q&A extension mechanism.

Why this matters even if you never protest: the enhanced debriefing is the only formal channel through which you can compel the Government to explain, in writing, the specific strengths and weaknesses it assessed against your proposal. That’s the closest you’ll ever get to seeing your own scoresheet.

Ask targeted questions. Not “how could we improve?” — ask which specific strengths were assessed under each factor, which weaknesses, and how your ratings compared. Then feed every answer into the annotated outline of your next proposal.

2. LPTA Rules Differ in Scope

Section 880 of the FY2019 NDAA extended LPTA restrictions government-wide through FAR 15.101-2. But the civilian list isn’t identical to DoD’s — it adds categories including health-care services and records and telecommunications devices and services. Don’t assume the DoD carve-outs apply verbatim at a civilian agency, or vice versa.

3. CMMC — an Eligibility Gate With No Civilian Equivalent

DFARS 252.204-7012 (safeguarding and incident reporting), -7019 and -7020 (NIST SP 800-171 assessment posted in SPRS), and -7021 (CMMC), together with solicitation provision -7025, make CMMC status a condition of eligibility for award.

The DFARS acquisition final rule published September 10, 2025 took effect November 10, 2025, beginning a three-year phased rollout. Phase 1 permits Level 1 or Level 2 (self-assessment) requirements in solicitations, with discretion to require Level 2 with third-party C3PAO certification. The clause flows down to subcontractors handling federal contract information or controlled unclassified information, and contractors must maintain a current status in SPRS with an annual affirmation.

Check your required level and your SPRS status before you invest bid-and-proposal dollars. No amount of proposal quality survives an eligibility failure.

Beyond the Big Three

Civilian agencies vary widely in technique. NASA, under NASA FAR Supplement Part 1815, is known for a more structured adjectival approach and heavy use of oral presentations. GSA, DHS, VA, HHS, DOE, and State each have distinctive practices around oral presentations, advisory down-selects, and page limits. There’s no single “civilian standard” comparable to the DoD Source Selection Procedures. If you’re moving from DoW work into civilian work, don’t assume the vocabulary transfers — read Section M as if you’ve never seen one before.

The Practitioner’s Playbook: Capture, Color Teams, and What GAO’s Data Tells You

Win rate is set before the RFP drops. Teams that first see a requirement on SAM.gov the day the RFP posts win at a fraction of the rate of teams that engaged months earlier.

Respond to Sources Sought notices and RFIs. They’re the mechanism through which agencies conduct market research under FAR Part 10 and inform set-aside decisions — including the Rule of Two analysis that determines whether a requirement is set aside for small business at all. A Sources Sought response is the cheapest, highest-leverage document in government contracting, and most small businesses skip it.

Then run a disciplined bid/no-bid with an explicit probability-of-win estimate weighing incumbency, depth of customer relationship, capability fit, teaming position, and price-to-win. If you can’t name a genuine discriminator, no-bid and redeploy the B&P funds. Winning more often is usually a function of bidding less often.

Color Team Reviews

The Shipley-derived review architecture, in practice terms:

• Blue Team — early validation of win strategy and solution.
• Pink Team — review of storyboards and first draft against strategy and compliance. Shipley notes that more proposals fail because of poorly executed or nonexistent Pink Teams than any other cause.
• Red Team — a near-final review predicting how a Government evaluator will score the proposal. Run it at roughly 60–70% completion so writers still have time to act, and staff it with people who did not write the document. As the saying goes: if your Red Team members are also your writers, you’re grading your own homework.
• Gold Team — executive go/no-go and final compliance review before submission.
• Green / White Glove — pricing and final production check.
• Black Hat — competitive analysis conducted during capture, not proposal. Model your competitors’ likely solutions and pricing so your discriminators are actually discriminating.

Two chronic failure modes: reviews staffed by the authors, and reviews scheduled so late that findings can’t be implemented.

Past Performance

Evaluated on recency, relevancy, and quality under FAR 15.305(a)(2). Three things clients routinely get wrong:

• No past performance is not bad past performance. FAR 15.305(a)(2)(iv) requires a neutral rating where an offeror has no relevant record — evaluated neither favorably nor unfavorably. Neutral can’t be used as a discriminator against you.
• You have more citations than you think. Key personnel experience counts under FAR 15.305(a)(2)(iii). Commercial and state/local work counts under FAR 15.305(a)(2)(ii). And under a 2022 FAR rule, small business joint venture members and first-tier small business subcontractors can bring past performance to the table.
• Relevancy beats size. A smaller contract with identical scope, complexity, and contract type usually rates more relevant than a large contract doing different work.

Pricing

Distinguish reasonableness (not too high) from realism (not unrealistically low for the technical approach proposed). Realism analysis is mandatory for cost-reimbursement contracts and used in fixed-price competitions when the solicitation says so.

A cautionary example: in Criterion Corporation (B-422309, April 16, 2024), GAO sustained a protest where the agency found the protester’s price unrealistic — more full-time equivalents at a slightly lower labor rate — but failed to examine whether the protester could realistically perform at its proposed price, ignoring differences in labor mix and technical solution.

The lesson for offerors: your price narrative must explicitly tie your labor mix and level of effort to your technical approach. Unexplained low prices invite an unrealistic finding. Explained ones invite a strength. And avoid unbalanced pricing, which can be grounds for rejection regardless of total price.

Small Business Specifics

The Rule of Two sets aside a requirement when two or more capable small businesses are expected to submit offers at fair market price. Under 13 CFR 125.6, for services the prime plus similarly situated entities must self-perform at least 50%, excluding work that similarly situated subcontractors perform with their own employees — and failure to comply can now produce a negative past performance rating.

Under 13 CFR 125.8, agencies must consider joint venture members’ experience and past performance in the aggregate and shall not require the JV itself to individually meet all the same evaluation or responsibility criteria; the protégé must perform at least 40% of the JV’s work. That’s the most underused competitive tool available to small businesses — it lets a capable small firm compete on a large, complex requirement without pretending to have a past performance record it doesn’t have.

Why Proposals Lose

The recurring, entirely avoidable causes: late or non-compliant submission; failure to follow Section L structure; failure to address a Section M factor at all; unsubstantiated claims and boilerplate; no discriminators; weak or generic risk mitigation; thin staffing and key personnel with no letters of commitment; and vague transition plans.

What GAO’s Data Tells You

In its Bid Protest Annual Report to Congress for FY2024 (GAO-25-900611), GAO reported 1,803 protests filed, down 11% from FY2023. GAO resolved 387 protests on the merits and sustained 61 — a 16% sustain rate — alongside a 52% effectiveness rate, the share of protesters obtaining some form of relief through a sustain or voluntary corrective action.

Most instructive is why GAO sustains. Per the FY2024 report, the most prevalent grounds were unreasonable technical evaluation, flawed selection decision, and unreasonable cost or price evaluation.

Set that beside the opening of this article. The same discipline that makes a proposal score well — findings tied explicitly to stated Section M factors, supported by documented evidence — is the discipline that makes an agency’s evaluation defensible, and the discipline that reveals when it isn’t. Write to be scored, and you’ll also know when you were scored wrongly.

The one idea to keep: the proposal isn’t the deliverable. The evaluator’s justification narrative is. Your job is to write a document from which that narrative can be assembled quickly, accurately, and defensibly. Compliance keeps you in the competition. Strengths win it.

Putting It to Work

The next step is a specific solicitation: pull the last one you lost, request or re-read the debriefing, and map the assessed findings against the Section M factors. That exercise tells you more about your win probability on the next bid than any general guidance can.

Sources

• Department of Defense, Source Selection Procedures (Aug. 20, 2022) — acq.osd.mil
• FAR Part 15, Contracting by Negotiation — acquisition.gov
• FAR 15.001, Definitions — acquisition.gov
• FAR 15.204, Contract format — acquisition.gov
• FAR Part 12, Acquisition of Commercial Products and Commercial Services — acquisition.gov
• FAR Subpart 8.4, Federal Supply Schedules — acquisition.gov
• FAR 16.505, Ordering — acquisition.gov
• DFARS PGI 215.300, Source Selection — acquisition.gov
• AFARS Appendix AA, Army Source Selection Supplement — acquisition.gov
• NMCARS Subpart 5215.3, Source Selection — acquisition.gov
• DAFFARS MP5315.3, Contracting by Negotiation — acquisition.gov
• DLA, SAR Guide — dla.mil
• DFARS 215.101-2-70, Limitations and prohibitions — acquisition.gov
• Lohfeld Consulting, FAR Overhaul Timeline: 2026 Changes and 2027 Outlook — lohfeldconsulting.com
• DFARS 215.506, Postaward debriefing of offerors — acquisition.gov
• Federal Register, DFARS: Postaward Debriefings, DFARS Case 2018-D009 (Mar. 18, 2022) — federalregister.gov
• Wiley Rein LLP, DoD Issues Final Rule on Enhanced Post-Award Debriefings — wiley.law
• FAR 15.506, Postaward debriefing of offerors — acquisition.gov
• Pillsbury Winthrop Shaw Pittman, NDAA Limitations on LPTA Procurements — pillsburylaw.com
• Cooley LLP, DoD Releases Long-Awaited Final Rule Implementing CMMC Contract Clause (Sept. 2025) — cooley.com
• Wiley Rein LLP, Additional Analysis on DoD’s Final Rule for the CMMC Program — wiley.law
• FAR Part 10, Market Research — acquisition.gov
• FAR 15.305, Proposal evaluation — acquisition.gov
• Federal Register, Past Performance Ratings for Small Business Joint Venture Members and Small Business First-Tier Subcontractors (July 22, 2022) — federalregister.gov
• 13 CFR 125.6, Prime contractor performance requirements — ecfr.gov
• 13 CFR 125.8, Requirements for joint venture agreements — ecfr.gov
• GAO, Bid Protest Annual Report to Congress for Fiscal Year 2024, GAO-25-900611 — gao.gov
• Holland & Knight, GAO Annual Report FY 2024: A Return to Business as Usual — hklaw.com
• Shipley Associates, Effective Color Team Reviews for Proposal Success — shipleywins.com
• Shipley Associates, Color Team Reviews: Who to Invite and Why — shipleywins.com
• The White House, Fact Sheet: Restoring the United States Department of War (Sept. 5, 2025) — whitehouse.gov