# Scope change record

Keiss Media · Version 1.0 · 15 October 2026

The example is fictional. It demonstrates completion, not the outcome of an actual project.

## Agreed baseline

A Russian-language promotional website with three routes is agreed. The launch date is recorded in a separate plan.

## Proposed change

The client proposes an English version for visitors. This is new scope, not a correction to the Russian version.

## Impact

Translation, editing, a language switch and checks of both versions are needed. Cost and timing are not yet estimated.

## Options

A: move the whole launch. B: launch Russian first, then add English. C: keep one language.

## Decision and authority

Status: proposed. Client and supplier decide after estimation. The work is not yet approved.

## Records to update

After approval, update the page list, translation plan, estimate, second release date and language checks.

## Sources and adaptation

- Civil Service, UK Government: [Contract Management Training & Accreditation Foundation level: takeaway guide, Change control](https://www.gov.uk/government/publications/civil-service-helping-you-with-managing-suppliers-and-contracts/contract-management-training-accreditation-foundation-level-takeaway-guide-html#change-control). Open Government Licence v3.0.

An operational adaptation of GOV.UK change-control guidance. Keiss created the record format and fields. Contract clauses and signature blocks are not reproduced. This worksheet does not select governing law.

Contains public sector information licensed under the Open Government Licence v3.0.
https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/