Requirements
Find and define mission needs before an award exists — need, owner, scope, required-by date and PR reference (RQ01, RQ02).
Program originator · Contract specialist · Contracting Officer
/pdcc/acquisitions/requirementsRequirements holds mission needs before any award exists. A requirement and a purchase request (PR) may exist without a PIID — the app never fabricates an award identifier.
- 1
Open Requirements
Acquisitions › Requirements (program personas see *My Requirements*).
- 2
Filter
By office (e.g. Field Operations) and status (e.g. Open).
- 3
Create requirement
Opens Define the requirement (RQ02).
- 4
Fill the required fields
Need, program owner, scope and required-by date.
- 5
Save draft
Partial drafts are saved; only applicable review gates block.
- 6
Define research questions
Optional: continue into Market Research.
Define the requirement (RQ02)
- Requirement
- ID such as
REQ-026-014. - Mission need
- What must be achieved, e.g. *Support field inspection capture during a full shift*. Required.
- Program owner
- Accountable owner (e.g. Morgan Reed). Required.
- Required by
- Date the need must be met (e.g. 1 Feb 2027). Required; dates must be chronological.
- PR reference
- Purchase request (e.g.
PR-DEMO-014). Optional. - Award identifier
- *Not yet awarded* until a verified award link exists.
- Funding
- Unknown funding and estimates stay explicit rather than zero.
Related guides
Requirement baselines and clarifications
Review proposed changes before a new planning baseline, and assign and resolve clarification questions (RQ03, RQ04).
Guided requirement work and procurement handoff
Build a requirement package with guided steps, prepare an internal procurement review package, and track the handoff.
Market Research overview
The research workspace and the MR01–MR21 flow from need to CO report decision.