Day 1 - Identification of Search Sheet Through Subjects - Sasine Advance Notices

Process Steps

Additional Information

2.1 Check if the search sheet number is noted on the advance notice form and that it is the correct search sheet.

2.1.1 If no search sheet number is provided or the wrong search sheet has been provided, identify the search sheet number through CSR/BOPS or RD index search facilities. See "Identify the search sheet(s) for your subjects" on Identify Correct Search Sheet - FR Intake and Closing Notes for guidance.

2.1.2 If there is no CSS for the subjects, create new search sheet in CSR. See Enter Closing Note - FR Intake and Closing Notes for guidance.

2.1.3 If search sheet cannot be found within 15 minutes, refer to advance notice referral officer.

2.2 Check the Advance Notice against the search sheet to check the description of the subjects of search and any exceptions match.

2.3 Check the search sheet does not contain a closing note .

2.3.1 When a closing note appears on the search sheet, the subjects narrated in that note have been transferred to the Land Register. Subsequent deeds can no longer be recorded in the Sasine Register and the Advance Notice must be rejected. 

2.3.2 When a closing note followed by '(KIR APP)' appears on the search sheet, the subjects narrated in that note have been transferred to the Land Register by Keeper-induced registration. Refer to advance notice referral officer. 

2.4 Add search sheet number, in pencil, to the advance notice form.

2.5 Add the county and the date of presentment on the advance notice form.

2.6 Complete rubric, noting any error(s).

2.7 Repeat steps 1.2 - 2.6 for the remainder of the advance notices in the batch.







Registers of Scotland (RoS) seeks to ensure that the information published in the 2012 Act Registration Manual is up to date and accurate but it may be amended from time to time.
The Manual is an internal document intended for RoS staff only. The information in the Manual does not constitute legal or professional advice and RoS cannot accept any liability for actions arising from its use.
Using this website requires you to accept cookies. More information on cookies.
Feedback