天美影院

Key thematic updates

• Creating a more user-friendly contract;
• Ensuring that the IPR clauses work as intended;
• In order to align with the other Standard Contracts:
  • Adding capped indemnities from the Supplier to the Buyer in relation to wilful misconduct of the Supplier / Supplier Staff that impacts the Contract; and for costs resulting from a breach of applicable Law to do with the Contract;
  • Adding optional capped indemnities from the Supplier to the Buyer in relation to damage / injury caused during delivery or installation of goods; and for costs arising out of recall of goods;
  • Adding a Buyer termination right so the Buyer retains the option to terminate the contract when a Supplier embarrasses or brings the Buyer into disrepute, or diminishes the public trust in the Buyer or where the Supplier made untrue and inaccurate written statements and representations in any written submissions as part of the procurement process;
• Updating as required by PPNs, particularly in respect of GDPR;
• Updating Schedule 7 (Staff Transfer) (TUPE);聽and
• Updating the indexation provisions.

Note: The list is divided into 鈥榯hemes鈥� for ease of use. Corrections of typos, very minor amendments, and renumbered cross-references may not be listed. We refer to the term 鈥楤uyer鈥� here, but the term in the MSC is the 鈥楢uthority鈥�.

Every effort has been made to create a fulsome list of the changes at an overview level. For a full picture of the changes, and to see all relevant clause references, please see the MSC Compare Document, comparing this version 2.1 against the previous version 2.0.

Clause and paragraph numbers refer to the clauses / paras as numbered in v2.1, unless otherwise stated.

List of changes by contract reference

Shorter & easier to use contract

Contracts reference	Area	Change
Throughout the contract	Tidying and optional split out schedules	Updating the MSC so that it is tidier, easier to navigate, more accessible, shorter (due to formatting), and has consistent numbering and clauses. Providing (i) a version of the MSC with the 32 schedules combined; and (ii) a version of the MSC with 32 separate schedules (available upon request from modelservicescontract@cabinetoffice.gov.uk).
鈥楽upply Chain Protection鈥� Core Terms	What is required to be included in sub-contracts	鈥楻unning together鈥� the clauses on what provisions are required to be included/the Supplier must take reasonable endeavours to try to include in sub-contracts entered into wholly or substantially for the purpose of performing or contributing to the performance of the whole or any part of the Contract - depending on whether the contract was entered into before or after the start date. No changes to the content of these clauses.
Throughout the contract	Central Government Body & Crown Body definitions - amalgamation	Deleting the definition of 鈥楥entral Government Body鈥� and replacing the references to this throughout the contract.

IPR working as intended & consistent

