U.S. Senate Web Dev 4

Amendment / Modification

This document is Amendment 001 to the solicitation.

• Section A, Block 10: Acknowledgement of Amendments, has been updated to include Amendment 001 with a date of 4/27/2026.

This amendment does not appear to alter proposal deadlines or submission requirements, but it is a formal update to the solicitation record.

Questions & Answers / Clarifications

This document contains questions submitted by potential offerors and the Government's responses regarding Solicitation 2026-R-038 (RFP) for Web Development Services for the Senate.

• Key Personnel: Resumes are required only for proposed Key Personnel. Offerors are responsible for identifying which positions are considered Key.
• Authority to Operate (ATO): An ATO is not required, but all proposed systems must undergo the SAA CIO Cybersecurity Risk Assessment Process.
• Past Performance: References can include proposed subcontractors and wholly owned subsidiaries. A mix of Prime Contractor and Subcontractor contracts is acceptable for the five required references.
• Payment Schedule: Payment is due within sixty (60) calendar days of receiving proper invoices, with efforts to process within thirty (30) days.
• Development Environments: The SAA will provision the production CMS platform. Staging and development environments will be made available through the Senate network.
• CAPTCHA License: The SAA will be responsible for procuring CAPTCHA licenses.
• Incumbent Information: The SAA does not disclose information regarding incumbent contractors.
• Website Success Metrics: Success is determined by the receiving Office's written acceptance and post-launch monitoring, with primary criteria being timely, within-budget, launch-ready delivery.
• Task Order Issuance: Task Order Proposal Requests (TOPRs) are typically issued with a 14-day response period, and award decisions generally range from 3 to 5 weeks.
• Plugin Approval: Requests for new plugins may take up to six months for review and approval. Offerors should scope based on the currently approved plugin list.
• End-User Support: Refers to support provided to Senate Office personnel using the CMS for content creation and maintenance.
• Remote Work: Remote performance is permitted and anticipated; there are no on-site requirements.
• Small Business Set-Asides: There is no preference or evaluation advantage for SDVOSB or other small business categories.
• Relevant Experience: Experience as a subcontractor on a Federal prime contract can satisfy the requirement. Experience gained by key personnel at prior firms or state/local government contracts do not qualify for the Go/No-Go Relevant Experience factor.
• CMS Platform: WordPress is the required CMS base build. Alternative CMS platforms are not being considered.
• Accessibility: The required accessibility delivery standard is WCAG 2.2 Level AA.
• Background Investigations: Personnel security processing requires a minimum lead time of two weeks.
• Proposal Submission: Resumes, references, past performance, certifications, and attachments do not count toward the Technical Proposal page limitation.
• AI Tools: Use of AI tools must comply with Section 1.15 and C.3.4.1.1, with no training on Senate data. Specifics on AI tool usage are generally addressed by stating compliance with Section 1.15.

This document clarifies numerous aspects of the solicitation, including requirements for personnel, past performance, technical execution, security, and proposal submission. Offerors should review these responses carefully to ensure their proposals align with the Government's clarified expectations.

Solicitation / RFP / RFQ

This solicitation is for website design and development, maintenance, and end-user support services for public-facing websites within the senate.gov domain. The U.S. Senate (Office of the Sergeant at Arms - SAA) requires these services to provide and maintain websites for Senate Offices and Committees.

• Website design and development

• Website maintenance and end-user support (hourly or monthly)

• Training for designated Senate Office staff

• Content migration

• Development of specific website features as defined in Task Orders (TOPRs)

• Compliance with Senate rules, regulations, and policies, including web development guides, design guides, and cybersecurity standards.

• Websites must be responsive and conform to OWASP coding practices.

• Adherence to Section 508, ADA Title II, and WCAG standards.

• Contract Type: Multiple Award Indefinite Delivery Indefinite Quantity (IDIQ) with Firm-Fixed-Price (FFP) or Labor-Hour (LH) Task Orders.

• Period of Performance: One-year base period (starting approx. January 1, 2027) with five (5) one-year option periods.

• Maximum Ceiling: $5,637,600.00 per IDIQ contract. No guaranteed minimum.

• Proposals are due by 12:00 Noon ET on May 4th, 2026.

• Technical and Administrative questions are due by 12:00 Noon ET on April 16th, 2026.

• Proposals will be evaluated on a best-value basis, considering Technical Capability, Past Performance, Key Personnel, and Price.

• Technical Proposal page limit: 50 pages (excluding resumes).

• Proposals must be submitted electronically.

• No specific set-aside mentioned. Open to all eligible offerors.

• The SAA anticipates making multiple contract awards.

• Task Orders will be competed among awarded IDIQ contract holders.

• Specific details for each Senate Office's website will be listed in individual Task Order Proposal Requests (TOPRs).

