The Rejection Register as a Visible Governance Artefact

A firm that accepts every engagement offered to it produces a file of records about every engagement it accepted. A firm that declines engagements for reasons of scope, conflict or evidential weakness produces, in addition, a record of what it declined and why. DC-SERVICES maintains a rejection register so the second record exists as a visible governance artefact rather than as an undocumented internal judgement.

The register records the date of the approach, the nature of the request, the ground for rejection, and the reviewer who recorded the decision. It does not record the personal data of the party who approached the firm beyond what is necessary to make the rejection auditable, and it does not record commentary about the party that would convert the register into a reputational note rather than a governance log.

Scope rejections cover engagements that would require activities the firm does not perform — custody, execution, advice or fund administration. The register entry records which excluded activity the engagement would have required and that the firm declined for that reason. The reviewer reading the register can see that the perimeter is enforced at intake rather than recovered later inside a deliverable.

Conflict rejections cover engagements where a counterparty, a venue or a previous client creates a position the firm cannot accept without compromising an existing engagement. The register entry names the conflict class — not the parties — and records the decision. The conflicts register sits alongside the rejection register and is used to test the conflict against future approaches as well as the present one.

Evidential rejections cover engagements where the records the client could supply would not support a defensible documentation file. The register entry records the evidential gap that made the engagement unworkable. It does not record speculation about the underlying facts, and it does not characterise the client beyond the documentary position the firm reviewed at intake.

The register is read by the firm's two-stage supervisory signoff as part of routine quality work. Patterns in the register — repeated rejections for the same scope reason, recurring conflict classes, recurring evidential gaps — feed back into the firm's own training, scope-letter drafting and intake checks. Governance is what happens to the register after entries are recorded, not the act of recording alone.

Counterparty reviewers, regulators and successor reviewers care because a firm that can show its rejection register can show that its delivered files are the files it accepted rather than the files it could not refuse. A firm that has no register, or will not show one, leaves the reviewer to infer that every approach was accepted, which is itself a quality signal the reviewer reads against the deliverable.

DC-SERVICES does not present the rejection register as a regulatory licence, does not publish its contents externally, and does not use it as a marketing artefact. The work is governance: record the decisions, audit the patterns, apply the lessons inside future scope letters, and keep a register that a regulator or a successor reviewer could read end-to-end and find consistent with the deliverables the firm produced over the same period.