Requirements Traceability for UAT
Connect business requirements to test cases and their results. Keep parent and child requirements organized so reviewers can follow what has been checked.
Start with the business requirement
Write requirements around observable outcomes. Separate functional behavior from non-functional expectations, add priorities and use acceptance criteria to explain what the reviewer should look for. Specific requirements make test coverage easier to discuss.
Keep parent and child requirements together
Use a parent for the overall capability and child requirements for its individual behaviors. For example, FR-1 might cover account access, with FR-1.1 covering sign-in and FR-1.2 covering password recovery. Codes belong to a project: another project can have its own FR-1.
Follow the evidence behind coverage
Link requirements to test cases, then review the execution results and any defects. A link alone does not show that a requirement passed: reviewers also need the outcome, the evidence and the unresolved risks. Use those details when discussing readiness with business stakeholders.
Bring an existing matrix into the workspace
Download the workspace matrix template, follow its column structure and review the import validation feedback. After importing, check the parent relationships and test-case links. Preserve meaningful references from the source rather than relying on description text alone to connect records.