DC-Services UK Company History

Formation of the supervisory QA function

A defined supervisory QA function was created and staffed with named individuals who do not perform production work on the documents they review. The function operates as the second stage of every release. Its formation is the reason the firm uses the term named-supervisor framework rather than peer review; the supervisor is a defined role with a fixed scope of authority, not a colleague reading a draft. The function maintains its own standing procedure and reports to the board on a fixed cycle.

• ›Written intake brief signed by the client
• ›Conflicts screen and independence check
• ›Defined deliverable list and retention envelope

Retention policy and sealed archive

A written retention policy was adopted that defines the sealed archive: how records are stored, who may unseal them, how unsealing is logged, the minimum retention period, and the conditions under which a record may be destroyed. Before this policy, retention practice was based on staff convention; afterwards, every retention decision is taken against a written rule. The policy is referenced on every released document so that the recipient knows the storage commitment under which the record exists.

• ›Source hashing at intake
• ›Role-based, time-bound access
• ›Two-stage review before release

Codification of exclusions

The firm's board moved the exclusion list from the remit document into a standing board register. The effect of the move was procedural rather than philosophical: amending the exclusion list now requires a board resolution. This change closed the possibility of an exclusion drifting through changing custom rather than through a recorded decision. The current exclusion list, in the same form as the day it was codified, appears on the public Clarity Check page so counterparties read the same wording the board reviews.

Annual review cycle and methodology change log

The firm adopted a fixed annual review of methodology, schemas and supervisory QA procedure. Outputs of the review are written into a dated change log. Interim revisions between annual reviews follow the same dating rule. The cycle has produced incremental, traceable change to the documentation framework rather than periodic overhauls; the public methodology pages reflect the current state at the date of the most recent log entry.