Policy manuals must balance efficiency with strong governance. Thresholds set when formal competition or specific procurement steps must occur are a crucial control, often tied to laws and policy. Increasing those thresholds to chase efficiency would weaken oversight, reduce competition, and raise the risk of waste or abuse. That’s why choosing that option is something to avoid. By contrast, staying aligned with best practices, being responsive to changing environments, and acting in the government’s best interest are appropriate aims in policy development, helping ensure sound, transparent procurement. Any changes to thresholds should follow formal governance and legal requirements rather than serve as a shortcut for efficiency.

In procurement, risk management is about identifying potential events that could affect the project's objectives, assessing how likely they are and how big an impact they could have, and then prioritizing those risks so you can focus mitigation where it matters most. The best basis for rating and prioritizing risks is the solicitation criteria because those criteria define what matters for the project: the requirements, constraints, evaluation factors, and compliance obligations. When you align risk scoring with the solicitation criteria, you target risks that could prevent meeting the advertised goals—such as technical feasibility, supplier capability, schedule, and cost—and allocate effort to the most significant threats. A properly kept risk register supports this process as a living document that records each identified risk, its owner, likelihood, impact, priority, and planned mitigations. It should be used throughout the procurement lifecycle, not only after award. Relying on external auditors’ reprimands as a basis for risk priorities isn’t appropriate, since those findings do not define the specific risks relevant to the procurement objectives.

Qualitative feedback describes performance through qualities, observations, and meaning using words rather than numbers. It captures how something was done, what stood out, and why it matters—focusing on aspects like style, clarity, engagement, and approach. Because its data are non-numeric and interpretive, describing it as descriptive and conceptual fits best, since it conveys qualities and underlying meaning rather than measurements. Quantitative feedback would rely on numbers and metrics, not descriptive language about quality. Delivery style—formal or informal—refers to how feedback is given, not the inherent nature of the feedback’s content. So the description that fits qualitative feedback is that it is descriptive and conceptual.

Lack of internal risk management during procurement creates exposure in contract performance because the risk allocation and obligations are defined in the contract and tied to what was assumed or promised in the proposal. Contractual risk covers the terms, conditions, warranties, liabilities, and change-management rules that govern how performance is to be delivered and what happens if things go wrong. If these elements aren’t identified and mitigated upfront, performance can be undermined by ambiguous requirements, unfunded or underestimated risks, or unfair liability allocations, leading to disputes, cost overruns, or delays. Proposal risk also matters here because the risks recognized or accepted during the bidding process carry into the contract if not properly addressed before award. If risks aren’t fully understood and priced or contingencies aren’t included, the organization is more vulnerable once performance begins. The other risk categories focus on narrower aspects—price fluctuations, the act of performing itself, or scheduling issues—and don’t capture the root problem: missing internal risk identification and mitigation in both the proposal and contract terms that leads to exposure during performance.