Difference between revisions of "Editorial Update/Amendment to Earlier Affecting Provision"

Revision as of 11:09, 7 October 2021

For guidance specific to EU Exit SIs, see EU Exit Update Guidance notes also Amendments to earlier affecting EU Exit SIs before their amendments come into force.

“Amendment to earlier affecting provision” effects

Amendments to Commencement Orders are usually captured before we have applied the I-notes and they are dealt with through changes to the TOES data and Appended Commentary, so shouldn’t appear very often during Editorial Update. Elsewhere, however, “Amendment to earlier affecting provision” effects can appear for both textual non-textual amendments during Editorial Update.

Non-textual “Amendment to earlier affecting provision” effects usually occur with a start date after the IF Date of the original amendment and they should be dealt with as described below.

Update Editors should particularly look out for “amendments to earlier affecting provisions” which may result in a change to the text, which usually come into force before or simultaneously with the original textual amendment. The approach to dealing with these effects is also described below.

Original Amendment is Non-textual

“Amendment to earlier affecting provision” effects usually happen to non-textual amendments where their start date is after the IF Date of the original amendment. In this case, we need to add an appended commentary to the end of the original I-note or C-note annotation text to say: “(as amended ([date]) by …, etc)”. To make sure that these new details don't “trickle” back into the earlier PiT, you should insert a new F-note for the “Amendment to earlier affecting provision” effect, change the annotation type to an I-Note or C-Note as relevant, copy the details of the original amendment from the existing annotation into this new annotation adding “as amended (date) by ...” to merge the existing text with the text of the new annotation. You can then delete the original annotation reference for the amendment, as it is no longer needed.

See, for example: https://www.legislation.gov.uk/ukpga/Eliz2/8-9/67/section/1/2020-08-01

S. 1 modified (E.) (4.4.2020) by The Local Authorities and Police and Crime Panels (Coronavirus) (Flexibility of Local Authority and Police and Crime Panel Meetings) (England and Wales) Regulations 2020 (S.I. 2020/392), regs. 1, 13 (with reg. 2(4)) (as amended (1.8.2020) by The Local Authorities and Police and Crime Panels (Coronavirus) (Flexibility of Local Authority and Police and Crime Panel Meetings) (England and Wales) (Amendment) Regulations 2020 (S.I. 2020/808), regs. 1, 2(4))

Original Amendment is Textual

“Amendment to earlier affecting provision” effects may happen to textual amendments where their start date is dated before or on the same date as the IF Date of the original amendment (i.e. they change the amendment while it’s still prospective). The start date should have been set to the same date as the original amendment in TOES, so the two dates coincide with each other. During update we would first carry out the original amendment and then insert an F-note for the "amendment to earlier affecting provision" and copy and paste its details as an appended commentary to the end of the original annotation (but this time we don’t mention the date), using the format “(as amended by …, etc)”.

We occasionally get changes to textual amendments after they have come into force, but these should be treated with caution as the drafters have probably also drafted a direct effect to the target item of legislation as well as changing the affecting document and we probably haven’t noticed this while entering TOES. However, probably due to drafting errors, it does happen occasionally. There may also be situations where a subsequent amendment is made to an affecting provision that doesn't result in a textual amendment to the original amendment, however the annotation will still need to be amended.

Carrying out the amendment

1. If the amendment does make a textual change to the original amendment, the text of the amendment itself needs to be changed (i.e. the words of the inserted or substituted text), or the text that gets repealed needs to be changed as the case may be, to reflect how the amendment has been changed. Do a manual edit of the text you are amending - not as an amendment (which would generate square brackets and an annotation), but by adjusting the tagging as needed and pasting in or removing any text. We don’t put new brackets around these additional changes as it’s all covered in our changed annotation.

2. Insert a new F-note for the "amendment to earlier affecting provision" effect, then:

