From the Amendment Manager—
Select Amendment Actions > Create Official List from the dropdown menu in the top right of the page
Select ‘Notice of Amendments’
Update the relevant information in the dialog box and click on Create
In the Editor—
The Notice of Amendments will appear in a new tab in the Editor, containing all relevant amendments sorted and grouped
Process and logic for auto-generating the Notice of Amendments
Filtering which amendments to include in the list
Amendments will appear in the Notice of Amendments if—
they were recorded as having been “tabled” up to the specified cut-off date (and time if supplied), and
they haven’t already been published on another list (to check if an amendment has been published on another list, open the amendment in a temporary list, place cursor in the amendment, open ‘Amendment status’ in the right-hand panel and click on the link “Manage lifecycle events” which will list all events, including ‘published’ if it has been published. If it was published in error, you can delete this event.)
Grouping the amendments
Amendments are grouped by proposer so that all amendments tabled at the same time by a particular proposer will appear together in the Notice.
Lawmaker uses the ‘Submitted’ date/time to determine sort order.
The groups of amendments are sorted by whoever submitted their amendments to the Bill Office earliest - the proposer to submit their amendments first will appear first in the Notice.
This can mean that if a proposer submitted another batch of amendments after their first batch, and after another proposer had submitted their amendments, this new batch of amendments would not be grouped with the first set of tabled amendments by the same proposer.
Sorting the amendments
Amendments within each proposer group are sorted by the order they appear in the bill - Clauses 1-n, Schedules 1-n and Long Title amendments appearing last.
As automatic sorting in Lawmaker is limited to page and line information gleaned from the amendment, you might sometimes need to add sort codes when there are 2 or more amendments with the same location information.
If an amendment is sorted incorrectly, you can use the structure view to drag & drop it to the correct location. However, you risk this error creeping in again when the Marshalled List is eventually generated. The best solution would be to update the amendment’s location information in the ‘Amendment Information’ right-hand panel. You may also need to other amendments immediately before and after it if the reason for incorrect sorting is because they all share the same page-line information.
In the Editor—
Place cursor in the amendment to amendment
View ‘Amendment Information’ in the right-hand panel
update the Sort Code to define which sort order the amendments should appear in e.g. “1” for the first and “2” for the next.
Once you have updated the amendments' location information, you can either refresh the list (Tools > Update List) or use the structure view to drag the amendment(s) to their correct location.
Amendments to amendments
If you have any amendments to amendments (a2a) in your Notice of Amendments, it’s likely you will need to update the location information for these amendments in the ‘Amendment Information’ right-hand panel. Generate a Notice of Amendments
In the Editor—
Place cursor in the amendment to amendment
View ‘Amendment Information’ in the right-hand panel
If the target amendment of your a2a is a new clause/schedule amendment
update the Location field with “before/after” depending on the source amendment,
update the Provision with “sec_x” if it is a Clause or “sch_y” if it is a Schedule - using the appropriate number in place of x and y, and
if there are more than one a2a with the same target amendment, consider using the sort code to define which sort order they should appear in e.g. “1” for the first and “2” for the next.
If the target amendment of your a2a is another page-line style amendment
update the Provision with “sec_x” if it is a Clause or “sch_y” if it is a Schedule - using the appropriate number in place of x and y,
update the Page with the target amendment's page,
update the Line with the target amendment’s page, and
if there are more than one a2a with the same target amendment, consider using the sort code to define which sort order they should appear in e.g. “1” for the first and “2” for the next.