Request-to-document ledger

Local planning guide

Handle rental application information in Queensland

Do not treat a long file as a stronger file. Start with the property manager or owner's actual request, then make every attachment earn its place.

Market
AU
Jurisdiction
Queensland
Updated
01

Short answer

Create one row for every requested item: the property, the exact request, the document you have, the detail it supports, its date and whether the recipient has confirmed it. If an item is not requested or its purpose is unclear, pause and ask before sending it. Keep your own copy of the request and of the version you provide.

Continue in RentFiles

Turn this guide into a clear application pack

Prepare a structured application PDF from details you enter yourself. The recipient decides the application outcome.

  • 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.

Useful context

Start with the Queensland request, not a generic bundle

A listing, application portal and follow-up email can ask different questions. Copy each request into one ledger before collecting files. Include the property address or listing reference, the date received and the channel so a later request does not become mixed with material for another property.

The useful distinction is between a document that answers a stated question and a document that merely feels reassuring to add. A statement may show more information than the question needs. A screenshot may omit the date or name required to make it useful. The ledger makes those limits visible before a file leaves your control.

  • Request: the recipient's words, copied without expanding them.
  • Purpose: the single application question the document can answer.
  • Status: ready, needs clarification, replaced or not available.

Working checklist

Ask a short clarification question before adding extras

If the request does not say whether a supporting record is wanted, ask the recipient which item or format it accepts. Keep the question narrow: name the property, the field you are trying to complete and the document you can provide. Do not turn a request for clarification into a detailed personal explanation.

Where there is a mismatch in dates, spelling or document availability, record it in the ledger and ask whether a short factual note is useful. Do not use a second document from another transaction simply because it looks similar. That can create a different inconsistency for the recipient to resolve.

  • What exact field remains unanswered?
  • Which document or alternative does the recipient accept?
  • Does the response apply to this property only?

Action plan

Map each attachment to one application question

For each row, note the source file name, the period it covers and what it cannot show. A recent income record may not explain an earlier address. A reference contact may not confirm an identity detail. This is not a reason to manufacture a fuller explanation. It is a prompt to identify the exact unanswered question.

When a portal accepts uploads without labels, keep the ledger beside the upload screen. Rename only the applicant copy if that helps tracking, and retain the original source separately. The goal is a clear record of what was supplied, not a claim that the document has been independently checked.

Keep in view

Keep the legal and practical boundary clear

In Queensland, give only information relevant to the application process and follow the RTA's current guidance on requested documents.

This page is a personal file-management method, not advice about what a recipient must accept or how any law applies to a particular application. Requirements can change and a property manager or owner may ask a property-specific question. Use the current RTA material and the recipient's actual instructions when the request is unclear.

RentFiles can help you enter your confirmed details and prepare a structured application PDF. It does not decide which records are sufficient, send an application, check the recipient's process or influence the application outcome.

Practical example

Example: a file with an unrequested bank record

A fictional applicant has a portal request for identity, income evidence and a prior address. Their bank record includes unrelated transactions and does not clearly answer the address field. Instead of uploading it as a catch-all attachment, the applicant records the gap and asks whether a dated address record is required and which format is acceptable.

The send record then contains only the requested files and the recipient's reply. The applicant keeps the unsubmitted record outside the package. This preserves an honest boundary: the file shows what was asked for and what was supplied, without implying that more material was necessary or accepted.

?

Questions

Common questions

Clear answers for the decisions people usually pause on.

What should I do when a new document request arrives?

Add the property-specific request to the ledger, identify the question it asks and confirm the accepted format before attaching a new document.

Keep building

Browse all resources

Your next step

Put your application documents in one clear pack

Prepare a structured application PDF from details you enter yourself. The recipient decides the application outcome.

Fill your application before payment