Pool Compliance
- Joanne Hocking
- 1 Overview
- 2 Pools Compliance Video
- 3 Setting up a new Pools Compliance event
- 4 Compliance Cases
- 5 Compliance Survey
- 6 Compliance Inspections (Technical & Non-Technical Inspections)
- 7 Compliance Notices
- 8 Status/Escalation Rules
- 9 Workflow
- 10 Configuring your merge templates
- 11 Technical Reference
- 11.1 Compliance Case
- 11.1.1 Default schema
- 11.2 Non-schema fields
- 11.3 Workflow
- 11.4 Compliance Inspections
- 11.5 Core schema
- 11.6 NonTechAssessment schema
- 11.7 TechAssessment schema
- 11.8 Non-schema fields
- 11.9 Workflow
- 11.10 Pool and Spa Surveys
- 11.10.1 Default schema
- 11.10.2 Non-schema fields
- 11.10.3 Workflow
- 11.11 Compliance Notices
- 11.12 Default schema
- 11.13 Non-schema fields
- 11.14 Workflow
- 11.1 Compliance Case
Overview
The Pool Compliance module allows you to manage pool compliance investigation for properties with a number of different registers and templates.
The module is made up of the following major features:
Initial Import of properties into Compliance Cases
Generating PDF enquiry letters via HTML template
Public Pool and Spa Survey form
Technical and Non-Technical Inspections
Generating PDF Notice of Inspections via HTML template
Generating PDF Infringement Notices via HTML template
Automated creation of technical inspections from cases, surveys and non-technical inspections
The Pool Compliance module is currently made up of 3 registers:
Compliance Case - the top-level register responsible for tracking an instance of a pool compliance investigation.
Compliance Inspection - various assessments are conducted as part of a compliance investigation, including:
A non-technical inspection
A technical inspection
These are each implemented as separate schemas, and can be related to the Case record many times.
Pool and Spa Survey - a self-service customer survey is available via a public form.
On submission, it finds any open compliance cases of the same property address and attaches itself, and then updates the case workflow state to alert the case officer. It also creates technical assessments when there is a case match and the user has indicated on the survey that they have a pool.
Pools Compliance Video
Below is a video outlining the main features of the Pools Compliance module
Setting up a new Pools Compliance event
An event template called Pools Compliance Template can be used to simplify this process.
When you create your new event, select this template from the Template drop down list (see screenshot below). This will ensure all of the necessary registers and positions will be created for your new event.
Positions/Competencies
Currently there are 4 positions created that have access to this module:
Compliance Coordinator - grant this position to users that wish to manage your pool compliance event. Any user with this competency can manage pool compliance applications
Compliance Officer - this position has full read access to items with the ability to edit data that is assigned
Compliance Limited - this position has limited read/write access to compliance only where the data is assigned
Compliance Read Only Assigned - this position can view compliance items that have been assigned to them
To accept public surveys put that Public User on duty to your event
The public submission process is controlled by the __PUBLIC__ user’s ability to submit surveys
To enable public survey submissions, you need to perform the following action:
Go to Administration > Users
Edit the Public User (User, Public)
Check that the user has the competency Pool Compliance Public User, or add it if it is missing.
Now click Duties on that user’s record
Put the user on duty as the Pool Compliance Public User position for the event you’re using for accepting surveys.
To disable subissions
Take the
__PUBLIC__user off duty for the Pool Compliance Public User position.
Public Submissions
When active, the public submission URL will be https://yoursite.crisisworks.com/register/public-item/new/register/complianceSurvey. You can link to this from your website.
The public submission form
The public submission form allows anonymous users to submit a survey form.
Configuring the public form help text
A special library item contains the help text that appears in the sidebar for the public form.
Edit the page Public Pool Compliance Survey Help Text which can be found in the global library items, to control the text that will appear in the sidebar for the public survey form.
Compliance Cases
This is the top-level register responsible for tracking an instance of a pool compliance investigation.
You can create cases from within Crisisworks by clicking on the blue New Compliance Case button or you can import new cases from a .CSV file which will create new cases in a DRAFT state.
You can then perform Desktop Assessments. From here you can update the status to either Generate Enquiry Letter or Generate Infringement. In these statuses, you can select the appropriate items from the datagrid and use the Generate Merge feature to generate either the Enquiry Letter or an Infringement Notice (infringement notices coming in February 2022).
Enquiry Letter
The Enquiry Letter will contain a link to the Pool and Spa Survey which is the public form. Once the user completes the form, on save it will detect if there are any open Compliance Cases in the same event that have the same property address and if so a link is created between the Compliance Case and the Compliance Survey.
When the Enquiry Letter has been generated for a case it will automatically set the Notice Printed Date with the date that it was generated. The status will then update to Awaiting Survey Response and the PDF document will be displayed in the case
Related Surveys
A list of the related survey results will appear as a read-only list on the case with a link to the survey.
If a matching between the Case and Survey is found, the case status will update to Survey Received.
Scheduling Inspections
The Case also has the statuses Schedule Technical Inspection and Schedule Non-Technical Inspection. If these statuses are selected, on save it will automatically create a new Compliance Inspection record and set the appropriate schema (Technical Inspection or Non-Technical Inspection). The status of the case will then automatically update to Awaiting Inspection.
The Awaiting Inspection status has a 30 days escalation period. If the status remains in this status for 30 days the status will automatically update to Inspection Due
A list of related Technical and Non-Technical Inspections will appear a a read-only list on the case with a link to the inspection.
Importing Compliance Cases
To import Compliance Cases you will need to create a .CSV file with the assets you want to create cases for. See below for the headings you can include in your .CSV file. The Asset Code field is the only required field.
To import your .csv file, go to the Administration menu and choose Import Data. Choose Compliance Cases from the drop down list. Choose Compliance Cases from the next screen as well.
On the page after that is where you can upload your import file. Ensure you choose the new Pool Compliance event you have created.
All imported Compliance Cases will be set to a DRAFT status. You will need to update this status when you begin managing the case(s).
Compliance Survey
The Compliance Survey is a public form which asks the user to enter their contact information, address details and whether they have a pool or not.
Once the user completes the form, on save it will detect if there are any open Compliance Cases in the same event that have the same asset and if so a link is created between the Compliance Case and the Compliance Survey.
If a match to a case is found, the Survey status will update to Matched. If no match is found it will update to Unmatched.
If the user selects they have a pool, it asks how many pools they have. If a matching case is found, it will create new Technical Inspections records for the number of pools they have. For example, if the user has 2 pools it will create 2 Technical Inspections (Compliance Assessment). These new Technical inspections will be listed on the related case.
Compliance Inspections (Technical & Non-Technical Inspections)
The Compliance Inspections register is made up of 2 schemas Non-Technical Inspection and Technical Inspection.
On save, it will detect if there are any open Compliance Cases in the same event that have the same asset and if so a link is created between the Compliance Case and the Inspection.
A list of Technical and Non-Technical Inspections are listed on the related case.
The Non-Technical inspection
This schema asks simple questions such as whether there is a pool/spa present at the property and if any technical inspections are required and how many. It is assumed it will generally be completed on-site by an inspector allowing them to add the inspection date and the inspector.
Technical Inspection
This schema asks more technical questions and is assumed it will generally be completed on-site by an inspector allowing them to add the inspection date and the inspector.
The inspector will select the purpose of the inspection which has two options:
Assessment of pool against AS1926.1-1993
Confirm absence or decommissioning of pool/spa
Depending on the selection, different form elements will appear.
For the Assessment option, questions regarding whether gates, barriers etc comply or does not comply.
Enforcement
Under the Enforcement section of the Technical Assessment, there is a question “Did Pool/Spa barrier comply?”. If this is set to Yes the inspection record status is updated to Compliant on Save. If this is set to No, the following further fields are displayed.
Refer to MBS - if ticked, this item with appear in the Refer to MBS counter for follow up)
Schedule a follow-up inspection - if ticked, a new Compliance Inspection record is created (Technical Assessment type). The current inspection will be set to Closed.
Issue one or more notices - if ticked, this opens up a new subform allowing you to create notices from within the assessment. See more information below.
Creating Notices from Inspections
When the “Issue one or more notices” checkbox is ticked, an Add button will appear. Click this button which will display a new subform allowing you to create notices from within the assessment.
Choose the appropriate Notice Type. Depending on the Notice Type selected, different fields will be displayed in the form which are appropriate to the type.
You can click on the Add button to create additional notices for the Inspection if needed.
On save, the property asset used for the Inspection will copy into the new Notice record(s). If a Case uses the same asset, a link will be created between the Notice and the Case.
See below for more information on Compliance Notices.
Compliance Notices
Compliance Notices manage all of the mail merge notices (except the initial Inquiry Letter). These notices can be created either via the Technical Assessment (as mentioned above) or from the New Compliance Notice blue button on the top right hand side.
When wanting to create a new Mail Merge notice (ie Notice of Inspection, Notice of Infringement etc), firstly a Compliance Notice record should be created, Once the notice has been created, you will generate your mail merge notices via this register.
Choose the appropriate Notice Type. These Notice Types are generated from Crisisworks Lookups (see Lookups section below) and can be added to if needed. Depending on the Notice Type selected, additional fields will appear in the form. See below for more information on Compliance Notices.
Current Notice Types:
Infringement (failure to register) - an Infringement Types multi select box will appear allowing you to choose multiple infringement types. These infringement types are also managed via Crisisworks Lookups and can be added to if needed. Select one or more infringement types by selecting from the list. These infringement types will appear on the Infringement Notice. The Infringement Fine Amount defaults to $330 but can be changed when needed. This amount appears on the Infringement Notice.
Infringement (pool not comply with standard) - a Non-Compliant Items area will display. Copy the items from the inspection that were not compliant into this section.
Notice of Inspection - an Inspection Date field will appear. This date will appear on the Notice of Inspection letter.
Building Order Minor Works - a Works Required field is displayed allowing the inspector to enter what works are required. These will appear on the merge template.
Emergency Order
When viewing the notice register (not via the Inspections register) additional fields will appear in this view.
Notice number - auto generated 10 digit sequential number that is used in the notice. This will be automatically populated.
Integration Reference Number - an optional field to help you identify this notice in your internal system
Integration Date - an optional field of the date the notice was integrated into your internal system
Before notices have been generated, they will appear in the Ready to Print state. Once a mail merge template has been generated for the notice, the Notice Printed Date will be populated and the notice will be attached to the record. The status will be updated to Printed.
To Generate Mail Merges in bulk, click on the appropriate Notice Type counter on the left hand side of the datagrid. Select the apprpriate items' checkboxes and click the Generate Mail Merge button. Choose the appropriate notice template to use.
Status/Escalation Rules
The following escalation and status rules have been setup.
Register | Action | Next Status | Escalation Time (Next Action Due date will override this escalation time set) | Comment |
|---|---|---|---|---|
Compliance Case | Survey generated | Awaiting Survey Response | 14 days |
|
Compliance Case | Survey not received within escalation time | Generate Infringement > Infringement Generated |
| The Generate Infringement status will create a new Compliance Notice and automatically update to Infringement Generated. |
Compliance Case | Survey received - has pool or spa but not registered | Not Registered | 14 days |
|
Compliance Case | Not Registered status not changed to Registered within escalation time | Generate Infringement > Infringement Generated |
| The Generate Infringement status will create a new Compliance Notice and automatically update to Infringement Generated. |
Compliance Case | Survey Received - has pool or spa and registered | Registered |
|
|
Compliance Case | Survey Received - no pool or spa on property | Awaiting Inspection |
| A non-technical assessment is created. Case status updated to Awaiting Inspection. |
Compliance Case | Survey Received - there was a previous pool or spa on property | Awaiting Inspection |
| A technical assessment is created. Case status updated to Awaiting Inspection. |
Compliance Case | Status set to Initial Assessment Required | Assessment Due | 4 weeks | After 4 weeks in the Initial Assessment Required status it will automatically transition to Assessment Due |
Compliance Case | Status set to Awaiting Inspection | Inspection Due | 4 weeks | After 4 weeks in the Awaiting Inspection status it will automatically transition to Inspection Due |
Compliance Inspection (Non-Technical Assessment) | Purpose - assessment. No Pool/Spa present selected | Compliant |
| On save the item will be updated to Compliant |
Compliance Inspection (Non-Technical Assessment) | Purpose - assessment. Pool or Spa present selected | Not Compliant |
| On save the item will be updated to Not Compliant |
Compliance Inspection (Technical Assessment) | Purpose - assessment. Did Pool/Spa barrier comply - set to Yes | Compliant |
| On save the item will be updated to Compliant |
Compliance Inspection (Technical Assessment) | Purpose - assessment. Did Pool/Spa barrier comply - set to No | Not Compliant |
| On save the item will be updated to Not Compliant |
Compliance Inspection (Technical Assessment) | Purpose - confirm absence. Either “Satisfied no pool/spa present” or “Satisfied pool/spa effectively decommissioned” have been selected | Compliant |
| On save the item will be updated to Compliant |
Compliance Inspection (Technical Assessment) | Purpose - confirm absence. If neither “Satisfied no pool/spa present” or “Satisfied pool/spa effectively decommissioned” have been selected | Not Compliant |
| On save the item will be updated to Not Compliant |
Compliance Inspection (Technical Assessment) | Schedule a follow-up inspection selected | Closed |
| A new technical assessment with the same property will be created and the current inspection will be set to closed. |
Compliance Notice | Notice has been generated | Printed |
| When a notice has been printed (generated), the Notice Printed Date will be set with the current date and the status updated to Printed. |
Workflow
Below is the current workflow for these registers:
Configuring your merge templates
Enquiry Letters, Notice of Inspections and Infringement notices are all generated using the Merge Templates system.
Click Administration > Settings
Click Merge Templates
You can create a new blank template, or you can use an existing template as a base. The system comes pre-loaded with the following sample templates that you can copy and customise.
Pool and Spa Survey HTML Template Sample
Pool Compliance Notice of Inspection (NOI) HTML Template Sample
See A guide to creating custom mail merge templates to learn more about merge templates.
Technical Reference
Compliance Case
This table is subject to change
Default schema
| Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
desktopAssessmentNotes | Desktop Assessment Notes | rte | clob |
| Enter notes resulting from the Desktop Assessment |
relatedSurveys | Survey response | itemLink |
|
| Read only unless 'id:true'; the following survey(s) have been submitted with the same address |
relatedNotices | Related Notices | itemLink |
|
| Read only unless 'id:true'; the following Notices have been created for this property |
mergedFile | Merged Documents | media |
|
| This is a collection of documents that have been generated for this item when running the Merge Documents process. |
relatedNonTechInspections | Related Non-Technical Inspections | itemLink |
|
| Read only unless 'id:true'; the following Non-Technical Inspection(s) have occurred for this address |
relatedTechInspections | Related Technical Inspections | itemLink |
|
| Read only unless 'id:true'; the following Technical Inspection(s) have occurred for this address |
assignee | Assigned | assignment |
|
| Single assignment to Arrays |
dateNoticePrinted | Notice Printed Date | datePicker | timestamp |
|
|
Non-schema fields
Field ID | Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
hasAsset | Property | asset |
|
| Supports Addresses (Vicmap), Properties (Vicmap), Properties (Imported), Points of Interest, Parcels (Vicmap) and Library Items; MDA94 projection used for geospatial assets |
hasDueDate | Next Action Due | duedate |
|
|
|
hasEvent |
| event |
|
|
|
hasStatus |
| status |
|
|
|
hasTags |
| tags |
|
|
|
Workflow
Workflow ID | Label | Value | Next States | Initial State |
|---|---|---|---|---|
NEW | New | 1 | NEW, DRAFT, ASSESSMENTREQUIRED | ✓ |
DRAFT | Draft | 10 | DRAFT, ASSESSMENTREQUIRED, INQUIRYLETTER |
|
ASSESSMENTREQUIRED | Initial Assessment Required | 20 | ASSESSMENTREQUIRED, ASSESSMENTDUE, INQUIRYLETTER, GENERATEINFRINGEMENT, SCHEDULETECHINSPECTION, AWAITINGINSPECTION |
|
ASSESSMENTDUE | Initial Assessment Due | 30 | ASSESSMENTDUE, ASSESSMENTREQUIRED, INQUIRYLETTER, GENERATEINFRINGEMENT, SCHEDULETECHINSPECTION, SCHEDULENONTECHINSPECTION, AWAITINGINSPECTION |
|
INQUIRYLETTER | Generate Inquiry Letter | 40 | INQUIRYLETTER, WAITINGSURVEY, SURVEYRECEIVED |
|
WAITINGSURVEY | Awaiting Survey Response | 50 | WAITINGSURVEY, SURVEYRECEIVED, SCHEDULETECHINSPECTION, SCHEDULENONTECHINSPECTION, AWAITINGINSPECTION, GENERATEINFRINGEMENT, INFRINGEMENTGENERATED, REGISTERED, NOTREGISTERED |
|
SURVEYRECEIVED | Survey Received | 60 | SURVEYRECEIVED, GENERATEINFRINGEMENT, INFRINGEMENTGENERATED, SCHEDULETECHINSPECTION, SCHEDULENONTECHINSPECTION, AWAITINGINSPECTION, NOTREGISTERED, REGISTERED |
|
GENERATEINFRINGEMENT | Generate Infringement | 70 | GENERATEINFRINGEMENT, INFRINGEMENTGENERATED, INQUIRYLETTER |
|
INFRINGEMENTGENERATED | Infringement Generated | 75 | INFRINGEMENTGENERATED, INQUIRYLETTER |
|
SCHEDULETECHINSPECTION | Schedule Tech Inspection | 80 | SCHEDULETECHINSPECTION, AWAITINGINSPECTION, INSPECTIONDUE, GENERATEINFRINGEMENT |
|
SCHEDULENONTECHINSPECTION | Schedule Non-tech Inspection | 90 | SCHEDULENONTECHINSPECTION, AWAITINGINSPECTION, INSPECTIONDUE, GENERATEINFRINGEMENT |
|
NOTREGISTERED | Not Registered | 95 | NOTREGISTERED, REGISTERED, SCHEDULETECHINSPECTION, SCHEDULENONTECHINSPECTION, GENERATEINFRINGEMENT, AWAITINGINSPECTION |
|
REGISTERED | Registered | 100 | REGISTERED, NOTREGISTERED, SCHEDULETECHINSPECTION, SCHEDULENONTECHINSPECTION, AWAITINGINSPECTION |
|
AWAITINGINSPECTION | Awaiting Inspection | 110 | AWAITINGINSPECTION, INSPECTIONDUE, COMPLIANT, NOTCOMPLIANT |
|
INSPECTIONDUE | Inspection Due | 120 | INSPECTIONDUE, COMPLIANT, NOTCOMPLIANT |
|
COMPLIANT | Compliant | 130 | COMPLIANT, CLOSEDCOMPLIANT |
|
NOTCOMPLIANT | Not Compliant | 140 | NOTCOMPLIANT, SCHEDULETECHINSPECTION, SCHEDULENONTECHINSPECTION, CLOSEDNOTCOMPLIANT |
|
CLOSEDCOMPLIANT | Closed: Compliant | -10 | CLOSEDCOMPLIANT |
|
CLOSEDNOTCOMPLIANT | Closed: Not Compliant | -20 | CLOSEDNOTCOMPLIANT |
|
Compliance Inspections
Core schema
Field ID | Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
inspectionDate | Inspection Date | dateTimePicker | timestamp |
| Required; please enter an inspection date |
assignee | Inspector | assignment |
|
| Single assignment to Arrays; select the inspector |
signedLetter | Has the occupier of the building/land signed the Inspection Letter (POE)? | radio | enum | yes, no | Required |
contactDetailsInfo | Details of person spoken to during inspection | info |
|
| Read only |
firstName | First Name | text | string(255) |
| Required |
lastName | Last Name | text | string(255) |
| Required |
phoneNumber | Mobile Phone Number | tel | string(255) |
|
|
|
|
| |||
ownerOccupier | Please select your relation to the above property address | radio | enum | owner, occupier, other | Required |
NonTechAssessment schema
Field ID | Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
inspectionDate | Inspection Date | dateTimePicker | timestamp |
| Required; please enter an inspection date |
assignee | Inspector | assignment |
|
| Single assignment to Arrays; select the inspector |
signedLetter | Has the occupier of the building/land signed the Inspection Letter (POE)? | radio | enum | yes, no | Required |
contactDetailsInfo | Details of person spoken to during inspection | info |
|
| Read only |
firstName | First Name | text | string(255) |
| Required |
lastName | Last Name | text | string(255) |
| Required |
phoneNumber | Mobile Phone Number | tel | string(255) |
|
|
|
|
| |||
ownerOccupier | Please select your relation to the above property address | radio | enum | owner, occupier, other | Required |
poolSpaPresent | Is there a pool/spa present at the property? | radio | enum | yes, no | Required |
isTechAssessmentRequired | Are any technical assessments required? | checkbox | boolean |
|
|
numberofTechAssessmentsRequired | Number of technical assessments required | number | integer |
| Only available if 'isTechAssessmentRequired:true'; defaults to 1 |
nonTechAssessmentMedia | Photo | media |
|
| Add any photos |
additionalNotesNonTech | Additional Information | textarea | clob |
|
|
relatedNonTechComplianceCases | Related Compliance Cases | related |
|
| Read only unless 'id:true'; related cases linked to the same asset |
TechAssessment schema
Field ID | Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
inspectionDate | Inspection Date | dateTimePicker | timestamp |
| Required; please enter an inspection date |
assignee | Inspector | assignment |
|
| Single assignment to Arrays; select the inspector |
signedLetter | Has the occupier of the building/land signed the Inspection Letter (POE)? | radio | enum | yes, no | Required |
contactDetailsInfo | Details of person spoken to during inspection | info |
|
| Read only |
firstName | First Name | text | string(255) |
| Required |
lastName | Last Name | text | string(255) |
| Required |
phoneNumber | Mobile Phone Number | tel | string(255) |
|
|
|
|
| |||
ownerOccupier | Please select your relation to the above property address | radio | enum | owner, occupier, other | Required |
obtainPermit | Did you obtain a building permit for the pool/spa and barrier? | radio | enum | yes, no | Required |
awareOfPermit | Are you aware that a building permit is required to install pool/spa barrier? | radio | enum | yes, no | Required |
awareOfRegistration | Are you aware that you are required to register your pool with your Local Council? | radio | enum | yes, no | Required |
reasonForNoPermit | What is your reason for failing to obtain a building permit? | textarea | clob |
| Only available if 'obtainPermit:no' |
reasonForNoRegistration | What is your reason for failing to register the pool with your Local Council? | textarea | clob |
| Only available if 'awareOfRegistration:no' |
purposeOfInspection | What is the purpose of this inspection? | radio | enum | assessment, confirmAbsence | Required |
poolType | Type | radio | enum | pool, spa | Required |
description | Description | radio | enum | aboveGround, belowGround | Required |
bldgPermitIssued | Building Permit Issued | radio | enum | yes, no | Required; only available if 'purposeOfInspection:assessment' |
yearConstructed | Year pool/spa constructed (if known) | text | string(255) |
| Only available if 'purposeOfInspection:assessment' |
yearDecommissioned | Approx year of removal/decommissioning (if known) | text | string(255) |
| Only available if 'purposeOfInspection:confirmAbsence' |
gatesSwingOutward | GATES SWINGS OUTWARDS - Does the gate swing away from the pool area? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
gatesSelfClosing | GATES SELF CLOSING & SELF LATCHING - Does the gate automatically close from any position from a stationary start without assistance? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
shieldingLatchDevice | SHIELDING OF LATCHING DEVICE - 450mm minimum radius around the latching device and free of sharp edges? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
gateHingeSpring | GATE HINGE/SPRING - Not cause a foothold. Hinge projections > 10mm inside & outside of gate are considered footholds if < 900mm apart and lowest hinge < 1100mm from top of barrier. Is a hinge cone cap (60°) fitted to bottom hinge to prevent hinge being a foothold? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment'; note - fitment of hinge cone cap will not prevent foothold if gap between hinge > 10mm. |
latchingDeviceTampering | LATCHING DEVICE TAMPERING - Gap not greater than 10mm between the gate and barrier or in any part of the latching device to prevent the latch from being released by inserting an implement. The latching device must only be adjustable with the use of a tool. | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
latchingDevice1500 | LATCHING DEVICE >1500mm - Is the latch located at least 1500mm above the finished ground level outside the pool and 1400mm above the highest lower climbable horizontal member? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
gateRenderedUnopenable | GATE RENDERED UN-OPENABLE - A gate considered un-openable, must be fixed permanently shut by more than one fastening device (ie. bolts, screws, nails. rivets, welds, etc) which can only be removed by a tool (key locking devices not acceptable). | radio | enum | yes, no, unsure | Required; only available if 'purposeOfInspection:assessment' |
gatesFittingsMedia | Photo | media |
|
| Only available if 'purposeOfInspection:assessment'; add any photos of Gates & Fittings |
additionalNotesGatesFittings | Additional Information for Gates & Fittings | textarea | clob |
| Only available if 'purposeOfInspection:assessment' |
barrierHeight | BARRIER HEIGHT - Minimum 1200mm measured from approach side. | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment'; [Clause 2.3] |
verticalMember | VERTICAL MEMBER - Clear space between adjacent vertical members such as palings, rods, wires, etc. 100mm. | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment'; [Clause 2.10] |
perforatedMeshMaterial | PERFORATED MESH MATERIAL - Minimum fence height 1200mm. Aperture measured diagonally - worst case dimension. (mesh ,13mm considered non climbable) | radio | enum | complies, doesNotComply, unsure | Only available if 'purposeOfInspection:assessment'; chicken wire not acceptable [Clause 2.3.2] |
outsideSurface | OUTSIDE SURFACE - No Projections or Indentations No climbable objects with a depth > 10mm exist positioned on or within a 1200mm quadrant of radius from top of barrier. | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment'; [Clause 2.3.1 & 2.6] eg plants and furniture |
perforatedMeshMaterial13mm | PERFORATED MESH MATERIAL > 13mm but <100mm Min fence height 2400mm | radio | enum | complies, doesNotComply, unsure | Only available if 'purposeOfInspection:assessment'; mesh <13mm considered climbable.[Clause 2.3.2] |
insideSurface | INSIDE SURFACES - No climbable objects located within 300mm of the inside of the barrier (Clause 2.9) eg plants and furniture | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
horizontalMembers | HORIZONTAL MEMBERS - To be >900mm apart and lowest climbable member minimum 1100mm below from top of barrier. Check stepped fencing? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment'; [Clause 2.7] |
brushwoodFencing | BRUSHWOOD TYPE FENCING - Brushwood must be tightly packed and horizontal wires interwoven to prevent finger/foot holds where gaps > 10mm exist between brushwood. (Generally not acceptable). | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment'; [Appendix E2(f)] |
groundClearance | GROUND CLEARANCE - Bottom of the pool barrier to be a maximum 100mm from finished and stabilised ground surface. Pavement completed? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment'; [Clause 2.5] |
glassBarrier | GLASS BARRIER - Complies with AS1288-2006 (copy of glazing certificate sited) A grade safety glass. | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment'; [Clause 3.3.1] |
barriersWallsFencesScreensMedia | Photo | media |
|
| Only available if 'purposeOfInspection:assessment'; add any photos of Barriers, Walls, Fences & Screens |
additionalNotesBarriers | Additional Information for Barriers, Walls, Fences & Screens | textarea | clob |
| Only available if 'purposeOfInspection:assessment' |
selfLatchingLocking | SELF LATCHING OR LOCKING - The door or gate must have a self-locking or self-latching device that prevents the door or gate, if the door or gate is in its closed position, from being opened by a person unable to reach the opening mechanism for the door or gate. | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
windowsInWall | WINDOWS IN A WALL - must be not less than 2·4 m above the ground or paving immediately external to the window; &bull must be not less than 1·5 m above the floor of the room containing the window; &bull must have a catch, bolt, lock or other stop located not less than 1⋅5 m above the floor of the room containing the window so that the openable part of the window cannot be opened more than 125 mm; &bull must have a securely fitted fly screen. | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
doorsWindowsFittingsMedia | Photo | media |
|
| Only available if 'purposeOfInspection:assessment'; add any photos of Doors, Windows & Fittings |
additionalNotesDoorsWindows | Additional Information for Doors, Windows & Fittings? | textarea | clob |
| Only available if 'purposeOfInspection:assessment' |
fenceHeight | FENCE HEIGHT - Is at least 1·5 m in height measured above the ground level on the approach side? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
nonClimbable | NON-CLIMBABLE - from neighbouring side of fence? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
propertyBoundaryMedia | Photo | media |
|
| Only available if 'purposeOfInspection:assessment'; add any photos of the Property Boundary/Dividing Fences |
additionalNotesPropertyBoundary | Additional Information for Property Boundary/Dividing Fences | textarea | clob |
|
|
poolWall | POOL WALL - minimum of 1200mm high from the ground? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
nonClimbableZonePrevention | NON-CLIMBABLE ZONE & PREVENTION - provided for fittings, plants, trees, furniture etc? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
accessLadder | ACCESS LADDER TO POOL - is provided with suitable barrier to prevent access? | radio | enum | complies, doesNotComply, unsure | Required; only available if 'purposeOfInspection:assessment' |
aboveGroundMedia | Photo | media |
|
| Only available if 'purposeOfInspection:assessment'; add any photos of the Above Ground Pool/Spa |
additionalNotesAboveGround | Additional Information for Above Ground Pool/Spa | textarea | clob |
| Only available if 'purposeOfInspection:assessment' |
siteDiagram | Site Diagram | canvas |
|
| Only available if 'purposeOfInspection:assessment'; draw a site diagram (showing dwelling, boundary fences, pool/spa, barrier line and gates) |
poolBarrierComply | Did Pool/Spa barrier comply? | radio | enum | yes, no | Required; only available if 'purposeOfInspection:assessment' |
enforcementDecisionInfo | Decision | info |
|
| Only available if 'poolBarrierComply:no'; read only |
enforcementReferMBS | Refer to MBS | checkbox | boolean |
| Only available if 'poolBarrierComply:no'; will be added to the Refer to MBS Counter for follow up |
enforcementRescheduleInspection | Schedule a follow-up inspection | checkbox | boolean |
| Only available if 'poolBarrierComply:no'; creates a new technical inspection record for this property on save of this record. The Inspection will then be set to Closed on save. |
enforcementOther | Other | checkbox | boolean |
| Only available if 'poolBarrierComply:no' |
enforcementOtherComment | Other (Please specify) | textArea | clob |
| Only available if 'enforcementOther:true' |
enforcementIssueNotice | Issue one or more notices | checkbox | boolean |
| Only available if 'poolBarrierComply:no'; creates notice records that you can mail merge from |
enforcementNoticeSubform | Notices | multiSubForm | relation | complianceNotice:default | Only available if 'enforcementIssueNotice:true'; add one or more notices to be created for this assessment |
confirmAbsenceMedia | Photo | media |
|
| Only available if 'purposeOfInspection:confirmAbsence'; photos of previous location of pool/spa (if possible) |
additionalNotesAbsence | Other Notes or Comments | textarea | clob |
| Only available if 'purposeOfInspection:confirmAbsence' |
confirmAbsenceDecisionInfo | Decision | info |
|
| Only available if 'purposeOfInspection:confirmAbsence'; read only |
satisfiedNoPoolSpaPresent | Satisfied no pool/spa present | checkbox | boolean |
| Only available if 'purposeOfInspection:confirmAbsence' |
satisfiedDecommissioned | Satisfied pool/spa effectively decommissioned | checkbox | boolean |
| Only available if 'purposeOfInspection:confirmAbsence' |
referMBS | Refer to MBS for further consideration | checkbox | boolean |
| Only available if 'purposeOfInspection:confirmAbsence' |
relatedTechComplianceCases | Related Compliance Cases | related |
|
| Read only unless 'id:true'; related cases linked to the same asset |
Non-schema fields
Field ID | Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
hasAsset | Property | asset |
|
| Supports Addresses (Vicmap), Properties (Vicmap), Properties (Imported), Points of Interest, Parcels (Vicmap) and Library Items; MDA94 projection used for geospatial assets; enter the address related to the inspection |
hasEvent |
| event |
|
|
|
hasMap | Location | geo |
|
| Uses MDA94 projection |
hasSchemaSelection | Inspection Type | schemaselection |
|
| Select between different form types here |
hasStatus |
| status |
|
|
|
hasTags |
| tags |
|
|
|
Workflow
Workflow ID | Label | Value | Next States | Initial State |
|---|---|---|---|---|
NEW | New Inspection | 20 | INSPECTIONREQUIRED, INSPECTIONDUE, COMPLIANT, NOTCOMPLIANT, CLOSED | ✓ |
INSPECTIONREQUIRED | Inspection Required | 30 | INSPECTIONREQUIRED, INSPECTIONDUE, COMPLIANT, NOTCOMPLIANT, CLOSED |
|
INSPECTIONDUE | Inspection Due | 40 | INSPECTIONDUE, INSPECTIONREQUIRED, COMPLIANT, NOTCOMPLIANT, CLOSED |
|
COMPLIANT | Compliant | 50 | COMPLIANT, INSPECTIONDUE, INSPECTIONREQUIRED, NOTCOMPLIANT, CLOSED |
|
NOTCOMPLIANT | Not Compliant | 60 | NOTCOMPLIANT, INSPECTIONDUE, INSPECTIONREQUIRED, COMPLIANT, CLOSED |
|
CLOSED | Inspection Closed | -10 | CLOSED |
|
Pool and Spa Surveys
Default schema
Field ID | Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
isPublicUser |
| hidden | string(255) |
|
|
letterInfo | Our records indicate that you have a pool or spa. Please fill out the survey below to confirm. | info |
|
| Only available if 'isPublicUser:1'; read only |
firstName | First Name | text | string(255) |
| Required |
lastName | Last Name | text | string(255) |
| Required |
phoneNumber | Mobile Phone Number | tel | string(255) |
|
|
text | string(255) |
|
| ||
locationManual | Manual Property Details (if not found in above search) | textarea | clob |
| If you can not find your address in the above search, please enter the location below. Please also enter the property number that appears on your rates notice. |
poolConfirmation | Do you currently have a swimming pool on your property? | radio | enum | yes, no | Required |
poolQuantity | How many swimming pools do you currently have on your property? | number | integer |
| Required; only available if 'poolConfirmation:yes'; defaults to 1 |
registered | Have you registered your swimming pool with Council? | radio | enum | yes, no | Required; only available if 'poolConfirmation:yes' |
previousPool | To your knowledge, has there been a swimming pool on your property in the past? | radio | enum | unsure, no, yes | Required; only available if 'poolConfirmation:no' |
yearPoolRemoved | Do you know when it was removed or decommissioned? | text | string(255) |
| Only available if 'previousPool:yes' |
assignee | Assigned | assignment |
|
| Single assignment to Arrays |
instructions |
| info |
|
| Read only |
relatedComplianceCases | Matched Compliance Cases | related |
|
| Only available if 'isPublicUser:/[^1]/', read only unless 'id:true'; matched cases linked to the same asset |
customName | Canonical name | hidden | string(255) |
|
|
Non-schema fields
Field ID | Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
hasAsset | Property Address | asset |
|
| Supports Properties (Vicmap) and Properties (Imported); MDA94 projection used for geospatial assets |
hasDueDate | Next Action Due | duedate |
|
|
|
hasEvent |
| event |
|
|
|
hasStatus |
| status |
|
|
|
hasTags |
| tags |
|
|
|
Workflow
Workflow ID | Label | Value | Next States | Initial State |
|---|---|---|---|---|
SUBMITTED | Submitted | 10 | SUBMITTED, MATCHED, UNMATCHED | ✓ |
UNMATCHED | Unmatched | 20 | UNMATCHED, CLOSED |
|
MATCHED | Matched | 30 | MATCHED |
|
CLOSED | Closed (Error) | -10 | CLOSED |
|
Compliance Notices
Default schema
Field ID | Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
noticeType | Notice Type | select | string(255) |
| Required |
infringementTypes | Infringement Types | multiselect |
|
| Only available if 'noticeType:infringementFailureToRegister' |
infringementFineAmount | Infringement Fine Amount | text | string(255) |
| Required; only available if 'noticeType:/infringementFailureToRegister |
worksRequired | Works Required | rte | clob |
| Only available if 'noticeType:bomw' |
nonCompliantItems | Non-Compliant Items | rte | clob |
| Only available if 'noticeType:infringementPoolNotComply'; list the standards that did not comply. These will appear on the Infringement Notice. |
inspectionDate | Inspection Date | dateTimePicker | timestamp |
| Only available if 'noticeType:NOI'; please enter an inspection date which will appear on the Notice of Inspection |
mergedFile | Notice Documents | media |
|
| This is a collection of documents that have been generated for this item when running the Merge Documents process. |
noticeNumber | Notice Number | text | string(255) |
|
|
dateNoticePrinted | Notice Printed Date | datePicker | timestamp |
|
|
integrationRef | Integration Reference Number | text | string(255) |
|
|
integrationDate | Integration Date | datePicker | timestamp |
|
|
relatedComplianceCases | Matched Compliance Cases | related |
|
| Read only unless 'id:true'; matched cases linked to the same asset |
Non-schema fields
Field ID | Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
hasAsset | Property Address | asset |
|
| Supports Properties (Vicmap) and Properties (Imported); MDA94 projection used for geospatial assets; enter the address related to the notice |
hasEvent |
| event |
|
|
|
hasMap | Location | geo |
|
| Uses MDA94 projection |
hasStatus |
| status |
|
|
|
hasTags |
| tags |
|
|
|
Workflow
Workflow ID | Label | Value | Next States | Initial State |
|---|---|---|---|---|
READYTOPRINT | Ready to Print | 30 | READYTOPRINT, PRINTED, CLOSED | ✓ |
PRINTED | Printed | 40 | PRINTED, CLOSED |
|
CLOSED | Notice Closed | -10 | CLOSED |
|