SPEAR

Help

Table of Contents > Validation Checks by Category

Check ePlan Metadata

Validation Rules


VR020 - Date of Survey Plan Manual Check


Example Messages

  • Plan was created on 12/05/2009; manual check is required to ensure currency.

Rule Description

If the plan was created more than two years ago, flag the plan for manual checking by an authorised plan examiner.


VR116 - Prior Survey Date


Example Messages

  • The previous plan "PS716856" with volume/folio of "10400/677" was surveyed more than 5 years prior to the current plan.
  • The previous plan "PS408798" with volume/folio of "10400/677" is not an ePlan in SPEAR, a manual check of the previous survey date is required.

Rule Description

Flag if the previous survey was surveyed more than 5 years before the current survey date.

  • Scenario 1: If previous survey is an existing ePlan in SPEAR then test the date, if it fails, fail with error.
  • Scenario 2: If previous survey is not an existing ePlan in SPEAR then flag that we are unable to check the previous surveys date.

Precondition

VR019 - Title Reference


VR102 - Mandatory Date of Survey if Surveyed


Example Messages

  • Plan is based on survey but does not specify a "Date of Survey".
  • "Date of Survey" cannot be later than today.
  • The plan has more than one "Date of Survey" specified.

Rule Description

  • If the ePlan is based on survey or partial survey, then a "Date of Survey" must exist.
  • If Date of Survey exists, date value must be equal or earlier than today.
  • There must be only one date of survey indicated for the plan.

VR021 - Plan Number Format


Example Messages

  • The plan number "PB123456" is not valid.
  • The plan is identified as a Plan of Consolidation but the plan number does not start with PC.
  • The plan is identified as a Plan of Subdivision but the plan number does not start with PS, SP, CS or RP.
  • The plan number "PS123456A" is not valid for a plan including Section 37 as the primary Dealing Type.
  • The primary Dealing Type must be a Section 37 for plan number "PC123456A/S3".
  • The primary Dealing Type must be either Section 37, Section 32 or Section 35 for compiled plan number "PS123456A/C3"
  • The primary Dealing Type must be Section 23, Section 24A or Section 26 for plan number "LV-To-Supply".
  • The number after 'C' in "PS123456A/C5" is not the same as the stage number "S2" in the SPEAR application.

Rule Description

  • Plan number of a subdivision plan number must be in a valid plan number format.

       a) A plan number must have a prefix of PS or PC, followed by a string of 6 numbers with no spaces and an alpha character representing the check digit. For section 32 plans, a plan number can start also with SP, CS or RP. Plan numbers starting with SP, CS or RP don't need to have an alpha character check digit (although some might)

       b) If the plan is a consolidation plan then the plan number should start with PC

       c) If the plan is NOT a consolidation plan then the plan number should start with PS (or SP, CS or RP as per above).

  • Plan number for any plan including Stage 37 Application Types must comply with PSXXXXXX$/S# or PSXXXXXX$/C#.
  • The primary Dealing Type for any Plan number which complies with PSXXXXXX$/S# must be a Section 37.
  • The primary Dealing Type for any Plan number which complies with PSXXXXXX$/C# must be Section 37, Section 32 or Section 35.
  • The primary Dealing Type for a Plan number of “LV-To-Supply” must be Section 23, Section 24A or Section 26. The check should not be case sensitive.
  • The number that comes after "C" in PS123456A/C3 must be the same as the stage number in the SPEAR application for Section 37 applications.

VR022 - Plan Number Allocation


Example Messages

  • The plan number "PS123456A" in ePlan is different to the plan number of the SPEAR application.
  • The plan number "PS123456" in the ePlan is already used by another application.
  • Compiled plan number "PS123456A/C4" is not consistent with Stage plan number "S4". Values after '/S' and '/C' must be the same.

Rule Description

  • Plan number used in ePlan must match the plan number specified in the SPEAR application.
  • Plan number used in the ePlan must not be already used by another application. Note: SPEAR already checks this at council certification time for all applications, do it at validation time as well for ePlan applications to identify the problem sooner.
  • Compiled plan number must be consistent with the Stage plan number, in the same SPEAR application e.g. expected compiled plan number for PS123456A/S2 is PS123456A/C2.

Precondition

VR021 - Plan Number Format


VR023 - Surveyor Registration Number


Example Messages

  • According to the Surveyors Registration Board of Victoria, "John Smith" has the registration number "1234". This does not match the provided surveyor name "Alex Ramsey".
  • "John Smith" was not registered and practicing according to the Surveyors Registration Board of Victoria at the time they performed the survey.

