Washington State's Bold Move: What the SAVES RFP Tells Us About Modern Program Administration
Washington State has made headlines in the public sector procurement world by issuing a Request for Proposals (RFP) for a Program Administrator for its SAVES (State Agency Vehicle and Equipment Services) program, alongside a Request for Information (RFI) targeting potential multi-state partnerships. This dual-track approach — simultaneously seeking a program administrator while exploring broader regional collaboration — is a textbook example of strategic procurement thinking. For procurement professionals, business owners, and anyone navigating the RFP landscape, there's a great deal to unpack and learn from Washington's approach.
Let's break down what's happening, why it matters, and what practical lessons you can take back to your own procurement processes.
Understanding the Washington SAVES Initiative
The SAVES program is Washington State's centralized system for managing vehicle and equipment acquisitions across state agencies. By pooling purchasing power, the program allows multiple state agencies to benefit from volume discounts, streamlined procurement processes, and standardized contract terms. It's a classic cooperative purchasing model — and it works.
The recent RFP seeks an external Program Administrator to manage and operate key aspects of the SAVES program. At the same time, the accompanying RFI is designed to gather market intelligence about whether other states might be interested in joining a multi-state cooperative partnership. This second layer is particularly interesting because it signals Washington's ambition to scale the program beyond its own borders.
For procurement professionals, this is a fascinating case study in layered procurement strategy: using an RFP to solve an immediate operational need while using an RFI to explore long-term strategic possibilities.
Why Program Administration Is a Critical Procurement Function
One of the most underappreciated aspects of large-scale procurement programs is the role of the program administrator. When people think about procurement, they often focus on the vendor selection process itself — the RFP, the evaluation, the contract award. But what happens after the contract is signed? Who keeps the engine running?
The Program Administrator's Role
A program administrator in a cooperative purchasing context is responsible for a wide range of functions, including:
- Contract management and compliance monitoring — ensuring vendors are adhering to agreed-upon terms and pricing
- Participant onboarding — helping new agencies or organizations join the program and understand how to use it
- Reporting and analytics — tracking spend, utilization, and program performance
- Vendor relationship management — serving as the primary point of contact between the contracting authority and vendors
- Stakeholder communication — keeping all participating entities informed and engaged
When you consider that a multi-state partnership could involve dozens of state agencies, hundreds of vendors, and billions of dollars in procurement activity, the importance of having a competent, experienced program administrator becomes crystal clear.
The Risk of Getting It Wrong
Poor program administration can unravel even the best-designed procurement program. Without strong oversight, contract terms can drift, pricing can become inconsistent, and participating agencies can lose confidence in the program. In the worst cases, non-compliance and audit failures can result in significant financial and reputational damage.
Washington's decision to issue a formal RFP for this role — rather than simply extending an existing contract or making a sole-source award — reflects a commitment to competitive, transparent procurement. That's a best practice worth emulating.
The Multi-State Partnership Angle: Why RFIs Matter
The RFI component of Washington's strategy deserves special attention. While an RFP is a formal solicitation with the intent to award a contract, an RFI is a softer, exploratory tool. It's used to gather information from the market without making any commitments.
In this case, Washington is using the RFI to test the waters with other states. Are there states that would benefit from joining a SAVES-style cooperative? What capabilities would they bring? What would they need from a partnership structure? The answers to these questions will shape how Washington designs any future multi-state program.
When to Use an RFI vs. an RFP
For procurement professionals who may be less familiar with the distinction, here's a quick breakdown:
RFI (Request for Information):
- Used early in the procurement process
- Non-binding and exploratory
- Helps the issuing organization understand the market landscape
- Responses inform the design of future RFPs or program structures
- Low barrier to participation for respondents
RFP (Request for Proposals):
- Used when the organization is ready to make a procurement decision
- Formal and binding upon award
- Requires detailed proposals from vendors
- Evaluated against specific criteria
- Results in a contract
Washington's use of both instruments simultaneously is a sophisticated approach. The RFP addresses an immediate need, while the RFI lays the groundwork for future expansion. Procurement teams working on complex, multi-phase programs should consider whether this dual-track model could work for their own initiatives.
Key Lessons for Procurement Professionals
Whether you're working in state government, a private corporation, or a nonprofit organization, Washington's SAVES procurement offers several actionable lessons.
1. Define the Scope of Program Administration Clearly
One of the most common mistakes in procurement RFPs is vague scope definition. If you're hiring a program administrator — whether for a cooperative purchasing program, a technology platform, or a managed services arrangement — you need to be precise about what that role entails.
Your RFP should clearly articulate:
- The specific functions the program administrator will be responsible for
- The performance metrics they will be held to
- The reporting relationships and governance structure
- The tools and systems they will be expected to use or implement
- The transition plan if a current administrator is being replaced
Vague scope language leads to vague proposals, which makes evaluation difficult and increases the risk of post-award disputes.
2. Use Market Intelligence Before You Write Your RFP
Washington's RFI is a reminder that good procurement starts with good research. Before you write an RFP, it's worth investing time in understanding the market. Who are the potential vendors? What are the going rates for the services you need? What innovative approaches are vendors using that you might not have considered?
This market intelligence can come from formal RFIs, industry reports, peer conversations, or even informal market scans. The goal is to ensure that your RFP reflects current market realities and doesn't inadvertently exclude strong candidates through overly prescriptive requirements.
3. Build Evaluation Criteria That Reflect Your Real Priorities
For a program administrator role like the one Washington is seeking, technical capabilities are important — but so are softer factors like communication skills, relationship management experience, and cultural fit with public sector norms. Your evaluation criteria should reflect the full picture of what success looks like.
Consider weighting criteria such as:
- Relevant experience with similar programs
- Proposed staffing and organizational structure
- Technology and reporting capabilities
- References from comparable engagements
- Pricing structure and value for money
- Approach to stakeholder engagement
A well-structured evaluation matrix helps ensure that the selection process is fair, transparent, and defensible.
4. Think Long-Term When Structuring Contracts
Multi-state partnerships, in particular, require contracts that can accommodate change over time. New states may join. Program scope may expand. Technology may evolve. Your contract structure should include provisions for:
- Scalability and volume adjustments
- Amendment processes for adding new participants
- Technology refresh requirements
- Exit provisions and transition assistance
- Performance review mechanisms
Building flexibility into your contracts upfront is far less costly than trying to renegotiate mid-term.
The Multi-State Partnership Model: Opportunities and Challenges
Washington's exploration of multi-state partnerships reflects a growing trend in public sector procurement. Cooperative purchasing programs like NASPO ValuePoint and OMNIA Partners have demonstrated that pooling demand across jurisdictions can deliver significant value. But multi-state partnerships also come with unique challenges.
Opportunities
- Greater purchasing power — more participants mean larger volumes and better pricing
- Shared administrative costs — the overhead of running a program can be distributed across multiple states
- Knowledge sharing — partners can learn from each other's experiences and best practices
- Vendor accountability — vendors serving a multi-state program have more at stake and may perform at a higher level
Challenges
- Governance complexity — who makes decisions when states disagree?
- Legal and regulatory differences — procurement laws vary significantly from state to state
- Technology integration — different states may use different systems that need to communicate with each other
- Equity of participation — larger states may dominate decision-making at the expense of smaller partners
Addressing these challenges requires careful program design, strong governance frameworks, and — you guessed it — a highly capable program administrator.
How Technology Is Changing the RFP Landscape
One thing that's worth noting as we look at complex procurements like Washington's SAVES initiative is how technology is transforming the way RFPs are created and managed. Gone are the days when procurement teams had to start from scratch with a blank document, manually assembling requirements, evaluation criteria, and legal boilerplate.
Today, tools like CreateYourRFP are helping procurement professionals generate structured, comprehensive RFP documents more efficiently. By leveraging AI-powered templates and guided workflows, these tools can help teams articulate their requirements clearly, ensure they haven't missed critical sections, and produce documents that are more likely to attract high-quality responses.
For smaller procurement teams — or for organizations that don't issue RFPs frequently — having access to a smart RFP generation tool can be the difference between a well-structured solicitation and a document that leaves vendors confused and evaluators frustrated. If you're facing a complex procurement challenge similar to Washington's, it's worth exploring how technology can support your process from the very beginning.
What Vendors Should Know About Responding to Program Administrator RFPs
If you're on the vendor side — perhaps a consulting firm, a managed services provider, or a technology company — and you're considering responding to a program administrator RFP, there are a few things to keep in mind.
Demonstrate Operational Depth
Program administration is an operational role. Procurement evaluators want to see that you have the systems, processes, and people in place to actually run the program — not just a polished proposal. Include specific examples of similar programs you've managed, the metrics you achieved, and any challenges you overcame.
Address the Stakeholder Management Challenge
Multi-agency and multi-state programs involve a lot of stakeholders with different needs and priorities. Your proposal should demonstrate that you understand this complexity and have a concrete plan for managing it. Communication plans, escalation procedures, and governance frameworks are all worth addressing explicitly.
Be Transparent About Technology
If you're proposing to use a specific platform or technology solution to manage the program, explain it clearly. Don't assume evaluators are familiar with your tools. Describe what data they'll have access to, how reporting works, and how the technology integrates with existing state systems.
Final Thoughts: What Washington's Approach Can Teach All of Us
Washington State's dual RFP/RFI strategy for the SAVES program is a masterclass in thoughtful, strategic procurement. It demonstrates that the best procurement teams don't just react to immediate needs — they think ahead, explore possibilities, and design processes that can scale and adapt over time.
For procurement professionals, the key takeaways are clear: invest in program administration as a strategic function, use market intelligence tools like RFIs before you commit to a formal solicitation, and build contracts that can accommodate the complexity and change that multi-party programs inevitably bring.
And for anyone who finds the RFP creation process daunting — whether you're drafting your first solicitation or your fiftieth — remember that you don't have to do it alone. Tools, templates, and resources like CreateYourRFP exist precisely to help you build better, clearer, and more effective RFPs from the ground up.
The procurement landscape is getting more complex. But with the right strategy, the right tools, and the right partners, it's entirely navigable.