Contracts reference	Area	Change
鈥業ntellectual Property Rights鈥� & signature block Core Terms, Definitions Schedule (1), Software Schedule (12), Exit Management Schedule (25) & IPR Schedule (32)	IPR	Making it clearer that where the Buyer is a Crown Body, the Supplier is contracting with the Crown as a whole, and adding guidance about how this interacts with IPR drafting options. Amending clause 17.3 of the Core Terms relating to IPR Claims, so that where a third party IPR claim is anticipated or made and if the Supplier is not able to resolve the IPR Claim, the Buyer can terminate the Contract in accordance with clause 31.1. In the Definitions Schedule (1), amending the definition for 鈥淒eliverable鈥� and 鈥淥pen Source鈥�, and adding as definition of 鈥淥pen Licence鈥� (which refers to and includes Open Source) Updating the Exit Management Schedule (25) at clause 6.7.4 so that the Supplier does not have to return software and Authority-owned IPR to the Buyer at termination or expiry or at the end of the Termination Assistance Period, and deleting previous clause 6.10 about all licences, leases and authorisations being terminated with effect from the end of the Termination Assistance Period 鈥� as this is adequately dealt with in the IPR Schedule (32). Deleting (previous) Annex 1 (FORM OF LETTER RE SUB-LICENSING OF SUPPLIER COTS SOFTWARE AND SUPPLIER COTS BACKGROUNDS IPRS) of the Software Schedule (12). In the IPR Schedule (32): a) Ensuring the IPR clauses cover both software (Specially Written Software) and other types of IPR; b) Aligning the approach to Commercial Off The Shelf software (鈥楥OTS鈥�) and non-COTS, to align with the DDAT Playbook refresh, including: i) Providing that the Buyer gets a licence to COTs software (Supplier鈥檚 own, or a third party鈥檚) at a price and on terms no less favourable than those standard commercial terms on which such software is usually made commercially available 鈥� removing the reference to these licence terms being agreed in line with Annex 1 to Schedule 12 (s a starting point, the Buyer gets the usual licence/EULA when the Supplier uses COTS, rather than extra rights to sublicense and assign and novate COTS); ii) The Supplier having to procure a direct licence to the COTS IPR from the third party to the Buyer, on normal commercial terms, rather than just using all reasonable endeavours to do so; iii) Giving the Buyer 10 working days to reject a Supplier鈥檚 use of COTS software (its own, or a third party鈥檚), and if a Buyer does not reject in the timeframe, the Buyer will have been deemed to approve this use; iv) Removing the ability for the Supplier and any third party) to terminate its background non-COTS IPR licence if the Buyer materially defaults on the licence. c) Ensuring that under drafting 鈥榦ption 1鈥� (Buyer owns foreground IPR, Supplier has licence to this to deliver the contract only) and 鈥榦ption 2鈥� (Buyer owns foreground IPR, Supplier has licence to this to deliver the contract & for commercial exploitation) the IPR licences the Buyer grants to the Supplier for foreground IPR and Buyer background IPR are effectively the same: i) In option 1, these are for the Supplier to fulfil its obligations under the contract, for the Term & any Termination Assistance Period, and can be sublicensed for this purpose. ii) In option 2, these are for the Supplier to fulfil its obligations under the contract and to enable commercial exploitation of the foreground IPR outside the contract. These can be sublicensed for the former purpose and termination / expiry of the contract does not terminate these licences. Buyer needs to approve exploitation of these outside the contract - deemed approval applies, and the Buyer can only refuse this for harm to reputation/interests. Adding in a clause stating that the Buyer has the right to terminate these licences if the Supplier breaches any conditions the Buyer has placed on the use of these licences; d) Ensuring that under drafting 鈥榦ption 3鈥� (Supplier owns foreground IPR, Buyer has licence to this for the current contract) and 鈥榦ption 4鈥� (Supplier owns foreground IPR, Buyer has licence to this for the current contract and other government purposes), the licence to Buyer background IPR is for the Supplier to fulfil its obligations under the contract and to enable commercial exploitation of the foreground IPR outside the contract. These can be sublicensed for the former purpose and termination/expiry of the contract does not terminate these licences. Buyer needs to approve exploitation of this outside the contract - deemed approval applies, and the Buyer can only refuse this for harm to reputation/interests. Adding in a clause stating that the Buyer has the right to terminate this licence if the Supplier breaches any conditions the Buyer has placed on the use of these licences; e) Ensuring that under drafting 鈥榦ption 3鈥� Ensuring that under drafting 鈥榦ption 3鈥� and 鈥榦ption 4鈥� the IPR licences the Supplier grants to the Buyer for foreground IPR and Supplier background IPR are effectively the same (below for the terms of the licence): i) In option 3, these are for the Term & any Termination Assistance Period. ii) In option 4, termination/expiry of the contract does not terminate these licences; f) Amending the approach to the licence the Buyer receives in respect of Supplier background IPR (this is limited to non-COTS IPR, as COTS IPR is dealt with differently - see above) so that where this is (a) embedded in a Deliverable; (b) is necessary for the Buyer to use the Deliverable, or (c) the Deliverable is a customisation or adaptation of Supplier background IPR - the Buyer gets different rights to this: i) In all cases* the Buyer gets a non-exclusive, perpetual, royalty-free, irrevocable, transferable, sub-licensable, and worldwide licence to the Supplier background IPR. *except for 鈥榦ption 3鈥� (Supplier owns foreground IPR, Buyer has licence to this for the current contract), where this is not perpetual. ii) Where this IPR is embedded in a Deliverable - Buyers / transferees / sub-licensees can use, adapt and copy this Supplier background IPR for particular purposes. There are no restrictions on the identity of any transferee or sub-licensee in this case. iii) Where this is necessary for the use of a Deliverable or the Deliverable is a customisation or adaptation of Supplier background IPR - Buyers / transferees / sub-licensees can use, copy, but not adapt, disassemble or reverse engineer this Supplier background IPR for particular purposes. It is transferable to a Crown Body, or any body that takes over the Buyer鈥檚 functions, or any body that is not a direct competitor of the Supplier (subject to, in this case, confidentiality undertakings). It is also sub-licensable to a replacement supplier, subject to confidentiality undertakings. These confidentiality undertakings can be either with the Supplier, in the form of the Confidentiality Undertaking annexed to Schedule 12, or an agreement with the Buyer on terms equivalent to clause 19 Core Terms (Confidentiality). iv) The purposes this can be used for are: 1) In 鈥榦ption 1鈥� and 鈥榦ption 2 - (a) to allow the Buyer or any End User to receive and use the Deliverables; (b) to allow the Buyer to commercially exploit the foreground IPR and foreground IPR Items; (c) for any purpose relating to the exercise of the Buyer鈥檚 (or, if the Buyer is a Public Sector Body, any other Public Sector Body鈥檚) business or function. 2) In option 3 - to allow the Buyer or any End User to receive and use the Deliverables. 3) In option 4 - (a) to allow the Buyer or any End User to receive and use the Deliverables; (b) for any purpose relating to the exercise of the Buyer鈥檚 (or, if the Buyer is a Public Sector Body, any other Public Sector Body鈥檚) business or function; g) Amending the approach (across all options) to the licence the Buyer receives in respect of any background third party IPR (this is limited to non-COTS IPR, as COTS IPR is dealt with differently - see above), so that either (a) the owner of the third party IPR grants a licence to the Buyer equivalent to the licence the Buyer gets from the Supplier for Supplier background IPR (see above for the terms of this licence); or - if the Supplier cannot, after commercially reasonable endeavours get that licence - (b) the Supplier tells the Buyer what alternative licence terms are available from the third party/other third parties and the Buyer accepts this and gets a direct licence from that third party; or (c) the Buyer gives authorisation to use third party IPR without a licence; h) Ensuring coherent provisions for publication of the foreground IPR as open licence by the Buyer if it wishes to under 鈥榦ption 1鈥� (Buyer owns foreground IPR, Supplier has licence to this to deliver the contract only), including removing the indemnity in respect of this, as it is covered by the existing Supplier indemnity to the Buyer for third party IPR claims; i) Moving clauses on the Buyer requiring detailed exploitation information including business plans and financials, and on clawback of any foreground IPR if not exploited by the Buyer to 鈥榦ption 5鈥� (Royalties) (not to be used when 鈥榦ption 2鈥� also used). Retaining clauses in options 3-5 on requiring some information to be provided about foreground IPR exploitation; and j) Amending 鈥榦ption 5鈥� (Royalties) so that the Buyer gets royalties upon Supplier exploitation, if this option is used. Providing a formula for their calculation and provisions around payment and supporting records. If required, the Parties may need to enter into additional agreements/variations in line with this royalties provision.

