RECORD TRACEABILITY

Good records make the testing program easier to explain.

Consistent employee identifiers, timestamps, user activity and retention rules help turn isolated testing events into a coherent program history.

Use stable identifiers

DTSMS is designed to use organization-assigned employee identifiers rather than Social Security Numbers for routine identification.

Track who changed what

Audit history records user activity and timestamps so administrators can review how a record changed over time.

Apply retention rules deliberately

Different testing records may have different retention needs. DTSMS supports structured recordkeeping so the organization can apply its policy and regulatory obligations consistently.