If the start date of the subsequent amendment is the same as the original amendment, make sure you have carried out the original amendment first (which will be at the same PiT), and then you can copy the details from the new F-note into the existing annotation for the original amendment adding "as amended by ... " to merge with the text of the new annotation. Once the annotations have been merged, the now obsolete F-note reference for the "amendment to earlier affecting provision" effect needs to be deleted.

If the start date of the subsequent amendment is after the original amendment, you will be working in a later PiT than the one in which the original amendment was carried out and you will need to deal with it slightly differently to make sure that the details for this amendment don't "trickle" back into the earlier PiT. After you have inserted the new F-note for the “Amendment to earlier affecting provision”, you should copy the details of the original amendment from the existing annotation into this new F-note adding "as amended (date) by ... " to merge with the text of the new annotation. You should also change the commentary ref attribute in the amendment bracket from its current id to the id of the newly inserted annotation, so it points to that new annotation instead. You can delete the original annotation for the amendment, as it is no longer needed, although it should be removed automatically when you check the provision back in if you have amended the CommentaryRef attribute of the F-note reference to point to the new annotation.

3. Check the amendment back in. If you preview the provision at this stage, you can check the annotation has formatted correctly and that any annotations that should have been removed have been. If you are working in a later PiT than that of the original amendment, you should also check the previous PiT, which should show the annotations in their original form, before the amendment to earlier affecting provision occurred.

For example:

Start date of the original amendment and the "amendment to earlier affecting provision" are the same

Sch. 3 substituted (27.10.2017) by The Public Water Supplies (Scotland) Amendment Regulations 2017 (S.S.I. 2017/281), reg. 1(1), sch. 2 (as amended by The Public and Private Water Supplies (Miscellaneous Amendments) (Scotland) Regulations 2017 (S.S.I. 2017/321), regs. 1, 3(3)(a)(b))

N.B. The date of the subsequent amendment is not included in the annotation

Start date of the original amendment is earlier than the "amendment to earlier affecting provision"

Words in Sch. 3 inserted (5.10.2015) by The Single Use Carrier Bags Charges (England) Order 2015 (S.I. 2015/776), arts. 1(c)(ii)(d), 17 (as amended (21.5.2021) by The Single Use Carrier Bags Charges (England) (Amendment) Order 2021 (S.I. 2021/598), arts. 1(2), 3)

N.B. The date of the subsequent amendment is included in the annotation

4. You will see in the preview that the amended annotation will not have all the hyperlinks enabled. To rectify this, you will need to check the provision out again, copy the plain text from your preview and paste it over the existing annotation text and then check it back in again. The system will then add in all the links, which you can check in preview.

For more detail see the first example in the Scenarios below (subsequent amendments are after the start date of the original amendment, and the dates for these subsequent amendments have been included in the annotation. Note that the example also shows how to deal with subsequent amendments for limited extent).

Note:

1. The insertion of an F-note for the "amendment to earlier affecting provision" effect will ensure that the commentary that is appended to the original amendment annotation will show from this PiT onwards, making it clearer that there has been a textual amendment at this PiT. However, this F-note can be deleted again once the new details have been merged into the original annotation where you are dealing with a subsequent amendment with the same start date as that of the original amendment. Where the subsequent amendment is made after the original amendment has come into force, the newly inserted F-note supersedes the original F-note and the original F-note is deleted once the annotation details have been merged. This ensures that the new details do not "trickle" back into the previous PiT.

2. The subsequent amendment may not alter the original amendment textually, in which case you should follow steps 2-4 and you won't need to make any amendments to the text. See an example here.

Inserting a new F-note for an "amendment to earlier affecting provision" effect

1. Place your cursor where you want the annotation reference to go in the XML. 2. Select the "amendment to earlier affecting provision effect" task in the Task Manager and select Insert Commentary from the Legislation/Non-textual Effects menu:

This will insert an F-note reference and annotation for the effect:

3. The F-note reference and annotation must then be amended according to the type of "amendment to earlier amending provision" effect, as detailed above;

Scenarios

“Amendment to earlier affecting provision" involving limited extent