• Attachments include various guides (Web Development, Web Design, Testing, etc.) and procedures.

Form / Attachment / Pricing Sheet

This document, titled "Senate Web Development Guide," provides guidelines and requirements for contractors involved in the creation and launch of Senate websites. It outlines the Senate environment, available resources, and standards for contractually compliant, high-quality websites. Awarded contractors will access the most current guidelines via an internal SAA site.

• Content Management System (CMS) Base Builds: The SAA provides WordPress development/testing and production sites with approved plugins.
• SAA Requirements: Details approved CMS plugins (WordPress 6.x) and configurations.
• Custom Code: Guidelines for using custom code when standard plugins are insufficient, requiring justification and adherence to OWASP standards.
• External IP Address Capture: Requirements for including constituent external IP addresses in web form submissions.
• Website Launch Process: A two-week minimum notice for website launch requests, with specific timelines for development, content lockdown, and testing.
• User Accounts & Data Collection: Procedures for creating user accounts and strict rules for collecting and transmitting user data, emphasizing privacy and prohibiting PII capture via certain methods. All web forms must include CAPTCHA.
• Website Analytics: Adobe Analytics is the only approved tool for website statistics.
• Social Media Integration: Policies on using approved social media platforms and restrictions on embedding third-party code or linking to unapproved sites.
• Responsibilities: Defines roles for Senate Contractors (design, development, support), SAA (backend maintenance, updates), and Senate Offices (content production, modifications).

This guide is crucial for any bidder proposing to develop or maintain Senate websites. It details technical requirements, approved tools, security protocols, data handling policies, and the overall process for website development and launch. Understanding these guidelines is essential for creating compliant and successful proposals and project execution.

Form / Attachment / Pricing Sheet

This document, "Senate Web Design Guide," provides essential information for designing and maintaining websites within the United States Senate web environment. It serves as an addendum to the Website Development Contract (2026-R-004) and outlines mandatory guidelines and permitted resources for creating contractually compliant, high-quality Senate websites.

• Overview: Explains the guide's purpose, mandatory compliance, future updates, and how to address questions.
• General Guidelines: Encourages innovation while adhering to Senate requirements, specifying WordPress as the only approved CMS and outlining plugin usage.
• Design Requirements: Details the need for design approval phases, including clickable mockups, and specifies that design elements must be approved by the Office's point of contact before development.
• Site Design Related Documents and Tasks: Lists tasks such as graphical design, template creation, HTML mockups, browser testing, and site documentation.
• User Data Collection: Mandates secure transmission of form data and prohibits the creation of preview/printable options for forms to prevent Personally Identifiable Information (PII) caching.
• Website Analytics: States that Adobe Analytics is the only approved tool for website statistics.
• Social Media Integration: Outlines rules for social media postings and prohibits embedding third-party platform code. Lists approved social media platforms (Instagram, LinkedIn, YouTube, Facebook, Scribd, X, Eventbrite).
• Requesting Other Integrations: Describes the process for requesting integrations with unapproved social media networks.
• Requirements Gathering Process: Details how requirements are gathered via a standardized questionnaire.
• Accessibility: Requires compliance with Section 508 of the Rehabilitation Act, ADA Title II, and WCAG standards.
• Usability: Mandates adherence to industry best practices for website usability.
• Helpful Resources: Provides links to relevant resources for Section 508, W3C Accessibility Standards, and Usability.

This guide is critical for any contractor involved in designing or maintaining Senate websites. It defines the mandatory standards, approved tools, and processes that must be followed. Failure to comply can lead to default and termination of the contract. Bidders must understand these requirements to accurately scope, propose, and execute any task orders related to website development for Senate offices.

Form / Attachment / Pricing Sheet

This document outlines the "Website Testing and Quality Assurance Requirements" for a contractor. It serves as a guide to ensure that specified website requirements and standards are met throughout the development and deployment lifecycle.

• Defect Review: Contractor must implement a defect assessment process, classifying defects as Critical, Serious (with workaround), or Other. Solutions must be documented and approved before implementation.
• Unit Testing: Evaluate if website components are installed and functioning correctly. Records of unit tests must be maintained.
• Integration Testing: Ensure all website components function together. Evaluation includes form processing, email delivery, web form interaction, link accuracy, graphics behavior, external component interaction, and content migration accuracy.
• System Testing: Verify the entire website functions properly and meets specified requirements. Results must be reported, and defects remediated.
• Readiness Review: Confirm all deficiencies are rectified, content migration is complete, the website functions with a current database, defects are corrected, and the Senate Office is trained for maintenance.
• Pre-Launch Production Testing: Test the website in the production environment before DNS addition to confirm component configurations, interactions, and overall functionality.
• Post-Launch Production Verification: Confirm the website is fully operational, working as designed, and accessible to external visitors after DNS addition.
• Post-Production Monitoring Period: Monitor the website for proper handling of inputs, performance under load, usability, accessibility, fault tolerance, and consistent behavior.
• Website Exception Period: A 30-day period post-acceptance where the contractor provides maintenance and support at no cost.

