Writing the Procurement Manual

The problem

RIAC had nine different ways to buy and no written playbook for most of them. The legacy five-phase procedures ended when the executed contract went back to the vendor, which left the entire post-award lifecycle undocumented. The real procedures lived in the heads of experienced staff. That is fragile for an agency, and it is fatal for automation: an AI assistant cannot cite a procedure that was never written down.

What was delivered

• An 87-page Comprehensive Guide covering procurement end to end, written to be executed, not filed.
• A procedure playbook for each of the nine procurement paths: local-funded IFB, federally funded IFB, professional services RFQ (QBS), RFP, PSA and task orders, cooperative agreements, requisitions, sole source, and emergency.
• Threshold and Board-approval rules, codified so the dollar amount tells you the path and the approvals before anyone has to ask.
• A one-to-one crosswalk from every legacy procedure to its OpenGov equivalent, prepared so Legal could review the transition line by line.
• Bonding and liquidated damages frameworks for construction and high-risk actions.

Writing as infrastructure

A manual earns its keep twice. First with people: a new hire can run a cooperative purchase or a sole-source justification from the playbook without pulling a senior buyer off their own work. Then with software: the guide is exactly the corpus a Government Knowledge Assistant retrieves over. When an employee asks the assistant which path a $180,000 professional services buy takes, the citation points to a page of this manual, and the employee can check it before acting.

Why it matters for Munivera

Most agencies are where RIAC started: procedures partly written, partly remembered. Munivera treats the manual as part of the automation work, not a separate consulting product. If a procedure is not written down, an agent cannot cite it; writing it down is therefore step one of making an agent safe.