Alignment of indemnities

Contracts reference	Area	Change
鈥楶rotection of Personal Data鈥� &鈥楩inancial and other limits鈥� Core Terms	Indemnity from Supplier to Buyer in relation to Data Protection 鈥� liability v indemnity	Amending the capped Supplier liability in favour of the Buyer for any Losses incurred if the Supplier breaches the data protection clauses or any Data Protection Legislation, so this is an indemnity instead. The existing liability caps will apply. Making clear that the indemnity at clause 21.1 only applies to the Supplier鈥檚 breaches - i.e. the Supplier would not be expected to indemnify if loss arose due to Buyer breach.
Supply of Goods & 鈥楩inancial and other limits鈥� Core Terms	Indemnity from Supplier to Buyer in relation to delivery of Goods	Aligning the MSC with the Short Form (and Mid-Tier) by including (on an optional basis) capped indemnity from the Supplier to the Buyer in respect of any Loss or injury (whether fatal or otherwise) occurring in the course of delivery or installation then the Supplier shall indemnify the Buyer from any losses, charges, costs or expenses which arise as a result of or in connection with such Loss or injury where it is attributable to any act or omission of the Supplier or any of its Subcontractors or Supplier Staff.
鈥楽upply of Goods & 鈥楩inancial and other limits鈥� Core Terms	Indemnity from Supplier to Buyer in relation to recall of Goods	Aligning the MSC with the Short Form and Mid-Tier by including a capped indemnity from the Supplier to the Buyer against the costs of any Recall of the Goods and give notice of actual or anticipated action about the Recall of the Goods, on an optional basis.
鈥榃arranties鈥� & 鈥楩inancial and other limits鈥� Core Terms	Indemnity from Supplier to Buyer in relation to wilful misconduct of staff	Aligning the MSC with the Short Form and Mid-Tier by including a capped indemnity from the Supplier to the Buyer in respect of wilful misconduct of the Supplier, Subcontractor and Supplier Personnel that impacts the Contract. Removing the reference to 鈥渨ilful default鈥� in the liability cap at clause 23.4, as this will be dealt with in the new indemnity. The higher suggested cap of [200%] is to apply to this indemnity.
Warranties & 鈥楩inancial and other limits鈥� Core Terms	Indemnity from Supplier to Buyer in relation to breaches of applicable law	Aligning the MSC with the Short Form and Mid-Tier by including a capped indemnity from the Supplier to the Buyer against any costs resulting from any Supplier breach of applicable Law to do with the Contract.

Alignment of Buyer termination provisions

Contracts reference	Area	Change
鈥淪upplier Termination Event鈥� Definitions Schedule (1)	Buyer termination right - embarrassment, disrepute or diminishing public trust	Adding in a Buyer termination right, so that the Buyer can terminate the Contract where 鈥渢he Supplier or its Affiliates embarrass or bring the Authority into disrepute or diminish the public trust in them鈥�.
鈥淪upplier Termination Event鈥� Definitions Schedule (1)	Buyer termination right - untrue and inaccurate written statements and representations in any written submissions made by the Supplier as part of the procurement process	Adding in a termination right, so the Buyer can terminate where the Supplier made untrue and inaccurate written statements and representations in any written submissions as part of the procurement process.

TUPE / Staff Transfer