Example 1 - amendment to earlier temporary insertion of sub-provisions

On 25.3.2020, 1977 c. 42, s.3(4A)-(4F) were temporarily inserted by 2020 c. 7, Sch. 29 para. 2(3) (note this is a modification being treated as a temporary insertion in accordance with the Coronavirus legislation guidance).

“S. 3(4A)-(4F) inserted (temp.) (25.3.2020) by virtue of Coronavirus Act 2020 (c. 7), s. 87(1), Sch. 29 para. 2(3) (with ss. 88-90)”

Subsequently, the original amending provision 2020 c. 7, Sch. 29 para. 2(3) was amended by S.I. 2020/914, reg. 3 on 28/8/2020 for E. as follows:

https://www.legislation.gov.uk/ukpga/2020/7/schedule/29/paragraph/2/2020-08-28#schedule-29-paragraph-2-3

The amendment of this earlier affecting provision was recorded in an “amendment to earlier affecting provision” effect against the affected provision 1977 c. 42, s.3(4A)-(4F), generating this update task:

To carry out this amendment, the inserted text from the amending provisions S.I. 2020/914, reg. 3(3)(c)(i)(ii) and (iii) was copied and pasted into the correct place in s. 3(4A)(4C) and (4F), not as an amendment (which would generate square brackets and an annotation), but by adjusting the tagging as needed and pasting in the text:

https://legislation.gov.uk/uksi/2020/914/regulation/3/made#regulation-3-3-c

Then a new commentary was inserted and made to read:

“S. 3(4A)-(4F) inserted (temp.) (25.3.2020) by virtue of Coronavirus Act 2020 (c. 7), s. 87(1), Sch. 29 para. 2(3) (with ss. 88-90) (as amended (E.) (28.8.2020) by The Coronavirus Act 2020 (Residential Tenancies: Protection from Eviction) (Amendment) (England) Regulations 2020 (S.I. 2020/914), regs. 1(2), 3(2)(3)(c) (with reg. 4))”

Then the commentary ref attribute in the amendment bracket for the insertion of s. 3(4A)-(4F) was changed from its current id to the id of the newly inserted commentary, so it points to that new annotation instead.

Finally, the original commentary reference was deleted for the inserted commentary as it’s no longer needed.

https://www.legislation.gov.uk/ukpga/1977/42/section/3/2020-08-28

Example 2 - amendment to earlier temporary substitution of words

On 26.3.2020, there was a whole extent temporary substitution of words in 1988 c.50 (note this is a modification being treated as a temporary substitution of words in accordance with the Coronavirus legislation guidance).

https://www.legislation.gov.uk/ukpga/1988/50/section/21/2020-03-26

“(b) the landlord or, in the case of joint landlords, at least one of them has given to the tenant not less than [F2two months’] [F2three months’] notice …”

“Words in s. 21(1)(b) substituted (temp.) (26.3.2020) by virtue of Coronavirus Act 2020 (c. 7), s. 87(1), Sch. 29 paras. 1, 7(a) (with ss. 88-90)”

This temporary substitution was subsequently amended to “six months’” for W. on 24.7.2020 by S.I. 2020/778, via an “amendment to earlier affecting provision” effect. The annotation was amended as follows:

https://www.legislation.gov.uk/ukpga/1988/50/section/21/2020-07-24

