A land referencing output shall be fit for its intended purpose, internally consistent and traceable to controlled source information.

The project instruction or applicable profile shall define the required content, format, approval and delivery arrangements for each output.

For each output type, the organisation shall define:

purpose and intended users;

authoritative status;

included object and relationship classes;

selection and ordering rules;

required fields;

treatment of unknown, disputed, reputed, excluded and not-applicable information;

identifier rules;

geographic, temporal and jurisdictional scope;

spatial portrayal requirements, where applicable;

format and accessibility requirements;

confidentiality and distribution classification;

validation and approval criteria;

update trigger; and

retention requirement.

Each controlled output shall identify:

title and purpose;

output UID;

version, status and issue date;

geographic and temporal scope;

project or requirement baseline used;

producing organisation;

author, checker and approver as required;

applicable jurisdictional or procedural profile;

confidentiality or access classification;

limitations and permitted use;

related outputs; and

means of reporting a correction or query.

Identifiers used across schedules, plans, notices, reports, digital datasets and other related outputs shall refer consistently to the same controlled object or derived parcel.

An output-specific display number may differ from the source-object UID, but the relationship shall be retained and unambiguous.

An identifier shall not be silently reassigned following a change. Where display numbering changes, a cross-reference between superseded and current numbers shall be retained where necessary for users.

A land schedule shall state:

the object represented by each row;

the geographic ordering or grouping rule;

the meaning of every column and code;

the relationship to an accompanying plan;

treatment of repeated parties or rights;

treatment of joint holdings and representatives;

status of unknown or disputed information;

version and date; and

any jurisdictional or procedural basis for inclusion.

Where one row combines more than one source object, the combination rule and source identifiers shall be traceable.

A land plan shall meet 10.14 and shall enable a user to relate each mapped object to the corresponding schedule or dataset.

Plan sheets shall provide unambiguous continuity, sheet references and match information. Insets, enlargements and schematic representations shall state their relationship to the main plan and shall not conceal a change of scale or status.

An apparent line position created by symbol width, offset or print scale shall not alter the underlying controlled geometry.

Where land referencing information is used to prepare a notice, letter, questionnaire, contact list or other communication output, the output shall be generated from or reconciled to:

current party identity;

current validated contact point;

relevant right and capacity;

representative and service arrangements;

applicable requirement and procedural basis;

necessary accessibility or communication adjustment; and

approved issue status.

The issue record shall identify the source-data version, recipient, channel, date, document identifier and delivery or return status.

A report presenting conclusions from land referencing information shall distinguish:

verified facts;

source assertions;

professional interpretations;

assumptions;

unresolved findings;

exclusions; and

recommendations.

The report shall identify the evidence and data baseline used and shall not extend a conclusion beyond the scope or competence of the organisation.

A digital output shall include:

schema and data dictionary;

object and version identifiers;

relationship definitions;

code lists;

data types and null-value rules;

spatial specification, where applicable;

metadata and quality status;

validation results;

known limitations;

security and use restrictions; and

delivery manifest.

A machine-readable output should be accompanied by a human-readable description sufficient for an informed user to interpret it.

Outputs intended for human use shall be clear, legible and accessible to the intended audience.

The organisation shall consider:

plain and consistent language;

readable typography and contrast;

colour-independent distinctions;

logical reading order;

alternative text or description for material graphics;

navigable headings and tables;

usable digital formats; and

required language or reasonable adjustments.

Where a prescribed format limits accessibility, an accessible companion version should be provided if permitted.

Before release, each controlled output shall be checked for:

correct requirement and data baseline;

completeness against the output specification;

internal consistency;

consistency with related plans, schedules and datasets;

identifier integrity;

current party and contact information;

correct geographic and temporal scope;

correct handling of unknown, disputed and excluded matters;

metadata, licence and confidentiality markings;

legibility and accessibility; and

approval.

Validation evidence shall be retained.

The organisation shall control:

who can approve an output;

where the authoritative version is held;

who receives it;

permitted use;

issue and acknowledgement;

supersession and withdrawal; and

correction of an issued error.

Where a material error or change affects an issued output, the organisation shall assess the consequence, notify defined recipients and issue a corrected or superseding version where required.

JURISDICTIONAL NOTE (informative)
Books of reference, land plans, schedules, notices, deposited plans, acquisition schedules and equivalent outputs have procedure-specific content and form. This clause specifies common controls only. The applicable procedural standard is to define who must be included, how land is described, required chapter or administrative-area structures, prescribed scales and statutory certification.