Right-Sized Public Tech working resource
A fictional, source-linked example with editable requirements, vendor evaluation, pricing, pilot acceptance, and exit materials for public teams.
Fictional worked example. Replace every illustrative entry with locally verified facts and requirements.
Do not place confidential procurement, resident, student, personnel, vendor, security, incident, or controlled information in an unapproved file or location.
Published and sources verified
August 26, 2026
The fictional decision
The example starts with a narrow administrative function: recommend an approved category and destination queue, then draft a factual acknowledgement. Authorized staff retain every decision and action. Eligibility, enforcement, benefits, payment, emergency response, case disposition, and final communication remain out of scope.
The method is reusable. The facts are not.
Use the structure for a real public workflow only after the responsible procurement, operational, legal, privacy, security, records, accessibility, finance, and technology owners verify what applies.
Download the editable pack
Both files are ungated. Nothing is submitted, and no email address is required.
What is inside
Each section creates a decision record that the next section can test. Teams can stop when a gate fails instead of treating procurement as inevitable.
Define the operational job, alternatives examined, affected people, prohibited actions, and unresolved questions.
Name decision owners, reviewers, data authority, retention, deletion, training-use, and human-approval boundaries.
Write outcome and control requirements that can be demonstrated, scored, and accepted.
Require every vendor to run the same representative and failure-focused scenarios.
Combine weighted evidence with mandatory gates that can block advancement regardless of score.
Resolve one material uncertainty with a time, user, data, integration, fallback, and stop boundary.
Compare implementation, operating, human-review, change, export, transition, and shutdown costs.
Record the current authority, source, owner, applicability, and verification date for every local requirement.
Source crosswalk
| Part of the pack | Primary support | Applicability boundary |
|---|---|---|
| Problem fit and alternatives | GSA AI Guide and Digital Services Playbook | Public service design discipline. Adapt to the organization and operating context. |
| Acquisition team, testing, pricing, rights, and portability | OMB M-25-22 and GAO-26-107859 | Federal acquisition sources. They do not automatically apply to state or local organizations. |
| Risk, evaluation, human oversight, and change | NIST AI RMF and Generative AI Profile | Voluntary frameworks unless adopted or otherwise made applicable. |
| State and local procurement life cycle | NASPO Practical Guide | Reference frame only. Verify current local authority, rules, and purchasing method. |
Office of Management and Budget. April 3, 2025. Last verified August 26, 2026.
Cross-functional acquisition teams, competition, testing, performance monitoring, pricing transparency, data rights, portability, privacy, and protection against vendor lock-in.
U.S. Government Accountability Office. April 13, 2026. Last verified August 26, 2026.
Current acquisition challenges, contract considerations, performance oversight, and systematic collection of lessons learned.
National Institute of Standards and Technology. AI RMF 1.0 with current NIST resource updates. Last verified August 26, 2026.
Voluntary risk management across Govern, Map, Measure, and Manage, including trustworthiness considerations throughout the AI life cycle.
National Institute of Standards and Technology. July 26, 2024. Last verified August 26, 2026.
Generative AI risks and suggested actions involving content provenance, information integrity, privacy, security, evaluation, and human oversight.
U.S. General Services Administration. Living public guide. Last verified August 26, 2026.
Problem selection, organizational readiness, integrated teams, buy-versus-build decisions, testing, data rights, sustainable capability, and lessons learned.
National Association of State Procurement Officials. 2024 edition. Last verified August 26, 2026.
A state and local procurement life-cycle frame. Access to the complete publication may require purchase.
U.S. DOGE Service. Current public edition. Last verified August 26, 2026.
User needs, iterative delivery, accountable ownership, security and privacy, and decision-linked measurement.
Separate commercial routes
JS Technology Solutions publishes this resource and also develops software. The neutral pack comes first. Each route below states its current status, fit, and non-fit conditions.
Transportation invoice review
K-12 transportation, finance, procurement, and IT teams
Working product demo available
Grant or subrecipient monitoring
Public program, grants, finance, and compliance teams
Proposed bounded pilot, not a finished product
Capital or IT portfolio intake
Public leadership, finance, facilities, procurement, and IT teams
Proposed bounded pilot, not a finished product
Permitting or licensing intake
State and local permitting, licensing, inspection, and IT teams
Proposed bounded pilot, not a finished product
A different operational lane
Describe the decision, handoff, evidence, and smallest reversible test. This requests a possible scoping conversation. It does not enroll you in resource updates or marketing.