Australian rental complete guide guide
Complete field guideRecord what you submitted and when
Once an application is sent, memory is a weak source for what happened. A compact record can answer whether the correct version was used and which channel received it. It should track the event while keeping the underlying personal records in their existing controlled location.
- Market
- AU
- Jurisdiction
- Australia
- Updated
Short answer
After submitting, record the property, recipient or portal, date, time and the names of files sent. Keep any receipt or reference number. Record follow up separately and avoid copying sensitive document contents into the log.
Continue in RentFiles
Turn this guide into a clear application pack
Create a private, structured rental application file when you are ready.
- 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.
Guide map
In this guide
Jump to the part that matches the decision in front of you.
Key points
Complete the final submission check
A good submission record is small, factual and useful when questions arise later. Track the handoff without creating another uncontrolled store of personal information.
Useful context
Capture the submission event
Record the property address, submission channel, date and local time immediately after the handoff. Add the recipient or portal name and any confirmation reference that appears. Do not claim success if the channel only shows an upload attempt. Distinguish submitted, confirmation received and follow up sent so the timeline reflects what was actually observed.
Action plan
Store receipts without duplicating content
Save the confirmation screen, email or receipt only when it adds evidence of the handoff. Give it a clear name and keep it separate from the files that may be reused for another property. A confirmation can contain personal details, so apply the same access and retention care used for the application. Avoid unnecessary screenshots.
Working checklist
Identify the exact file set
List the final file names or one controlled package name and its version. If your workflow already records a hash, keep that existing value; do not create a new system for it. The purpose is to identify the set, not reproduce its contents. Never paste identity numbers, financial figures or full application answers into the log.
Keep in view
Log follow up as a separate event
For later contact, add a dated line describing the channel and narrow purpose. Do not overwrite the original submission entry or imply that a follow up changed the files already sent. If corrected material is requested and sent, create a new event identifying only the replacement file and the corresponding confirmation.
Practical example
Keep the record proportionate
Provide information relevant to the recipient's application process and handle identity or financial material carefully.
A renter records that a package was uploaded at 3:15 pm, names the five final files and saves the portal reference. Two days later they add a separate note for a clarification email, without copying the application answers into the log.
Keep building
Continue with a related guide
Questions
Common questions
Clear answers for the decisions people usually pause on.
Should a submission record contain copies of all application details?
No. Record the event, channel, file set and confirmation. Keep sensitive content in its controlled source files rather than duplicating it into a log.
How should a corrected attachment be recorded?
Add a new dated event naming the replacement and how it was sent. Preserve the original entry so the history does not falsely imply the first file was different.
Your next step
Put your application documents in one clear pack
Create a private, structured rental application file when you are ready.
Start your rental application