# Requirements Baseline

An approved, version-controlled set of requirements used as a reference for design, verification, contracts, and controlled change.

- Type: artifact
- Domain: Delivery & agility
- Level: Advanced
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/requirements-baseline/>)

## What it means

A requirements baseline is an agreed snapshot of a requirement set at a meaningful point in a product or system life cycle. The baseline establishes a reference against which later changes and conformance can be assessed; it does not mean requirements can never change, but changes should be visible and governed.

## Why it matters

When products involve contracts, regulation, safety, suppliers, or many dependent teams, an unambiguous reference reduces version confusion and supports impact analysis, acceptance, and audit evidence.

## When to use it

Use baselines where the cost of inconsistent requirement versions is material, especially at contractual or engineering decision gates. Avoid formal baselining for early discovery or low-risk adaptive work where it would freeze assumptions before sufficient learning.

## How it works

1. Define the scope, purpose, required maturity, and authority for the baseline.
2. Verify and validate the candidate requirement set and resolve known conflicts.
3. Approve the set at a named version with its assumptions, status, and effective date.
4. Control access and preserve traceability to designs, tests, suppliers, and releases as needed.
5. Assess proposed changes against the baseline and record authorized revisions.
6. Retire or supersede the baseline explicitly when a new reference becomes effective.

## A practical example

A payments platform baselines the requirements for a regulated authentication release before two vendors begin implementation. A later exemption-rule change is assessed across contracts, interfaces, tests, and launch timing, then incorporated as a new approved version.

## Where it breaks

Baselines impose configuration and review cost and can encourage false certainty. Premature baselines create change bureaucracy, while stale references are worse than no baseline. They confirm agreement on a version, not that the requirements are valuable or complete.

## Common mistakes

- Treating a baseline as a permanent ban on change.
- Baselining requirements before verification and validation.
- Failing to identify which version suppliers and teams are using.
- Applying formal baseline control to every small product decision.

## Sources

1. [Needs, Requirements, Verification, and Validation Management](<https://www.incose.org/docs/default-source/working-groups/requirements-wg/needsandrequirementsmanual/nrm_section_14_nrvv_management_042924.pdf>) — International Council on Systems Engineering · Professional engineering guidance
2. [Delivering Successful Projects Every Time](<https://www.pmi.org/learning/library/delivering-successful-projects-requirements-management-7020>) — Project Management Institute · Professional conference paper

## Related topics

- [Requirements Management](<https://wiki.soroush.uk/topic/requirements-management/>)
- [Requirements Traceability](<https://wiki.soroush.uk/topic/requirements-traceability/>)
- [Change Control](<https://wiki.soroush.uk/topic/change-control/>)
