Understand what a mapped or credited requirement does and does not establish.
Follow a requirement through the matrix
Product location: /reqms/traceability
Open Traceability Matrix, select a standard or all standards, and expand a requirement row. Inspect mapped documents and sections, evidence and approved processes.
Your role can hide evidence or process columns. Hidden data is not the same as no evidence or no process. Mapped, no evidence means a documentary association exists without the displayed supporting proof.
Review gaps on the correct axis
Product location: /reqms/gaps
Open Coverage Gaps and select Documentation gaps or Control gaps. A documented requirement can still have no approved process performing it. Draft processes and unresolved clause links do not count as live controls.
Use the row's matrix link to inspect what is missing and choose the appropriate work: document authoring, evidence collection, process approval or link correction.
Apply equivalence carefully
Product location: /reqms/traceability
Choose Direct coverage only, central crosswalk credit, or crosswalk plus your organisation's equivalences. Credit annotates a structural gap; it does not replace a direct mapping or remove the gap from the list.
An organisation equivalence needs a rationale, strength and direction. Equivalent can grant full credit, Partial only partial credit, and Related is informational. A one-way assertion does not imply the reverse. Retiring an equivalence stops its credit immediately.
Export CSV or PDF from the matrix when needed, then check the report's scope and included information before sharing it.