Identity file selection

Document workspace

Rental application identity document checklist for Australia

An identity checklist is useful only when it starts with the recipient's actual request and ends with a deliberate choice about each sensitive file.

Market: AU
Jurisdiction: Australia
Updated: 2026-07-20

Short answer

Copy the recipient's identity request into a table, identify the attribute each line is meant to establish, and list the applicant controlled files that could answer it. Select only a current and readable option in the requested format. Record any name, expiry, cropping or redaction question before sending, and never treat this guide as a universal list of documents required across Australia.

Continue in RentFiles

Turn this guide into a clear application pack

Prepare a structured application PDF from details you enter yourself. RentFiles does not assess evidence, submit the application or decide the outcome.

Fill your application before payment

Prepare a structured rental application PDF with RentFiles.
Fill your application before you choose whether to pay for a PDF export.
RentFiles helps organise the file; the agent or landlord decides the application outcome.

Working checklist

Inspect each possible identity file before selecting it

Work from the applicant's own current files. For every option, record the document label, issuing source as displayed, visible name, expiry or issue date where present, page count and file condition. Check whether both sides or more than one page contain relevant information. Keep this inventory private; it is a working aid, not an attachment that needs to be shared automatically.

Open the actual scan or image at normal size and at a readable zoom. A thumbnail can hide glare, clipped edges, an obsolete version or a page saved in the wrong orientation. If the current name differs across records, do not create an explanation from guesswork. Mark the mismatch and ask what supporting context, if any, the recipient expects.

Current version
Readable details
Complete page set
Consistent file label
Visible mismatch flag

Working checklist

Run a final identity file handoff check

Read the manifest from top to bottom as if you had never seen the folder. Each request should point to one readable attachment or one visible question. Open every final attachment, confirm that its filename matches the manifest, check that the intended pages are present and remove drafts or duplicates. The application should not rely on a note that contradicts the source file.

For example, if a request names an identity attribute and the applicant has two possible files, the checklist can record why the current readable option was selected and why the older scan stayed out of the sharing folder. It should not predict recipient acceptance. After the files and questions are settled, the applicant can enter checked details into the structured application PDF workflow.

All final files open
Manifest names match
No silent alteration
No acceptance claim
Checked details only

Action plan

Build a bounded identity attachment manifest

Create one manifest row for every selected attachment. Include the request it answers, the filename, the version checked, the page or side included and the date of the check. Use neutral filenames that help the applicant and recipient locate a file without placing full identifier numbers or other sensitive values in the filename. Store the unchanged source separately from the sharing copy.

If one file appears to answer two requested attributes, point both request rows to that same attachment instead of duplicating it. If the recipient has asked for a specific complete copy, do not alter it silently. Ask whether a narrower copy is acceptable and retain the answer with the manifest. A question is a valid outcome when format or treatment has not been confirmed.

One row per attachment
Purpose based filename
Checked version date
No duplicate copy
Open treatment question

Useful context

Translate the request into identity attributes

Begin with the words used on the application form or in the recipient's message. Put each request on its own row and describe the attribute it appears to seek, such as a current name, a photograph, a date of birth, an address link or a signature. If the purpose is unclear, leave the purpose cell open and ask. A document name alone does not explain why the recipient wants it.

Do not turn examples into a compulsory national checklist. A recipient may specify particular formats, combinations or alternatives, and the applicant may not hold every example mentioned. The useful decision is narrower: which existing file answers the stated line with the least unrelated information, and what still needs confirmation before that file is copied into the application folder?

Exact request wording
Requested attribute
Possible applicant file
Unanswered format question
Decision owner

Keep in view

Pause before sharing sensitive identity material

Identity files can expose government related identifiers, addresses, dates and details about other people. Compare every visible field with the purpose recorded in the request table. Look for unrelated pages, reverse sides, numbers or third party details before the file leaves the applicant's controlled folder. Do not assume that more personal information makes an application stronger.

The OAIC tenancy guidance supplies the narrow privacy boundary for this page. It does not decide which file a particular agent may request, and this guide does not give legal advice. When a field seems unnecessary, ask the recipient whether an altered copy is acceptable before changing a requested source document. Preserve the original and record the answer rather than relying on memory.

Provide information relevant to the recipient's application process and handle identity or financial material carefully.

Purpose check
Unrelated field check
Third party detail check
Recipient treatment question
Original preserved

Questions

Common questions

Clear answers for the decisions people usually pause on.

Is there one identity document checklist for every Australian rental application?

No. Use the form or recipient's current instructions as the controlling request. This page helps map that request to applicant controlled files without presenting a universal document rule.

Should I attach two identity files when one appears to answer the request?

Do not add a second sensitive file by default. Record what the first file answers and ask the recipient whether another file or attribute is still needed.

What should I do if the only available identity file appears expired?

Mark the date and status plainly, do not describe it as current, and ask which alternative or explanation the recipient accepts. Do not edit the date or hide the issue.

Can I blank out an identifier before sharing an identity document?

Check the stated purpose and ask whether the recipient accepts that treatment before altering a requested copy. Keep an unchanged original in the applicant's secure records.

Does RentFiles verify identity documents for an application?

No. RentFiles helps organise details the applicant enters into a structured application PDF. It does not verify identity files, submit them or decide the application outcome.

Keep building

Browse all resources

Your next step

Put your application documents in one clear pack