Writing the procurement manual

The problem

RIAC had nine ways to buy and no written playbook for most of them. The legacy procedures ended when the executed contract went back to the vendor, which left the whole post-award lifecycle undocumented. The real procedures lived in experienced staff's heads. That's fragile for an agency, and it rules out automation: an assistant can't 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 paths: locally funded IFB, federally funded IFB, professional-services RFQ (qualifications-based selection), RFP, PSA and task orders, cooperative agreements, requisitions, sole source, and emergency.
• Threshold and board-approval rules, written 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, so Legal could review the transition line by line.
• Bonding and liquidated-damages frameworks for construction and high-risk actions.

If a procedure isn't written down, an agent can't cite it. Writing it down is step one of making an agent safe.

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 which path a $180,000 professional-services buy takes, the citation points to a page of the manual, and the employee checks it before acting.

Why it matters

Most agencies are where RIAC started: procedures partly written, partly remembered. That's why Munivera sells playbooks and operating guides as their own engagement: a guide staff can execute, not a binder on a shelf.