Contracts reference	Area	Change
Staff Transfer Schedule (28)	Relevant Transfer Dates	Amending the references throughout the schedule from 鈥渢he鈥� Relevant Transfer Date(s) to 鈥渁ny鈥� Relevant Transfer Date(s) and from 鈥渢he Effective Transfer Date鈥� to 鈥渢he relevant Relevant Transfer Date鈥�.
Staff Transfer Schedule (28)	Reg 10 Employment Regulations	Amending the references to Reg 10(2) of the Transfer of Undertakings (Protection of Employment) Regulations 2006 throughout the schedule to Reg 10.
Staff Transfer Schedule (28)	Part D 鈥� Pensions is to apply if unexpected transfers	In Parts A, B, and C, amending the provisions dealing with unexpected transfers, by extending the requirement that the new employer comply with applicable law, to also include the new employer complying with the 鈥減rovisions of Part D (Pensions) and its Annexes鈥�, including New Fair Deal.
Staff Transfer Schedule (28)	Part C 鈥� no staff transfer expected	Amending the references throughout the schedules from 鈥淣o Staff Transfer On Start Date鈥� to 鈥淣o Staff Transfer Expected On Start Date鈥�, as well as any reference to agreeing that there 鈥渨ill not鈥� be a relevant transfer to 鈥渋s not expected to be鈥� a relevant transfer.
Staff Transfer Schedule (28)	Reflecting changes to statement of practice, paper, or other guidance in the contract	Rewording the provision dealing with changes to a relevant statement of practice, paper, or other guidance (to include Cabinet Office Statement of Practice on Staff Transfers, the Fair Deal and/or the New Fair Deal) and how these are reflected in the contract via the change control procedure, so that instead of stating that 鈥淎ny changes embodied in鈥� replacements to these documents will be agreed in accordance with the change control procedure, it states that 鈥淎ny changes necessary to this Contract as a result of changes to, or any replacement of鈥� these documents with be changed in accordance with the change control procedure.
Part A, Staff Transfer Schedule (28) & Guidance	Civil Service Compensation Scheme to apply	Including in Part A (first generation outsourcing TUPE transfers) a clause stating that 鈥淭he Supplier acknowledges, in respect of those Transferring Authority Employees who were eligible for compensation under the terms of Civil Service Compensation Scheme (鈥淐SCS鈥�) immediately prior to transfer, that the right to benefits calculated in accordance with the terms of the CSCS will transfer under the Employment Regulations. The Supplier acknowledges and accepts that for any employee who was eligible for compensation under or in accordance with the terms of the CSCS, the right to compensation, is a right to compensation in accordance with the terms of the CSCS applicable at the time at which the employee becomes entitled to such compensation (including voluntary or compulsory redundancy). Suppliers are advised to check the Civil Service Pensions website for the current CSCS terms.鈥� Adding guidance to the MSC Guidance document on the CSCS.
Part B, Staff Transfer Schedule (28)	Identification of transferring former supplier employees in Part B	Deleting the references to 鈥渢he Authority鈥� [not] identifying transferring former supplier employees, where Part B deals with employees transferring unexpectedly, and the resulting obligations and indemnities.
Part B, Staff Transfer Schedule (28)	Reg 13(4) Employment Regulations	Amending the reference to 鈥淩eg 13鈥� of the Transfer of Undertakings (Protection of Employment) Regulations 2006 to 鈥淩eg 13(4)鈥� in para 3.1.8 of Part B.
鈥淎dmission Agreement鈥� Definitions Schedule (1) & Part D, Staff Transfer Schedule (28)	Definition of Admission Agreement	Amending the definition of Admission Agreement at para 1 of the Staff Transfer Schedule by replacing the current definition with 鈥渆ither or both of the CSPS Admission Agreement (as defined in Annex D1: CSPS) or the LGPS Admission Agreement) as defined in Annex D3: LGPS), as the context requires,鈥� so it aligns with how it is defined in Part D. Removing this definition in para 1 of Part D of the Staff Transfer Schedule, to avoid repetition. Amending this definition in the Definitions Schedule, referring to Part D, rather than Part A or B of the Staff Transfer Schedule.
Part D, Staff Transfer Schedule (28)	Definition of Fair Deal Employees	Amending the definition of Fair Deal Employees, by fixing the formatting, so it is clear the final sentence (鈥渨ho at the Relevant Transfer Date are or become entitled to New Fair Deal or Best Value Direction protection in respect of any of the Statutory Schemes or a Broadly Comparable pension scheme provided in accordance with Paragraph 10 of this Part D as notified by the Authority鈥�) applies to each of (a)-(d) of the definition.
Annex D1 Staff Transfer Schedule (28)	Definition of CSPS	Amending the definition of CSPS by replacing the start of the definition 鈥渢he Principal Civil Service Pension Scheme鈥� with 鈥淭he 鈥淎lpha鈥� pension scheme introduced under The Public Service (Civil Servants and Others) Pensions Regulations 2014鈥� and deleting the reference to 鈥渁nd 鈥渁lpha鈥� introduced under The Public Service (Civil Servants and Others) Pensions Regulations 2014鈥� at the end of the definition.
Part E, Staff Transfer Schedule (28)	Definition of DPA	Updating the reference from 鈥淒PA鈥� to 鈥淒PA 2018鈥�.
Annex D3, Staff Transfer Schedule (28)	LGPS Admission Agreement - timing	Amending the clause around the Supplier becoming a LGPS Admission Body, by making it clear that if required, the Supplier will need to enter into an LGPS Admission Agreement 鈥渨ith effect from鈥� the Relevant Transfer Date to enable the LGPS Fair Deal Employees to retain either continuous active membership of or eligibility for the LGPS.
Para 1.6, Part E, Staff Transfer Schedule (28)	Suppliers and subcontractors providing TUPE information about way in which services organised	Updating the clause requiring suppliers and subcontractors to provide information to the Buyer on exit relating to the manner in which the 天美影院 are organised by: a) Requiring this information to be provided within 20 working days; b) Amending sub-paras 1.6.1, 1.6.2, and 1.6.4 so they refer to 鈥淪upplier Personnel鈥� rather than 鈥渆mployees鈥�& including a guidance note at the start of Part E to explain this change.
Part E Staff Transfer Schedule (28)	New clauses - aligning to future delivery models 鈥� avoiding split contracts	Inserting a new clause in Part E stating that 鈥淔rom the date of the earliest event referred to in Paragraph 1.1.1, 1.1.2, and 1.1.3 the Supplier agrees that following a request from the Authority it shall and shall procure that each Sub-contractor shall use reasonable endeavours to comply with any reasonable request to align and assign Supplier Personnel to any future delivery model proposed by the Authority for Replacement 天美影院 within 30 Working Days or such longer timescale as may be agreed. Inserting a new clause in Part E stating that 鈥淎ny changes necessary to this Contract as a result of alignment referred to in [the above Para] shall be agreed in accordance with the Change Control Procedure.鈥�
Para 1.7, Part E Staff Transfer Schedule (28) & Guidance	Additional information about transferring employees to ensure smooth transition and employees being paid	Adding two additional sub-paras so that the Supplier must also provide (for each transferring employee) (a) a copy of any personnel file and/or any other records regarding the service of the Transferring Supplier Employee; and (b) a complete copy of the information required to meet the minimum recording keeping requirements under the Working Time Regulations 1998 and the National Minimum Wage Regulations 1998 to the Buyer/Replacement Supplier. Adding guidance to the MSC Guidance document on the ICO TUPE Guidance.
Part E, Staff Transfer Schedule (28); MT: Part E optional Staff Transfer Schedule (7)	Obligations at relevant transfer date	Amending the time periods for the obligations and indemnities given by the [Former] Supplier in Part E, so that these apply up until (but excluding) the Relevant Transfer Date, since the obligations and indemnities given the [Replacement] Supplier are from and including the Relevant Transfer Date in the remainder of the Schedule. Similarly, Amending the time periods relating to the Replacement Supplier indemnification of the Supplier for financial obligations (e.g. HMRC claims, PAYE and NI contributions), making it clear that this only relates to these financial obligations arising 鈥渙n and鈥� after the transfer date. Amalgamating para 2.2 and (previous) para 2.10 in Part E as these are essentially the same. Para 2.10 will be deleted and any additional wording carried over to para 2.2. Referring to 鈥淪tatutory Schemes鈥� rather than 鈥淪chemes鈥� as this is the defined term.
Annex E2 Staff Transfer Schedule (28) & Guidance	Employee information template 鈥� age / DOB	Updating the template table in Annex E2 for employee details/information by amending the 鈥渁ge鈥� category to 鈥渄ate of birth鈥�. Adding guidance to the MSC Guidance document on the ICO TUPE Guidance.
鈥淪upplier Termination Event鈥� Definition Schedule (1)	Definition of Supplier Termination Event - TUPE related	Amending the definition of 鈥淪upplier Termination Event鈥� so that it covers 鈥渁ny failure by the Supplier to enter into or to comply with an Admission Agreement under Part D鈥� of the Staff Transfer Schedule, rather than 鈥渢he Annex to either Part A or Part B鈥� of this Schedule 28.

