General Contractor Procurement Playbook

The operating principles

• Start with scope and decision criteria, not a bidder list.
• Use one controlled source of truth for current procurement documents and revisions.
• Qualify proportionally to risk instead of using either no gate or an excessive gate for everything.
• Match the request type to the decision: RFQ for defined scope, RFP when approach and best value matter.
• Give active bidders materially consistent information.
• Preserve submitted offers; show normalization and evaluation adjustments separately.
• Keep accountable people in control of contractual and award decisions.
• Carry final clarifications into execution so procurement promises do not disappear at handoff.

The playbook by stage

• Stage 1 — Package definition: identify trade, scope, documents, schedule, logistics, commercial requirements, and what the award decision must optimize.
• Stage 2 — Sourcing: identify relevant firms using geography, trade, experience, capacity, relationship history, and project fit.
• Stage 3 — Qualification: verify eligibility, insurance, licensing where required, comparable experience, safety, capacity, and project-specific requirements.
• Stage 4 — Request strategy: select RFQ, RFP, direct negotiation, or another approved procurement path based on scope maturity and risk.
• Stage 5 — Market engagement: issue the controlled package, track bidder status, answer questions, and publish material addenda.
• Stage 6 — Evaluation: level RFQ bids or score RFP proposals against the approved comparison basis.
• Stage 7 — Clarification and award: resolve material unknowns, document the award basis, and obtain required human approvals.
• Stage 8 — Handoff and learning: move final scope into execution and capture vendor performance for the next procurement cycle.

Minimum controls vs. higher-risk controls

The playbook should scale with the work. The same core stages can remain intact while the evidence and approvals become deeper as consequences increase.

• Minimum controls: clear scope, bidder identity, basic qualification, controlled request, response record, comparison, accountable award, and execution handoff.
• Higher-risk controls: deeper qualification, formal scoring, bonding or financial review, stronger approval gates, detailed schedule analysis, negotiated exceptions, and enhanced audit evidence.
• Repeat vendors: reuse verified history but refresh expiring documents, current capacity, and project-specific fit.
• Urgent procurement: accelerate timing without silently removing required authority or losing the reason for exceptions.

The questions every award packet should answer

• What exactly did we ask the market to provide?
• Which firms were considered and why were they included?
• Were the finalists qualified for this specific work?
• Did all active bidders receive the material clarifications and revisions?
• What did each bidder include, exclude, assume, or propose differently?
• How did we normalize or score those differences?
• Why was the selected bidder the best decision under the approved criteria?
• What final clarifications, exceptions, and commitments must appear in the execution documents?

Where the procurement knowledge graph fits

This playbook is the pillar page for the procurement cluster. Each stage links to a deeper guide so a GC can get a fast operating overview here, then drill into the exact problem they are solving without losing the broader workflow.

That structure also makes OttoServ's public knowledge easier for search engines and AI systems to understand: the playbook defines the full topic, while the supporting pages answer narrower questions in depth.

• RFQ Management — controlled quote collection and clarification.
• RFP Management — best-value proposal evaluation.
• RFQ vs. RFP — request-type selection.
• Vendor Qualification — bidder eligibility and project fit.
• Bid Leveling — apples-to-apples commercial comparison.
• Procurement Workflow — the end-to-end sourcing-to-handoff sequence.

How OttoServ helps

OttoServ is being built to help general contractors and service businesses move from scattered procurement activity to a structured, auditable workflow. The goal is not to replace human judgment; it is to make the information needed for that judgment easier to collect, compare, and act on.

• Turn the playbook into a connected operating workflow instead of a static policy document.
• Carry project, bidder, qualification, request, response, clarification, and comparison context forward between stages.
• Use AI assistance on repetitive document and comparison work while keeping human authority explicit at controlled decision points.
• Build a reusable performance history so future sourcing and qualification decisions improve with real project evidence.

Frequently asked questions

What is a procurement playbook for a general contractor?

A procurement playbook is a repeatable operating framework that tells the team how to move from scope definition through sourcing, qualification, bidding or proposals, comparison, award, and handoff while preserving decision history and human accountability.

What should be standardized in a procurement playbook?

At minimum: package naming, scope references, bidder status, qualification gates, RFQ/RFP rules, question handling, addenda, bid comparison, award approvals, and the transfer of final clarifications into execution documents.

Should every trade use the exact same procurement process?

No. The operating framework should be consistent, but the depth of qualification, request format, evaluation criteria, and approval gates should reflect trade risk, contract value, schedule sensitivity, and project requirements.

Where does AI fit in a procurement playbook?

AI can assist with document intake, extraction, bidder tracking, gap detection, comparison, and drafting clarification questions. Final contractual commitments, exceptions, negotiations, and awards should remain under authorized human control.

How do you keep procurement from becoming too bureaucratic?

Use proportional controls. Small, low-risk scopes should pass through a lighter version of the same framework, while high-value or high-risk packages receive deeper qualification, evaluation, and approval.

What is the biggest benefit of a procurement playbook?

Consistency. The team spends less time reinventing the process, reduces lost context between stages, and creates a clearer record of what was requested, compared, clarified, and awarded.

Explore the procurement knowledge hub

These guides are intentionally connected. Start with the playbook or workflow for the full process, then move into the specific procurement decision you are working through.

Related reading