Court blocks OPM ‘loyalty question’ from use in agency job applications

TL;DR

A federal court has blocked OPM’s “loyalty question” that required federal job applicants to explain how they would advance the President’s Executive Orders and policy priorities; the court found the question likely violates the Administrative Procedure Act and undermines merit-based civil service hiring principles. The ruling requires agencies to cease using the question within seven days and to return to traditional merit-based hiring criteria. This affects government contractors that hire personnel to support federal contracts, because agency hiring practices and any contractor processes tied to those agency requirements must be adjusted immediately. Expect agencies and contracting officers to direct primes and subcontractors to remove or revise any application language tied to the blocked question. Contractors should audit active job postings and proposal staffing language, notify internal HR and capture teams, and use monitoring tools to track agency follow-on guidance or appeals. Failure to act quickly risks noncompliance with agency instructions and could complicate pending hires supporting contract performance.

Key Points

• What happened: A federal court blocked OPM’s “loyalty question,” finding it likely violates the Administrative Procedure Act and undermines merit-based civil service hiring principles.
• Who is affected: NAICS codes 561311, 561320, 541611, 541612, 541614, 541618, 541990, 561110; agencies listed: OPM, DOD, DHS (Department of Homeland Security), GSA (General Services Administration), VA, HHS, DOJ, DOE, DOT, DOI; contract vehicles listed: OASIS+, OASIS, Alliant 2, 8(a) STARS III, VETS 2, HCaTS, PSS; market segments: Professional Services, Human Resources Services, Staffing and Recruiting, Management Consulting, Administrative Support Services.
• Timeline: Agencies must cease using this question within seven days and return to traditional merit-based hiring criteria.
• What contractors should do NOW: Immediately audit and remove any “loyalty question” language from job postings and application forms for roles that support federal contracts; notify HR, capture, and contracts/compliance teams; coordinate with affected contracting officers/primes as required; document changes and retain audit records of removals; begin continuous monitoring for agency guidance or appeals.

Who Is Affected

This ruling primarily affects contractors and service providers that recruit, staff, or place personnel in roles supporting federal contracts across Professional Services, Human Resources Services, Staffing and Recruiting, Management Consulting, and Administrative Support Services. Explicitly named NAICS codes include 561311, 561320, 541611, 541612, 541614, 541618, 541990, and 561110. Affected agencies listed include OPM, DOD, DHS, GSA, VA, HHS, DOJ, DOE, DOT, and DOI. Named contract vehicles include OASIS+, OASIS, Alliant 2, 8(a) STARS III, VETS 2, HCaTS, and PSS. Specific additional NAICS codes, agencies, and contract vehicles pending source review.

Frequently Asked Questions

Q: Does this ruling apply to contractors who hire staff for federal contract positions?

A: Yes. The Summary states this affects government contractors who may be hiring for positions supporting federal contracts; contractors should assume any contractor-held application language tied to the blocked question must be removed.

Q: What is the compliance timeline for agencies and contractors?

A: The Summary specifies that agencies must cease using the question within seven days and return to traditional merit-based hiring criteria. Further agency guidance or appeals are possible — Pending source review.

Q: Will this change impact current solicitations, task orders, or staffing requirements?

A: Potentially, but the Summary does not provide details on solicitations or task orders. Impact on specific solicitations and staffing clauses is Pending source review.

Definitions

• loyalty question: The OPM question requiring federal job applicants to explain how they would advance the President’s Executive Orders and policy priorities.
• Administrative Procedure Act: The federal statute governing agency rulemaking and administrative procedures; the court found the loyalty question likely violates this Act.
• merit-based civil service hiring principles: Hiring standards intended to ensure selection based on qualifications and merit rather than political considerations; the court found the question undermined these principles.

Intelligence Response

• Cabrillo Signals War Room — Already detected this event and delivered this briefing. The War Room continuously monitors policy changes and court rulings impacting federal hiring and contractor obligations and issued this alert to affected subscribers.
• Cabrillo Signals Match Engine — Will automatically rescore opportunity pipelines and active capture lists where agency staffing requirements or hiring-related evaluation factors may be affected by this policy change.
• Cabrillo Signals Intelligence Hub — Tracking the listed affected agencies, NAICS codes, and contract vehicles. Saved searches will alert when agencies publish implementing guidance, appeals, or follow-on solicitations on SAM.gov (System for Award Management).
• Proposal Studio (Proposal OS) — Use to update proposal language, compliance matrices, and staffing narratives to remove any references to the blocked question and align with merit-based hiring criteria.
• Proposal Studio Workflow Tracker — Use the 9-gate capture workflow to route audits of job posting language, capture team notifications, and produce audit-ready documentation of actions taken.

Who to notify internally: Capture/Business Development leads, HR/Recruiting leads, Contracts/Compliance leads, Proposal/Capture managers, and Legal counsel (as required). For implementation guidance, review the Secure Operations Guide (/insights/secure-operations-guide) and related materials such as the CMMC (Cybersecurity Maturity Model Certification) Compliance Guide (/insights/cmmc-compliance-guide) and CUI (Controlled Unclassified Information)-Safe CRM Guide (/insights/cui-safe-crm-guide).

First 48-hour response playbook

• Hour 0–4: Stop using any OPM-style “loyalty question” language in active application forms and postings for roles supporting federal contracts. Record timestamped evidence of removal.
• Hour 4–12: Alert HR/Recruiting, Capture, Contracts/Compliance, and Proposal leads. Initiate a rapid sweep of all open requisitions for affected roles and tag them in the Proposal Studio Workflow Tracker.
• Hour 12–24: Use Cabrillo Signals Intelligence Hub saved searches to monitor for agency guidance, and run Match Engine rescoring on active opportunities to identify proposals likely impacted. Prepare standard messaging for contracting officers/primes.
• Hour 24–48: Update proposal templates and compliance matrices in Proposal Studio, finalize internal audit trail, and schedule decision meeting for capture teams to adjust staffing plans. Continue War Room monitoring for appellate action or agency implementing guidance.