This document details the rigorous testing and quality assurance processes a contractor must adhere to for website development and deployment. Bidders should understand these requirements to accurately scope their proposals, resource planning, and to ensure compliance with the government's quality standards. It outlines the phases from initial testing through post-launch monitoring and acceptance.

Form / Attachment / Pricing Sheet

This document is a sample Task Order Proposal Request (TOPR) for informational purposes, related to a solicitation for website services. It outlines the requirements and expectations for potential bidders responding to a task order under an existing IDIQ contract.

• Scope: Request for website services for the Office of the United States Senate.
• Statement of Work: Includes design and development, ongoing maintenance, end-user support, training, and post-launch emergency support.
• Project Requirements: Modern, responsive, intuitive, user-friendly design; ability for staff to manage content; adherence to Section 508 accessibility guidelines.
• Specific Sections: Home page features, About section, Constituent Services (including scheduling, flag requests, tour requests, casework, internships, grant support, special recognitions, veterans services), Issues Features, News/Press, Contact, and Social Media.
• Optional Features: About the State, Alternative Language Content.
• Proposal Instructions: Competitive TOPR, no direct contact with the Senate Office, submission via Contractor portal or email, no extensions, specific delivery methods.
• Technical and Administration Questions: Submission via Contractor portal or email.
• Proposals Not Selected: Notification process and debriefing policy.

This TOPR provides detailed requirements for website design, development, and content management. Bidders must understand these requirements to prepare a comprehensive proposal, including pricing for base project and optional features. It also outlines the submission process and evaluation context.

Form / Attachment / Pricing Sheet

This document, "Senate Supported Software List," details the software and applications that the Senate officially supports. It serves as a reference for individuals and offices to understand what software is approved for use and for which support is available. The list is effective as of March 1, 2026, and is updated monthly. It also notes which items may no longer be available for purchase.

• Cybersecurity: Lists supported endpoint security and vulnerability management tools.
• Browsers: Specifies supported web browsers, including version notes for Chrome and Internet Explorer.
• Communications: Details supported email, instant messaging, and video conferencing applications.
• Productivity Suites: Lists supported office applications, including Microsoft Office 365 Cloud Applications and Microsoft Office Enterprise Agreement Software.
• Operating Systems: Outlines supported client and server operating systems.
• Databases: Lists supported database management systems.
• Software as a Service (SaaS): Includes cloud-based applications for project management, storage, translation, and more.

This document is crucial for bidders to understand the existing technology environment and approved software within the Senate. Any proposed solution or service must be compatible with or integrate into this supported software ecosystem. Bidders should pay close attention to the specified versions and any notes regarding support limitations or legacy systems, as this can impact the feasibility and requirements of a potential contract.

Form / Attachment / Pricing Sheet

This document, "Attachment J-005 - U.S. Sergeant at Arms Standard Operating Procedures (SOPS) for Cybersecurity," outlines the comprehensive cybersecurity policies and procedures for the U.S. Senate Sergeant at Arms (SAA) and its contractors. It serves as a foundational document for ensuring the security of Senate information systems and data.

• Senate Cybersecurity Policy: Details the overall policy for protecting Senate unclassified systems and networks, including goals for confidentiality, integrity, and availability.
• SAA Cybersecurity Policy: Specifies the protection of information throughout its lifecycle and the responsibilities of SAA departments.
• Office of the Chief Information Officer (CIO) Cybersecurity Policy: Outlines objectives for security, integrity, and accountability.
• Contractor Responsibilities: A significant portion details cybersecurity requirements for contractors, including adherence to NIST standards, risk assessments, data protection, incident response, cybersecurity training, supply chain security, and software updates.
• System Administration and Computer User Guidelines: Provides specific instructions for system administrators and general users regarding security practices, password management, data handling, and reporting violations.
• Access Control: Covers policies for accessing restricted areas and the use of Senate ID cards.
• Remote Access and Network Security: Details procedures for remote network access, including Multi-Factor Authentication (MFA), and perimeter email filtering.
• Classified Information Handling: Outlines procedures for managing classified national security information.
• Forms: Includes a "Senate System Remote Access Authorization Form" and a "Cybersecurity Responsibilities Acknowledgement" form.

This document is critical for any contractor seeking to work with the U.S. Senate Sergeant at Arms. It establishes the stringent cybersecurity requirements that must be met, including adherence to specific NIST standards, implementation of robust security plans, personnel training, and incident reporting protocols. Bidders must understand and be prepared to comply with these detailed cybersecurity obligations as part of any contract.

