AIHW logo

METEOR logo

Our sites
AIHW GEN Aged Care Data Aboriginal and Torres Strait Islander
Health Performance Framework
Indigenous Mental Health and
Suicide Prevention Clearinghouse
Australian Mesothelioma Registry Housing data Regional Insights for Indigenous Communities
Contact FAQs

Site Navigation

  • Find metadata
    • Find metadata
    • Getting started
    • Data set specifications
    • Indicator sets
    • Data quality statements
    • Data dictionary archives
  • Metadata management
    • Metadata management
    • Data standards
    • Registration authorities
    • Registration statuses
  • How to use METEOR
    • How to use METEOR
    • First steps
    • Using My Page
    • Downloading and printing
    • FAQs
    • About METEOR
  • Learn about metadata
    • Learn about metadata
    • Metadata explained
    • How to create metadata
    • Metadata development resources
Your session is about to end!
Your session will expire at [TIME]
Select Extend at the top right corner or you will be logged out

Juvenile Justice Order file cluster

Data Set Specification Attributes

Identifying and definitional attributes

Metadata item type:Help on this termData Set Specification
METEOR identifier:Help on this term512358
Registration status:Help on this term
  • Youth Justice, Superseded 24/03/2023
DSS type:Help on this termData Element Cluster
Scope:Help on this term

The Order file cluster contains information about the supervised orders handed down by courts and parole boards to young people under youth justice supervision. All supervised orders, even if they are concurrent, are captured in the order file.

Collection and usage attributes

Guide for use:Help on this term

Data elements in this cluster assist in describing the types of supervision young people under the youth justice system experience. For example, the information provided in the order file aids in analysing how many youth justice orders were:

  • active during the year
  • had by a young person under supervision (on average)
  • for community-based supervision
  • for detention
  • sentenced
  • unsentenced.

The person identifier in the order file cluster is used to link with the client file cluster, in order to connect information on the characteristics of young people with the types of orders they experienced.

The order end reason data elements in this file provides information on why an order ended, including reasons such as completed, revoked, cancelled and stayed pending appeal. This aids in describing how a young person exited a period of supervision.

The last known postcode of the young person in this file is used to describe whether the young person lived in a major city, regional, or remote area prior to receiving the order, as well as whether the young person was from areas of lowest or highest socioeconomic status.

The order file is also used to create episodes of community-based supervision (in combination with the detention file), based on the order start and end dates (and detention start and end dates).

Source and reference attributes

Submitting organisation:Help on this termAustralian Youth Justice Administrators (AYJA)

Relational attributes

Related metadata references:Help on this term
Supersedes Juvenile Justice Order file cluster
  • Community Services (retired), Standard 14/09/2009
Has been superseded by Juvenile Justice Order file cluster
  • Youth Justice, Superseded 23/08/2022
Implementation in Data Set Specifications:Help on this term
All attributes +
Juvenile Justice NMDS 2011–12
Youth Justice, Superseded 23/03/2023
DSS specific attributes +
Implementation start date: 01/07/2011
Implementation end date: 30/06/2012

Juvenile Justice NMDS 2012–15
Youth Justice, Superseded 24/03/2023
DSS specific attributes +
Implementation start date: 01/07/2012
Implementation end date: 30/06/2015

Metadata items in this Data Set Specification Help on this term

Show more detail
Seq No.Help on this termMetadata itemHelp on this termObligationHelp on this termMax occursHelp on this term
1Person—person identifier, XXXXXX[X(14)]

DSS specific information:

The person identifier is a jurisdictionally-specific code that uniquely identifies a young person (youth justice client) within the State or Territory youth justice department responsible for the young person.

A State or Territory identifier should be the first character of the person identifier according to the following:

1 New South Wales
 
2 Victoria
 
3 Queensland
 
4 South Australia
 
5 Western Australia
 
6 Tasmania
 
7 Northern Territory
 
8 Australian Capital Territory
 
9 Other territories (e.g. Christmas Island)
 

Mandatory1
2Order—order identifier, X[X(49)]

DSS specific information:

For the purposes of the Juvenile Justice NMDS, this unique identifier is retained across collection periods. The identifier is assigned by the State or Territory youth justice department.

In the order file, the order identifier will in most cases be unique. However, where a single order specifies multiple types of supervision, for example a blended order that specifies a period in detention followed by a period of community-based supervision, the information relating to each type of supervision will comprise a separate record but the order identifier will remain the same.

In the example below, order #10001 is a blended order that comprises a period in detention from 1/1/08 to 1/6/08 followed by a period in the community from 1/6/08 to 1/12/08. Order #10002 is an unrelated remand order.

 

 

Person identifierOrder identifierOrder start dateOrder end dateOrder type-nationalOrder end reasonComment
11000101/01/0801/06/0835 (sentenced detention)completedblended order part 1
11000101/06/0801/12/0831 (sentenced community-based with or without additional mandated requirements)completedblended order part 2
11000215/01/0920/01/0921 (remand)completedunrelated order

Queensland: Don't count detention orders that are followed by a period of supervised release as blended orders.

