Guided requirement work and procurement handoff
Build a requirement package with guided steps, prepare an internal procurement review package, and track the handoff.
Program originator · Contract specialist
/pdcc/acquisitions/requirements/guided/startGuided work turns a need into a reviewable package step by step. Section completion is saved as you go and dates are validated against source support.
Requirement package to procurement
1. Start Work
Choose a guided job or describe an intent.
2. Build requirement package
Need, outcomes, funding section, source contracts, transition deliverables.
3. Request inputs
e.g. *Request updated program estimate* — recipients resolved from assignments and confirmed before send.
4. Preflight
Distinguishes review readiness from formal submission authorization.
5. Submit
The package version is frozen.
6. Handoff status
Receipts, owner and checkpoints; a clarification opens a revision path.
When a package is returned
A return creates a revision task and retains the submitted version. A return is not contract execution or a funding obligation.
Follow-on acquisitions
- Choose source contracts — only accessible documents can become sources; each version and its reuse rights are saved.
- Follow-on change comparison — changes save against a source baseline; each accepted change creates a draft revision without modifying the old contract.
- Draft transition deliverable — authorship and source provenance are kept per change; accepting suggested text is not package approval.
Related guides
Start Work and guided jobs
Launch a guided job — define a requirement, research a need, register external work — or describe an intent and let guided work plan it (SH03).
Requirements
Find and define mission needs before an award exists — need, owner, scope, required-by date and PR reference (RQ01, RQ02).
Acquisition Actions: planning workspace
Assemble research, requirement, estimates and review into a versioned plan; prepare follow-on acquisitions (AP01, AP02).