Plans Ident Process for FRs and VRs in Plan Creator - COF not suitable for approval
This section contains guidance on how to ident standalone First Registration (FR) and Voluntary Registration (VR) applications in the Plan Creator when there is a COF but it is not suitable to approve as there are differences in the extents or references.
Plans Ident for FRs & VRs - COF not suitable for approval
1 In CMS, take on the next case at Plans Standard (or click on next assignment, depending on individual setting settings).
2 Take on the case at Plans Settle in the LRS using the application number.
3. 1 Examine the DIR and any extent deeds to determine the extent of the property/area of ground to be registered and any rights and burdens to ensure these agree with the references on the COF.
3.2 Complete a Cadastral Check of the COF references to ensure that no titles have been registered since the COF file was prepared.
3.3 If any extent issues are identified, or if the references required are different to those shown in the COF, then the COF cannot be approved.
4 In the Plan Creator, create a DCU .
Plan type is DCU.
Plan ID is the Application Number of the case.
Use the postal address if available to locate the subjects in the DCU, and if no postal address exists then use other available information to locate the subjects for the seed point.
5 Create Plan. The seed point will pre-set on the subjects if a postal address was used. If no postal address then move the seed point onto the subjects, preferably within a building if there is one on the subjects.
6 Copy the existing COF extent into the DCU, make any amendments necessary to the extent, and hatch the polygon(s) red and classify as ident.
7 In the case notes box please add a note to the effect of "The area hatched in red is the ident extent for the DCU 20MID12345, Title MID12345".
8 When the subjects have been idented, Save the DCU.
9 In the CMS, complete the Plans Ident process and categorise the case as a Cat 3 or Cat 4 depending on complexity.
10 If the supporting documents are not categorised with the relevant deed details and recording date then ensure this is done before releasing.
11 Ensure the case gets released to the correct Plans Settle destination depending on the category and complexity., i.e. Plans Standard, Advanced or Authority.
12 In the LRS, ensure the Category is the same as the CMS Category (If these are different, it causes issues further down the line).
13 Release the case on LRS to Plans Settle.
DCU already exists - error message
When creating a DCU and the following error message appears:
then ensure that the title is unapproved in the Plan Approver (see "Title Plan already exists" solution). If problems are still encountered, speak to a business lead user who can contact the mapping domain if they cannot resolve the issue for you.