Business rules

  • If the order identifier matches the order identifier of another record and the person identifiers are the same, the order end date of the first record should equal the order start date of the second record.
  • The order identifier (charge file) must be in the order file.
  • If the order type (order file) is an unsentenced order then there must be a record in the charge file with a matching order ID.
  • The order identifier (offence file) must be in the order file.
Mandatory99
3Order—order start date, DDMMYYYY

DSS specific information:

Guide for use

This date may not necessarily be the date that supervision began; for example, if a sentence of detention is backdated to the start of the young person’s remand period, the order start date will be before the period of sentenced detention actually began.

Orders may be concurrent and overlap; that is, the order start date may be before the order end date of the previous order.

The order start date is the date the order first comes into effect, which may not necessarily be the same as the date the court handed down the order. Orders that are handed down by a court to take effect in the future should not be backdated to the date they were handed down.

Business rules

  • The order start date must be on or before the order end date.
  • The young person must be aged at least 10 years (based on date of birth) at the order start date.
  • The young person should be aged 10–25 years at the order start date.
  • The order start date must be on or before the end of the reporting period.
  • If the order end reason for a previous order was 3 (death) there must not be any subsequent orders.
  • If the order identifier matches the order identifier of another record and the person identifiers are the same, the order end date of the first record should equal the order start date of the second record.
Mandatory99
4Order—order end date, DDMMYYYY

DSS specific information:

Guide for use

The order end date is the date the order ceases to be in effect, as specified on the order.

If a young person ceases to be under the supervision relating to the order, but the order is still in effect, the order does not end. For example, if a young person is given a sentenced detention order with an end date of 1 December but is released on supervised release or parole on 1 November, the order end date remains 1 December unless the court varies the end date of the order.

If the court varies the end date of the order, the new (varied) end date is the order end date.

If an order is revoked or cancelled, the order end date is the date that the order was revoked or cancelled. This includes orders that are revoked or cancelled due to re-offending or failure to comply with conditions and orders that are cancelled, quashed or varied on appeal.

If an order extends over two or more reporting periods and the order end date changes because the order was revoked, cancelled, quashed or varied, the order end date and the order end reason will differ between data submissions. The changed order end date should be supplied in the reporting period in which the order was revoked, cancelled, quashed or varied; however, a related record supplied in a previous data submission should not be updated. For example, a record relating to order ID 101 was supplied for the reporting period 2009–10 with an end date of 1/6/11 (that is, the order end date was after the end of the reporting period). A record relating to the same order was supplied in the following reporting period, 2010–11, but the order had been varied and now has an end date of 1/7/09. It is sufficient to report this new end date in the 2010–11 reporting period; a ‘fix’ is not required for the records relating to this order supplied in previous data submissions.

When an order end date is after the end of the reporting period (e.g. for the 2009–10 reporting period, after the 30/06/2010) or if the order end date is null in the local data system, supply the order end date or insert the dummy date (22/02/2222) if the order end date is unknown. Do not end the order at the end of the reporting period.

Business rules

  • The order end date must be on or after the start of the reporting period.
  • The order start date must be on or before the order end date.
  • If the order end date is on or before the end of the reporting period, the order end reason must be a reason other than 0 (not applicable).
  • If the order identifier matches the order identifier of another record and the person identifiers are the same, the order end date of the first record should equal the order start date of the second record.
Mandatory99
5Order—order type, national juvenile justice legal order code NNMandatory99
6Order—order end reason, juvenile justice code N[N]Mandatory99
7Address—suburb/town/locality name, text X[X(45)]

DSS specific information:

This item is collected for the young person’s last known home address before entering youth justice supervision.

Guide for Use

A Suburb/Town/Locality may be a town, city, suburb or commonly used location name such as a large agricultural property or Aboriginal community. The name should be spelt correctly and consistently and should not be a youth justice detention facility.

Enter ‘UNKNOWN’ where the locality name or geographic area is not known.

Enter ‘NO FIXED ADDRESS’ where the young person has no fixed address or is homeless.

Mandatory99
8Address—Australian postcode, Australian postcode code (Postcode datafile) {NNNN}

DSS specific information:

This item is collected for the young person’s last known home address before entering youth justice supervision.

Guide for Use

Use the Australian Post postcode file.

Leave the field blank if:

  • the last known home address is unknown
  • the last known home address is outside Australia
  • the young person had no fixed address. 
Mandatory99
9Person—Australian state/territory identifier, code N

DSS specific information:

This item is collected for the young person’s last known home address before entering youth justice supervision.

Guide for Use

Leave the field blank if:

  • the last known home address is unknown
  • the last known home address is outside Australia
  • the young person had no fixed address. 
Mandatory99
<Title>
<body>
<footer>

View

  • Show more
  • Print view

Download

  • Word
  • PDF
  • Advanced Download

Review

  • Compare items
Help
Downloading

The download may take a while, please wait.

Do not refresh the screen until the download is complete.

Terms & Conditions
Do you agree with the Terms and Conditions?

<Title>

<body>
<footer>
Loading...
© Australian Institute of Health and Welfare
Version 1.1.20230418.4