The Regulatory Perimeter Around Documentation and Record Review

Documentation and record review sit outside the activities the UK and most other jurisdictions regulate as financial services. The work does not touch client money, does not execute trades, does not advise on positions and does not administer funds. DC-SERVICES records the perimeter inside the engagement file so the reviewer reading the deliverable knows precisely what the engagement covered and what it did not, before reading any finding.

The perimeter is operational, not promotional. It is recorded in the scope letter at intake, repeated in the file's summary section, and reflected in every classification inside the file. A finding presented as documentation is structured as documentation; nothing is allowed to drift across the line into territory that would require permissions the firm does not hold or representations the engagement is not equipped to make.

Four activities are explicitly excluded. The firm does not take custody of any client asset, fiat or digital. It does not execute transactions on a client's behalf. It does not provide advice — legal, financial, tax or investment — on any holding the records describe. It does not administer funds, manage portfolios or hold any discretionary authority over client positions at any stage of the engagement.

Two-stage supervisory signoff is recorded in the file as a quality step rather than a regulatory imprimatur. The signoff confirms the reconstruction follows the firm's documented methodology and that the classifications are consistent with the source. It does not confirm legal entitlement, regulatory status or any conclusion the source does not support, and the file says so on the page where the signoff appears.

The rejection register and the conflicts register sit alongside the perimeter as visible governance artefacts. Engagements declined for scope, conflict or evidential reasons are recorded. Conflicts identified during an engagement are recorded. Neither register is shown to the counterparty as proof of quality; they exist so the firm's own discipline is auditable to a regulator or to a successor reviewer if one is ever appointed.

Counterparty reviewers — banks, registrars, counsel, accountants — care about the perimeter because a file that overstates the engagement is a file that cannot be relied on. A documentation deliverable that quietly behaves like an audit, or like advice, invites the reviewer to discount it and to ask for a clean version from a provider whose scope is honestly drawn and visibly enforced on every page.

The perimeter also protects the client. A documentation file delivered under a clear scope does not commit the client to representations the records cannot support, and does not expose the client to claims the engagement did not anticipate. The discipline of saying what was not done is part of the value of saying clearly what was done, and the file is structured so both halves are readable together.

DC-SERVICES does not hold permissions it does not need and does not represent itself as a regulated provider of activities it does not perform. The work is documentation: reconstruct what the records support, classify what they support it to, identify what remains unresolved, and deliver a source-linked file inside a perimeter the engagement file makes visible to every reader at the moment they open the deliverable.