VotedBy VotedBy ⌕
Election Day · Tue, Nov 3See how your members of Congress voted →

H.R. 3850 · 116th Congress

Creating Candidate Capacity to Protect Act

Key: what the circles and colors mean

Each circle is a bill. The ring fills as it moves through Congress:

IntroducedPassed one chamberPassed both chambersBecame law (gold)Resolution agreed to (full, dark)Failed or vetoed (gray)

Under the number: the Yea · Nay count of its final (or latest) recorded vote. On a member's page, the small badge is how that member voted: Y Yea / Aye, N Nay / No, P Present, – Not voting.

Gold and violet are only for Yea and Nay; they never mean a party. A member's party is the letter on their photo.

Never voted on. It didn't reach a floor vote before the 116th Congress ended, so it expired. A bill has to be introduced again to be considered in a new Congress.

No cosponsors.

This bill provides an exception to limits on campaign expenditures made by the national or state committees of political parties. Specifically, political parties may make expenditures for secure information communications technology or a cybersecurity product or service.

What it does: CRS summary · Introduced in House · Jul 18, 2019

Creating Candidate Capacity to Protect Act

This bill provides an exception to limits on campaign expenditures made by the national or state committees of political parties. Specifically, political parties may make expenditures for secure information communications technology or a cybersecurity product or service.

Written by the nonpartisan Congressional Research Service. All summary versions on Congress.gov

About this bill and sources

Official title: Creating Candidate Capacity to Protect Act

Latest action (Jul 18, 2019): Referred to the House Committee on House Administration.

Policy area: Government Operations and Politics · Origin: House · Introduced: Jul 18, 2019

Official page on Congress.gov · Bill text (GovInfo) · Status record (XML)

No recorded floor vote found.