Rule Description

  • Registration numbers for surveyors must be valid according to Surveyors Registration Board of Victoria. This rule is executed only if the validation is run from within SPEAR.
  • The registration status of the surveyor must be "Registered and Practicing" at the Date of Survey.

Rule does not apply if there is no date of survey.

Precondition

VR002 - Survey Header Completeness


VR025 - Primary and Secondary Purpose Combination


Example Messages

  • The plan does not specify a valid dealing type (Section of Subdivision Act).
  • Plan under Section 22-Plan of Subdivision of the Subdivision Act 1988 cannot have a Section 35 dealing type.

Rule Description

All plans must specify at least one primary purpose and can have additional secondary purposes.

  • In the CIF, primary and secondary purposes are not separately specified. However this rule checks that one of the primary purposes listed below must exist.
  • VR001 - ePlan CIF Schema Validation checks the survey purpose specified are in the list of primary and secondary purposes. This rule checks at least one primary purpose is provided and if multiple purposes are provided they are valid secondary purposes.

The following table shows a combination of secondary purposes that can be used with each of the primary purposes:

Primary Purpose

Secondary Purpose(s)

Section 22

Section 6(1)(K), Section 23, Section 24A, Section 32B

Section 23

Section 24A

Section 6(1)(K), Section 23

Section 26

Section 32

Section 6(1)(K), Section 23, Section 24A, Section 35

Section 32A

Section 6(1)(K), Section 23, Section 24A

Section 32B

Section 35

Section 6(1)(K), Section 23, Section 24A

Section 35(8)

Section 6(1)(K), Section 23, Section 24A

Section 37

Section 6(1)(K), Section 23, Section 24A, Section 35, Section 37(8)

Precondition

VR002 - Survey Header Completeness

VR138 - Legislation and Relevant Dealing Types


VR026 - Purpose of Survey Section 22


Example Messages

  • Plan under Section 22 of the Subdivision Act 1988 has not subdivided any transferable parcels.
  • Plan under Section 22 of the Subdivision Act 1988 has not created any lot, stage lot, road, reserve or common property.

Rule Description

Plans with purpose of Section 22 must

  • Cancel at least one lot, stage lot, reserve, crown allotment or portion; and,
  • Create at least one primary parcel.

Precondition

VR025 - Primary and Secondary Purpose Combination


VR027 - Purpose of Survey Section 23


Example Messages

  • Plan utilising Section 23 component has not created, varied or removed any easement or restrictions.
  • Plan with primary purpose of Section 23 must have at least 1 affected primary parcel.
  • Section 23 of the Subdivision Act 1988 has not been specified when easements are being varied or removed in the plan.

Rule Description

  • Plans with purpose of Section 23 must include at least one created, affected or cancelled easement or restriction. If the primary purpose is Section 23 then there must also be at least 1 affected primary parcel.
  • If any easements or restrictions are affected or cancelled in the plan, Section 23 must be specified as a survey purpose.
  • If easement purpose or beneficiary is changed, then cancel the easement then re-create.
  • If easement/restriction extent is changed or if description of a restriction is changed, then this is considered as a variation (affected).
  • Blank parcelFormat in Parcels is treated as parcelFormat="Standard".

Precondition

VR025 - Primary and Secondary Purpose Combination


VR028 - Purpose of Survey Section 24A


Example Messages

  • Plan under Section 24A of the Subdivision Act 1988 cannot be used to vary or remove parcels other than reserves. "6~25\PP3473B" should be excluded from the survey plan or quote the appropriate section of the Subdivision Act.
  • A plan under Section 24A of Subdivision Act 1988 that does not provide a new PS number can only deal with affected reserves. There is no 'affected' 'reserve' within the parcels in this plan.
  • A plan under Section 24A of Subdivision Act 1988 that provides a new PS number can only deal with extinguished reserves. There is no 'extinguished' 'reserve' within the parcels in this plan.

Rule Description

  • Plans with purpose of Section 24A must deal with existing affected or extinguished reserves only.
  • If the above condition passes then check:
       a) If dealing type is Section 24a-Vesting of a Reserve, then the plan must deal with affected reserves.
       b) If dealing type is Section 24a-Removal of a Reserve (Plan of Subdivision), Section 24a-Removal of a Reserve (Plan of Consolidation), Section 24a-Removal and Vesting of a Reserve (Plan of Subdivision), or Section 24a-Removal and Vesting of a Reserve (Plan of Consolidation), then the plan must deal with extinguished reserves.
  • Section 24A plans typically remove existing reserves then create new lots, roads or reserves. If Section 24A is used as the only survey purpose, then creating, affecting or extinguishing other types of parcels must report the error condition.

