Workforce Wonkery bee logo

Workforce Wonkery

Policy. Data. Practice. Decoded.

Workforce in PracticeModule 5 of 16Run the Institution
Learner rights
Workforce Wonkery LearningFoundations CourseWorkforce in PracticeQuickstartsTools

Operational learning aid. This AI-assisted module does not receive human legal or compliance review. Verify current official sources and applicable local policy before acting on consequential decisions. Trust standard →

Course HomePart I: Run the InstitutionModule 5 of 16

WORKFORCE WONKERY · Workforce in Practice · Run the Institution

Procure, Contract, and Manage the Relationship

Workforce systems buy services, make subawards, amend agreements, pay invoices, and monitor performance. The hard part is not producing a contract. It is choosing the right relationship, using a defensible process, and managing the agreement from award through closeout.

OUTCOME 1

Distinguish the operating questions behind subrecipient, contractor, and partner relationships.

OUTCOME 2

Connect procurement method, scope, budget, performance terms, monitoring, invoicing, and closeout as one lifecycle.

OUTCOME 3

Recognize when a modification is fixing a legitimate change versus hiding weak planning or performance.

A practical operating model

Use this sequence when the issue lands on your desk.

1
Define the need before the vehicle

Clarify the service, population, result, authority, funding source, and decision owner before choosing a procurement or agreement path.

2
Classify the relationship

Use the substance of the arrangement, not the label on the document, to determine the appropriate relationship and oversight model.

3
Build a decision-ready scope

Describe deliverables, outcomes, responsibilities, data, invoicing, performance, monitoring, and change control clearly enough to manage later.

4
Manage the agreement actively

Review performance, spending, risks, documentation, and emerging changes throughout the term instead of waiting for closeout.

5
Close the loop

Resolve deliverables, property, data, invoices, findings, records, and lessons learned before the relationship is treated as complete.

MAKE THE CALL

A long-time service provider asks for a midyear contract increase because participant demand was higher than expected. What comes first?

Open each option, then compare the reasoning. In practice, the strongest answer often starts by gathering the evidence needed to make the decision defensible.

A. Approve the increase because the provider is performing well

Performance matters, but it does not replace authority, funding, procurement, scope, price reasonableness, or modification rules.

B. Recompete the entire service automatically

Possibly unnecessary. First determine whether the requested change fits the existing relationship and lawful modification path.

C. Test the request against scope, performance, budget, procurement history, authority, and the reason the original amount changed

Strongest starting point. The decision should explain both why the change is needed and why the chosen method is appropriate.

D. Tell the provider to absorb the cost

That may be appropriate in some contracts, but only after the agreement and circumstances are reviewed.

Common failure modes

FailureStronger practice
Starting with the contract templateStart with the need, authority, relationship, and result before drafting the instrument.
Calling every provider a contractorClassification affects procurement, monitoring, risk, and federal award responsibilities.
Monitoring only at year endUse ongoing performance and fiscal signals so problems can still be corrected.
Using modifications to avoid hard decisionsA modification should document a legitimate change, not quietly reset expectations without analysis.

EVIDENCE LENS

Know what kind of guidance you are using.

OFFICIAL RULE

Verify controlling requirements against the official source.

LOCAL DISCRETION

A choice the Local Area may make within governing limits.

OPERATING PRACTICE

A practical management or implementation approach.

WONKERY READ

Interpretation or synthesis, not authority.

Primary authorities to verify: 2 CFR Part 200 → · 2 CFR 200.320 → · WSD18-06 → · WSD24-11 → · WSIN25-17 →

Competency: Governance & Stewardship  ·  Sources last checked: September 22, 2026

KNOWLEDGE CHECK

Apply the lesson.

These are practice questions, not trivia. Decide what you would do before opening the feedback. No response is submitted or stored.

1. A provider is called a contractor in the agreement. Does that settle the classification?
Feedback: No. The substance of the relationship controls. Review what the entity does, the level of discretion, program responsibility, and the applicable federal classification factors.
2. A provider requests a midyear increase. What should be tested before the modification path is chosen?
Feedback: Scope, performance, need, funding, procurement history, price or cost basis, authority, and whether the proposed change remains within an allowable modification path.
3. Why should monitoring begin before closeout?
Feedback: Because performance, spending, documentation, and risk signals can still be corrected during the agreement. Year-end monitoring often discovers problems after the useful management window has closed.
Module 5 of 16Not marked complete on this device.

Progress is stored only in this browser. No account is required and this completion marker is not submitted to Workforce Wonkery.