Sourcing Playbook & associated Guidance Notes updates

Contracts reference	Area	Change
Standards Schedule (4)	Supplier Code of Conduct update	Updating the references to the Supplier Code of Conduct in the contract to refer to the most recent version of the Code (v3).
Charges and Invoicing Schedule (15) & Guidance document	Index referred to; Indexation included	Amending the indexation clauses by replacing the reference to 鈥楥PI鈥� with a reference to inserting an appropriate index / indices so that Buyers can insert an appropriate index. Updating the indexation guidance in the MSC about the use of appropriate indices, including referring to the updated Sourcing Playbook.
Charges and Invoicing Schedule (15)	What happens if index is revised / missing	Adding some wording into the indexation section to align with the Mid-Tier. This wording covers what happens if an index is (a) updated (for example, due to it being provisional): indexation calculation shall also be updated unless the Buyer and the Supplier agree otherwise and; (b) if an index is no longer published: the Buyer and the Supplier shall agree an appropriate replacement index which shall cover to the maximum extent possible the same economic activities as the original index.
Charges and Invoicing Schedule (15)	Adjustments for deflation	Amending the wording in the Charges Schedule referring only to 鈥榠ncreases鈥� for indexation, to make it clearer that 鈥榙ecreases鈥� will also be adjusted for - referring to 鈥榓djustment鈥� instead.
Charges and Invoicing Schedule (15)	Reference period for index changes	Amending the wording allowing for a period during which Indexation will not occur, which refers to indexation not occurring until the 1st April on second April following the Effective Date, and the adjustment occurring every 1st April after this. Aligning this with the approach in the Mid-Tier, so it states that charges are 鈥渘ot to be indexed for [insert number] years following the Operational Service Commencement Date鈥� (the 鈥淣on-Indexation Period鈥�). Removing the reference to the 1 April date in the annual adjustments part, so this remains annual but does not reference the April date. Amending the wording in the stating that adjustments will be made by multiplying the relevant amount or sum by the percentage increase or changes in the in the relevant selected index published for the 12 months ended on the 31 January immediately preceding the relevant adjustment date, replacing this with Indexation occurring annually on the anniversary of the Operational Service Commencement Date, with it first occurring 12 months after the end of the Non-Indexation Period by reference to the 12 months following the end of the Non-Indexation Period.
Guidance document	Guidance on indexation	Including some guidance in the contract that OBCM can be a helpful compliment to Indexation (where proportionate to use).
Charges and Invoicing Schedule (15)	Excluding from indexation historical costs incurred but not yet recovered through charges	Including wording providing that 鈥渁ny costs charged by the Supplier to the Buyer in respect of Supplier Assets or Buyer Assets (including capital costs and installation, maintenance and support costs) which are incurred by the Supplier prior to the relevant adjustment date but which remain to be recovered through the Charges鈥� are not to be adjusted, and will be exempt from indexation.