Precondition

VR025 - Primary and Secondary Purpose Combination


VR081 - Purpose of Survey Section 32B


Example Messages

  • Plan under Section 32B of the Subdivision Act 1988 has not created any Owners Corporations.

Rule Description

Plans with purpose of Section 32B must include at least one created Owners Corporation.

Precondition

VR025 - Primary and Secondary Purpose Combination


VR082 - Purpose of Survey for Lands Affected by OC


Example Messages

  • "2\PS123456" affected by Owners Corporation "OC1\PS123456" is being varied. Plan varying or subdividing land affected by existing Owners Corporation must quote Section 32 or Section 32A of the Subdivision Act.

Rule Description

If lots or common properties affected by existing owners corporation are being varied or cancelled, Section 32 or Section 32A must be included as a purpose of survey.

Precondition

VR025 - Primary and Secondary Purpose Combination


VR030 - Purpose of Survey Section 35 Vesting Manual Check


Example Messages

  • Plan under Section 35 of the Subdivision Act 1988 has recording of vesting table attached.
  • Plan under Section 35 of the Subdivision Act 1988 does not have recording of vesting table attached.

Rule Description

Plans with purpose of Section 35 should always have an associated vesting annotation, whether it does or not, bring to the attention of examiners.

Precondition

VR025 - Primary and Secondary Purpose Combination


VR031 - Purpose of Survey Section 35, 32, 37 Manual Check


Example Messages

  • Plan utilising both Section 32 and Section 35 of the Subdivision Act 1988 must be manually checked.

Rule Description

If plans specify purpose of Section 35 also specifies Section 32 or Section 37, manual check is required by authorised examiners.

Precondition

VR025 - Primary and Secondary Purpose Combination


VR103 - Purpose of Survey Section 35 Annotations


Example Messages

  • Plan has specified a purpose of "Section 35" but does not contain the required Section 35 annotations: "Section 35 Compulsory" or "Section 35 Agreement".
  • Section 35 annotation has not been linked to at least one valid parcel. This annotation must be linked to only Lots, Roads and Reserves (except abuttals).
  • Annotation(s) with type "Section 35 Compulsary" have been specified but the plan purpose is not Section 35.
  • "3\PS123456" cannot be referenced by both "Section 35 Compulsory" and "Section 35 Agreement" annotations.

Rule Description

  • If the plan purpose is Section 35, one or both of the following annotation types must be present: "Section 35 Compulsory" and "Section 35 Agreement".

  • If Section 35 annotation exists,
       a) Each annotation must be linked to one or more Lot, Road or Reserve.
       b) "Section 35" must be specified as one of the plan purpose.
       c) A Lot, Road or Reserve cannot be associated with both annotations.

Precondition

VR025 - Primary and Secondary Purpose Combination


VR032 - Purpose of Survey Section 37


Example Messages

  • Plan under Section 37-Plan of Subdivision (Staged Plan) of the Subdivision Act 1988 has not subdivided any stage lots.

Rule Description

Plans with purpose of Section 37 must include at least one extinguished stage lot.

Precondition

VR025 - Primary and Secondary Purpose Combination


VR140 - Purpose of Survey Section 26


Example Messages

  • Plan under Section 26 of the Subdivision Act must deal with existing primary parcels only.
  • This boundary plan has easements. Please ensure all existing easements are included.

Rule Description

Plans with purpose of Section 26 must deal with existing primary parcels only. If there are easements, show an info message that all existing easements are included.

Precondition

VR025 - Primary and Secondary Purpose Combination


VR033 - Planning Permit Annotation Manual Check


Example Messages

  • Planning permit number has been provided for the survey plan. Check for validity.

Rule Description

If planning permit number is provided, bring to the attention of examiners.


VR034 - Depth Limitation Manual Check


Example Messages

  • Plan has identified that depth limitation does not apply.
  • Plan has identified a depth limitation of "15.24 metres".

Rule Description

Identifies whether depth limitation applies on the plan for review by authorised examiners.

Precondition

VR018 - Annotation Parcel References

VR079 - Depth Limitation Parcel Structure


