An Amendment Gazettal Health Check is a workflow that can be run to advise you if your amendment contains any structural errors that will prevent it from gazetting due to conflicts with current ordinance in the Planning Scheme or if any parts of content requires a refresh from the master copy.

This Amendment Health Check WILL NOT advise if planning content in the provision is correct. Consultation is still required with the Department or Planning Authority.

The following guide will assist users on how to run an Amendment Health Check in ATS Authoring:

1. When in the amendment document in ATS Authoring (Keystone), select the amendment name.

2. Select TASKS from under the Actions menu.

Running the amendment check workflow

3. Select APPLY WORKFLOW

Apply the amendment health check workflow

4. Type in ‘amendment’ in the Search workflow field
5. Select ‘Amendment Health Check’ when it appears in the listing

Run the Amendment Health Check Workflow

6. Select the ‘+’ symbol to add the workflow

Select the Amendment Health Check Workflow

7. Select APPLY to run the workflow on the amendment document.

Apply the Amendment Health Check Workflow

8. The user running the workflow will receive an email advising of the success or fail of the workflow with additional information regarding the results of the workflow.

In the below example, the email is alerting the user that the ‘content requires a refresh from master copy’, meaning that the master content has changed since the amendment was first created therefore the user will need to run the Refresh Workflow process (see guide: How to Refresh Amendment Workflow)

Example of email with errors after the running of the Amendment Health Check

Further examples of other emails received from running the Amendment Health Check Workflow:

  • Success - No Issues (Process worked and no issues with amendment found)
    • User initiating the workflow receives email

    example of successful email with no issues found

  • Success – 1 to 5 Issues (Process worked but issues found)
    • User initiating the workflow and Planning Support receives email

    example of successful email with 1 to 5 issues found

  • Success > 5 Issues (Process worked but issues found)
    • User initiating the workflow and Planning Support receives email

    Example of email with more than 5 issues found

  • Technical Failure (Process did not work)
    • User initiating the workflow receives email

    example of email to user where process failed

  • Technical Failure (Process did not work)
    • Planning Support receives email

    example of email tp Planning Support where process failed

Page last updated: 06/04/21