Back
State of Washington
· State
· Washington
Legislation Tracking System Replacement Solution
PROPOSALS DUE
October 05, 2026, 5:00 pm PDT
Closed
WHAT THEY WANT
(Summarized from the RFP)
The Washington State Department of Revenue is seeking proposals for a replacement of its legacy Legislative Tracking System, a custom-built application created in 2007 that supports the analysis, monitoring, and response to legislative proposals impacting taxes and programs administered by the agency. On average, the Department generates 300 to 500 fiscal notes and 500 to 700 bill analyses per legislative session, with fiscal notes required within 72 hours and responses often needed within 24 hours.
DOCUMENT SET
5 documents
· 4.1MB
CHANGES SINCE PUBLISHED
2 changes
WHAT OTHERS ASKED
190 questions answered
▶
Price Submission: We are seeking clarification regarding the submission of pricing in the proposal. While the first response appears to indicate that no prices are to be submitted, the subsequent responses suggest that pricing is required and may be considered during proposal evaluation. Could you please clarify the intended requirement?
Pricing · Preference
▶
System Integration Inventory Attachment: We are seeking clarification regarding the "System Integration Inventory" - We have not been able to locate the "worksheet" or "prior spreadsheet" within the RFP documents as referenced below – or on the WEBS page as an attachment or amendment. Could you please confirm whether the System Integration Inventory has already been provided? If so, where can we find it? If not, can you clarify when it will be provided?
Administrative
▶
We want to make sure we are scoping and pricing the integration work against the right list. The Tech Stack tab of the Q&A workbook identifies seven systems — Washington State Legislature Web Services, OFM’s Fiscal Note System, SharePoint, DOR Employee Services, DOR Error Logger, the DOR SMTP relay, and SQL Server — with a protocol for each, and we have taken that tab as the inventory TR-602 refers to. BT is named in Section 1.5 of the RFP and in the introduction to Exhibit B Section 4.6 as a required integration, but it does not appear on that tab. Two things would help: First, could DOR confirm that the Tech Stack tab is the intended System Integration Inventory, and whether BT should be read as an eighth entry? Second, if BT is in scope, could DOR provide its protocol and data contract, or indicate when that information will be available? It is the one named integration for which we have no interface detail, and we would rather design and price it than carry an allowance for it.
Scope/requirements
▶
We read the seven items on the Tech Stack worksheet (Legislature Web Services, OFM FNS, SharePoint, Employee Services, Error Logger, SMTP relay, SQL Server) as the complete set of integrations required at initial go-live. BEARS, APIS, EBB and the internal FTE, cost-rule and revenue-fund systems behind B.COM.36 are named elsewhere in the RFP but are not listed there. Please confirm the seven are the full go-live set, or clarify which of the others must be integrated at go-live and their protocol and purpose.
Scope/requirements
▶
Unsuccessful Bidder Intellectual Property: RFP 7.9 states that all proposals and materials submitted become DOR property and that DOR may use information or adaptations of information presented in a response. Please confirm that an unsuccessful bidder retains all ownership and intellectual-property rights in its pre-existing software, methodologies, architecture patterns, configurations, workflows, demonstration materials, concepts, and other intellectual property presented during the proposal or demonstration, and that DOR will not acquire a license or right to use such intellectual property merely because it was presented during this procurement.
Award & contract
▶
Two-Hour Resolution Requirement: Please confirm whether the statement that system issues should be resolved within two hours is a contractual vendor SLA after go-live, an implementation/stabilization expectation, or a description of DOR's desired future internal support capability. If it is a vendor SLA, please identify the applicable severity level and when the two-hour clock begins.
Scope/requirements
All 190 answers open with a free account.
ABOUT THIS RFP
RFP number
DOR-RFP-2026-02
Budget
$1,120,000
Published
Entity type
State
State
Washington
Summarized from the State of Washington portal.
HOW TO SUBMIT
Electronic submission via email to DORbidresponses@dor.wa.gov with subject line 'RFP 2026-02 - LTS Upgrade - [Entity Name]'. Submit administrative documents and full proposals via this email address. Files must be Word, Excel, or PDF attached directly to email; no zipped files.
NAICS CODES & TAGS
541511
541512
541519
Information Technology Support Services
Legislative Strategy
Policy Analysis
ACROSS 539 RFPS
MORE THAN
RFPs changed their terms while active.
25 days is the median window from publication to due date; day 16 is the median first change for the 113 that changed. 539 RFPs published and due: July 23 - Sept. 30, 2026.
Bid on five RFPs, and the odds are better than two in three that at least one changes its terms before the deadline. Larger firms have staff tracking this. Start free and you’ll have it at your fingertips too.
This RFP has closed
Proposals were due October 05, 2026, 5:00 pm PDT. Leads tracks active RFPs from posting to deadline.