VR093 - Section 32 Non-survey Plans


Example Messages

  • The non-survey plan has a section 32 component, manual check is required for validity.

Rule Description

If a non-survey plan has a section 32 component, flag it to examiners.


VR108 - NICO Plans


Example Messages

  • Created lot(s) 1 have multiple registered proprietors of A, B from VOTS. This Plan is a NICO Plan.

Rule Description

If the plan with purpose of Section 22, 32, 35 or 37 is a Not In Common Ownership (NICO) plan, flag it for attention.


VR120 - Parent Plan In ePlan Format


Example Messages

  • The previous plan "PS123456" with volume/folio of "12345/678" is available in ePlan format.

Rule Description

Flag if the previous survey exists in ePlan format.

Rule does not apply if previous plan is not in SPEAR or is not in ePlan format.


VR138 - Legislation And Relevant Dealing Types


Example Messages

  • The plan specifies that it was prepared under both the Subdivision Act 1988 and the Transfer of Land Act 1958 but only one is allowed.
  • The plan is prepared under the Subdivision Act 1998 but the provided purpose(s) "Section 99" are not allowed under that act.

Rule Description

1) Only one of Subdivision Act 1988 and Transfer of Land Act 1958 is allowed.

2) If the legislation is Subdivision Act 1988 then only the following purposes are allowed:

  • Section 22-Plan of Subdivision
  • Section 22-Plan of Consolidation
  • Section 23-Creation of Easement
  • Section 23-Removal of Easement
  • Section 23-Variation of Easement
  • Section 23-Creation and Removal of Easement
  • Section 23-Creation and Variation of Easement
  • Section 23-Removal and Variation of Easement
  • Section 23-Creation and Removal and Variation of Easement
  • Section 23-Variation of Condition in Crown Grant
  • Section 23-Removal of Condition in Crown Grant
  • Section 23-Creation of Restriction
  • Section 23-Removal of Restriction
  • Section 23-Variation of Restriction
  • Section 24a-Vesting of a Reserve
  • Section 24a-Removal of a Reserve (Plan of Subdivision)
  • Section 24a-Removal of a Reserve (Plan of Consolidation)
  • Section 24a-Removal and Vesting of a Reserve (Plan of Subdivision)
  • Section 24a-Removal and Vesting of a Reserve (Plan of Consolidation)
  • Section 26
  • Section 32-Plan to alter land affected by an owners corporation (Plan of Subdivision)
  • Section 32-Plan to alter land affected by an owners corporation (Registered Plan)
  • Section 32-Plan to alter land affected by an owners corporation (Strata Plan)
  • Section 32-Plan to alter land affected by an owners corporation (Cluster Subdivision)
  • Section 32a-Plan of Subdivision of land if an owners corporation is affected
  • Section 32a-Plan of Consolidation of land if an owners corporation is affected
  • Section 32b-Plan to create an owners corporation (Existing Plan)
  • Section 32b-Plan to create an owners corporation (New Plan)
  • Section 35-Acquisition of land by acquiring authority
  • Section 35-Acquisition of land if an owners corporation is affected (Plan of Subdivision)
  • Section 35-Acquisition of land if an owners corporation is affected (Registered Plan)
  • Section 35-Acquisition of land if an owners corporation is affected (Strata Plan)
  • Section 35-Acquisition of land if an owners corporation is affected (Cluster Subdivision)
  • Section 35(8)-Subdivision of land vested or registered in authority
  • Section 35(8)-Consolidation of land vested or registered in authority
  • Section 37-Plan of Subdivision (Staged Plan)
  • Section 37-Acquisition of land (Plan of Subdivision (Staged))
  • Section 6(1)(K)

Precondition

VR002 - Survey Header Completeness


VR139 - Future Plan Number Annotation


Example Messages

  • The "Future Plan Number" annotation can only be provided in a Boundary Plan.
  • The plan number "PS123456A" provided by the "Future Plan Number" annotation is not valid.
  • The plan number "PS123456A" provided by the "Future Plan Number" annotation is already used by another application.

Rule Description

The 'Future Plan Number' annotation:

  • is optional, but if provided can only be provided in a Boundary Plan
  • must be in a valid plan number format: A plan number must have a prefix of PS or PC, followed by a string of 6 numbers with no spaces and an alpha character representing the check digit.
  • must not be already used by another application. Note: SPEAR already checks this at council certification time for all applications, do it at validation time as well for ePlan applications to identify the problem sooner.