Editorial Update/Renumbering
DRAFT - this page is under construction
Basic approach
Whole provision is renumbered
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
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 a renumbering amendment should follow 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
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 |
Whole provision is renumbered to create a sub-provision
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
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 a renumbering amendment should follow 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 |
Whole provision is renumbered and moved to a new location
2020 asp 18, 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-4
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
What the amendment looks like on the website:
Repeal of original provision
The original provision is repealed in the usual way, resulting in a dotty line.
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 example 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, if you are not sure consult a Review Editor. For straightforward numbering amendments, please use the usual format [Original provision number] renumbered as [Renumbered provision number], see above.
Renumbering in more detail
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:
- 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: - The new reg. 6A was then substituted for the old reg. 6A using the insertion task to generate the square brackets and correct annotation for that task:
- The annotation for the original insertion of reg. 6A was also amended to say that 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):
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 task so both the omitted old provision and the renumbered new provision had the same annotation.
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 update task 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.
Sub-provisions
This often involves a provision being renumbered as a sub-provision and a new sub-provision (or sub-provisions) being inserted into the provision. 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 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 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.