DDAT Playbook & associated Guidance Notes updates

Contracts reference	Area	Change
Guidance	Guidance - refer to IPR Guidance Note	In line with the publication of the IPR Guidance Note with the DDAT Playbook refresh, reflecting this guidance in our IPR guidance across the contract and referring out to it.
Sustainability Annex in Standard Schedule (4)	Guidance - Tech Code of Practice & Greening Gov ICT 鈥� Sustainability	In line with the DDAT Playbook refresh, updating the guidance sections of the 鈥楨nvironmental - Further Requirements鈥� section of the Sustainability Schedule to refer to the #12 Tech Code of Practice (Make your technology sustainable), and Greening government: ICT and digital services strategy 2020 to 2025, as places where you might look for sustainability requirements where buying DDAT/ICT.

PPNs

Contracts reference	Area	Change
鈥楶rotection of Personal Data鈥� Core Terms & Definitions Schedule (1), Change Control Schedule (22) & Processing Personal Data Schedule (31)	Data Protection Legislation PPN	In line with PPN 03/22 鈥� Updated Guidance on Data Protection Legislation, amending the data protection clauses in the contract in line with the model clauses in Annex A of that PPN. However, in light of Supplier and Buyer feedback, retaining the wording covering either party as Controller or Processor, the parties as Joint Controllers, and the parties as Independent Controllers, in case one of these scenarios applies, although it is rarer than Buyer as Controller and Supplier as Processor. Adding guidance that the Buyer will be the Controller, and the Supplier the Processor in the vast majority of cases, and Buyers must speak to their DPO if they believe another data processing scenario applies. Retaining the drafting covering transfers outside of the EEA, and responding to other regulatory authorities where the EU GDPR applies (see below). These updates include amendments to the 鈥楧ata Protection鈥� Core Terms and the Data Processing Schedule (31) of the MSC, including additional clauses on instructions infringing legislation, providing assistance for DPIAs, using the term 鈥淒ata Loss Event鈥� rather than 鈥淒ata Protection Breach鈥�, the term 鈥渂est endeavours鈥� as opposed to 鈥渁ll reasonable endeavours鈥� and removing the clause about the Buyer being able to revise data protection clauses on notice to the Supplier. It also covers updated section references in the DPA 2018 and removes references to the parties agreeing to take account of guidance issued by a Central Government Body. These updates include amendments to the Definition Schedules (1), including adding a definition of 鈥淒ata Loss Event鈥�, amending the definitions of 鈥淛oint Controllers鈥�, 鈥淧rotective Measures鈥�, and 鈥淯K GDPR鈥�. Updating the Annex to be completed by the Controller in line with Annex A - Part 2 (Schedule of Processing, Personal Data and Data Subjects) to PPN 03/22. This includes adding a section for 鈥榮ubject matter of the processing鈥� and more details about transfers. In the Change Control Procedure Schedule (22) at para 5.2, amending this clause to state, instead of the 鈥淓uropean Economic Area鈥�, the 鈥淯K, in the event of the Personal Data being subject to UK GDPR, or the EU, in the event of the Personal Data being subject to EU GDPR.鈥�
鈥楳odern Slavery鈥� Core Terms	Modern Slavery PPN	In line with the revised Modern Slavery Procurement Guidance published with PPN 02/23: Tackling Modern Slavery in Government Supply Chains, amending the clauses dealing with modern slavery, in line with the model clauses in Annex C of that document.
Annex 1 鈥楾ransparency Reports鈥� 鈥� Reports and Records Schedule (24)	Procuring Steel PPN	In line with PPN 04/23: Procuring Steel in Government Contracts, including guidance in the transparency reports annexe about when the PPN applies, and the types of draft clauses that will need inserting in this case, to enable the Buyer to collect data and report on steel usage.

Data Protection* protection of Government Data, and Security

*other than GDPR PPN, above.

Contracts reference	Area	Change
Throughout the contract	Exempting some Supplier Data from the definition of Government Data for certain provisions	Carving out 鈥榓ny data which is owned or licenced by the Supplier and is in the joint or independent control of the Parties鈥� from certain data protection provisions which use the definition of 鈥楪overnment Data鈥�: a) the need to destroy storage media holding the Government Data. b) securely erasing Government Data held by the Supplier when requested to do so by the Buyer
鈥楶rotection of Personal Data鈥� Core Terms, Processing Personal Data Schedule (31) & Guidance	Transfers of data overseas	Combining the clauses on transfers of data outside the UK under UK GDPR and transfers of data outside the EEA under EU GDPR, so that this is now contained in one clause (applicable for either party as Controller or Processor, the parties as Joint Controllers, and the parties as Independent Controllers). Aligning these clauses on transfers out of the EEA and UK, across all 3 contracts, and all 3 processing scenarios (either party as Controller or Processor, the parties as Joint Controllers, and the parties as Independent Controllers) - e.g. including references in each to s 119A(1) of the DPA 2018. Adding guidance around the use of Transfer Risk Assessments for transfers overseas.
鈥楶rotection of Personal Data鈥� Core Terms & Processing Personal Data Schedule (31)	Independent Controllers - Replacing 鈥渂usiness contact details鈥� with 鈥減ersonally identifiable information鈥�	In the tables where details of data processing are to be recorded, in the provision for the scenario where the parties are Independent Controllers, replacing the references to 鈥渂usiness contact details鈥� with 鈥減ersonally identifiable information鈥�.
Annex 1 - Protection of Personal Data Core Terms - Processing Personal Data Schedule (31)	Joint Controllers 鈥� cooperation and costs between parties	In the clause that says that when the parties are joint controllers, they must provide the other Party with full cooperation and assistance in relation to particular requests, complaints or to enable the other Party to comply with the relevant timescales set out in the Data Protection Legislation, also cross-referring to the clauses that say one party will be responsible re: Data Subject management. In the clause that says that when the parties are joint controllers, they must use best endeavours to restore, re-constitute and/or reconstruct any Personal Data where it has lost, damaged, destroyed, altered or corrupted as a result of a Personal Data Breach, amending the reference to this being at the Party鈥檚 own cost, so it the cost is met by the Party at fault.
鈥楶rotection of Personal Data鈥� & 鈥楽tandard Contractual Clauses鈥� Core Terms & Processing Personal Data Schedule (31)	SCCs and IDTA Annexes	Amending the MSC drafting so that Buyers can decide whether they wish to include the SCCs and IDATA Annexes to Schedule 31, or instead refer out to these on the ICO or EU Commission websites. Drafting amended in clause 21 of the MSC Core Terms and Schedule 31, where the annexes are referred to, to enable this optionality. Guidance provided about how to choose these options. Correcting a typo in the 鈥楽tandard Contractual Clauses鈥� clauses of the MSC Core Terms, referring to Annex 3, rather than Annex 4 to Schedule 31.
鈥楢uthority Data and Security Requirements鈥� Core Terms & Security Schedule (5)	Protection of Government Data	Amending the requirements in the Security Schedule (5) that Government Data is to be provided in an agreed 鈥渙pen鈥� format upon Buyer request - replacing this with the requirement that it must be an 鈥渁greed format (provided it is secure and readable)鈥�. Amending the requirements in the Security Schedule (5) around Supplier erasure of Government Data on Buyer request, so that Suppliers must certify to the Buyer when this is completed. Stating that where Suppliers are required by Law to retain this data and therefore are not required to delete it, they may only rely on this to the extent required by Law.
Security Schedule (5)	Security - Other	In Security Schedule (5), including the types of Personal Data set out in Article 10 UK GDPR (personal data relating to criminal convictions and offences or related security measures based on Article 6(1)) within the 鈥淪pecial Category Personal Data鈥�.

Miscellaneous

