DC-Services UK Transparent Process

Visible signoff record on every release

When a release reaches the counterparty it carries two named signatures and a numbered release identifier. The counterparty can read both names, verify them against the scope letter and the conflicts outcome, and quote the release identifier in their own files. The internal mechanics of the two-stage supervisory signoff are defined on its own page; the counterparty's view is the signed cover and the numbered release.

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

Visible delivery and receipt trail

Releases reach the counterparty through a single outbound channel managed by the secretariat. The counterparty signs a delivery receipt; that receipt closes the release on the matter file. Re-sends, re-issues and partial extracts all carry their own logged receipts. The counterparty therefore holds a matched pair of documents — release and signed receipt — for every item the firm has sent out.

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

Visible boundary at the point of request

If a counterparty requests an activity the firm does not perform, the visible response is a written decline at intake with a reason filed against the matter. The counterparty sees the decline; they do not receive a partial workaround. The full list of declined activities, and the reason they sit outside the firm's mandate, is published on the clarity check page so that compliance teams can verify the boundary before they ask.

Visible route to questions after release

After a release reaches the counterparty, follow-up questions are routed to the secretariat rather than to the named practitioners. The counterparty sees one inbound contact and one set of logged answers. The reason that the secretariat owns this channel — conflicts, sealed archive, single outbound — is documented on its own page and is not restated here.