Effects Spreadsheet
Overview
The effects spreadsheet (also known as Table of Effects Spreadsheet or TOES) is a record of the effects that a newly made item of legislation has on existing legislation.
You can read more on the background to TOES (Table of Effects Spreadsheet) in the Introduction to Record Effects.
The columns within the effects spreadsheet are populated during the record effects task with the data described below.
You can view the effects spreadsheet for an item of legislation that has had its effects researched by typing the following links in you browser (replacing <type> (e.g. ukpga, uksi, ssi, etc.), <year> and <number> with the appropriate values):
Affected document
https://editorial.legislation.gov.uk/changes/affected/<type>/<year>/<number>/data.xls?extended=full-with-co&sort=affecting-year-number
Affecting document
https://editorial.legislation.gov.uk/changes/affecting/<type>/<year>/<number>/data.xls?extended=full-with-co&sort=affecting-year-number
TOES Style Guide
The table below gives a summary of the style requirements for data entry into TOES, to be used by more experienced editors. For all the detail about the Record Effects task, where TOES gets populated with the information from the Identify Effects task, please see the Record Effects page.
Leading zeros: numbers entered into TOES should include leading zeros as indicated in the table below. Note that the number of leading zeros that need to be entered may vary (e.g. s. 0001 but reg. 001), and not all columns require leading zeros to be entered (e.g. free text fields).
| Column heading | Description of column contents | Column entry format | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Affected Legislation | The affected legislation is the item of legislation to which an amendment will be applied.
The affected legislation column is populated with the legislation number, which identifies the year, document number and type of legislation. Examples of these are shown in bold for each type of legislation in the column to the right. Note that the legislation number will either be made up of 3 or 4 numbers (depending on the document type) and should include leading zeros, if appropriate (e.g. 001, 0001). The preparation task Record Effects guidance on Affected and Affecting Legislation gives more detail about the different types of legislation and corresponding formatting that you should expect to see in this column. |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Affected or Affecting Provision
(for the Affected Provision if a whole document is the affected provision, see the second to last column in the row above)
|
The affected provision(s) is the provision of the affected legislation to which an amendment will be applied.
The preparation task Record Effects guidance on Affected and Affecting Provisions sets out the different levels of provision and the corresponding formatting that you should expect to see in this column. Note that the affected provision is entered from the point of view of the result of the effect, for example where a provision is to be renumbered (e.g. where s. 12 is being renumbered as s. 12(1)) then the result of the renumbering (s. 0012(01)) will have been entered as the affected provision. There should be one affected provision per row, with the exception of affected unbroken consecutive ranges of provisions/sub-provisions for example (e.g. s. 0010-0015).
The affecting provision column will be populated with the lowest, numbered (or lettered as the case may be) affecting provision/sub-provision which contains the amendment to be made to the affected legislation. The preparation task Record Effects guidance on Affected and Affecting Provisions sets out the different levels of provisions and the corresponding formatting that you should expect to see in this column.
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Type of Effect | The “type of effect” column captures what an affecting provision does to an affected provision. Effects are either textual (altering the text of the provision) or non-textual (modifying the provision’s scope or application without actually changing its text). The Record Effects guidance on Type of Effect lists out the different types of effects and the format that you should expect to see in this column. Note, any numbers in this column, whether referring to legislation or provisions, do not need leading zeros (as used in other columns in the spreadsheet, for example, an Act would be entered as “2003 c. 14” in the Type of Effect column, compared with “2003 c. 014” in the Affected Legislation column). Pluralised provisions would be referred to as, e.g. “substituted for ss. 1-5”.
See more on types of effect in Editorial Principles - Effects. |
added inserted substituted omitted ceases to have effect repealed revoked renumbered amendment to earlier affecting provision amendment to earlier Commencement Order knock on effect e.g. applied by 1997 c. 44, s. 32BC(3) (as inserted) applied X construed as one with Y continued/ continued in force excluded explained extended extended (territorially) extended (with modifications) definition extended incorporated incorporated (with modifications) modified power to amend conferred power to apply conferred power to apply (with modifications) conferred power to modify conferred restricted restored functions made exercisable concurrently transfer of functions/ certain functions transferred frequent upratings saving for effects of [legislation] transitional provisions for effects of [legislation] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Affecting Extent and Affecting Territorial Application | The extent of the affecting provision or, if different, the effect itself (or in other words, the geographical jurisdiction or jurisdictions for which the effect is operative) should be entered in the Affecting Extent column for each effect. There is a dropdown menu of the various extents available for you to choose from: | E+W+S+NI
S NI E+W S+NI E+W+S E+W+NI Same as affected | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sav | Savings, transitional provisions and other ancillary provisions which limit or in some other way qualify the scope and application of an effect are entered in this column during the Record Effects tasks.
There is no need to type “with”, “with savings in” or “subject to”, etc in the Sav column, please just enter the number or numbers of the provisions involved. If there are no savings or transitional provisions, etc. enter “No” here to remind yourself that you have researched this. Where there are multiple savings, the savings provisions should be put in numerical order, separated by a space without any punctuation. See more detail about savings in Editorial Principles - Savings. |
The provision format will be the same as used for the Affected and Affecting provision columns, including leading zeros.
e.g. art. 004 45 Sch. 09 para. 006 46 54(01)
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comments for Editor | Comments should be made here where the effect contains any peculiarities that the update editor should be aware of when applying that effect at the end of the process. This generally includes anything that would normally be referenced in the commentary but that doesn’t fit into the rigid Extended TOES schema as well as instances where a power-conferring provision is being imported. | For example:
Also see Record Effects - Comments for Editor. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Notes | Notes are published on the Changes to Legislation pages on legislation.gov.uk for the user’s information and, as such, should be used sparingly.
The usual purpose of a Note is to explain why we have not and will not apply an amendment to legislation.gov.uk and such a note should take the form shown in the next column.
|
“This amendment not applied to legislation.gov.uk. [Explanation].”
See more: Record Effects - Notes. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Suggested Commentary | Where an effect requires a commentary that does not fit into our usual commentary formats and so we need to draft a bespoke version of the commentary that will replace the automatic commentary that would otherwise be generated from the Extended TOES data for that effect, this should be entered in the Suggested Commentary column. If you are considering using this field, please consult with a reviewer about the appropriate wording to use.
See more: Record Effects - Suggested Commentary.
|
“Sch. 1A para. 2 superseded (6.2.2020) by The Administration of Estates Act 1925 (Fixed Net Sum) Order 2020 (S.I. 2020/33), by virtue of para. 3(3) of this Schedule.” | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Appended Commentary | The Appended Commentary column should be used to add additional commentary information that you want to be displayed after the core effect commentary information which will be generated using the preceding Extended TOES columns. It should be worded in our house style exactly as you expect it to appear in the eventual annotation. Unless the appended commentary text is placed within brackets in TOES, the eventual annotation will separate the text of the appended commentary from the rest of the system-generated annotation using a semicolon.
See more: Record Effects - Appended Commentary. |
“S. 10 repealed (1.4.2012) by S.I. 2012/1526, art. 4 (as amended by S.I. 2012/1534, art. 2)”
“Words in s. 14(3) omitted (1.4.2019) by virtue of The Forestry and Land Management (Scotland) Act 2018 (Consequential Provisions and Modifications) Order 2019 (S.I. 2019/734), reg. 1(2), Sch. para. 2; S.S.I. 2019/47, reg. 2” | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Commencement Authority | Enter the details of the provision giving authority for the In Force Date(s) here. Where there is no in force date because the amendment is "prosp.", you should include the commencement provision which gives authority for the amendment to be brought into force prospectively by commencement/appointed day order. If there is no commencement provision and you have to assume the default commencement date then leave this column blank or put a “No” here to remind yourself that you’ve researched this. | The provision format will be the same as used for the Affected and Affecting provision columns, including leading zeros, for example:
art. 001 reg. 001(01) s. 0392
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| IF Date 1, 2, 3 … etc | The In Force Date for the effect is entered here.
Note that there are further, hidden, IFDate and IFDate Qualification columns (labelled IFDate2, 3, etc.) you can use if you need to enter more than one In Force Date and Qualification; you will need to “unhide” them to access these columns. See further: How to enter commencement information in TOES. |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| IF Date … Qualification | The IF Date Qualification column is used to specify the extent to which the commenced provision is being brought into force, for example it may be wholly in force or in force only for some of its purposes, for its whole extent or for only a limited portion of that extent, etc.
There is a dropdown menu pre-populated with the most common IF Date Qualification options, as listed in the next column, see further: |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| IF Date … Other Qualification | If you selected “Other” in the IF Date Qualification column, use this free text field to type the details of the qualification. |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Note that there are further, hidden, IFDate and IFDate Qualification columns (labelled IFDate2, 3, etc.) you can use if you need to enter more than one In Force Date and Qualification; you will need to “unhide” them to access these columns as explained here.
List of all TOES columns
Id
The Id is automatically generated and is a protected column in the spreadsheet. If you try to enter data in this column, a pop-up will state "Do not change effect IDs. When you create a new effect, leave the ID blank. A new ID will be automatically created for it." Select cancel in this pop-up.
The Id is the unique group of numbers and letters that you normally see in XMetaL after the opening "ukl:Commentary" tag of an amendment's annotation.
You do not need to do anything with this column.
Affected Legislation
The affected legislation is the item of legislation to which an amendment will be applied.
The affected legislation column will be populated with the year, number and type of legislation. The preparation task Record Effects guidance on Affected and Affecting Legislation lists the different types of legislation and corresponding formatting that you should expect to see in this column.
Affected Provision(s)
The affected provision(s) is the provision of the affected legislation to which an amendment will be applied.
The preparation task Record Effects guidance on Affected and Affecting Provisions sets out the different levels of provision and the corresponding formatting that you should expect to see in this column.
The affected provision will have been entered from the point of view of the result of the effect, for example where a provision is to be renumbered (e.g. where s. 12 is being renumbered as s. 12(1)) then the result of the renumbering (s. 0012(01)) will have been entered as the affected provision. There will be one affected provision per row, with the exception of affected unbroken consecutive ranges of provisions/sub-provisions for example (e.g. s. 0010-0015).
When carrying out your Update task, you should also check the "Comments For Editor" column for any exceptions to the provision entered in the Affected Provision column. For example, where the affected provision has been drafted in the legislation as an Act or Part or even a range of provisions, but excluding certain provisions (for example, an “Act (except sections 1, 13, 25 and Schedule 1)” is repealed), the affected provision as drafted e.g. “Act” will be entered into column C and the provisions excluded from the amendment will be in "Comments For Editor" (e.g. “except sections 1, 13, 25 and Schedule 1”).
Type of Effect
The type of effect describes what an amendment contained within an affecting provision does to an affected provision. Effects are either textual (altering the text of the provision) or non-textual (modifying the provision’s scope or application without actually changing its text).
The type of effect column will be populated with a very brief description of the type of textual or non-textual effect to be applied to the affected provision, as described in the affecting legislation. The preparation task Record Effects guidance on Type of Effect lists out the different types of effects and the corresponding formatting that you should expect to see in this column. Note, any numbers in this column, whether referring to legislation or provisions, will not be formatted with leading zeros as they are in other columns in the spreadsheet such as Affected Legislation. For example, an Act would be entered as "2003 c. 14" in the Type of Effect column, compared to "2003 c. 014" in the Affected Legislation column.
When completing the Update task, this column will alert you to the type of textual amendment you will need to carry out in XMetaL, or the type of non-textual effect that you will need to check has had an auto-annotation correctly generated. Note that to determine if the effect will be carried out in XMetaL either wholly or be restricted by either the geographical extent or commencement dates of the affecting legislation, you will also need to check the "Affected Extent", "Affecting Territorial Application" and the "IF Date1" columns.
See more on types of effect in Editorial Principles - Effects.
Affected Extent
The Affected Extent column will be populated with a letter or letters denoting the provision's jurisdiction, chosen from one of the pre-set options in the drop-down list. This can range from UK: "E+W+S+NI" to the separate jurisdiction of Scotland or Northern Ireland: "S" or "NI", with various combinations in between. You can see a list of these combinations and further information in the preparation task Record Effects guidance on Affecting Extent and Affecting Territorial Application.
When completing the Research Affected Extent task, you will identify the affected legislation's extent provisions (in the latest version of the legislation) and populate this column with the precise extent of the lowest sub-provision that is affected.
When completing the Update task, the relationship between the entry in this column and the Affecting Extent and the Affecting Territorial Application columns will determine if the amendment carried out in XMetaL will be whole or limited extent. Limited extent amendments occur when the amendment to be applied has a narrower geographical extent (or territorial application) than that of the affected provision. We have to make sure that we don’t remove or replace text that still applies in other jurisdictions. Further information can be found on the Limited Extent Amendments page.
See more on extent in Editorial Principles - Extent and Territorial Application.
Affected Effects Extent
The Affected Effects Extent will be populated during the Research Affected Extent task if the extent of the effects within an affected provision is different from that of the affected provision itself. For example, a provision may extend to E+W+S (the Affected Extent value), but it may contain amendments to other legislation which are said to extend only to E+W or to have the same extent as the provisions they amend (i.e. 'Same as affected'). This is its Affected Effects Extent value.
See more on extent in Editorial Principles - Extent and Territorial Application.
Affected Territorial Application
The Affected Territorial Application column will be populated a letter or letters denoting the provision's territorial application (if there is one), chosen from one of the pre-set options in the drop-down list. For example, "E", "W", "S" or "NI", or a combination of these (or 'No' if there isn't one). You can see a list of the combinations and further information in the preparation task Record Effects guidance on Affecting Extent and Affecting Territorial Application.
When completing the Research Affected Extent task, you will identify the affected legislation's extent provisions (in the latest version of the legislation) and populate this column with the precise territorial appliation of the lowest sub-provision that is affected (if territorial application is specified).
When completing the Update task, the relationship between the entry in this column and the Affecting Extent and the Affecting Territorial Application columns will determine if the amendment carried out in XMetaL will be whole or limited extent. Limited extent amendments occur when the amendment to be applied has a narrower geographical extent (or territorial application) than that of the affected provision. We have to make sure that we don’t remove or replace text that still applies in other jurisdictions. Further information can be found on the Limited Extent Amendments page.
See more on territorial application in Editorial Principles - Extent and Territorial Application.
Affecting Provision Extent
The Affecting Provision Extent column will be populated with a letter or letters denoting provision's jurisdiction, chosen from one of the pre-set options in the drop-down list. This can range from UK: "E+W+S+NI" to the separate jurisdiction of Scotland or Northern Ireland: "S" or "NI", with various combinations in between. You can see a list of these combinations and further information in the preparation task Record Effects guidance on Affecting Extent and Affecting Territorial Application.
See more on extent in Editorial Principles - Extent and Territorial Application.
Affecting Extent
The Affecting Extent column will be populated with the initial of the provision's jurisdiction, chosen from one of the pre-set options in the drop-down list. This can range from UK: "E+W+S+NI" to the separate jurisdiction of Scotland or Northern Ireland: "S" or "NI", with various combinations in between. You can see a list of these combinations and further information in the preparation task Record Effects guidance on Affecting Extent and Affecting Territorial Application.
When completing the Research Affected Extent task, the contents of this column and the Affecting Territorial Application column will determine if this task can be skipped. If the affecting extent is marked as 'UK' or 'same as affected' and the Affecting Territorial Application column is either empty or matches the affecting extent then this task can be skipped.
When completing the Update task, the relationship between the entry in this column and the Affected Extent and the Affected Territorial Application columns will determine if the amendment carried out in XMetaL will be whole or limited extent. Limited extent amendments occur when the amendment to be applied has a narrower geographical extent (or territorial application) than that of the affected provision. We have to make sure that we don’t remove or replace text that still applies in other jurisdictions. Further information can be found on the Limited Extent Amendments page of the wiki.
See more on extent in Editorial Principles - Extent and Territorial Application.
Affecting Territorial Application
The affecting Territorial Application column will be populated a letter or letters denoting the provision's territorial application (if there is one), chosen from one of the pre-set options in the drop-down list. For example, "E", "W", "S" or "NI", or a combination of these (or 'No' if there isn't one). You can see a list of the combinations and further information in the preparation task Record Effects guidance on Affecting Extent and Affecting Territorial Application.
When completing the Research Affected Extent task, the contents of this column and the Affecting Extent column will determine if this task can be skipped. If the affecting extent is marked as 'UK' or 'same as affected' and this column is either empty or matches the affecting extent then this task can be skipped.
When completing the Update task, the relationship between the entry in this column and the Affected Territorial Application, and Affected Extent and Affected Territorial Application will determine if the amendment carried out in XMetaL will be whole or limited extent. Limited extent amendments occur when the amendment to be applied has a narrower geographical extent (or territorial application) than that of the affected provision. We have to make sure that we don’t remove or replace text that still applies in other jurisdictions. Further information can be found on the Limited Extent Amendments page.
See more on territorial application in Editorial Principles - Extent and Territorial Application.
Affecting Legislation
The affecting legislation is item of legislation which contains the provisions that make the amendment(s) to the affected legislation.
The affecting legislation column will be populated with the year, number and type of legislation. The preparation task Record Effects guidance on Affected and Affecting Legislation lists the different types of legislation and their corresponding formatting that you should expect to see in this column.
When completing your Update task, there may be several different items of legislation in this column, as the spreadsheet records every item of legislation which affects the item of legislation you are updating.
Affecting Provision
The affecting provision(s) is the provision of the affecting legislation which contains the amendment which makes an amendment to another item of legislation.
The affecting provision column will be populated with the lowest, numbered (or lettered as the case may be) affecting provision/sub-provision which contains the amendment to be made to the affected legislation. The preparation task Record Effects guidance on Affected and Affecting Provisions sets out the different levels of provisions and the corresponding formatting that you should expect to see in this column.
Sav
Savings, transitional provisions and other ancillary provisions which limit or in some other way qualify the scope and application of an effect are entered in this column during the Record Effects tasks.
For Update tasks, this column will need to be checked to determine whether the annotation should contain details of any savings.
See more on savings in Editorial Principles - Savings.
Comments for Editor
Comments should be made here where the effect contains any peculiarities that the update editor should be aware of when applying that effect at update stage. This generally includes anything that would normally be referenced in the commentary but that doesn’t fit into the rigid Extended TOES schema as well as instances where a power-conferring provision is being imported and the Update Editor will need to set the attributes accordingly during update.
This is a important column to check during Update tasks, as it will alert the Update Editor to anything unusual in the effect that they will need to know to apply the update correctly, including checking and if necessary manually amending the resulting annotation. If this cell contains the words “contains power”, the update editor will also need to set the ConfersPower attribute for any newly inserted or substituted provisions.
See more on Comments for Editor.
Notes
Notes are published on the Changes to Legislation pages on legislation.gov.uk for the user’s information and are used sparingly. It may need to be used to duplicate the Comments for Editor where the website user needs to be alerted to the same information, e.g. to flag up a change in extent.
See more on Notes.
Amendment applied to Database
- A Y in this column indicates that an effect has been applied.
- An N in this column indicates that an effect will never be applied.
- Where the column is empty, this indicates that the effect has not yet been applied.
See more on Amendment applied to Database.
Suggested Commentary
Where an effect requires a commentary that does not fit into our usual commentary formats and so we need to draft a bespoke version of the commentary that will replace the automatic commentary that would otherwise be generated from the Extended TOES data for that effect, this will have been entered in the Suggested Commentary column when the effect is recorded.
Appended Commentary
The Appended Commentary column is used to add additional commentary information that should be displayed after the core effect commentary information. If it is surrounded by brackets, the contents will be included in brackets at the end of the annotation. If it is not surrounded by brackets, a semicolon will be added after the core effect commentary information and it will be displayed after that (without brackets). For example,
S. 10 repealed (1.4.2012) by S.I. 2012/1526, art. 4 (as amended by S.I. 2012/1534, art. 2)
S. 21 heading substituted (31.12.2020) by The Data Protection, Privacy and Electronic Communications (Amendments etc) (EU Exit) Regulations 2019 (S.I. 2019/419), reg. 1(2), Sch. 2 para. 29(2) (with reg. 5); 2020 c. 1, Sch. 5 para. 1(1)
Commencement Authority
The details of the provision giving authority for the In Force Date(s) are entered here during the Record Effects task. If there is no commencement provision and the default commencement date has to be assumed, this column should have been left blank or may contain “No” as a reminder that this has been researched.
See more on Commencement Authority.
IF Date1
The In Force Date for the effect is entered here during the Record Effects task. This is to be found in the commencement provision(s) of the affecting legislation and is entered in the format DD/MM/YYYY. If there is no start date and the effect is therefore prospective, the column will contain “prosp”. If the commencement is qualified as "coming into force in accordance with” [provision], the default commencement date should have been entered here.
See more on IF Date1.
IF Date1 Qualification
The IF Date Qualification column is used to specify the extent to which the commenced provision is being brought into force, for example it may be wholly in force or in force only for some of its purposes, for its whole extent or for only a limited portion of that extent, etc.
See more on IF Date1 Qualification.
IF Date1Other Qualification
This column can be populated if "Other” has been selected in the IF Date Qualification column; this free text field is used to type a tailor-made qualification: e.g. where 2008 c. 23, s. 14, Sch. 4 conditionally repeals 2008 c. 23, s. 11 it would be helpful to reflect the conditions in the free text field thus, “if no order has been made under s. 11 by the relevant time”. Another common example would be where a provision is brought into force at a specific time of day: e.g. “at 1.00 p.m.”
If the following options have been selected: “with effect in accordance with”, “with application in accordance with” or “coming into force in accordance with” in the IF Date Qualification column, this column is used to type the provision(s) in accordance with which the commencement is “with effect”, “with application” or “coming into force”: e.g. “art. 1(1)”.
Further commencement information columns (if needed)
If there is more than one commencement date (for example if a provision has been brought into force for specified purposes on different dates), these columns can be populated with this commencement information.
IF Date2,3, etc. IF Date2 Qualification, IF Date3 Qualification, etc. IF Date2Other Qualification, IF Date3Other Qualification, etc.
The following columns are populated with the relevant information for any Commencement Orders, if applicable:
IFCO Date1Commencing Legislation
IFCO Date1Commencing Provision
IFCO Date1Sav
IFCO Date1COMMENTS for Editor
IFCO Date1Notes
IFCO Date1
IFCO Date1 Qualification
IFCO Date1Other Qualification
IFCO Date1Appended Commentary
IFCODate2 ..., IFCODate3 ..., etc.