H.R. 7551, the HILTON Act, forbids the head of any executive‑branch agency from entering into an agreement for a listed “covered service” with an entity that, during the prior year, either refused a Federal law enforcement officer a covered service citing the officer’s official duty or maintained a policy expressly permitting such refusals. The statute lists seven covered services (lodging, transportation, food and beverage, healthcare, vehicle rental, property rental, and storage) and treats entities under common control as a single entity for purposes of the prohibition.
The bill creates two narrow waiver paths: an agency head may waive the prohibition if no comparable provider exists within a 50‑mile radius for a necessary covered service, or if a parent company takes “sufficient remedial action” against an affiliate that refused service. Absent in the text are detailed procedures for proof, enforcement mechanisms beyond the contract bar, or standards defining remedial action — all practical gaps that will shape how agencies implement the rule and how vendors change policies or documentation practices.
At a Glance
What It Does
The bill prohibits executive‑branch agency heads from entering into agreements for certain services with any entity that refused a federal law enforcement officer a covered service in the previous year or had a policy expressly permitting such refusals. It provides two discretionary waivers—no comparable provider within 50 miles or remedial action by a parent company—and treats corporate groups under common control as one entity.
Who It Affects
Federal contracting officers and agency procurement offices must screen vendors for refusal incidents and policies; vendors of lodging, transportation, food/beverage, healthcare, vehicle rental, property rental, and storage face new eligibility risks; parent companies and corporate affiliates will need to coordinate policies and remedial responses. Federal law enforcement officers are the protected class the statute targets.
Why It Matters
The bill changes vendor eligibility criteria by adding a non‑discrimination test tied to past conduct and corporate policies rather than traditional statutory protected classes. That shifts some enforcement power into procurement decisions, creates compliance and documentation burdens for agencies and vendors, and could force corporate policy changes or restructuring to preserve government contracting opportunities.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
H.R. 7551 establishes a procurement‑based prohibition: if, within the prior year, an entity refused a federal law enforcement officer a covered service and the refusal was tied to the officer’s official duties—or the entity has a policy that expressly allows such refusals—the head of any executive agency may not enter into an agreement with that entity to provide listed services. The rule applies to agreements for lodging, transportation, food and beverage, healthcare, vehicle rental, property rental, and storage, and it folds affiliated companies under common control into a single contracting unit.
The bill empowers agency heads to waive the bar in two situations. First, if a covered service is necessary and no other provider offers a comparable service within a 50‑mile radius, the agency head can waive the prohibition.
Second, if the entity that refused service is an affiliate and the parent company takes sufficient remedial action against the affiliate, the agency head may grant a waiver. Both waiver paths are discretionary; the statute gives no required process, timeline, or standard for documentation of availability or remedial measures.Because the statute defines ‘‘Federal agency’’ by reference to the executive‑agency definition in title 41, procurement staff will treat the rule as part of executive‑branch contracting practices.
The bill does not create a private right of action, fines, or criminal penalties; its effect is to make entities ineligible for agreements unless a waiver applies. That design focuses enforcement through procurement choices, meaning contracting officers and agency legal teams will need to develop due diligence checks, recordkeeping practices, and waiver procedures to operationalize the prohibition.Several implementation questions arise immediately from the text: how agencies will prove an entity ‘‘refused’’ service (written denial, documented incident, public policy statements), how they will evaluate whether a service is ‘‘necessary,’’ what qualifies as ‘‘comparable’’ within a 50‑mile radius, and what counts as ‘‘sufficient remedial action’’ by a parent company.
Those gaps mean the statute will invite agency rulemaking, internal guidance, or litigation over interpretation once applied in practice.
The Five Things You Need to Know
The bill bars an executive‑branch agency head from entering into an agreement for a covered service with any entity that, in the prior year, refused a Federal law enforcement officer a covered service because of the officer’s official duty or maintained a policy expressly permitting such refusals.
Covered services are limited and explicit: lodging, transportation, food and beverage, healthcare, vehicle rental, property rental, and storage.
An agency head may waive the prohibition if no other entity provides a comparable necessary covered service within a 50‑mile radius.
An agency head may also waive the prohibition if the refusing entity is an affiliate and the parent company takes ‘‘sufficient remedial action’’ against the affiliate.
Entities that are members of the same controlled group of corporations or are otherwise under common control (per IRC §52(a)/(b)) are treated as one entity for purposes of the prohibition.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Designates the statute as the ‘‘Halting Inappropriate Limits Targeting Officers Now Act’’ or ‘‘HILTON Act.’
Contracts prohibited for entities that refused service or have refusal policies
Sets the central prohibition: agency heads may not enter into agreements for covered services with entities that during the preceding year either refused a federal law enforcement officer a covered service due to the officer’s official duty or maintained a policy expressly allowing such refusals. The provision is immediate and categorical; it disqualifies entities from being parties to agreements unless a waiver applies. Practically, this forces contracting officers to obtain or verify vendor history and policies before executing agreements for any listed service.
Waiver authority for necessity and remedial action
Creates two explicit, discretionary waiver bases. The first is geographic/market‑supply: if a necessary covered service has no comparable provider within a 50‑mile radius, the agency head may waive the ban. The second is corporate remediation: a parent company can cure an affiliate’s disqualifying conduct by taking ‘‘sufficient remedial action,’’ again at the agency head’s discretion. The statute does not define ‘‘necessary,’’ ‘‘comparable,’’ or ‘‘sufficient remedial action,’’ leaving those determinations to agencies or future adjudication.
Entities under common control treated as one entity
Adopts the Internal Revenue Code §52(a)/(b) controlled‑group definitions to aggregate affiliates: all corporations in the same controlled group and other entities under common control count as a single entity for the prohibition. That makes a parent company potentially liable for affiliate conduct and can extend disqualification across an entire corporate family.
Definitions of covered service and Federal agency
Defines ‘‘covered service’’ by an enumerated list (lodging; transportation; food and beverage; healthcare; vehicle rental; property rental; storage) and imports the title 41 definition of ‘‘executive agency’’ for ‘‘Federal agency.’’ These definitions fix the statute’s scope to procurement activity by executive‑branch agencies and to specific commercial services rather than to all government interactions.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Federal law enforcement officers — the statute creates an express procurement safeguard intended to reduce instances where officers are denied essential services while performing official duties, improving operational access to lodging, transport, healthcare, and related services.
- Executive‑branch agencies reliant on predictable access to services — by disqualifying vendors who refuse service, agencies gain a tool to pressure market participants to serve law enforcement or to justify procuring elsewhere. That can reduce mission disruption in environments where vendor refusals have occurred.
- Vendors that already serve federal law enforcement without restriction — such firms gain a competitive advantage when contracting officers prefer eligible vendors and can undercut or replace disqualified competitors.
- Parent companies that proactively align affiliate policies — companies that standardize conduct across affiliates or quickly remediate problematic affiliates can preserve or expand government contracting opportunities.
Who Bears the Cost
- Private vendors and service providers that have policies or practices of refusing service to federal law enforcement — they risk losing eligibility for agency agreements and may need to change policies, provide training, or document incidents to regain eligibility.
- Parent companies and corporate groups — because the statute aggregates affiliates, a single affiliate’s refusal can ripple across the whole controlled group, creating reputational and contractual risk and pushing parents to monitor and discipline subsidiaries.
- Agency procurement and legal offices — contracting officers will face added due diligence, recordkeeping, and waiver decision burdens; agencies may need new policy guidance and staff time to document availability and remedial actions.
- Small or rural providers — in areas where the market is thin, the 50‑mile waiver threshold could produce operational strain: providers might be pressured to accept government business under threat of disqualification, or agencies may face higher costs to find comparable services beyond the radius.
Key Issues
The Core Tension
The bill pits two legitimate goals against each other: preventing vendors from denying essential services to federal law enforcement versus preserving vendors’ ability to set service rules for safety, ethical, or legal reasons (especially in healthcare or areas implicating confidentiality). Enforcement through procurement shifts the remedy into contracting discretion, which can coerce vendor behavior without clear standards for proof or remediation—an effective tool to curb refusals, but one that risks overreach, inconsistent application, and collateral impacts on affiliates and small local providers.
The bill is concise but leaves critical implementation questions unanswered. It does not set an evidentiary standard for proving a ‘‘refusal’’ (e.g., written policy, incident report, public statement), nor does it prescribe an administrative process for agencies to collect, verify, and record such proof.
Because the only statutory remedy is a contract bar, enforcement will be mediated through procurement officers’ decisions rather than a centralized enforcement agency, which will produce uneven application across agencies and regions.
Several textual ambiguities matter in practice. ‘‘Official duty’’ is unspecified and could prompt disputes when officers are off‑duty but in uniform, or when duties intersect with public health or privacy rules (notably healthcare). The 50‑mile geographic test and ‘‘comparable’’ service standard create metric and evidentiary challenges in urban vs. rural markets. ‘‘Sufficient remedial action’’ by a parent company is unqualified; that vagueness enables broad deference to agency judgment but invites litigation and inconsistent corporate responses.
Finally, applying the IRC controlled‑group tests brings tax‑law definitions into procurement decisions, which may sweep non‑corporate affiliates into the rule unexpectedly.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.