PKPEEK Docs
Docs/Requirements & acquisition planning

Requirement baselines and clarifications

Review proposed changes before a new planning baseline, and assign and resolve clarification questions (RQ03, RQ04).

Program originator · Research owner

/pdcc/acquisitions/requirements?screen=RQ03
Live walkthrough · Requirement baselines and clarifications
/pdcc/acquisitions/requirements?screen=RQ03
/pdcc/acquisitions/requirements?screen=RQ04

Requirement baseline (RQ03)

A baseline is the approved version of a requirement (e.g. REQ-026-014 v1.0). Proposed changes are reviewed against it before anything changes.

Baseline
The approved version.
Proposed change
e.g. *Delivery target scenario only*.
Current target / Scenario target
e.g. 60 vs 90 calendar days.
Approval state
e.g. *Baseline unchanged*.
  1. 1

    Compare

    Review the proposed change next to the baseline.

  2. 2

    Keep baseline

    Scenario stays a scenario; nothing changes.

  3. 3

    Or request formal revision

    Routes through the configured program review and flags dependent work.

Heads up — Scenario changes never alter approved requirements. A suggestion (including from Scout) cannot silently change a baseline; accepted edits create an attributable revision.

Clarifications (RQ04)

When something in the need is uncertain — e.g. *What workload defines a full inspection shift?* — assign a clarification question.

  1. 1

    Add clarification

    Question, requested from, due date and affected requirement element (e.g. R1 runtime).

  2. 2

    Save clarification

    The owner sees it in My Work.

  3. 3

    Answer

    The owner responds; the answer creates a new need version and identifies affected findings.

Note — Required clarifications block only the affected downstream actions under the active workflow. Unresolved questions stay visible — the app never invents missing requirements.