“(b) the landlord or, in the case of joint landlords, at least one of them has given to the tenant not less than [F2two months’][F2three months’ in relation to a dwelling-house in Engl

“Suspension of earlier affecting provision” effects

For a description of how to deal with suspended effects during Editorial Update, see:

Coronavirus Legislation - Suspended and revived effects

“Expiry of earlier affecting provision” effects

For a description of how to deal with suspended effects during Editorial Update, see:

Coronavirus Legislation - Applying "expiry of earlier affecting provision" effects

"Savings for effects of ..." and "transitional provisions for effects of ..."

"Savings [or transitional provisions] for effects of ..." types of effect occur where savings (or transitional provisions) are subsequently added to an existing amendment. Rather than automatically overwriting the original existing annotation the editorial tool inserts a new C-note auto annotation for this type of effect, for example:

Existing annotation for the original effect

“S. 3 applied (with modifications) (22.2.2020 for all purposes except in respect of infant formula and follow-on formula manufactured from protein hydrolysates and 22.2.2021 in so far as not already in force) by The Infant Formula and Follow-on Formula (Wales) Regulations 2020 (S.I. 2020/89), regs. 1(1)(2), 4(7)(a), Sch. 2 para. 6”

Newly inserted auto annotation for the “savings for effects of ...” type of effect

“S. 3 savings for effects of S.I. 2020/89, regs. 2-4 (16.9.2021) by The Infant Formula and Follow-on Formula (Wales) (Amendment) Regulations 2021 (S.I. 2021/955), reg. 1(2), Sch. (with savings in reg. 5(4)(5), Sch. 4 para. 26(1)(2)”

However, what we want to end up with here is a merging of the original existing annotation with an appended commentary for the savings added to the end of the text, for example:

“S. 3 applied (with modifications) (22.2.2020 for all purposes except in respect of infant formula and follow-on formula manufactured from protein hydrolysates and 22.2.2021 in so far as not already in force) by The Infant Formula and Follow-on Formula (Wales) Regulations 2020 (S.I. 2020/89), regs. 1(1)(2), 4(7)(a), Sch. 2 para. 6 (with savings in reg. 5(4)(5), Sch. 4 para. 26(1)(2) (as inserted (16.9.2021) by S.I. 2021/955, reg. 2(2), Sch.))”

The text of the existing C-note should be copied from the Preview and used to overwrite the new C-note and the appended commentary should be added (if this has been included as a Comment in TOES, you can copy it from there). The existing C-note reference should then be deleted from its position within the <ukl:pnumber> tagging and the new C-note moved into its position to replace it:

By replacing the old C-note with the new one, it will avoid the new C-note details from trickling back into the earlier version (which would happen if you just added the appended commentary to the existing annotation). See, for example:

https://www.legislation.gov.uk/ukpga/1990/16/section/3

XMetaL and XML tagging - Fixing Hyperlinks

@@ Line 13: / Line 13: @@
 ===Original Amendment is Non-textual===
-“Amendment to earlier affecting provision” effects usually happen to non-textual amendments where their start date is after the IF Date of the original amendment.  In this case, we need to add an appended commentary to the end of the original I-note or C-note annotation text to say: “(as amended ([date]) by …, etc)”. To make sure that these new details don't “trickle” back into the earlier PiT, you should insert a new F-note for the “Amendment to earlier affecting provision” effect, [[Editorial_Update/XMetaL_and_XML_tagging#Type_Attribute|change the annotation type]] to an I-Note or C-Note as relevant, copy the details of the original amendment from the existing annotation into this new annotation adding “as amended (date) by ...” to merge the existing text with the text of the new annotation. You can then delete the original annotation reference for the amendment, as it is no longer needed.
+“Amendment to earlier affecting provision” effects usually happen to non-textual amendments where their start date is after the IF Date of the original amendment.  In this case, we need to add an appended commentary to the end of the original I-note or C-note annotation text to say: “(as amended ([date]) by …, etc)”. To make sure that these new details don't “trickle” back into the earlier PiT, you should [[Editorial_Update/Amendment_to_Earlier_Affecting_Provision#Inserting_a_new_F-note_for_an_.22amendment_to_earlier_affecting_provision.22_effect|insert a new F-note]] for the “Amendment to earlier affecting provision” effect, [[Editorial_Update/XMetaL_and_XML_tagging#Type_Attribute|change the annotation type]] to an I-Note or C-Note as relevant, copy the details of the original amendment from the existing annotation into this new annotation adding “as amended (date) by ...” to merge the existing text with the text of the new annotation. You can then delete the original annotation reference for the amendment, as it is no longer needed.
 See, for example: