Corrections
Page being edited
Carrying out correction tasks
TOES correction
You can allocate a TOES correction task to yourself by searching for the relevant document in the Editorial System and selecting the "Corrections" tab. Next, select the appropriate radial button ("Made by ..." or "Changes that affect ...") and then enter the affecting document details in the box below. Finally, select your details in the "Allocate to" dropdown box and click "Create task":
The task will be created by the Editorial System and you will be able to start the task from your dashboard once it becomes available. When you select the task, you will be taken to the following screen, where you will be able to download the TOES that you need to correct by selecting "Download file":
Once you have carried out the correction to the TOES, save the spreadsheet with an appropriate filename (for an example, see the image below) and select "Next stage" and you will be taken to the screen below:
Browse to locate the corrected file that you saved and, once located, select that file and click "Publish", you will be taken to the following screen which you can close and you will receive an email once the task is complete:
Amendment coming into force before the provision it is amending comes into force
This scenario results in “later sld version errors” which prevent you from starting update. It is caused because at least one amendment has a start date earlier than one of the provisions in the affected document, so there are several different ways of getting round this depending on the exact situation:
- If the amended doc is being revoked before it comes into force, then you will have to reset update and re-do sld initial edit to make it prosp and redeploy and then do the update to revoke it;
- If an amendment comes into force before the affected provision comes into force, there are two options:
- do a TOES correction to change the IFDate of the effect to make it the same as the start date of the affected provision, ensuring that you also provide a “Suggested Commentary” for the effect that contains its REAL start date. (A suggested commentary should be written properly in our house style, including punctuation, legislation title and commencement order details). Then do update.
- if the amendments have start dates between the earliest date that the affected doc comes into force and one or more subsequent commencements, then you should reset update, re-do sld initial edit to make the subsequently commenced provisions prosp; then you should do a TOES correction to add coming into force effects for those now prosp provisions. Then when you re-allocate update the coming into force effects will be added as I-notes as part of the update task and will appear in the update timeline.
"Later Legislation version" error: amendment made to affected legislation before it comes into force
Error message on starting update:
"Later legislation version dated '2007-05-01' found. Your request to update PiT dated '2007-03-28' cannot be completed. There is a later version of this legislation and this is not currently supported for updates other than commencements"
The "Later legislation version" error message occurs here because the IF Date of the effects (28.3.2007) is earlier than the start date of the affected legislation (1.5.2007).
https://www.legislation.gov.uk/ssi/2006/534/regulation/1/made
https://www.legislation.gov.uk/ssi/2007/166/regulation/1/made
We can work around by changing the TOES data so that the IF Dates for the effects coincide with the start date (1.5.2007) of the affected provisions, but we also need to add a Suggested Commentary using our house style so that the annotation contains the actual date (28.3.2007) that the amendments come into force:
After correcting the TOES data, we need to reset update (in fact it’s easier to correct TOES if we reset the Act first) and (as is the case here) we may also need to actually delete the existing update tasks (e.g. “Update to 28/3/2007”) and allocate them over again from scratch because they have the wrong date in them. Also, the timeline may need to be regenerated before reallocation of update is allowed.
See another example in S.I. 2018/1199, regs. 6(5) and 15(2)(b), where a Comment for the Editor has also been included in the TOES correction to explain what is going on (TOES corrections are highlighted red; previously the IF Date was 30/12/2020 and this needed to be changed to 31/12/2020 to resolve the "later version error"):
https://www.legislation.gov.uk/uksi/2018/1199/regulation/6
https://www.legislation.gov.uk/uksi/2018/1199/regulation/15
"Later Legislation version" error: affected legislation revoked before it comes into force
Error message on starting update:
"Later legislation version dated '2021-07-12' found. Your request to update PiT dated '2021-07-11' cannot be completed. There is a later version of this legislation and this is not currently supported for updates other than commencements"
The "Later legislation version" error message occurs here because the IF Date of the revocation (11.7.2021) is earlier than the start date of the affected legislation (12.7.2021).
If it had been offline initial edited, it would have been possible to reset the update, delete the update tasks and then redo the initial edit on sld to make it prospective, then redeploy it before re-allocating the update.
However, because it had been online initial edited, the update needed to be reset and the update tasks were deleted and a TOES correction was carried out to make the IF Date of the revocation (11.7.2021) match the date the affected document comes into force (12.7.2021). A suggested commentary (where we write the annotation out in our proper house style) was also added for the revocation containing the real date of the revocation (11.7.2021):
This allowed the update to go ahead. Then during update, the legislation was revoked using the auto repeal function:
The Timeline Resolver in Preview was then used to remove the PiT so it looks prospective (Note: the resolution of the timeline was done by TSO as we were unable to use the Timeline Resolver at the top level of the document. TSO suggested resolving the intro, sig block, notes and body levels before resolving timeline at the legislation level).
Before Timeline Resolver used to remove PiT 12/7/2021:
After Timeline Resolver used to remove PiT 12/7/2021:
Notes about Corrections
TOES
- Be careful when doing TOES corrections not to delete and re-insert entries i.e. you should amend the existing entries as doing so will preserve the KeyIDs for the existing entries (which should not be removed).