View source for Editorial Update/Applying “coming into force” effects

==What are “coming into force” effects?==

There are various ways in which legislation may be brought into force, see [[Editorial_Principles#Commencement|Editorial Principles - Commencement]] for further details. “Coming into force” effects are used to capture commencement information in TOES during the [[Research_Tasks/Initial_Edit|Initial Edit]] and [[Preparation_Tasks/Record_Effects|Record Effects]] tasks. These effects subsequently add commencement information to provisions via [[Editorial_Update/Annotation_Conventions#I-notes_.28Commencement_information.29|I-notes]] (“In Force” notes) that are generated:

* during the [[Research_Tasks/Initial Edit|Initial Edit]] task that is carried out on new items of legislation in order for these documents to be deployed to the website as the “Latest Available (Revised)” version;

* when [[Preparation_Tasks/Record_Effects/Commencement_Orders|Commencement Order “coming into force” effects]] are applied during Editorial Update. 

Revised legislation also includes a timeline of changes that is displayed in each provision, with the earliest date that a provision comes into force to any extent or for any purpose (or the basedate if that was later) as the first PiT (the start date). The in force dates that are recorded in TOES are included as ‘restrictstartdate’ attributes in the XML in the legislation data and these are used to set up the timeline, for example:

<strong>TOES data:</strong>
 
 [[File: Coming_into_force_6.png|900px]]

<strong>“Latest Available (Revised)” version on the website:</strong>

 [[File: Coming_into_force_7.png|900px]]
 
I-notes describe how an item of legislation comes into force, annotating a provision with its commencement details. The information entered during the Initial Edit task generates the “coming into force” effects that correspond with the I-notes that are included when the “Latest Available (Revised)” version gets deployed to the website. Note that all provisions get a “coming into force” effect in TOES after Initial Edit, even if they are still prospective. If a prospective provision is brought into force on a later date by a Commencement Order, another “coming into force” effect will be added to TOES when the Commencement Order effects are recorded during the Record Effects task and this effect will be applied during Editorial Update, when another I-note will be added <strong>in addition to the original one</strong> that came from the Initial Edit task.

It is often the case that the provisions of an item of legislation will not have in force dates when that document is originally published and these provisions remain ‘prospective’. In such cases, the ‘restrictstartdate’ attributes are left blank until a date is appointed, usually by Commencement Order. We apply these later in force dates through online update.

==How “coming into force” effects get applied==


“Coming into force” effects are auto-applied by the Editorial System during Editorial Update. The system will:

*Apply an I-note annotation citing the in force date and the commencement authority or Commencement Order which gives the authority to apply that date.

*If the provision was previously entirely prospective and is now in force, it will add a start date to the provision (this can be seen on the timeline for the provision in the preview). Note: The first date on the timeline for any provision will be the earliest date for which it came into force (for any purpose). Where the provision comes into force on multiple dates, a new PiT will be made for each date. 

*If the ‘parent’ of the provision that is now in force was prospective, then the start date will also be added to the parent. If an earlier date was already on the parent (because another provision below it was already in force) then the existing start date will be retained, and a new PiT added for the coming into force of the provision that is being commenced. Note: The first date on the timeline for any “parent heading” will be the earliest date that any of its child provisions come into force (for any purpose).

*If the provision was previously entirely prospective but has a fixed future date (FFD) for coming into force it will still look prospective (although it will have an I-note detailing the FFD when it will come into force). 

===“Coming into force” effects added to TOES from data entered during the Initial Edit task===
“Coming into force” effects that that get added to TOES from data entered during the Initial Edit task are auto-applied when the “Latest Available (Revised)” version is deployed to the website. They are treated slightly different depending on whether they are prospective, in force at Royal Assent (RA)/Made date or come into force within one month of this date, or whether they come into force more than 28 days after the RA/Made date. 

====Provisions that come into force on either Royal Assent(RA)/Made date or dates within one month of RA/Made date==== 

When the “Latest Available (Revised)” version is deployed to the website, the “coming into force” effects for provisions coming into force on either Royal Assent (RA)/Made date or dates within one month of RA/Made date will be auto-applied by the Editorial System, the Edit Status will be marked as “Edit Complete”, and you will see a message message saying:

<blockquote>“<strong>Initial Edit Effects:</strong> This Coming into Force effect was added and reviewed by the initial edit task. No further action is necessary.”</blockquote>

Despite this system message you should still perform a <strong>brief spot check</strong>, using the website preview, opening the whole document and doing Ctrl+F to search for the date (or for “Royal Assent” or “made date” if that is the case) and click through all the instances checking for <strong>duplicate I-notes</strong>.  [[Editorial_Update/Approach_to_Update,_Specific_Update_Issues_and_Update_Troubleshooting#Duplicate_I-notes_where_there_are_multiple_provisions_within_one_P1Group|Duplicate I-notes may appear where we have multiple P1s in a P1group]] in the xml or where a change made to an I-note annotation during initial edit review has resulted in a slight discrepancy between the key-id in the annotation and the key-id in the TOES data.  [Note: we have raised a Jira story to ask TSO to change the system note to say at the end: "Brief spot check required to check for duplicate I-Notes." RLH, 13/10/2023]

 
[[File:Coming_into_force_8.png|900px]]

The provision will get a start date and when you preview it, you should see the date that the provision comes into force as the first date on the timeline. There will be an I-note containing the details of the commencement of that provision:


[[File:Coming_into_force_9.png|900px]]

====Provisions that come into force more than 28 dates after RA/Made date====
If a provision has a start date is <strong>more than 28 days</strong> after the Royal Assent or Made date of the document, it will show as prospective but with an I-note explaining that it comes into force at a fixed future date (FFD). Instead of getting a start date when the “Latest Available (Revised)” version is deployed to the website during Initial Edit (which would cause errors during editorial update if the provision subsequently got amended before it came into force), the application of the “coming into force” effect is completed during editorial update. This means that if there are subsequently any effects that need to be applied to the document before it comes into force, they can still be added to the update task (it is not possible to generate a PiT earlier than the start date of a provision). 
In the following update task, you can see there are 6 effects at an earlier PiT (which can be carried out as normal update), before the coming into force effects get applied on 12/10/2022 (when the provision will get a start date on the timeline): 


 [[File:Coming_into_force_10.png|900px]]

  
Before the coming into force effects are applied on 12/10/2022, the provision still looks prospective (but note that the I-note detailing the commencement is visible, even though the effects haven’t been fully applied yet, which will happen when the 12/10/2022 PiT update task is carried out):  

 [[File:Coming_into_force_11.png|900px]]

<!--Add screenshot of reg. 1 when SI 2022/725 publishes, to show what it looks like when an effect has been applied pre-commencement. Update 27/9/2023 - it is not possible to include screenshot of what it looks like when the coming into force effects have been applied, as it was corrected to a new start date of 1/8/2022 and the dates of the earlier effects were also corrected, so none of the above screenshots will relate to this-->

When you reach the commencement PiT in an update task with a “coming into force effect” more than 28 dates after RA/Made date, the “coming into force” effect update will be auto-applied and the Edit Status will be marked as “Edit Complete”. You will see a message saying: 

<blockquote><strong>“Initial Edit Effects:</strong> This Coming into Force effect was added and reviewed by the initial edit task. The start date needs to be checked for this provision.”</blockquote>

 [[File:Coming_into_force_12.png|900px]]
 
As the start date on the timeline has been generated during the update task rather than during Initial Edit, <strong>you need to check it is correct in the website preview as part of your editorial checks</strong>. Note that the I-note itself will have been reviewed during the Initial Edit task, before deployment to the website.

You can see what a document that comes into force at a FFD looks like when the coming into force effects have been applied in update here (the SI was made on 20/2/2018, but came into force on 1/10/2018):

https://www.legislation.gov.uk/uksi/2018/230/introduction/made

 [[File:Coming_into_force_13.png|900px]]

===Provisions that are not yet in force===
If a provision is not in force when the revised version is deployed to the website, and it does not have a start date, its status will be prospective and there will be an I-note explaining it is not in force at RA/Made date:  


 [[File:Coming_into_force_14.png|900px]]


When the provision is brought into force by a Commencement Order, it will have an I-note added via a Commencement Order “coming into force” effect as detailed in the next section.

<strong>Note:</strong> “not in force” I-note <strong>should not be removed</strong> when a provision is later brought into force by a commencement order because the original I-note forms part of the story of the commencement. For example:

https://www.legislation.gov.uk/uksi/2019/411/regulation/1/2019-03-25
 

 [[File:Coming_into_force_15.png|800px]]

===“Coming into force” effects entered into TOES during Commencement Order Record Effects tasks=== 
When a Commencement Order brings existing legislation into force we record the resulting effect as a “coming into force” effect. These are identified, recorded and researched during the [[Preparation_and_Research_Tasks#Preparation_Tasks|preparation stages]] of the editorial process. These “coming into force” effects are auto-applied by the editorial system during an update task. If a provision is brought into force by commencement orders in stages over time, the dates of “coming into force” effects that are applied will be arranged on the timeline like any other amendments, by in force date.

https://www.legislation.gov.uk/ukpga/2021/35/section/2
 

 [[File:Coming_into_force_16.png|800px]]

==The role of the update editor in applying coming into force effects==

“Coming into force” effects applied during editorial update are treated as non-textual amendments and are applied as <strong>auto annotations</strong> by the editorial system. 

When dealing with “coming into force” effects in editorial update, you should:

* Where the corresponding I-notes have been reviewed during the Initial Edit task, <strong>despite the “no further action” system message, you should perform a brief spot check</strong>, using the website preview, opening the whole document and doing Ctrl+F to search for the date (or for “Royal Assent” or “made date” if that is the case) and click through all the instances checking for duplicate I-notes and anything else that looks wrong.

* Where the corresponding I-notes have not previously been reviewed during the Initial Edit task, ensure that you are happy with the <strong>content of the auto annotation</strong>, double checking the commencement provision (whether this be in the commenced document itself or in a commencement order) and TOES to make sure that the [[Editorial_Update/Annotation_Conventions#I-notes_.28Commencement_information.29|annotation has rendered correctly]].

* Check that no <strong>duplicate I-notes</strong> have been generated during the editorial update task. If there are any duplicates, first check the tagging of the provisions concerned to check the duplicates aren't appearing due to multiple provisions being tagged as <code>P1s</code> within one <code>P1Group</code>. If duplicate I-notes are appearing due to the way the provisions have been tagged, you will need to retag the provisions rather than just removing the duplicate I-note references, see: [[Editorial_Update/Approach_to_Update,_Specific_Update_Issues_and_Update_Troubleshooting#Duplicate_I-notes_where_there_are_multiple_provisions_within_one_P1Group|Duplicate I-notes where there are multiple provisions within one P1Group]]. If the provisions are correctly tagged but there are duplicate <code>ukl:CommentaryRef</code> tags causing the duplicate I-notes to appear, please open the relevant provisions in XMetaL and remove the duplicate I-note by removing the <code>ukl:CommentaryRef</code> tagging for each duplicate I-note ref from each relevant provision before moving to next step. You can check out the main body and then Schedules to do this using the Table of Contents button in the update tool. You should usually delete the second one, but compare them with the commencement provision and see which best fits. Be careful where the provision is commenced at sub-provision level as the initial edit task will have added its I-note next to the provision number, whereas the update task will have added one or more duplicate I-notes next to each relevant sub-provision and they all need to be deleted.

* Check there are no <strong>missing I-notes in Schedules</strong>. Where an I-note is missing in a schedule because the online initial edit tool couldn’t cope with the xml structure and has entered <strong>schedule “wrapper” effects</strong> in TOES, you will need to add the I-note manually.  The TOES data should also be corrected so add a note to reviewer.

* Check the <strong>start dates of provisions</strong> that have been brought into force (N.B. remember to check start dates for “coming into force” effects that were reviewed at Initial edit, but come into force more than 28 days after RA/made date):

<blockquote>&#8212;	Use the ‘Preview Provision’ to check the start date on the timeline, it is recommended that you preview at least one provision this way.</blockquote>

<blockquote>&#8212;	Use the ‘Skeleton Preview’ to spot check start dates and annotations in the rest of the document. The Skeleton Preview can be found on the Update Overview Page:</blockquote>

 [[File:Coming_Into_Force_Effects_image_2.jpg|800px]]
 
The ‘Skeleton Preview’ gives an overview of the start dates for all the provisions in the item of legislation along with any I-notes that have been added. This can be very useful when spot checking start dates and any I-notes that have been added by the system when applying the “coming into force” effects:

 [[File:Coming_into_force_effects_3.png|800px]]



<strong>Note:</strong>
* It is advisable, especially with more complex coming into force scenarios, to refer back to the recorded effects and view the timeline for the whole document on legislation.gov.uk to establish the initial in force position for the item of legislation.

* You should also open the whole item of legislation in Preview and check that there are no prospective provisions that should be in force (prospective provisions will appear with grey background and be labelled prosp.)

* You will not need to change the ‘status’ of the effects, they will remain as ‘auto applied’.

* If you find an error in the auto annotation that needs fixing you can check the provisions out in the normal way.

* Do not remove any existing I-notes, which should be left in place to tell the story of the commencement, for example:

https://www.legislation.gov.uk/ukpga/2021/17/section/1/2021-10-01.


 [[File:Coming_into_force_19.png|800px]]

See also the following sections of the Wiki that also relate to I-notes: 

<strong>Specific Update Issues</strong>

[[Editorial_Update/Approach_to_Update,_Specific_Update_Issues_and_Update_Troubleshooting#Issues_with_I-notes|Issues with I-notes]]

<strong>EU Exit Update Guidance Notes</strong>

[[EU_Exit_Update_Guidance_Notes#I-notes_still_referring_to_.E2.80.9Cexit_day.E2.80.9D|I-notes still referring to exit day]]

[[EU_Exit_Update_Guidance_Notes#I-notes_needed_for_provisions_inserted_prior_to_IP_completion_day|I-notes needed for provisions inserted prior to IP completion day]]

[[EU_Exit_Update_Guidance_Notes#Child_provisions_revoked_immediately_before_IP_completion_day_should_look_prospective_and_their_I-notes_should_be_removed|Child provisions revoked immediately before IP completion day should look prospective and their I-notes should be removed]]

==Related pages==

[[Editorial_Principles#Commencement|Editorial Principles - Commencement]]

[[Editorial_Update/Annotation_Conventions#I-notes_.28Commencement_information.29| Editorial Update - Annotation Conventions/I-notes]]

[[Editorial_Update/Non-textual_Amendments | Editorial Update - Non-textual Amendments]]