What should be decided before drafting a technology RFP?

Resolve the operating outcome, alternatives, owners, data boundary, evidence method, whole-life cost, acceptance conditions, and locally verified purchasing route before product language takes over.

How can a public team tell whether an RFP is still doing discovery work?

If vendors would need to define the problem, choose the authoritative records, invent the evaluation method, or decide what success means, the project still has material discovery work to complete.

Does this checklist determine whether a solicitation is legally ready?

No. It is an operating readiness aid. Responsible local officials must verify authority, competition, funding, policy, legal requirements, approvals, contract terms, and schedule.

Right-Sized Public Tech release gate

Technology RFP readiness before release

Resolve seven operating, evidence, cost, and ownership decisions before a public technology RFP becomes the discovery process.

The central risk

The RFP should carry a decision into the market. It should not discover the decision for you.

A public technology project becomes harder to compare when the solicitation must define the problem, settle ownership, discover the data, and invent acceptance at the same time. Vendors then answer different versions of the need, even when the document looks detailed.

Use this release gate before drafting product-specific requirements. It does not determine legal readiness. It exposes operating questions that should reach procurement, finance, technology, security, and other responsible officials while the team can still change course.

Run the release gate Take the five-minute pressure test

Decision 1Operating decisionName the outcome, affected users, current baseline, and decision this procurement must improve. Decision 2Alternatives and smallest scopeRecord why process repair, current-system changes, shared service, or a smaller scope are not enough. Decision 3Decision ownersName the operational owner, finance or procurement owner, and technology or security owner. Decision 4Data and system boundaryDefine necessary data, authoritative records, interfaces, access, retention, export, and unresolved discovery. Decision 5Requirements and proofMake each must-have observable through the same demonstration, document, sample, or test for every vendor. Decision 6Whole-life cost and changeInclude implementation, integration, migration, support, usage, renewal, material service changes, and exit. Decision 7Acceptance, monitoring, and local routeDefine acceptance evidence, operating review, remedies, stop conditions, and the locally verified purchasing route.

Neutral next routes

Keep the work centered on the decision.

Pressure-test the project

Produce a scored gap brief before release.

Build the Decision Pack

Record the outcome, owners, evidence, boundary, and smallest test.

Cut the scope

Reduce a broad effort to one responsible working boundary.

Disclosed commercial route

Need facilitation before the RFP takes over?

JS Technology Solutions publishes this free guide and offers a paid Decision-Ready Procurement Sprint. The sprint helps a cross-functional public team resolve one operating decision into a working scope and evidence plan. It does not select a vendor or guarantee a purchasing route.

See the facilitated sprint

Source record

Primary sources behind the release gate

Last verified August 26, 2026

These sources provide useful acquisition, service-design, and control disciplines. They do not make every cited rule applicable to every state, local, or K-12 organization.

Technology RFP readiness before release

The RFP should carry a decision into the market. It should not discover the decision for you.

Supported now

Resolve before release

Keep the work centered on the decision.

Pressure-test the project

Build the Decision Pack

Cut the scope

Need facilitation before the RFP takes over?

Primary sources behind the release gate

Digital Services Playbook

State & Local Government Procurement: A Practical Guide, Fourth Edition

AI Guide for Government

Standards for Internal Control in the Federal Government, 2025 Revision