COR Solutions Services Limited Public canonical commercial-contract templates

This page hosts the canonical, publicly-readable, versioned commercial-contract templates issued by COR Solutions Services Limited. These templates are the legal frame referenced by every COR commercial-client engagement. When a Client signs a Client Profile under a COR engagement, they are bound by the specific versions of the templates identified in their Client Profile as in force at signature date.

Current canonical templates

Machine-readable metadata: current.json · Audit trail of all publications: changelog.md

How a COR commercial engagement is structured

Each COR commercial-client engagement is governed by four documents:

• The Master Services Agreement at the URL above — the relationship terms (parties, term, payment principles, intellectual property, data-protection framework, confidentiality, liability cap, governing law).
• One or more Statements of Work at the URL above — service-specific scope, service-level commitments, sub-processor categories, and data-processing terms.
• A bespoke Client Profile counter-signed by the Client — the only document the Client physically signs. It identifies the Client, lists the Services elected and supported domains, names the specific sub-processors engaged for that Client, and incorporates the MSA and SOWs by reference.
• A bespoke Pricing Agreement counter-signed alongside the Client Profile — the applicable List Rates, applied Credits, elected payment frequency and resulting charges.

Signing the Client Profile is sufficient to execute the entire contract package (per MSA clauses 14.8 and 14.9). The bespoke Client Profile and Pricing Agreement are not published here; they are exchanged privately between COR and the Client.

Immutable versions

Once a versioned URL is published (for example, /msa-v5.pdf), it is never overwritten. A future revision is published at a new URL (for example, /msa-v6.pdf); the original remains available for the contractual audit period of any engagement that referenced it. Existing Clients remain bound by the version they originally signed under unless a re-issued Client Profile or Pricing Agreement is counter-signed referencing a newer version.

Sub-processor changes

The Statements of Work above describe sub-processor categories (for example, "Microsoft 365 backup provider", "endpoint detection and response provider", "application hosting provider"). The specific sub-processors engaged for any given Client are listed in that Client's bespoke Client Profile and are subject to the change-notification procedure in MSA clause 7.5.

Older or superseded versions

Older versions remain accessible at their original URLs for the audit period. There is no directory listing on this site — use the specific URL identified in the Client Profile that bound you to that version.