Form / Attachment / Pricing Sheet

This document is a Past Performance Questionnaire used in support of source selection for Solicitation Number 2026-R-038. It is designed to gather information on a contractor's past performance.

• Contractor Information: Requires details about the company, contract/task order number, contract type, project title, and performance period.
• Evaluator Information: Requires the name of the evaluating company/agency, the name and signature of the person completing the questionnaire, their role, contact information, time period of involvement, and a brief description of the work performed.
• Performance Assessment: Evaluators rate the contractor's performance across several categories using a scale: Exceptional (EX), Very Good (VG), Satisfactory (S), Marginal (MG), Unsatisfactory (US), and Not Applicable (N/A). Categories include:
  • Quality of Products and Services (Problem Anticipation/Prevention, Problem Resolution, Thoroughness, Accuracy, Overall Quality)
  • Quality of Capabilities (Expertise and Knowledge of Personnel, Ability to provide ongoing application support, Ability to provide applicable and effective solutions)
  • Quality of Deliverables (Project Management, Testing and Quality Assurance, Training, Software Maintenance)
  • Schedule (Services, Products)
  • Cost and Budget Control (Performed within Estimates, Budget Control)
  • Customer Satisfaction (Requirements Gathering, Documentation, Interaction with Users, Responsiveness with Users)
  • Management of Key Personnel (Met Contract Requirements, Retention, Replacement Speed and Quality, Transition to New Key Personnel)
  • Overall Assessment
• Specific Questions: Includes questions on the acceptability of software/websites developed by the contractor and whether the evaluator would contract with the firm again.
• Further Comments: Provides space for specific strengths/weaknesses and troublesome areas of performance.

This questionnaire is to be completed by evaluators to assess a contractor's past performance. Bidders should be aware that their past performance on previous contracts will be evaluated using this form as part of the source selection process for Solicitation 2026-R-038. The completed questionnaire is considered SOURCE SELECTION SENSITIVE INFORMATION.

Form / Attachment / Pricing Sheet

This document, "Attachment J-007 - Past Performance - Website Information," is a form designed to collect detailed information about a contractor's past performance related to website development and management. It is intended for bidders to provide specific data on websites they have developed or managed.

• Contractor Name
• Period of Performance
• Attachment J-007 Point-of-Contact information (Phone and Email)
• For each website (up to 5):
  • Site Title
  • Site URL
  • Date Launched
  • Target Audience
  • Primary and Secondary Programming Languages
  • Description of special mobile device platform specific features/capabilities
  • CMS Software (name and versions)
  • Whether the CMS was developed in-house
  • Whether the CMS was customized for specific client needs (with a field for customization description)
  • Number of users & admins who regularly use the CMS

Bidders must complete this form to provide evidence of their past performance in website development and management. The information submitted will likely be used by the government to evaluate the bidder's experience and capabilities relevant to the opportunity's requirements.

Form / Attachment / Pricing Sheet

This document outlines the procedures for deliveries to the United States Capitol Police Off-Site Inspection Center and subsequent access to Capitol Complex buildings. It details requirements for package labeling, vehicle inspection, and personnel processing.

• Package Labeling: Requires Purchase Order/Contract Number, Deliver To information, Recipient's name, building, room number, and telephone number for deliveries to the U.S. House of Representatives, U.S. Senate, Architect of the Capitol, and Library of Congress.
• Vehicle Reporting: All delivery vehicles must report to the Off-Site Inspection Center at 4700 Shepherd Parkway SW for inspection before proceeding to Capitol Complex loading docks.
• Screening: All delivery contents are subject to x-ray screening prior to access.
• Hours of Operation: The Off-Site Inspection Center operates Monday through Friday, 4:30 AM to 3:00 PM, and is closed on Federal Holidays.
• Personnel Requirements: Delivery personnel must provide picture identification and undergo National Crime Information Center (NCIC) processing.
• Novitex Deliveries: Mail and parcels delivered by Federal Express, UPS, U.S. Mail, and couriers must report to Novitex at 9140 East Hampton Drive, Capitol Heights, Maryland, unless delivering directly from a Federal Agency.
• Capitol Complex Access Letter: A letter on company letterhead, signed by the owner/president/manager, is required for access to Capitol/CVC, House, Senate, and Library of Congress loading docks. This letter must include company name, driver/employee names, SSNs, DOBs, buildings to be accessed, and contact information.

This document is critical for any vendor planning to deliver goods or materials to the Capitol Complex. Bidders must understand and comply with these procedures to ensure timely and successful deliveries. Failure to adhere to these requirements may result in delivery delays or rejection. Key information includes specific addresses, operating hours, required documentation, and the distinction between direct deliveries and those routed through Novitex.