The Scope Letter as the Spine of a Documentation Engagement

A documentation engagement that begins without a written scope letter begins without a perimeter. DC-SERVICES treats the scope letter as the spine of the engagement: it defines the records to be reviewed, the classifications that will be applied, the activities that are explicitly excluded, and the form the deliverable will take. Everything that enters the file later is traceable back to a clause in the letter.

The letter records what the client supplied at intake and what the firm agreed to obtain on the client's behalf. A request the firm will make of a bank, a venue or a counterparty is named in the letter rather than improvised mid-engagement, so that the reviewer reading the final file can see which records were supplied directly and which were obtained under a written request the engagement itself recorded.

Exclusions are stated as plainly as inclusions. The letter records that the firm does not take custody, does not execute transactions, does not advise on positions and does not administer funds. These are repeated rather than assumed because the value of the perimeter depends on the client and the reviewer reading the same boundary at the start of the engagement and at the bottom of the deliverable.

The classification framework is named in the letter. A reader of the final file should not encounter the strength scale, the rejection rules or the gap-flagging convention for the first time inside the findings. Naming the framework at intake means that every classification inside the file is the application of a rule the client agreed to in writing before any record was reviewed.

Deliverable form is fixed in the letter. The file format, the section structure, the sealed-archive copy, the rejection register entry where applicable and the route by which the deliverable reaches the client are all recorded. A change to any of these later in the engagement is recorded as an amendment to the scope letter rather than as a quiet adjustment inside the working file.

Conflicts are checked against the scope before the engagement opens and recorded against the scope during the engagement. A counterparty that appears mid-engagement and triggers a conflict is recorded in the conflicts register, the letter is amended if the engagement continues, and the reviewer reading the file can see when the conflict surfaced and how it was treated rather than encountering a silent narrowing of scope.

Counterparty reviewers care because the scope letter tells them what weight the deliverable carries. A file produced under a letter that names its inclusions, exclusions, framework and deliverable form is a file that can be read at face value. A file produced under no letter, or under one the firm will not show, leaves the reviewer to guess the perimeter and to discount the document accordingly.

DC-SERVICES does not begin a documentation engagement without a scope letter, does not amend the scope outside a written amendment, and does not present a deliverable that exceeds the perimeter the letter defined. The work is documentation: write the scope, work inside it, record amendments where they occur, and deliver a file in which every finding traces back to a clause the client signed before the file existed.