Editorial Update/Renumbering
OVERVIEW
Whole provision renumbering
For example, S.I. 2020/150, reg. 6A renumbered as reg. 6B and a new reg. 6A inserted:
Affecting provision: https://www.legislation.gov.uk/nisr/2020/356/regulation/16/made
Affected provision: https://www.legislation.gov.uk/nisr/2020/150/regulation/6B
TOES: 
What the amendment looks like on the website:
Position of brackets
The renumbering amendment is presented with square brackets around the provision number (not the whole provision).
Annotation format
The style of the annotation for the renumbering amendment follows the format:
[Original provision number] renumbered as [Renumbered provision number]
For example:
Reg. 6A renumbered as reg. 6B (25.12.2020 at midnight) by The Health Protection (Coronavirus, Restrictions) (No. 2) (Amendment No. 24) Regulations (Northern Ireland) 2020 (S.R. 2020/356), regs. 1(2), 16
Note: if the affecting provision had said "reg. 6A becomes reg. 6B", the wording for the effect should be "Reg. 6A renumbered as reg. 6B by virtue of . . .".
Also note: In this example, the original provision reg. 6A was originally inserted on 13.11.2020, and the annotation for this insertion was subsequently amended when the provision was renumbered as reg. 6B on 25.12.2020.
| Skip to more detailed example |
Renumbering a Schedule
See, for example:
https://www.legislation.gov.uk/uksi/2020/916/schedule
Renumbering involving sub-provisions
2017 c. 3, s. 50 renumbered as s. 50(1)
Affecting provision: https://www.legislation.gov.uk/ukpga/2018/12/schedule/19/paragraph/210
Affected provision: https://www.legislation.gov.uk/ukpga/2017/3/section/50
TOES: 
What the amendment looks like on the website:
Position of brackets
The renumbering amendment is presented with square brackets around the sub-provision number (not the entire sub-provision).
Annotation format
The style of the annotation for the renumbering amendment follows the format:
[Original provision number] renumbered as [Renumbered provision number]
For example:
S. 50 renumbered as s. 50(1) (25.5.2018) by Data Protection Act 2018 (c. 12), s. 212(1), Sch. 19 para. 210(2) (with ss. 117, 209, 210); S.I. 2018/625, reg. 2(1)(g)
| Skip to more detailed example |
S.I. 2001/838, reg. 46(2)-(4) omitted and reg. 46(1) renumbered as reg. 46
In this example, sub-provisions are omitted to leave one sub-provision that gets renumbered as a whole provision:
https://www.legislation.gov.uk/uksi/2001/838/regulation/46/2003-04-01
Renumbering involving relocation of provisions
Note that when provisions are relocated, this should be achieved by inserting new tagging (to include new attributes that reflect the new id of the renumbered provision) and copying the content rather than trying to copy and paste provisions (including their tagging) as the attributes will be wrong and so the URLs won't be correct.
2018 asp 9, s. 75 and cross-heading re-numbered as s. 84A and cross-heading, s. 76 re-numbered as s. 84B
Affecting provision: https://www.legislation.gov.uk/asp/2020/18/section/5#section-5
Affected provisions:
https://www.legislation.gov.uk/asp/2018/9/part/2/chapter/6/crossheading/investigations
https://www.legislation.gov.uk/asp/2018/9/part/4/crossheading/investigations
TOES: 
What the amendment looks like on the website:
1. Original provision moved to new location and renumbered:
The movement of the original provision to a new location was achieved by inserting the tagging for the renumbered provision (in this case a cross-heading and its child provision) into the parent at the appropriate position and copying the content from the original provision. The provision number was then renumbered in the usual way, using the renumbering task to generate the square brackets and the annotation. Note: don't try to copy and paste a provision including it's tagging into a new location; the attributes of the tagging won't be correct and that is why new tagging for the provision needs to be inserted in the new location.
2. Original provision is repealed:
The original provision is then repealed in the usual way using the renumbering update task in the Task Manager, resulting in a dotty line. In this example, the cross-heading was repealed by carrying out a repeal of words in the cross-heading (again using the same renumbering task).
Note: although the provision has been repealed, the wording of the annotation is taken from the renumbering update task in the format:
[Original provision number] renumbered as [Renumbered provision number]
Position of brackets
The renumbering amendment is presented with square brackets around the provision number (not the entire provision).
Annotation format
Note the deviation in this situation from the usual annotation format [Original provision number] renumbered as [Renumbered provision number] to: [Renumbered provision number]: [Original provision number] renumbered as [Renumbered provision number]
This approach was deemed to be clearer in this scenario where the provisions were moved to a new location. This renumbering annotation format should only be used for more complex renumbering scenarios. For straightforward numbering amendments, please use the usual format [Original provision number] renumbered as [Renumbered provision number], see above.
SI 2020/759, Pt. 47: omission of whole provisions with renumbering of remaining whole provisions to maintain the numerical order
| BEWARE: simply amending provision numbers in the text is NOT a correct method for dealing with the scenario where drafters omit whole provisions and then renumber the remaining whole provisions in order to retain the numerical order. We need to remember to take into account the URL identifiers of the provisions and maintain their continuity, which means we are forced to copy and paste the content of the renumbered provisions over the omitted provisions and then dotty line the renumbered provisions and account for all this in our annotations. |
See, for example:
Amending provision
2021 SI0040, art. 27(k)-(o):
“(k) omit Section 9 (European investigation orders), comprising rules 47.59 to 47.61 and the notes to those rules;
(l) renumber Section 10 and rules 47.62 to 47.65 as Section 9 and rules 47.59 to 47.62 respectively; (m) in rule 47.59 as thus renumbered (When this Section applies), in the fourth paragraph of the note to the rule for “47.64” substitute “47.61”; (n) in rule 47.60 as thus renumbered (Exercise of court’s powers), in paragraph (1) for “47.64” substitute “47.61”;
(o) renumber Section 11 and rules 47.66 to 47.71 as Section 10 and rules 47.63 to 47.68 respectively;”
https://www.legislation.gov.uk/uksi/2021/40/article/27/made
Amended provisions
It is important to maintain the integrity of the URL structure whilst carrying an amendment like this. We therefore had to copy the content of the renumbered provisions from Section 10 into the now omitted provisions in Section 9, and copy the content of the renumbered Section 11 provisions into the provisions of Section 10 (the original versions of which had themselves been renumbered):
https://www.legislation.gov.uk/uksi/2020/759/part/47/crossheading/13/2021-02-08
https://www.legislation.gov.uk/uksi/2020/759/part/47/crossheading/14/2021-02-08
https://www.legislation.gov.uk/uksi/2020/759/part/47/crossheading/15/2021-02-08
Note the explanatory annotation to Section 9, which details that the original Section 9 is omitted and Section 10 renumbered as Section 9. Also note the omission of Rules 47.69-47.71 in Section 11 (which are left behind after the renumbering of Rules 47.66-47.71 into Section 10) with annotations explaining the renumbering.
You can see how the ToC changed before and after the renumbering:
Before
After
Whilst some of the provisions have moved sections, the structure of the URLs has been maintained so you still can navigate back and forth on the timeline within each provision. For example, Rule 47.65 stays in Section 10 but is replaced by the content of Rule 47.68, and the content of Rule 47.68 itself gets replaced by the content of Rule 47.71 and moved into Section 10. To achieve this, the content of Rule 47.68 was copied into Rule 47.65 (which was itself omitted at the same PiT, but this amendment was not carried out as the provision was replaced by renumbering of Rule 47.68). The tagging for the original Rule 47.68 was then moved from cross-heading 15 to cross-heading 14, and the content was replaced with the content of the existing Rule 47.71:
Before renumbering: https://www.legislation.gov.uk/uksi/2020/759/rule/47.65/2020-10-05
After renumbering: https://www.legislation.gov.uk/uksi/2020/759/rule/47.65/2021-02-08
and
Before renumbering: https://www.legislation.gov.uk/uksi/2020/759/rule/47.68/2020-10-05
After renumbering: https://www.legislation.gov.uk/uksi/2020/759/rule/47.68/2021-02-08
Renumbering for a limited extent
See the renumbering of sub-provisions in 1992 c. 51, s.10(2) for S only, which was dealt with using composite text:
https://www.legislation.gov.uk/ukpga/1992/51/section/10/2011-06-29#section-10-2
S. 10(2)(a)-(d) renumbered as s. 10(1)(g)-(j) (S.) (29.6.2011) by Wildlife and Natural Environment (Scotland) Act 2011 (asp 6), ss. 33(6)(b)(ii), 43(1) (with s. 41(1)); S.S.I. 2011/279, art. 2(1)(m)
Renumbering for specified purposes
See this example where 2022 c. 10. Sch. 2 para. 2 gets renumbered as Sch. 2 para. 2(1) for specified purposes:
https://www.legislation.gov.uk/ukpga/2022/10/schedule/2/paragraph/2/2023-10-26
Sch. 2 para. 2 renumbered as Sch. 2 para. 2(1) (26.10.2023 for specified purposes) by Economic Crime and Corporate Transparency Act 2023 (c. 56), ss. 162(3)(a)(i), 219(1)(2)(b)
Renumbering within amendment text
See the renumbering of the second paragraphs 5 and 6 to become paragraphs 8 and 9 in the new Article 2a inserted by S.I. 2019/588, reg. 9:
https://www.legislation.gov.uk/uksi/2019/588/regulation/9/2020-12-31
Reg. 9(14): in text of inserted Art. 24a, second paras. 5, 6 renumbered as paras. 8, 9 (31.12.2020 immediately before IP completion day) by The Animal Welfare and Invasive Non-native Species (Amendment etc.) (EU Exit) Regulations 2020 (S.I. 2020/1590), regs. 1(1)(b)(i), 3(4)(b)(ii)
Renumbering within a definition
If a numbered paragraph within a definition gets renumbered, insert an F-note reference for the amendments in appropriate location and an explanatory F-note. See for example:
IN MORE DETAIL
Renumbering whole provisions
When a whole provision is renumbered, it should be treated as though the original provision is omitted and a new provision (with exactly the same text) is inserted. This will maintain the correct URL for each provision and so preserve the continuity of the URLs. Firstly, the context of the provision should be checked to determine what type of tagging to insert for the provision that is to be renumbered (i.e. <ukl:P1group> and/or <ukl:P1>).
Basic structure of a provision:
<P1group>
<Title></Title>
<P1>
<Pnumber></Pnumber>
<P1para>
<P2>
<Pnumber></Pnumber>
<P2para>
<Text></Text>
</P2para>
</P2>
</P1para>
</P1>
</P1group>
Note: Whole provisions are often tagged with <ukl:P1group> tags surrounding the <ukl:P1> tags in the main body, and <ukl:P1> tags are often used without surrounding <ukl:P1group> tags in the Schedules, however this may not always be the case.
To renumber a whole provision, a new outer structure (consisting of <P1group> and/or <P1> tags) for the renumbered provision should be inserted in the appropriate position and the content of the original provision should be copied and pasted into this new tagging (i.e. select the <P1para> tags and their contents in the original provision and copy and paste this into the newly renumbered provision. Also copy and paste the title from the original provision into the title tagging if appropriate). The provision number should be copied from the amending provision and inserted into the <Pnumber> tagging using the the update task in the Task Manager to generate the square brackets and annotation.
Finally, the original provision should be repealed using the same task so both the omitted old provision and the renumbered new provision have the same annotation. If a new provision is to be inserted for the original provision, substitute the content of the original provision using the insertion task.
Example: S.I. 2020/150, reg. 6A renumbered as reg. 6B
On 25/12/2020 S.I. 2020/150 reg. 6A was renumbered as reg. 6B and a new reg. 6A was inserted.
https://www.legislation.gov.uk/nisr/2020/150/regulation/6A
https://www.legislation.gov.uk/nisr/2020/150/regulation/6B
This was achieved by:
1. Inserting new <ukl:P1group> tagging for reg. 6B and new <ukl:P1> tagging was inserted into this (using the Element List). The existing content of reg. 6A was copied into this new tagging (via straightforward copy and paste of everything within the <ukl:P1para> tagging and the same was done for the title in the <ukl:title> tagging). The number 6A was copied from the amending provision and inserted into the number tagging using the update task in the Task Manager to generate the square brackets and annotation:
2. The annotation for the original insertion of reg. 6A was also amended to explain that the original reg. 6A was subsequently renumbered as reg. 6B (so this information is visible both in the old reg. 6A at the previous PiT and also in the new reg. 6B at the current PiT):
3. The new reg. 6A was substituted for the old reg. 6A using the insertion task to generate the square brackets and correct annotation for that task:
In this example, there was a new provision inserted for the provision that was renumbered. However, if there had been no insertion of a new provision, the original provision should have been repealed using the same update task in the Task Manager, so both the omitted old provision and the renumbered new provision had the same annotation.
Renumbering paragraphs within a Schedule
To renumber a paragraph within a Schedule, new <ukl:P1> tags should be inserted for the new renumbered provision using the Element List. The number of the renumbered paragraph should then be copied and inserted into the number tags using the renumbering update task in the Task Manager to generate the annotation and brackets around the new paragraph number. Next, the <ukl:P1para> tagging containing all the content from the original paragraph should be copied and pasted into the newly renumbered paragraph. Finally, the same task should be used to repeal the original paragraph so that both the omitted old paragraph and the renumbered new paragraph have the same annotation (or if a new paragraph is to be inserted to replace the original paragraph, this can be achieved by substitution of the paragraph using the insertion task).
Note: it is important to check the context of the tagging of the provision you are renumbering to ensure that you follow the existing structure of the document you are working on. If there is anything unusual about the structure of the tagging and you are not sure which tags to insert for the renumbered provision, check with a Review Editor.
Renumbering sub-provisions
A provision may be renumbered as a sub-provision where there are no existing sub-provisions and a new sub-provision/sub-provisions is/are being inserted. Sub-provision renumbering may also involve words within a provision being renumbered as a sub-provision. Care should be taken with punctuation in this situation, for example it may be necessary to insert an em dash where the renumbering results in a new indent, as described here. The <ukl:P1group> and/or <ukl:P1> tagging of the provision should be preserved, and new <ukl:P2> tagging should be inserted for the renumbered sub-provision(s) as appropriate.
New <ukl:P2> tagging for the newly renumbered sub-provision should be inserted in the appropriate position within the existing tagging of the provision (i.e. within the <ukl:P1para> tagging), then the number of the renumbered sub-provision is copied from the amending provision and inserted into the number tags using the renumbering update task to get the annotation. The brackets should remain around the new sub-provision number:
The content of the original provision or sub-provision should be moved into <ukl:P2para> tagging in the newly renumbered sub-provision:
Note: the complete tagging of the whole provision has not been included in this screenshot.
Further sub-provisions can then be inserted in the usual way according to the update task.
Example: S.I. 2010/959, reg. 5 renumbered as reg. 5(1)
On 8.8.2015, S.I. 2010/959 reg. 5 was renumbered as reg. 5(1) and new reg. 5(1)(f) and (2) were inserted. This was achieved by inserting new <ukl:P2> tagging within the existing <ukl:P1para> of reg. 5. The contents of this <ukl:P1para> were moved into <ukl:P2para> tagging within this new <ukl:P2> tagging. The number (1) was copied from the amending provision and inserted into the number tagging using the update task in the Task Manager to generate the square brackets and annotation:
Sub-provisions (1)(f) and (2) were subsequently inserted into reg. 5 in the usual way.
Example: 1951 c. 65, words in s. 46(3) renumbered as s. 46(3)(a)
On 5.12.2005, words in 1951 c. 65, s. 46(3) were renumbered as s. 46(3)(a) and a new s. 46(3)(b) was inserted. This was achieved by inserting new <ukl:P3> tagging within the existing <ukl:P2para> of s.46(3). The relevant words were moved into <ukl:P3para> tagging within this new <ukl:P3> tagging. The <Pnumber>“a” was copied from the amending provision and inserted into the <Pnumber> tagging using the update task in the Task Manager to generate the square brackets and annotation. As it had not been inserted as part of the amendment, an em dash was also inserted after the word “leaves” at the start of the new indent (circled in red above).
Note: The square brackets are positioned around the renumbered provision number, not all the words in s. 46(3) that were renumbered.
S. 46(3)(b) was subsequently inserted into s. 46(3) in the usual way.
https://www.legislation.gov.uk/ukpga/Geo6/14-15/65/section/46/2005-12-05
RELATED PAGES
Approach, errors and troubleshooting: