RegTech and Compliance · 27 March 2026 · 9 min read

Scope Letters and Why Engagement Boundaries Are Written Down

A scope letter is the part of the engagement that survives goodwill. DC-Services writes the perimeter early because the perimeter is what gets tested later.

Engagements drift when their boundaries live in goodwill rather than on paper. A scope letter is the part of the file that survives a change of contact, a change of expectations, or a counterparty who reads the engagement differently a year later. DC-Services writes the perimeter early, lists explicitly what falls outside it, and keeps a register of items rejected against that perimeter — because the perimeter is the part that gets tested.

Defining The Perimeter Before The Work

The scope letter identifies the entities covered, the date range, the document types in play, the deliverables, and the explicit limits on what we will and will not do. It is short on aspiration and specific on operation: the work is described in terms anyone reading the engagement in two years would still understand.

Where a request describes a vague exploratory theme, the scope letter narrows it to a specific evidential question that records can actually answer. Themes that resist narrowing are returned for redefinition rather than accepted in optimistic terms; clairvoyance requires a different regulatory framework, and we do not offer it.

What We Will Not Do, In Writing

Negative scoping is more useful than positive scoping for keeping an engagement honest. The letter records, by name, the things we are not doing: no legal advice, no tax advice, no investment advice, no custody, no execution, no fund administration, no opinions on regulatory acceptance. The list is unromantic and shortens later disagreements.

When stakeholders later push into excluded territory, the letter is the reference. The rejection is recorded in the engagement register with the date and the basis, and the work continues on the agreed perimeter rather than drifting into territory the engagement never covered.

Conflicts Check Before Acceptance

Before the letter is issued, the proposed parties are checked against the conflicts register. Prior mandates, related entities and contested assets are identified. Where a real conflict exists, the engagement is declined or restricted; where a potential conflict exists, the restriction is written into the scope letter rather than left to be remembered.

The conflicts check is recorded as having happened, with the conclusion attached. An engagement accepted without a recorded conflicts check is an engagement whose independence cannot be defended on demand.

Evidence Acceptance Rules

The scope letter sets the rules for the form in which evidence will be accepted into the file: format, metadata, source attribution, and the minimum information required for a record to be usable. Submitting parties then know what to provide before they provide it, which reduces the volume of unusable material that has to be turned away later.

Non-compliant submissions are routed to the rejection register with the specific reason. The register is itself part of the file and is producible on request, so the discipline holds up under review rather than depending on goodwill at the time.

Changing The Perimeter, Deliberately

Engagements legitimately grow. A new question, a new entity, a new date range — all of these can be added, but they are added in writing, with the new perimeter recorded as an amendment rather than absorbed silently. The amendment runs through the same conflicts and acceptance checks as the original.

An engagement that has grown without amendment is one whose boundaries no longer match the letter, and the disagreement between the work being done and the work that was agreed will, eventually, surface awkwardly. Writing the change down is faster than apologising for it later.

Scope Letter and Perimeter Checklist

List the entities, accounts and date range covered.
Identify the document types within and outside scope.
State explicitly what we will not do, by name.
Run the conflicts check and record the conclusion.
Set the evidence acceptance rules and rejection criteria.
Provide a route for amendment in writing only.
Make the rejection register producible on request.

Frequently asked questions

Why does a scope letter need to list what we will not do?

Because that list is what survives goodwill. When stakeholders later expect work outside the engagement, the letter is the reference and the conversation is short rather than acrimonious.

How does the rejection register work in practice?

Submissions or requests that fall outside the perimeter are recorded with the date and the specific reason for rejection. The register is part of the file and can be produced on request, so the discipline is auditable.

What is the role of the conflicts register?

Prospective parties and assets are checked against prior mandates and known relationships before the letter is issued. The check and its conclusion are recorded. An engagement whose independence is not documented in advance is harder to defend afterwards.

Can the engagement be expanded later?

Yes, in writing. New entities, dates or questions are added by amendment, with the conflicts and acceptance checks rerun on the new perimeter. Silent expansion is the route to disputes about what was actually agreed.

Does a scope letter guarantee a particular outcome?

No. It defines the perimeter of the work. Conclusions are still drawn from the evidence available, and the engagement does not promise legal validity, regulatory acceptance, or recovery — none of which are within the documentation remit.

The perimeter is the part of the engagement that gets tested. Written early, it shortens disputes; left to memory, it produces them.