How do we prove every requirement was delivered and tested?
Missing requirements traceabilityConnect each accepted requirement to its delivery and verification evidence. Traceability should reveal omissions and changes, not become a spreadsheet maintained only for an audit.
What to do now
- Assign stable requirement identifiers
- Link requirements to deliverables
- Link deliverables to verification evidence
- Review gaps before acceptance
When to escalate
Escalate when
A mandatory requirement lacks delivery or test evidence.
Who decides
The scope owner and authorized sponsor
Example
An export requirement links to the implemented report, test result, and business acceptance record.
Mistake to avoid
Counting completed tasks as proof that all requirements were satisfied.
Prevent a repeat
Review ambiguous requirements and unresolved acceptance conditions before the affected work begins.
Suggested ApprovedFlow setup
- Projects
- Tasks
- Documents
- Approvals
Keep the agreed scope and acceptance evidence with the project; record any proposed change and its decision separately. See the platform
Related cases
- A requirement changed after testing began. How do we handle it?Late requirement change
- The requirements say the system must be user friendly. How can we test that?Untestable requirement
- An acceptance test fails because the requirement was wrong. What should happen?Requirement validation failure
- We want to prove our AI feature works. What should we test?Missing task-specific evaluation