Contracts reference	Area	Change
New clause 鈥楪eneral Provisions on Expiry and Termination鈥� - Core Terms	Consequences of termination - accumulated rights	Adding in a new clause to ensure that, where a right has accrued before termination or expiry of the Contract, that right survives, regardless of whether the clause survives termination.
鈥淪upplier Termination Event鈥� Definitions Schedule (1)	Changes to Definition of Supplier Termination Event - reflecting existing termination right for material breach of Joint Controller Agreement	Adding the existing termination right around the Supplier being in material default of a joint controller agreement into the definition of 鈥淪upplier Termination Event鈥�.
Insurance Schedule (6)	Insurance in the aggregate wording	Inserting clauses on 鈥淢aking sure you are insured to the required amount鈥� stating that 鈥渢he Supplier must ensure insurances that are stated to have a minimum limit 鈥渋n the aggregate鈥� are maintained for the minimum limit of indemnity for the periods specified in this Schedule, and that where the Supplier intends to claim under any of the Insurances for any matters that are not related to the Deliverables and/or the Contract the Supplier shall, where such claim is likely to result in the level of cover available being reduced below the minimum limit of indemnity specified in this Schedule, promptly notify the Buyer and provide details of its proposed solution for maintaining such minimum limit of indemnity.鈥�
鈥楽everance鈥� Core Terms Contract鈥� Core Terms	Severance / invalid clauses	Replacing the current clauses on severance / invalid parts of the contract with the clause 鈥淚f any provision or part provision of this Contract is or becomes invalid, illegal or unenforceable for any reason, such provision or part-provision shall be deemed deleted, but that shall not affect the validity and enforceability of the rest of this Contract鈥�
鈥楪eneral Provisions on Expiry or Termination鈥� Core Terms	Clauses intended to survive termination / expiry of contract	To reflect the new indemnity on the cost of recall of goods, adding this indemnity to the list of clauses surviving the end of the contract.
Throughout the contract	Supplier entering into Contract	Amending the wording within the contract so that the Contract only need be signed by one director/signatory of the Supplier. This includes changing signature blocks and referring to the contact being 鈥渆ntered into鈥� rather than being 鈥渆xecuted鈥� by the Supplier.
Change Control Schedule (22)	Change control - updates to contractual documents	Amending the Change Control Schedule (22) so that the default position is that a Change Authorisation Note and the actual drafting of a change to the contract will be drafted by the Supplier, but the Buyer may direct otherwise, meaning that the Buyer may draft these instead, if it prefers.
鈥楧efinitions & interpretation鈥� Core Terms	Precedence wording	Adding wording to the order of precedence clauses after the reference to Schedule 8 (Supplier Solution) and its Annexes (if any) - namely 鈥渦nless any part of the Supplier Solution offers a better commercial position for the Authority (as decided by the Authority, in its absolute discretion), in which case that part of the Supplier Solution will take precedence over the documents above.鈥�
鈥楶ower of Attorney鈥�	Power of Attorney	Amending clause 5.13 relating to the POA granted to the Buyer, as this is required to be executed by way of deed. Amending this so that, if the Buyer requests, the Parties execute a separate deed to put this in place.

Minor / Clarificatory Changes

Contracts reference	Area	Change
Throughout the contract	Minor non-substantive updates	Correcting typos, removal of square brackets, updating incorrect cross-references.
Throughout the contract	KPIs/Service Levels language	Amending the wording in the contract where incorrect terminology has been used when describing KPIs/PIs/Service Levels/Service Credits etc, e.g. in the Benchmarking Schedule (17) we refer to 鈥淭arget Performance Levels鈥� rather than 鈥淭arget Service Levels鈥�.
Throughout Definitions Schedule (1)	Definitions	Amending the definitions in the contract as required, to reflect all of these changes and otherwise as required, e.g. adding in a definition of 鈥淩ecall鈥� - 鈥渁 request by the Supplier to return Goods to the Supplier or the manufacturer after the discovery of safety issues or defects (including defects in the IPR rights) that might endanger health or hinder performance鈥�, as a result of the insertion of the indemnity from the Supplier to the Buyer in relation to Recall of Goods. [Note - some of these types of definitions may be mentioned elsewhere in the table].
鈥淐ontract鈥� Definitions Schedule (1)	Adding 鈥楥ontract鈥� definition	We have added a definition of 鈥淐ontract鈥� to the MSC, namely 鈥渢he contract between the Authority and the Supplier.鈥�
鈥淪upplier Termination Event鈥� Definitions Schedule (1)	Supplier Termination Event definition - Critical Performance Failure	Amending the first limb (Critical Performance Failure) of the definition Supplier Termination Event by adding 鈥渋n accordance with Clause 7.6鈥� at the end.
鈥淟aw鈥� Definition Schedule (1)	Law definition - Retained EU Law (Revocation and Reform) Act	Amending the definition of 鈥淟aw鈥� to refer to statutes/statutory provisions that may be replaced as a result of the Retained EU Law (Revocation and Reform) Act.
鈥淐rown Body鈥� Definitions Sch
Key Personnel Schedule (29) & Guidance throughout Staff Transfer Schedule (28)	Replacing reference to Start Date with Effective Date	Replacing the references to the Start Date with Effective Date.
Throughout the contract	Replacing reference to Operational 天美影院 Commencement Date with Operational Service Commencement Date	Replacing the references to the Operational 天美影院 Commencement Date with Operational Service Commencement Date.
Throughout the contract	Replacing gendered terminology	Amending use of 鈥渉is/her鈥� to 鈥渢hey/them鈥� wording throughout the contract.
Reports and Records Schedule (24)	Updating Virtual Library	Amending Annex 3 of the Reports and Records Schedule so as to reflect the above changes.
Throughout all guidance documents & contract	Guidance	Amending the guidance documents for the contract, and the guidance in the contract itself, so as to reflect the above changes and otherwise as required, e.g. adding in some guidance for Buyers to consider whether any subcontractors processing personal data should be designated as a key subcontractor, updating the guidance around the Rose Book: Guidance on knowledge asset management in government
MSC Scottish version (separate contract)	Scottish version	Updating this Contract, as required, making sure that any changes reflected elsewhere in the Contract are amended for Scottish or law.